The Meta Pixel on your OpenCart store reports the purchases of the buyers whose browser let it run and who came back to the checkout success page. Meta’s Conversions API (CAPI) reports the rest: it sends each order from a server, where no ad blocker, Safari setting or closed tab can stop it. Meta itself recommends running both.
This guide covers what the Conversions API changes on OpenCart, the three ways to add it, and how to set it up in about ten minutes without Google Tag Manager.
What the pixel alone misses on OpenCart
- Buyers who pay off-site and never return. The pixel fires on
checkout/success. A buyer who pays on the payment provider’s page and closes the tab never loads it. - Blocked browsers. Ad blockers and privacy browsers block the pixel script before it loads.
- Expired click cookies. The
_fbccookie holds the click on your ad. Safari caps the life of such cookies, so a buyer who orders a few days after the click often reaches Meta without it, and Meta cannot tie the sale to the ad. - Thin customer data. A browser event carries little Meta can match a person on, which keeps Event Match Quality low.
Each missing purchase is a sale Meta’s delivery never learns from. With a big enough gap, Meta optimises toward the buyers it happens to see, not the ones who buy.
Three ways to add the Conversions API to OpenCart
| Approach | What you set up | Where the purchase comes from |
|---|---|---|
| Pixel extension with a CAPI option | An extension, often one per ad platform, and your access token | Usually the success page, sent on by the server |
| Server-side Google Tag Manager | A web container, a server container, hosting, every tag yourself | The browser, through your container |
| Server-side extension (AxiTrace) | One extension and your public key | Your OpenCart server, when the order reaches a sale status |
The difference that matters is the source of the purchase. If the server event is still triggered by the success page, a buyer who never sees that page is still lost; the Conversions API only adds a second road for the same browser signal. The order should leave your store when OpenCart records it as a sale.
How the AxiTrace extension sends purchases to Meta
The free AxiTrace extension for OpenCart (OpenCart 3.0.3.x to 3.0.5.x and 4.0.2.x to 4.1.x) records each order on your server and AxiTrace forwards it to the Meta Conversions API:
- Sent at your sale statuses. An order is sent once, the first time it reaches a status your store counts as processing or complete, read live from your OpenCart settings. Pending counts by default; untick it to wait for bank transfers to be paid. Cash on delivery orders are sent when they are placed.
- Deduplicated against your pixel. The event id is made from the OpenCart order id. When the browser also reports the purchase, both copies carry the same id and Meta counts the order once. If another extension also sends purchases to the same pixel, switch its purchase event off.
- Customer data Meta can match. Email and phone go out hashed, with the
fbpbrowser id and thefbcclick id. When the_fbccookie has expired by the day of the purchase, AxiTrace rebuildsfbcfrom the ad click it stored with the visitor, so a late buyer still reaches Meta with the click that brought them in. - Consent respected. Three consent modes: load at once, wait for consent in the browser, or wait for consent for the server-side order too. Your cookie banner grants consent with a cookie or one line of JavaScript, and on OpenCart 4 the default is the cookie of OpenCart’s own cookie notice.
- Refunds stay out of Meta. Refunds, cancellations and returns correct your revenue and profit in AxiTrace and are never sent to an ad platform.
The same order also goes to Google Ads, GA4, TikTok and five more platforms you connect, from the same extension. More on how the Meta side works: Facebook Conversions API.
Set it up
- Create a free AxiTrace account at axitrace.com/register and copy your workspace public key.
- Install the extension. Download the package for your version (both are named
axitrace.ocmod.zip; do not unpack it), upload it under Extensions, Installer, then install AxiTrace under Extensions, Extensions, Analytics. - Paste your public key in the extension settings, check the purchase statuses and save.
- Connect Meta in AxiTrace. Paste your dataset (pixel) ID and a Conversions API access token from Events Manager, then press Test connection. No container to build, no tag to write.
- Place a test order and look for it in Events Manager. The full steps are in the OpenCart setup guide.
How to check it works
- In Events Manager, open your pixel and look at the Purchase event: it should list both Browser and Server as sources, deduplicated.
- Compare purchases in Meta with the orders OpenCart recorded for the same days. The gap should close to the orders Meta cannot match to anyone.
- Use the free Meta Pixel and CAPI checker to see what your store sends, and our guide to testing a deduplication pair.
Common questions
Do I keep my existing Meta Pixel? Yes. The pixel and the server event share one event id, so Meta keeps one purchase per order. AxiTrace never pushes to your dataLayer, so your Google Tag Manager tags do not fire twice.
Does it slow down checkout? No. Events are sent with a short timeout after the page is served. If AxiTrace cannot be reached, the event waits in a queue on your store and is retried with the same event id. No system cron is needed.
What does it cost? The extension is free and open source (GPL). AxiTrace has a Free plan with 10,000 visits a month and all nine ad platforms, no credit card; see pricing.