Skip to content

Send a test event to Meta Conversions API

Paste your Meta dataset (pixel) ID and a Conversions API access token, pick events and send them straight to the Graph API. Add the Test Event Code from Events Manager to see them in Test Events instead of your live data.

Pixel ID and token are used for this request and are not stored or logged by our server.

Where do I get the ID and token?

Copy it from Events Manager → Test Events of the same dataset. Without a code, events are recorded as real.
Left empty, events are sent without a website source (offline/chat).
Events 0/5 Pick up to 5. Events that need an amount are sent with value = 1 USD.

1 239 events sent through the service

What does Way2 Pixel send to Meta?

Way2 Pixel (Pixel Activator) builds one Conversions API request per click and posts it to graph.facebook.com/v21.0/{dataset_id}/events. Every selected event becomes one item in data[]. The token travels as access_token in the request body; our server uses it for this request only and does not store it.

FieldWhat the tool sendsNote
event_name The event you ticked, e.g. Purchase A custom name is sent exactly as typed
event_time Current Unix time in seconds
event_id {event}_{time}_{random} New on every send
action_source website if Event source URL is filled, otherwise chat
event_source_url Your URL, https:// added if missing Only when filled
user_data client_ip_address and client_user_agent of your browser No email, phone or other hashed identifiers
custom_data value: 1, currency: USD Purchase only
test_event_code Top-level field of the request Only when you enter a code

Supported events

Events marked $1 are sent with an amount of 1 USD. You can also add one custom event name: letters, digits and underscore, up to 50 characters.

How does test mode work on Meta?

Meta uses a code, not a switch. Open Events Manager, select the dataset, go to Test Events and copy the code shown on that screen. Paste it into Test event code before you press Send.

With the code, the request carries test_event_code and the events are routed to the Server section of Test Events. Without it, the same events land in the dataset as real conversions and can reach reporting and campaign optimisation.

How do I know Meta accepted the events?

  1. Read the response under the form: HTTP 200 with events_received equal to the number of events you sent means Meta accepted all of them.
  2. Open Events Manager, select the same dataset and go to Test Events.
  3. Check the Server section: events sent with a Test Event Code usually appear within seconds.
  4. Compare event names and times with your send. Keep fbtrace_id from the response if you need to contact Meta support.

Where do I get the dataset ID and access token?

Both live in Events Manager. The dataset ID is in the dataset's Settings; the token is generated under Settings > Set up direct integration. Meta shows the token once, so copy it straight into a password manager.

Step by step: find the Meta dataset ID and generate a token

Common Meta errors in this tool

What you seeLikely causeWhat to do
Error code 190 The access token is invalid, revoked or belongs to another dataset Generate a new token in the settings of this dataset
Error code 100 or 803 Meta cannot find the dataset for this request, usually a wrong ID Copy the ID again from the dataset's Settings in Events Manager
HTTP 429 Too many requests in a short time Wait a minute, then send once more
HTTP 200, but nothing in Test Events No Test event code, or a code from another dataset Copy the current code from Test Events of the same dataset

Meta CAPI error codes and how to fix them

FAQ

Is the dataset ID the same as the pixel ID?

Yes. Events Manager now calls the pixel a dataset; the number is the same and goes into the Pixel ID field.

Why is Purchase sent with value 1 USD?

Meta expects value and currency for Purchase, so the tool adds value 1 and currency USD. Other Meta events are sent without custom_data.

Will test events affect my campaigns?

Events sent with a Test Event Code are routed to Test Events. Events sent without a code are recorded as real ones, so keep the code in place while you check the setup.

Can I check Pixel and CAPI deduplication here?

No. Every send gets a fresh event_id, so it never matches a browser Pixel event. Deduplication needs the same event_id and event_name from both sources.

Further reading

Official documentation

Free test form
No account or payment card required; request limits still apply.
No login
Nothing to sign up for. Open the page and send.
No server token storage
Your token is used for the request and is not stored by our server.
Need an ongoing conversion route?
Most can map and route conversion events from connected sources to advertising platforms. Discuss your setup in Telegram.
What Most does →
Write in Telegram

Updated: 2026-10-14