Meta Conversions API for Shoper, without a developer

Why the Pixel on Shoper loses or doubles purchases

The Pixel is a script in the buyer’s browser. It sends a purchase only when the buyer comes back to the thank-you page, accepts cookies and runs no ad blocker. After paying in the bank, some buyers close the tab and the purchase is gone. Reloading the thank-you page, on the other hand, can send the same purchase twice. A server-side GTM container solves this, but it needs a server, its running costs and someone to maintain it.

What Basketly does on Shoper

You give the login of a shop API user. The app does the rest, and you see every purchase and where it went.

• It creates its webhooks in Shoper (new order, paid, status change, product changes) and checks their signature.
• Shoper sends each webhook only once, so orders are also read every 15 minutes. Nothing hangs on a single notification.
• A paid order becomes a purchase: value, currency, products from the order lines, e-mail and phone (hashed before sending), the buyer’s IP.
• Every purchase is saved first and then sent with retries. When Meta has an outage, the purchase waits instead of getting lost.
• Shoper products land on the Products screen with a diagnosis for Google Merchant Center and the Meta catalogue, and become a fixed feed.
• Disconnecting removes the webhook from the shop and forgets the login.

Connect Shoper in 4 steps

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

1. 1

   Create an API user in Shoper

   In the Shoper admin, add a user with access to the shop API and note its login and password.

2. 2

   Connect the shop in the app

   In Basketly open Integrations → Shoper, enter the shop address, login and password, choose 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

   Send a Test event with the code from Events Manager and, after the first orders, open the purchase balance.

Cash on delivery

Shoper marks an order paid only after payment. With cash on delivery that can take days or never happen. When connecting, you choose the statuses that count as paid (for example “Shipped”), so a cash-on-delivery purchase reaches Meta when the order gets that status. 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 Shoper’s product_id. If your Meta catalogue uses another field, pick stock_id, the product code or the EAN. 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 has a purchase-sending column with a dot: accepted, failed or waiting.