Configure the Meta pixel in Shopify and verify events

The Facebook and Instagram by Meta channel connects Shopify with the pixel and, depending on the selected data level, Conversions API. Verifying integration means checking events and catalogue, not merely seeing a saved pixel ID. Configuration must respect applicable consent and privacy decisions.

An AI-powered advertising tool still needs correct data. If an event arrives twice or the product identifier does not match the catalogue, optimisation technology will not necessarily fix it.

Pixel, Conversions API and catalogue have different roles

Data sharing documentation distinguishes Standard, Enhanced and Maximum levels. Tools and details may vary by installation. Review what your selection enables rather than assuming all levels send the same data.

Prepare installation without duplicating the old setup

1. Identify the business, ad account, pixel and catalogue to use.
2. Check who has permission to connect and maintain them.
3. Review the Facebook and Instagram channel and its data sharing level.
4. Inventory old installations: theme code, custom pixels, tag managers and other apps.
5. Plan removal of duplicates once the new integration is verified.

Do not delete every tracking script without reviewing its purpose. An older installation may send events to another tool. Document replacements and retain a reference for investigating later differences.

Run a test that provides evidence

Check one session without consent and another with accepted preferences where applicable. Visit product, cart and checkout, using Shopify and Meta testing tools. For purchase events, use a controlled transaction compatible with payment configuration.

Review event identifier, time, currency, value and products. If the same order arrives through browser and server, check deduplication in the destination platform. Two routes sending information should not mean counting two purchases.

• Does the event product match a catalogue item?
• Does the amount use the correct currency?
• Does the purchase appear once in the expected count?
• Does reloading the final page produce an incorrect repeat event?
• Are consent states respected throughout the journey?

The catalogue needs its own review

Check rejected products, variants, prices and availability. A visible Shopify page does not guarantee eligibility for every Meta surface. Review policies and channel messages if an offer does not synchronise.

Keep website structured data, product page, feed and ad consistent. If an ERP changes prices or inventory, include that change in testing. The issue may originate in source data rather than the pixel.

What to do when sales do not match

Meta attribution and Shopify order records do not necessarily represent the same thing. Review attribution windows, time zones, refunds and consent. Sample orders and reconstruct their journey before changing campaigns based on an aggregate difference.

During platform changes, retain a previous reference and confirm events afterwards. No universal “AI pixel” update automatically promises more conversions, a better catalogue or privacy compliance. A comprehensible, verified integration remains the foundation.

Continue working on your store

Understand optimised access and consent · Review measurement when migrating from PrestaShop · Check Google events too.

If this issue already affects your store, a Shopify audit can review configuration and prioritise corrections by impact instead of accumulating changes without diagnosis. Tell us what your store needs.

Sources and review

• Data sharing with Meta.
• Facebook and Instagram by Meta.
• Testing app pixels.

Editorial review: the Migraciones.io team · 30 October 2026. Features, plans and availability are checked against the linked sources.