Setting Up the Meta Conversions API in PXME

Overview

The Meta Conversions API (CAPI) allows PXME to send events—like form submissions, lead ads, bookings, and pipeline stage changes—directly from PXME’s servers to Meta. Unlike the Meta Pixel, which relies on browser tracking, CAPI provides more accurate and reliable data, even when cookies or browser restrictions limit Pixel performance.

By combining CAPI with the Pixel, you’ll have a stronger tracking setup that improves ad optimization, reporting accuracy, and retargeting capabilities.

Step 1: Create Your Meta Pixel

1. In your Meta Business Portfolio, go to Events Manager.

2. Select or create a Pixel under Web Data Sources.

3. Copy your Pixel ID (Dataset ID).

4. In Pixel Settings, generate and copy an Access Token.

Step 2: Set Up Workflows in PXME

Workflow 1: Capture New Leads (Lead Event)

1. Go to Automations → Workflows → Create Workflow.

2. Add a trigger, such as:

   • Facebook Lead Form Submission (for Lead Ads), or another relevant trigger.

3. Add these actions:

   • Facebook Conversion API → Lead Event → paste Pixel ID and Access Token.

   • Create/Update Opportunity → select your pipeline and stage.

Workflow 2: Track Pipeline Stage Changes

1. Create another workflow.

2. Set trigger: Pipeline Stage Changed.

3. Add action:

   • Facebook Conversion API → Lead Event → paste Pixel ID and Access Token.

   • Map to the appropriate stage.

Step 3: Funnel Events (Optional)

To track funnel-based activity like form submissions, bookings, or orders:

1. Create a workflow with triggers such as:

   • Form Submitted

   • Survey Submitted

   • Appointment Booked

   • Order Form Submitted

2. Add a Facebook Conversion API action.

3. Set the event type to Funnel Event.

4. Paste your Pixel ID and Access Token.

Step 4: Test Your Setup

1. In Meta Events Manager, open the Test Events tab.

2. Run a test lead, form, or booking through your PXME funnel.

3. Confirm events appear in both:

   • Browser Events (Pixel)

   • Server Events (Conversions API)

Best Practices

• Use Pixel + CAPI Together: Running both gives you the most complete tracking coverage.

• Store Credentials in PXME Custom Values: Save your Pixel ID and Access Token for easy reuse across workflows.

• Track Only What You Need: Avoid creating duplicate events by configuring only relevant workflows.

• Troubleshoot Quickly: If events don’t appear, double-check:

  • Pixel ID and Access Token are correct

  • Workflow triggers are active

  • You have admin access in your Meta Business Portfolio