IdoSell’s Meta integration or Basketly: what to pick
IdoSell has a Facebook module in its admin: you paste the Pixel id and switch the Conversions API on with a sign-in wizard for your business account. You do not have to give it up for Basketly. We add a check that purchases from orders reached Meta, and sending to other platforms.
The demo has sample data; the login comes to your e-mail.
| Basketly | IdoSell | |
|---|---|---|
| Where it lives | A separate app that reads orders through the shop API | In the shop admin, in the Facebook module |
| What you set up | An IdoSell API user and a Meta sign-in | The Pixel id; the Conversions API via a business-account sign-in and the FBE2 wizard |
| Events | Purchases from orders | Pixel: cart, product view, wishlist, purchase, page view; the page does not list API events |
| Other platforms | GA4, TikTok, Pinterest, ChatGPT Ads, Klaviyo, Google Ads, Microsoft Ads | The page we read only covers Facebook |
| Where you see if a purchase arrived | Purchase balance day by day with reasons, a self-check, a test event | IdoSell’s page does not describe one; events must be active on the Facebook side |
| Price | Free up to 100 orders; Start USD 39 a month up to 1,000 orders | The help page gives no separate price for the module |
What the built-in module gives, and what a separate tool adds
IdoSell’s module sits in the shop, so it also covers browser events such as cart and product view, which we do not send. A separate tool makes sense when you want to check every day that purchases from orders arrived, send them to GA4 or TikTok as well, or find the cause when the numbers drift apart.
What you get with Basketly
- Purchase balance: shop orders next to the purchases each platform accepted, day by day, with error reasons.
- A one-click test event and a self-check of your datasets.
- A durable queue with retries and a fixed event id.
- The same purchases to several platforms, without more plugins.
- In the same app: product feeds with fixes and a sales report.
Adding Basketly next to the built-in module
- Connect IdoSell to Basketly through the shop API and point it at your Meta dataset.
- Send a test event and check it in Events Manager.
- Turn off sending the purchase in one of the two places: the Conversions API in IdoSell or ours. Otherwise the same purchase reaches Meta twice.
- Keep IdoSell’s Pixel for the browser events.
- After a few days, check in the Purchase balance that order and accepted-purchase counts match.
When Basketly is the better pick
- You want to see whether purchases from orders really arrived, and why some did not.
- You also send purchases to GA4, TikTok, Pinterest, Google Ads or Microsoft Ads.
- You want a product feed, product diagnosis and a sales report in one place.
When IdoSell’s built-in module is enough
- You send to Meta only, and purchases in Events Manager match your orders.
- You want no extra tool and do not need a daily check.
- You need the full set of Pixel events from the shop itself.
What Basketly does not do
- It does not put a pixel in the shop or send browser events.
- It does not replace Meta Events Manager: it uses your dataset.
- Meta accepting a purchase does not prove a campaign optimises on it or that an ad gets the credit.
Sources
For purchases it can, but it does not have to. IdoSell’s Pixel stays for browser events. You can also keep IdoSell’s Conversions API and use us only for the checks.
You can, but the same purchase reaches Meta twice unless both use the same event id. The simplest setup sends the purchase from one place.
The IdoSell help page we read gives no separate price. Check your IdoSell plan’s price list.
Free up to 100 orders a month, Start USD 39 a month up to 1,000 orders.
Nobody can honestly promise that. The difference is how much you see and how fast you catch a fault. How many purchases Meta credits to ads depends on Meta and its attribution windows.
See also
- Self-checkOne check of your whole setup: the shop, purchases sent to Meta, logins, background jobs and automations, with a link to the fix for every problem.Read
- Meta Conversions APIPaid shop orders sent to Meta from the server, through a queue that does not drop purchases, with a result for every delivery.Read
- Basketly vs Shoper’s Meta integrationShoper’s built-in Facebook integration (FBE2) next to Basketly: what Shoper’s page describes, what it does not, when the built-in is enough and when to add Basketly.Read
- Purchase balance: how to check that shop orders really reach Meta and other platformsHow to read the day-by-day purchase balance: shop orders, purchases Basketly accepted and sends to Meta and other platforms. What each gap means and what to check.Read
- Pixel and Conversions API Deduplication: event_id, event_name and the 48-Hour WindowHow Meta merges the same event from the Pixel and the Conversions API: event_id, event_name, the 48-hour window, the fbp method, common mistakes and how to check.Read
Get started in under 5 minutes
Connect your shop and Meta and see how many purchases really arrive.
- Free up to 100 orders a month
- No developer needed
- Purchase balance and self-check