Meta CAPI Test Mode

After connecting your Facebook Tracking Tag and enabling the Conversion API in AnyTrack, you need a way to confirm that conversion data is actually reaching Meta and that the event payload contains the right parameters.

Meta provides a Test Events tool inside Event Manager that shows server-side events in near real-time. AnyTrack supports this by letting you paste the test event code directly into your Tracking Tag settings, so every CAPI call AnyTrack makes gets flagged as a test event in Meta.

How It Works

Meta Event Manager includes a Test Events tab that listens for incoming events tagged with a specific test code. When you paste that code into AnyTrack, every server-side event AnyTrack sends to the Conversion API includes the test_event_code parameter. Meta then routes those events into the Test Events view instead of processing them silently, giving you a near real-time feed of what AnyTrack is sending.

This lets you validate your setup without waiting for data to appear in Event Manager (which can take up to 20 minutes for event parameters) or Ads Manager (which can take up to 3 days for attributed conversions).

Step-by-Step Setup

1. Get the Test Event Code from Meta

1. Open Meta Event Manager
2. Select the pixel (data source) connected to your AnyTrack Tracking Tag
3. Click the Test Events tab
4. Copy the test event code displayed at the top of the page (e.g., TEST12345)

📘

Note

Meta generates a new test event code each time you open the Test Events tab. The code expires after a period of inactivity.

2. Paste the Code into AnyTrack

1. Go to your AnyTrack Dashboard
2. Navigate to Tracking Pixels and open your Facebook Tracking Tag
3. Scroll to the Facebook Conversion API section
4. Paste the test event code into the Test Event Code field
5. Click Server events test mode to expand the test event viewer

3. Trigger a Test Conversion

Generate a real event on your website or landing page — submit a form, complete a checkout, or click an affiliate link. The event should appear in both:

• AnyTrack: Under the Server events test mode section in your Tracking Tag settings
• Meta Event Manager: Under the Test Events tab, marked as a Server event

What to Check in Meta Test Events

Once your test event appears in Event Manager, click into it to review the details:

Event Basics

Confirm the event name matches what you expect (e.g., Purchase, Lead, AddToCart). If you use custom Event Mapping, verify that your custom events appear under the correct Facebook event name.

User Matching Parameters

Meta shows which customer information parameters were included in the event payload. These directly affect your Event Match Quality score. Look for:

• Client IP Address and Client User Agent . collected automatically by the AnyTrack Tracking Tag
• Facebook Click ID (fbclid) . captured from the ad click URL when the UTM template is configured
• Facebook Browser ID (fbp) . first-party cookie set by the Facebook pixel
• Email or Phone . available when passed through form submissions, CRM integrations, or webhooks

📘

Note

All personally identifiable information (PII) is hashed before it reaches Meta. Hashed values in the Test Events view are expected and do not affect match quality. See the EMQ Parameters guide for details on each parameter.

Revenue and Content Data

For events that carry monetary values (Purchase, InitiateCheckout), confirm:

• Value and Currency match the actual transaction
• Content IDs and Content Type are present for product-level events

Incorrect revenue values will skew ROAS calculations in Ads Manager.

When to Use Test Mode

Test Mode is most useful in these situations:

• Initial setup . After connecting your Facebook Tracking Tag for the first time, confirm events flow correctly before running ads.
• Custom event mapping changes . After modifying your event mapping, verify that custom events appear under the correct Facebook event names.
• New property onboarding . When adding a new website or funnel, confirm the AnyTrack Tracking Tag fires events and that they reach Meta.
• Debugging match quality . When your EMQ scores are lower than expected, inspect the payload to see which parameters are missing.
• After troubleshooting . After resolving issues from the Troubleshooting Guide, confirm the fix by checking that events appear correctly in Test Events.

Removing the Test Event Code

Once you have verified your setup, remove the test event code from your Tracking Tag settings. Test events still count toward your event totals in Event Manager, and leaving the code active will mix test traffic with production data.

1. Go to Tracking Pixels and open your Facebook Tracking Tag
2. Clear the Test Event Code field
3. Save changes

⚠️

Warning

Do not leave the test event code active in production. Events sent with a test code appear in the Test Events tab but may not be processed the same way for campaign optimization.

Related Resources

• Install AnyTrack Tag
• Ad Platforms Attribution