Connect Meta Pixel and Conversions API to the same data source and check events, consent, and deduplication.
This guide is for store administrators on Go, Plus, and Pro with access to the correct Meta Business Portfolio and data source. The Abicart steps shown apply to an active theme with Add-ons → Facebook. Check the editor variant and sub-store; TPL or another configuration should not be assumed to have the same fields. A Meta account and a valid connection are required separately from the subscription.
Meta Conversions API (CAPI)
With the Meta Conversions API (CAPI), your online store can send information about visitor activities and conversions directly from Abicart's servers to Meta.
CAPI works together with Meta Pixel, which records events via the visitor's browser. By using both methods, you can get more reliable conversion tracking and give Meta a better basis for measuring the results of your advertising.
Read more in Meta's official documentation about the Conversions API .
What is the difference between CAPI and Meta Pixel?
Both solutions record activities in your online store, but the information is sent to Meta in different ways.
Meta Pixel | Meta Conversions API |
Sends events from the visitor's browser. | Sends events from Abicart's servers to Meta. |
Can be affected by browser settings, ad blockers, and tracking protection. | Sends via the server, but this theme integration still needs events that are recorded via the browser. |
Important: CAPI does not replace Meta Pixel. The two solutions complement each other. In this theme integration, CAPI also relies on store events recorded via the browser. If the theme's event code does not run, the server event may also be missed. Therefore, server-side transfer is not a guarantee of complete tracking and must not be used to bypass consent.
When the same event is sent via both Meta Pixel and CAPI, Meta can identify that it is the same activity using event names and unique identifiers. This is called deduplication and helps prevent the same conversion from being counted twice.
Configure the Conversions API
To activate the Conversions API in Abicart, you need:
A Meta business account (Business Portfolio) with access to the online store's data source.
Your Meta Pixel ID (also called Dataset ID in the Meta interface).
A Conversions API access token.
Step 1: Find your Meta Pixel ID
Open Meta Events Manager .
Select the business account associated with your online store, if prompted.
Go to Datasets and select the data source associated with your online store.
Under Overview you will find your Pixel ID on the right side of the page, as shown in the image below.
Copy your Pixel ID.
Don't have a Meta Pixel yet? Click Connect data in Events Manager, select Web and follow Meta's instructions to create a new data source.
Need help? Read Meta's guide to setting up Meta Pixel .
Step 2: Create a Conversions API access token
Go to Meta Events Manager and select the same data source as in the previous step.
Open Settings.
Scroll to Conversions API.
Find the manual setup option and click Generate access token.
Copy the generated access token.
Note: The names of menus and settings may differ slightly depending on how Meta updates Events Manager.
Important: Keep your access token secure. Do not share it publicly or place it in code that is visible to visitors on your website.
Step 3: Activate the Conversions API in Abicart
Once you have your Pixel ID and access token, do the following. The screenshot shows Swedish labels.
Go to Appearance → Themes → Edit theme.
Select Add-ons → Facebook.
Enter your Meta Pixel ID.
Enter your Conversions API access token.
Click Save.
Tip: Use the same data source for Meta Pixel and the Conversions API. It's not enough for the Pixel ID to be the same: The Browser and Server events for the same activity also need matching event names and event_id. Check the reception and deduplication diagnostics in Events Manager; two displayed rows are not in themselves proof of two counted conversions.
Which events are tracked?
The integration can send the following events from your online store to Meta:
Event | When is it recorded? |
PageView | During the integration's page view events. Distinguish the Pixel's first initiating PageView from subsequent navigation events; not every possible page opening generates a new server event. |
ViewContent | When the integration receives a product-view event with a product number (SKU). |
AddToCart | When the integration receives an add-to-cart event with a product number (SKU). |
InitiateCheckout | When the checkout event has an active order in the store's state. A reload without an order does not trigger a new such event. |
Purchase | From the integration's checkout callback upon purchase. An arbitrary opening or reloading of a confirmation page is not in itself proof of a new Purchase event. |
You can see which events Meta has received in Events Manager.
Verify that the Conversions API is working
After saving the settings, you can test if Meta is receiving events from your online store.
Open Meta Events Manager .
Select your data source and open Test Events.
Follow Meta's instructions to start the test.
Open your online store in another tab.
Visit a product page and add a product to the cart.
Go back to Events Manager and check which events have been recorded.
In Meta, you can see how the events were sent:
Browser: Events sent via Meta Pixel.
Server: Events sent via the Conversions API.
If the same activity has been recorded via both the browser and the server, Meta can deduplicate the events, provided they have matching identifiers.
Note: Server events may require additional test settings to appear under Test Events. You can also check recorded events under Overview in Events Manager.
Troubleshooting
No events appear in Events Manager
Check that you have entered the correct Pixel ID and access token in Abicart. Also, make sure you have selected the correct data source in Meta Events Manager.
Browser events appear, but server events do not
Verify that your Conversions API access token is valid and that the settings have been saved correctly in Abicart. An empty view in Test Events is not sole proof of a broken token; also check the correct data source, Overview, and Diagnostics. Check for consent and that the theme's event code is running for the current activity before changing the token.
Events seem to be recorded twice
Meta uses matching event names and identifiers to avoid double recording. Check the Diagnostics section in Events Manager to see if Meta has detected any problems with deduplication.
You can find more technical information in Meta's documentation on the Conversions API .
Privacy and consent
The Conversions API sends information via the server, but this does not mean that privacy and data protection requirements no longer apply.
Tracking must still comply with visitors' consent choices and the privacy settings that apply to your online store.
Need help?
Are you having trouble configuring the Meta Conversions API in Abicart? Contact our support, and we will help you check the settings.
Understand the consent queue and evaluate the test correctly
Denied marketing consent stops new server dispatches in the integration. Events can remain in the page's memory and be sent if consent is given later. Revoked consent stops new server dispatches; it does not mean that already transferred data is automatically deleted at Meta. Explain this in your store's privacy information and follow applicable regulations.
Check that the Browser and Server versions of the same activity have matching event names and event_id. More rows in Events Manager do not automatically mean double-counted conversions; read the deduplication diagnostics.
Test Events is not a complete receipt for all server events. The server's test mode may require a test_event_code for which the theme's default settings do not offer a field. Do not put the code or an access token in public script code to bypass this. Also use Overview/Diagnostics and the correct data source. Do not make a real purchase just to get a test event.
Quick start
Select the correct Meta data source and retrieve the Pixel ID and token securely.
Enter them in the correct active theme and save.
Check for granted consent, real event conditions, and Browser/Server source.
Review deduplication and diagnostics without publishing secrets.
Subscription and access
Meta CAPI is available in the current Go, Plus, and Pro plans. Meta permissions, a data source, consent settings, and a supported active theme configuration are also required. Neither server-side transfer nor the subscription removes data protection requirements.
