Skip to main content

Verify Conversion Events using the Meta Conversion API Log

The Meta Conversion API Log in Phoenix helps you confirm that your conversion events are being sent correctly to Meta. You can use this log to check whether an event fired, which Order ID it belongs to, and which Pixel ID was used. This verification is helpful when you troubleshoot attribution, reporting delays, or missing events in Ads Manager.

What This Log Shows​

The Meta Conversion API Log records every conversion event Phoenix sends to Meta. This includes actions such as purchases, subscription renewals, and upsells. Reviewing this log helps you confirm that your events are tracked accurately and aligned with your Meta setup.

How the Conversion API Log Works​

The log creates an entry each time Phoenix sends an event through the Conversion API. Every entry includes identifiers that help you confirm whether the correct event fired at the expected time. This information lets you validate your configuration without relying only on Ads Manager.

What You Can Verify in the Log​

You can use the Meta Conversion API Log to review several details about each event.

Event Trigger

Shows which event type was fired, such as Purchase, Initial Subscription Charge, or Recurring Charge. Use this to confirm that the correct event is being sent based on customer activity.

Order ID

Links the event to a specific transaction in Phoenix. Use this to verify whether Meta received the correct event for the order you're checking.

Pixel ID

Shows the exact Pixel ID Phoenix used when sending the event. Use this to confirm that the event belongs to the correct ad account.

C_Date

Displays when the event was sent to Meta. Use this to troubleshoot delays or missing conversions.

How to Review Events in the Log​

You can review your Conversion API entries directly from your Phoenix Dashboard.

  1. Log in to your Phoenix Dashboard.

  2. From the left panel, go to Reporting.

  3. Select Meta Conversion API Log.

  4. Click the Filter icon to narrow your results.

  5. Use any of the available filters:

    • Date Range
    • Start Date
    • End Date
    • IP Address
    • Browser ID (FBP)
    • Click ID (FBC)
    • Pixel ID
    • Event Type

  6. Click Apply Filter to update the results.

  7. If you want to review the event details, click View to see the Payload and Meta’s Response.

This helps you confirm that Phoenix successfully delivered the event to Meta and lets you verify specific triggers.

Using the Log for Troubleshooting​

You can use this log to identify and resolve common tracking issues.

  • Missing conversions in Meta Ads Manager

  • Events firing under the wrong Pixel

  • Duplicate events or inconsistent reporting

  • Attribution differences between Phoenix and Meta

  • Incorrect event mapping or setup

If the event appears correctly in the Phoenix log but not in Meta Ads Manager, the issue may be related to Meta’s processing, filters, or attribution windows.

Best Practices​

Following these practices helps you keep your Meta Conversion API setup accurate and reliable.

  • Use the Order ID search to confirm that each purchase sent an event.

  • Check Pixel ID entries regularly, especially after changes in your store configuration.

  • Confirm that purchases, renewals, upsells, and refunds fire the expected events.

  • Review the timestamp to identify delays or repeated attempts.

  • Test the Pixel after major checkout edits or gateway updates.

To continue verifying and improving your tracking setup, review these guides: