Meta Conversions API for IdoSell, without a developer

What happens to a purchase in the browser

The Pixel is a script in the buyer’s browser. It sends a purchase only when the buyer returns to the thank-you page, accepts cookies and runs no ad blocker. After a bank payment some buyers close the tab, and reloading the thank-you page can send the same purchase twice. A purchase taken from the shop’s order depends on none of that.

What Basketly does on IdoSell

You give the shop address and an Admin API key. The app does the rest, and you see every purchase and where it went.

• Saving the key checks it with an order search (and a product search; a refused product search only warns), then queues the read of orders, 24 months of history and products.
• IdoSell gives Basketly no webhook to register, so the 15-minute read is the only way in. Orders changed since the last read come back with lines, buyer, total and shipping.
• A bought, not cancelled order becomes a purchase: value, currency, products from the lines (by the chosen field), e-mail, phone and customer id. E-mail and phone are hashed before sending.
• Every purchase is saved first and then sent with retries. When Meta has an outage, the purchase waits instead of getting lost.
• IdoSell products land on the Products screen with a diagnosis for Google Merchant Center and the Meta catalogue, and from there in a fixed feed.
• IdoSell’s rate limit is respected: after a refusal the read returns to the queue after the time in the answer, or after a minute.

Connect IdoSell in 4 steps

It takes a few minutes. You need no developer and no server access.

1. 1

   Create an Admin API key in IdoSell

   In the IdoSell admin open Administracja → API → Klucze dostępowe do API Admin and create a key. Copy it right away, because it is not shown again in Basketly.

2. 2

   Connect the shop in the app

   In Basketly open Integrations, choose the IdoSell tile and enter a name, the shop address and the key. Tick the cash-on-delivery statuses and the product id field, and confirm the legal basis for passing the data.

3. 3

   Connect Meta

   Sign in with your Meta account, choose the dataset (Pixel) and keep the purchase flow from the shop to Meta. The getting-started checklist in the app shows what is still missing.

4. 4

   Check the first purchase

   Click “Fetch now”, send a Test event with the code from Events Manager and, after the first orders, open the purchase balance.

Cash on delivery and statuses

IdoSell has 17 standard order statuses and Basketly knows their Polish names. An order with a confirmed payment is bought at once. With cash on delivery the payment is confirmed only after pickup, so when connecting you tick the statuses that count as bought (for example “Zrealizowane”). An order cancelled by the customer, false, lost, missing or merged never becomes a purchase. Keep Meta’s limit in mind: a purchase older than 7 days is not accepted.

Which product id reaches the catalogue

Catalogue ads match a purchase to a product by its id. By default that is the IdoSell product id. If your Meta catalogue uses another field, pick the product size, the code or the external code. The id in the purchase must match the catalogue, or Meta cannot tie the purchase to the product.

How to check that it works

• Test event: one click sends the newest shop purchase with the test code from Events Manager, and you see it under Test Events.
• Purchase balance: shop orders next to purchases Meta accepted, day by day, with the most common error reasons.
• Self-check: compares the dataset’s statistics in Meta with what was actually sent, and says what to fix.
• Orders: each order shows whether its purchase was accepted, failed or is waiting.