How to install Meta Pixel and Conversions API on your store

Pixel and Conversions API: why you need both

The Pixel runs in the browser: blockers, declined consent or a page closed too soon can lose an event. The Conversions API sends the same event from the server. So Meta doesn’t count it twice, the deduplication documentation requires the Pixel’s eventID to match the API’s event_id and the event name to be identical; events are deduplicated if received within 48 hours. For more, see our Meta Pixel vs Conversions API resource.

Steps 1 and 2: create the Pixel and get credentials

You create the Pixel in your business portfolio’s Events Manager (see our guide on how to create a Meta Business Manager). Note two things:

• the dataset ID (often called the Pixel ID);
• an access token for the Conversions API, generated in the dataset settings. Treat it like a password: never publish it or send it in a message.

Step 3: install Meta Pixel and Conversions API in ReadyStore

In the dashboard, open Configuration > Pixels and click Ajouter (Add). The dashboard is in French; labels are translated below:

Step 4: link the Pixel to your products

In each product form, pick the Pixel in the Pixel field. A product is linked to one Pixel; a store can use several. That’s handy to keep test products apart from validated ones, or several brands in the same store.

Events sent by ReadyStore

Steps 5 and 6: test and check deduplication

In Events Manager, open your dataset and check that each event arrives from both the browser and the server, and is deduplicated. The Test Events tool shows live activity; according to Meta’s documentation, events sent with a test code are not dropped: they are used for targeting and measurement.

Step 7: monitor event quality

Meta defines Event Match Quality as a score out of 10 indicating how effective the customer information sent from your server may be at matching events to a Meta account. ReadyStore sends hashed form information plus the click and browser identifiers kept with the order; a well-filled form (correct phone number) helps matching.

Common mistakes

• Pasting the Pixel code into header snippets (“Codes header”) on top of the Pixels setup: events are then sent twice, with no shared ID.
• Wrong credentials: a dataset ID from another account, or a revoked token.
• Mixing Pixels from several stores on the same product.
• Judging too fast: give events time to show up and look at deduplication over several days.

Key takeaways

Installing the Meta Pixel and Conversions API with ReadyStore comes down to a few fields: dataset ID, access token, objective and abandoned-order behavior, then one Pixel per product. Then check reception, deduplication and quality in Events Manager, without polluting your data with test orders. Next step: how to structure a test campaign. Create your ReadyStore store to connect your Pixel.