Skip to content
Lunor Medya

05 Sep 2026 · 4 min read · Lunor Medya · Updated 21 Nov 2026

Meta Pixel and Conversions API Setup Checklist: From Event Plan to Verification

A step-by-step checklist for setting up the pixel and Conversions API: event plan, parameters, event_id deduplication, domain verification and testing.

Ticked checklist for setting up the Meta Pixel and the Conversions API

Tracking setup is often declared done once "the code is on the site", and problems surface weeks later when reports stop adding up. This checklist splits the Meta Pixel and Conversions API setup into planning, implementation and verification, with what to check at each step. If you want the concepts first, read What the Meta Pixel and the Conversions API are.

Stage 1: Preparation

  • Asset ownership: the pixel (also shown as a dataset in Meta's interface), ad account and domain should sit in your own business portfolio. Agencies and developers get access, not ownership.
  • One pixel: if the site carries several legacy pixels, decide which one to keep. Different snippets sending the same event to different pixels split your reporting.
  • Access: identify who can reach the site admin, tag manager and, if needed, the server.
  • Consent setup: if the site uses a cookie consent tool, plan up front how pixel and server events behave depending on consent status.

Stage 2: Event plan

Before touching code, write down which events fire, when, and with what data. A sample ecommerce plan:

EventFires whenParameters
ViewContentA product page loadscontent_ids, content_type, value, currency
AddToCartAdd to cart succeedscontent_ids, value, currency
InitiateCheckoutThe checkout page loadsvalue, currency, num_items
PurchaseThe order is confirmed (once)value, currency, content_ids, order_id

A service business may need less: contact page views, form submissions (Lead) and bookings (Schedule). The key rule is to fire on successful completion: count a form that was actually submitted, not a button click.

Stage 3: Pixel installation

  1. Load the base code once per page on every page, using one method only: direct code, a plugin or a tag manager.
  2. Add the standard events from your plan; do not invent custom names where standard ones exist.
  3. Make sure parameters are dynamic: value should not be a fixed "0" or identical for every product, and currency should use the correct code (TRY).
  4. Check that refreshing the thank-you page does not fire Purchase again.

Stage 4: Conversions API setup

  1. Choose a method: direct API integration, a platform plugin, server-side tag management or a partner integration. For Laravel or custom-built sites, a direct integration usually gives the most control.
  2. Access token: never hard-code the API token; keep it in server environment variables and share it only with those who need it.
  3. Customer information parameters: normalise email, phone and name as Meta specifies and hash them with SHA-256. Include IP address, user agent and Meta's browser cookie values (fbp, fbc) where available; they improve match quality.
  4. event_source_url and action_source: state the page and channel (website) where the event happened.

Stage 5: Deduplication

  • When an event is sent from both pixel and server, both must use the same event name and the same event_id.
  • event_id must be unique per event; the order number is a good base for purchases.
  • If the ID is generated in the browser, pass it to the server, or vice versa. Two sides generating their own random IDs breaks deduplication.

Stage 6: Domain and account settings

  • Verify your domain in the business portfolio (DNS record, HTML file or meta tag).
  • Requirements around web event prioritisation and iOS-related measurement limits have changed over time; check in Events Manager whether any configuration is still requested today.
  • Confirm that the event you will optimise for is active and arriving regularly in the dataset.

Stage 7: Verification

  1. Test events: use the testing tool in Events Manager, browse the site and trigger each event by hand; confirm both browser and server events arrive.
  2. Browser extension: Meta's pixel helper extension shows which events fire on a page and flags errors.
  3. Deduplication check: look at event details for the indicator that browser and server events are being deduplicated.
  4. Parameter check: confirm value, currency and product IDs against a few real orders.
  5. Reconciliation: after a week, compare Meta's purchase count with your order system. Expect some gap, but large unexplained differences point to a problem.

After setup

Match quality, missing or duplicate events and consent issues that appear after go-live are covered in troubleshooting the Meta pixel and Conversions API. If you need development help for the server-side integration, see custom software development; for the campaign side, see Meta Ads management.