Support

Set up Meta value sending

On this page

Meta value sending, alone in the Values sent to ad platforms group of Setup > Data sources, is the one source Tapper writes to: your own Meta dataset, through Meta's Conversions API.

You connect the dataset your ads optimise on, and Send test event sends one test event and shows Meta's answer. The connection is in Test mode: Tapper sends only the test event you ask for, and no purchase values. The mode is not set on this page.

Before you start

  • You need the Owner or Admin role to connect or change it. Managers can see it.
  • Someone with access to Meta Events Manager follows the steps the form lists under Before you start, in your own Meta Events Manager:
    1. Open the dataset (pixel) your ads optimise on and copy its ID.
    2. Under Settings, Conversions API, generate an access token for it.
    3. Under Test events, copy the test event code.

Connect your dataset

  1. With several protected entities, pick the entity in the switcher at the top of the sidebar.
  2. Under Setup, click Data sources.
  3. Click Set up on the Meta value sending row.
  4. Enter the Dataset ID (digits only), Access token and Test event code, then click Connect.

The Values sent to ad platforms group of Data sources with the Meta value sending row: Not connected and its Set up button

The Set up Meta value sending dialog with the steps in your own Meta Events Manager and the Dataset ID, Access token and Test event code fields

Send a test event

  1. Click Manage on the row, then Send test event.
  2. "Meta received the test event. It shows under Test events." means the dataset and token work. Check Test events in Events Manager.

The event carries your test event code, so Meta does not count it as real. Without a code the button is off: "Add the test event code first. Without it Meta would count the event as real."

Once connected

  • The row reads Connected, with the mode and the last test's result and time.
  • Settings shows the Dataset ID, Access token (last characters only), Test event code and Mode (Test mode). Edit changes them.
  • Activity shows the Last test, Meta's answer, Events received and Meta's Trace ID, which Meta support may ask for.
  • Disconnect deletes the stored token and test code. To end access on Meta's side, revoke the token in Events Manager.

If something goes wrong

  • Meta refuses the access token: generate a new one under Settings in Events Manager, then click Edit and paste it.
  • "The save failed. Paste the access token again.": the token is not kept after a failed save. Paste it and save.
  • "Too many test events.": the limit is 30 an hour per address and per workspace. Try again in an hour.

Still need help?

Chat with our team and mention this article.