Send Meta Conversions API events with Pixel Activator

Related: Meta pixel ID and token, TikTok Events API, and event deduplication.

What are Meta Conversions API events?

Meta calls the former Pixel a dataset in Events Manager. A server event can complement a browser Pixel event, but it does not repair an incorrect campaign setup or replace consent requirements.

Testing an event without a website takes three inputs: the dataset ID, a Conversions API access token, and one test request. The request itself needs no web page or browser tag; without a source URL, Pixel Activator sends the event with action_source: chat, one of Meta's documented values. Pixel Activator performs the request and shows the platform's answer; that answer proves receipt, not attribution or deduplication.

Which Meta values do you need?

1. Open Meta Events Manager and select the web dataset used by the campaign.
2. In Settings, copy the dataset ID.
3. In the Conversions API or direct-integration setup, generate an access token and save it securely.
4. Enter both values in Pixel Activator when you run the test.

The detailed screen-by-screen path is in the Meta ID and token guide.

Which event should you test first?

Use the same business rule in Pixel Activator, your tracker, and later automation. A Purchase should not mean a button click in one system and a paid order in another.

How do you send a safe first test?

1. Enter the dataset ID and access token.
2. Copy the test event code: in Events Manager, open the dataset, go to the Test events tab, and copy the code shown for server events.
3. Paste that code into the "Test event code" field in Pixel Activator.
4. Select one event and use a recognisable test value if the tool offers one.
5. Send it once and read the response: a successful receipt reports events_received with the number of accepted events.
6. Open the dataset's Test events tab and confirm the event name, source, and diagnostics match the action you tested.
7. Remove the test event code before sending production events; Meta documents that events sent with a test code still flow into Events Manager.

If the event is absent, stop before retrying repeatedly. Re-check the selected dataset, token, and test event code first. Test information stays in the Test events tool for 24 hours or until you clear it.

When is deduplication required?

Meta documents deduplication for Pixel and server events. For a dual setup, preserve one event_id from the conversion moment and use it on both paths. Read the project deduplication concept before enabling both senders.

What should you check before using production traffic?

• The selected dataset belongs to the correct business and ad account.
• Store the current token as a secret.
• Make sure the event represents an actual user action.
• Browser and server copies share a stable event ID when both are enabled.
• The event appears once where you expect it in Events Manager.

Common Meta CAPI mistakes

What comes after the first test?

Pixel Activator is useful for a manual credential and delivery check. For recurring conversion routing, use a system that retains the same event mapping and deduplication rules.

Sources