Question

I've managed to set up my Meta Conversions API using a partner integration (Shopify), and the Events Manager says events are being deduplicated. However, I'm still seeing a significant discrepancy between the sales reported in Shopify and the conversions reported in my Meta Ads account. What could be causing this, and what should be my next troubleshooting step?

Answer 1

The core idea behind the Conversions API is to send conversion data directly from your server to Meta's server, creating a more reliable connection that isn't affected by browser blockers or ad blockers.

Here is a step-by-step breakdown of how to approach this, from the initial setup to the technical implementation that can help you.

Step 1: The Initial Setup in Meta Events Manager

This is the non-technical part you can do yourself.

1. Navigate to Events Manager: Log in to your Meta Business Manager, then go to the "Events Manager" section.

2. Select Your Pixel: Find and select the pixel you want to connect the Conversions API to.

3. Choose the Setup Method: In the "Settings" tab of your Pixel, scroll down to the "Conversions API" section. You will see several options to set it up. The three most common are:

   • Partner Integrations: This is the easiest method for most users who run their websites on a common platform.

   • Manual Setup: This is for developers and requires custom server-side coding.

   • Gateways or Tag Management: This is a good middle ground, often using a server-side container in a tool like Google Tag Manager.

4. Generate an Access Token: Regardless of the method you choose, you will need a unique Access Token. This is like a secret key that authenticates the data you send to Meta. Make sure to save it somewhere safe; you will need to provide it to your developer or use it in the next steps.

Step 2: The Technical Implementation (Choosing Your Path)

This is where you need to decide if you can handle it yourself or if you need to hire someone.

Path A: Use a Partner Integration (Recommended for Most Users)

If your website is built on a popular platform like Shopify, WordPress, WooCommerce, or Magento, this is your best option. It requires little to no coding.

• How it works: The platform has a built-in integration that sends data directly to Meta's API for you.

• What you do:

  1. In the Events Manager, select "Choose a Partner."

  2. Select your platform from the list (e.g., Shopify, WordPress).

  3. Follow the on-screen instructions. This usually involves installing a plugin or app and simply entering your Access Token. The partner platform handles all the code for you.

Path B: Manual Integration (Requires a Developer)

This is the most powerful and precise method, but it requires a developer to write custom code.

• How it works: Your website's server sends a copy of every conversion event (e.g., "Purchase," "Lead," "Add to Cart") directly to Meta's API endpoint.

• What to tell your developer:

  1. Provide the Access Token: Give them the Access Token you generated in Step 1.

  2. Explain the Data: Tell them that they need to send conversion data in a JSON format to Meta's API. This data should include:

     • The event name (e.g., 'Purchase').

     • The event time (the exact timestamp).

     • User data (hashed for privacy): Email, phone number, name, IP address, and user agent. Hashing this data is a crucial privacy step.

     • Event data (e.g., value, currency, content IDs).

     • The FBP (Facebook Browser Pixel) and FBC (Facebook Click) parameters, which help Meta deduplicate events and attribute them correctly.

  3. Explain Deduplication: Emphasize that for CAPI to work alongside your Meta Pixel, they must implement event deduplication. This means sending a unique event_id with both the Pixel event and the CAPI event so Meta knows not to count the same conversion twice.

Path C: Use Google Tag Manager (GTM) Server-Side

This is a great middle ground for marketers who use GTM but want to avoid a full manual server integration.

• How it works: You send data from your website to a GTM server-side container, which then forwards the data to the Conversions API.

• What to tell your developer or GTM expert:

  1. Tell them you need to set up a server-side container in GTM.

  2. Explain that they need to configure GTM to receive data from your website (e.g., using a Google Analytics 4 tag) and then send that data to Meta's CAPI using a pre-built CAPI tag.

  3. Again, emphasize the importance of deduplication and passing the event_id, fbp, and fbc parameters correctly.

Step 3: Test and Verify

This is the final, crucial step to ensure everything is working correctly.

1. Use the Test Events Tool: In the Events Manager, go to the "Test Events" tab.

2. Send Test Events: Enter your website's URL and click "Open Website." Perform a test conversion (e.g., make a test purchase).

3. Check for Data: Go back to the Events Manager. You should see a log of events coming from both the Browser (your Pixel) and the Server (your Conversions API), with a "Deduplicated" status if set up correctly.

By following this process, you can get the Conversions API fully operational, whether you handle it yourself via a partner integration or work with a developer on a manual or server-side GTM setup.