Basketly or Stape: what to pick for a shop
Both get purchases to Meta server-side, from different ends. Stape hosts your Google Tag Manager container or a gateway for the Pixel. Basketly takes the purchase straight from the shop order, so you configure no tags and maintain no server.
The demo has sample data; the login comes to your e-mail.
| Basketly | Stape | |
|---|---|---|
| What it is | An app for the shop: purchases from orders to ad platforms, product feeds, a sales report | Hosting for a server-side Google Tag Manager container (sGTM) and a separate Meta CAPI Gateway |
| Where the purchase comes from | The shop order: the shop API and webhooks | sGTM: events your site or system sends to the container; gateway: your Pixel’s events |
| What you set up | A shop API user and a Meta sign-in, no code | sGTM: the container, clients and tags in GTM; the gateway, per Stape, without GTM or code |
| Who maintains it | Everything runs in the app, nothing sits on the shop side | Stape hosts the server; you or your agency maintain the container setup |
| Where it sends | Purchases: Meta, GA4, TikTok, Pinterest, ChatGPT Ads, Klaviyo, Google Ads, Microsoft Ads | sGTM: wherever you set up tags; gateway: Meta |
| Full browser funnel | No: it sends purchases | sGTM: yes, if you set it up |
| What you pay for | Orders per month | sGTM: requests; gateway: Pixels |
| Price from | Free up to 100 orders; Start USD 39 a month up to 1,000 orders | sGTM: Free up to 10K requests, Pro USD 20 a month up to 500K requests; gateway: USD 10 a month per Pixel |
Two different answers to the same problem
The browser Pixel loses purchases to ad blockers, missing consent and buyers who never come back after paying. Server-side GTM moves the sending to a server, but events still have to reach it and tags have to be set up. A container gives a lot of control; it just needs a server, its costs and someone to maintain it.
What you get with Basketly
- The purchase from the shop order, not the browser. A buyer who closed the tab after paying still counts.
- A fixed event id and a durable queue with retries: a purchase is not lost in an outage and not counted twice on our side.
- Purchase balance: shop orders next to the purchases each platform accepted, day by day, with error reasons.
- A self-check and a one-click test event, no digging through Events Manager by hand.
- In the same app: product feeds with fixes, a product diagnosis and a sales report with MER.
When Basketly is the better pick
- You want your shop’s purchases to reach Meta without a developer and without maintaining a server.
- You want to see every day how many shop orders reached each platform, and why some did not.
- You also need a fixed feed and a sales report, not one more tool for each.
When Stape is the better pick
- You run or want a server-side GTM container and send the whole funnel through it: product views, cart, forms.
- You send events to tools we do not support and have GTM tags for each of them.
- Your shop is not on Shoper, IdoSell, BaseLinker, WooCommerce or Shopify, and someone can set up the container.
What Basketly does not do
- It does not send browser events such as product views or add to cart; the Pixel on the shop stays.
- It is not a GTM container: you cannot add your own tags to it.
- Meta accepting a purchase does not prove a campaign optimises on it or that an ad gets the credit.
Sources
- Stape: Pricing (sGTM hosting) (checked )
- Stape: Meta Conversions API Gateway (checked )
For shop purchases, yes: you need no container for purchases to reach Meta and other platforms server-side. If you also send the whole browser funnel or events to other tools through the container, you will still need Stape.
You can, but then the same purchase reaches Meta twice. Meta counts it once only with the same event id. The simplest setup turns the purchase off in the container and keeps the rest of the funnel there.
According to stape.io/price on 29 Oct 2026: server-side GTM hosting has a Free plan up to 10K requests a month, Pro at USD 20 a month up to 500K requests and Business at USD 100 up to 5M requests, less when billed annually. The Meta CAPI Gateway costs USD 10 a month per Pixel. Check the current price on Stape’s site.
Free up to 100 orders a month, Start USD 39 a month up to 1,000 orders. The limit counts orders, not sends to platforms or server requests.
Nobody can honestly promise that. Both send server-side; the difference is where the purchase comes from. Ours comes from the shop order, so it does not depend on the browser. How many of those purchases Meta credits to ads depends on Meta and its attribution windows.
See also
- ShoperShoper purchases to Meta from the shop’s orders, without a developer or a GTM server.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
- ConversionsShop purchases sent server-side to Meta and seven more platforms, and a day-by-day balance: how many orders, how many purchases accepted and where something got lost.Read
- Conversions API (CAPI)Sending events, such as purchases, to Meta from the shop’s server instead of the buyer’s browser.Read
- What Is the Meta Conversions API? How It Differs from the Pixel and What It Won't DoWhat the Meta Conversions API is, how it differs from the Pixel, which data it accepts, how deduplication works and what CAPI does not guarantee.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