Marketing · Merchants running Facebook or Instagram ads

Connect Meta Pixel and Conversions API

Track the MeroByapaar shopping funnel in Meta Events Manager with browser and server Purchase event deduplication.

By MeroByapaar7 minute guide

Before you begin

  • A published MeroByapaar store
  • Access to a Meta Business portfolio and Events Manager
  • A Meta Pixel ID and Conversions API access token
  • A privacy policy that explains the advertising measurement you enable

Follow these steps

  1. 1

    Create or select your Meta dataset

    In Meta Events Manager, create or select the Pixel/dataset used for this store. Keep different businesses separated so reporting and audiences remain accurate.

  2. 2

    Copy the Pixel ID

    Open the dataset settings and copy its numeric Pixel ID. Never substitute an ad account ID or business portfolio ID.

  3. 3

    Generate a Conversions API token

    Use Meta Events Manager to generate an access token for the same dataset. Treat this token as a secret.

  4. 4

    Save the integration

    In MeroByapaar, open Settings, choose Marketing, enter the Pixel ID and access token, then enable Meta commerce tracking. The token is encrypted and is not displayed again.

  5. 5

    Test the funnel

    Use Meta Test Events while opening a product, adding it to cart, starting checkout and placing a controlled order. MeroByapaar emits PageView, ViewContent, AddToCart, InitiateCheckout and Purchase.

  6. 6

    Check Purchase deduplication

    Purchase is sent through the browser Pixel and server Conversions API with the same order event ID. Confirm Meta reports one deduplicated purchase rather than two purchases.

  7. 7

    Remove the test code

    After test events are visible and correct, remove the optional test event code and save again before launching campaigns.

Verify before going live

Completion checklist

  • □All five funnel events appear in Meta Test Events
  • □Purchase value and NPR currency are correct
  • □Browser and server Purchase events are deduplicated
  • □No access token appears in the storefront or browser response

If something is not working

Browser events do not appear

Confirm tracking is enabled, the Pixel ID is correct, the storefront is published and browser privacy tools are not blocking Meta scripts.

Server Purchase does not appear

Replace the Conversions API token with a current token for the same dataset, add a Meta test event code and place one controlled test order.

Two purchases appear for one order

Confirm both browser and server events use the same dataset. MeroByapaar uses the order ID as the shared event ID for deduplication.