Connect Shopify to Meta: pixel, Conversions API and a proper test

Use Shopify's current integration as the starting point

Start with the official Facebook and Instagram by Meta sales channel in Shopify, not a copied pixel snippet pasted into the theme. Shopify documents that the channel connects Meta business assets and manages its Meta pixel setup. As documented in September 2026, channel screens can change; follow the current Shopify prompts.

In Shopify admin, install or open Facebook and Instagram by Meta under Sales channels, sign in to the intended Meta account, and connect the correct business portfolio, Page, Instagram account, catalogue and pixel when prompted. These assets should belong to the same business operation. If the setup asks you to create or select a pixel, select the one used by the intended ad account; do not create a second dataset simply because an existing one is not immediately visible.

Choose customer data sharing with privacy in mind

Shopify's Meta pixel documentation explains that the Standard sharing level sends customer behaviour, while Enhanced and Maximum include additional customer information. Shopify's data-sharing guide also describes the pixel and Facebook Conversions API as tools that can send online-store events. With Enhanced or Maximum, the Shopify integration can send events through both browser and server pathways; this can help measurement when a browser event is unavailable, but it does not guarantee every order is attributed or remove consent obligations.

Select the level that matches your privacy notices, consent implementation, legal advice and customers' expectations. Update the privacy policy to explain the data sharing you actually use. Do not assume choosing the highest level is automatically appropriate, or that a platform connection overrides the customer's choices. Confirm how your cookie-consent solution interacts with Shopify's customer privacy settings and the Meta channel.

• Check the Shopify customer privacy and cookie-consent configuration for the countries where you sell.
• Choose and document the data-sharing level; ask your privacy adviser if the correct setting is unclear.
• Review the privacy policy and any consent banner so the description matches the real configuration.

Prevent duplicate or misleading event data

If a Meta pixel was previously hard-coded in the Shopify theme or installed by another app, remove or disable that old implementation after confirming the channel integration is active. Shopify explicitly warns that earlier theme pixel code should be removed after setting up the pixel through Facebook and Instagram by Meta. Keeping multiple independent implementations may cause duplicate browser events and confusing reports.

Do not manually add Conversions API credentials or a second server-side integration on top of Shopify's managed connection unless you have a specific architecture and can deduplicate events correctly. If another tool sends the same purchase event, work with its documentation or support to ensure browser and server events carry compatible event identifiers. Never send data you are not permitted to share.

Test the customer journey, not just the connection badge

Use Shopify's channel status and Meta Events Manager's diagnostics or test-event view to inspect activity. Test product view, add to cart, checkout and a completed test order where your payment setup permits. Check that product identifiers and currency match the catalogue, purchase value reflects the expected order amount, and the event does not appear twice. A green connection state confirms only part of the journey.

Write down what you tested, the date and any known limitation. A real customer order should still be reconciled against Shopify's order records and your own analytics; ad-platform reporting uses its own attribution and may not match store totals. Recheck after changing the theme, checkout, consent tool, channel configuration or another tracking app.

Illustrative example: test before your first campaign

Illustrative example, not a guarantee of attribution: a founder connects the official Shopify channel to the intended Meta business and pixel, selects Enhanced data sharing after reviewing the policy with their adviser, and removes an old theme snippet. They use a test order to confirm a purchase event with the expected currency and value, then check for a single properly deduplicated purchase signal. They launch only once the store's consent behaviour and event trail make sense.

Purchase and duplicate-event review

Illustrative worked example, not a measured customer result. Replace assumptions with checked facts.

Common questions

What is the difference between the Meta pixel and Conversions API?

The pixel sends browser-side events. Conversions API sends events from a server-side integration. Neither removes consent obligations or guarantees complete attribution.

Why does event deduplication matter?

Sending the same purchase through both connections can double-count it unless corresponding events are deduplicated. Check event names and matching event IDs in the current integration and test the setup.