Conversions API for a Shopify store: pick a setup path and record it

Meta's comparison page describes five ways to set up the Conversions API: Meta-enabled, direct integration using code, partner integrations, commerce platform partner integrations, and CRM partner integrations. This guide covers the first four and leaves out CRM partner integrations, which Meta describes as connecting lead data. Meta's comparison chart itself has only three columns: Meta-enabled, Direct Integration and Meta Partners.

Meta names Shopify among commerce platforms and says setup takes just a few clicks at no additional cost. For a store that only needs website events, that is the option to evaluate first.

Direct integration is for more control or for sources beyond the web. Meta says it requires a developer, cost depends on development and maintenance, and a new integration takes 2 to 4 weeks. For mobile app or physical store (offline) events, Meta says direct integration is the only available option at this time.

The Meta-enabled setup is web-only, one click, free, and needs a Meta Pixel. Meta's page does not say how it interacts with a Shopify store's own channel, so treat it as a comparison point, not a Shopify recommendation.

Shopify's help page offers three data-sharing levels. Standard uses the Meta pixel only, and a browser-based ad blocker can stop it. Enhanced uses the Conversions API as well as the pixel; Shopify says the purchase event is sent server to server, which browser ad blockers cannot block. Maximum also uses the Conversions API and the pixel, and is updated with Meta's latest advertising technology. Shopify adds that the levels offer different privacy settings depending on when you installed Facebook and Instagram by Meta.

Shopify says Enhanced and Maximum share customer name, location, email address and phone number, plus browsing behavior, to match users on Meta's network. Shopify tells merchants to keep their privacy policy up to date and says reviewing Meta's privacy best practices is their obligation. Record the level you pick and who approved it, because it is a data decision as well as a tracking one.

In Shopify admin, go to Sales channels > Facebook & Instagram > Settings > Data sharing settings. Activate customer data sharing, select the level, and click Connect on a pixel if none is connected.

This is a suggested manual procedure from the editors, not an Adrails feature or documented product behavior. It keeps the evidence from each system separate.

• Step 1: List every current event source. Check the Facebook & Instagram settings in Shopify for the connected pixel and level, and note other pixels or server senders you know about.
• Step 2: Note the event types you need. Shopify lists the pixel events PageView, ViewContent, Search, AddToCart, InitiateCheckout, AddPaymentInfo and Purchase. For app or offline events, Meta points to direct integration.
• Step 3: Choose a path from Meta's comparison and write down why, citing cost, time, resources and action source.
• Step 4: Record a baseline for the 7 days before the change: Shopify order count and Purchase events in Events Manager.
• Step 5: Make the change in Shopify and note the date, time and person.
• Step 6: After a full 7 days, record the same two numbers and any diagnostics Events Manager shows.
• Step 7: Check deduplication yourself. Meta says automatic deduplication applies to pixel events shared through the Meta-enabled setup; the sources do not state it for your Shopify configuration, so verify and log the result.

Harbor Lane Candles is invented, for illustration only. It has one Shopify store, one Meta pixel and no app or offline sales. It was on Standard. The owner picks the Shopify commerce platform partner path and Enhanced, because the store needs web purchase events and has no developer.

In the 7 days before, Shopify showed 140 orders and Events Manager showed 98 Purchase events: 98 / 140 = 70 percent. In the 7 days after, Shopify showed 150 orders and Events Manager 132 Purchase events: 132 / 150 = 88 percent. These numbers are made up and prove nothing about any real store.

Even with real numbers, a rise would not prove the Conversions API caused it. Order volume, ad blockers, traffic mix and reporting delays can all move the ratio. Meta notes that Ads Manager, Ads Reporting and Events Manager can differ, so compare the same screen across both periods.

Adrails documents a separate forwarding path. Once your server sends events signed with the server key, Adrails can pass them to Meta's Conversions API. Events from the script on your pages stay in Adrails and are not forwarded. Adrails sends event_id so Meta can match it with the same event from your pixel and count it once.

Adrails also holds back signed events above its per-event value limit or its daily limit per platform; they are still recorded in Adrails. Only owners and administrators can change these settings. The tracking settings show Sent, Waiting and Refused counts for the last 30 days.

The Adrails page does not describe a Shopify integration, so do not assume Shopify orders reach Meta through Adrails. If you add Adrails forwarding alongside Shopify's data sharing, run and log your own deduplication check.

The sources do not show how many more conversions you will see, how Shopify's levels map to Meta's option names beyond Enhanced and Maximum using the Conversions API, or how match quality will change. They do not cover your legal obligations, so check your privacy policy and local rules. Treat the worksheet as a record of a decision and of your own measurements.