Connect Meta the right way

Find (or create) your dataset Events Manager

In Meta Events Manager → Data sources, pick the dataset (pixel) this client's ads use. No dataset yet? Connect data → Web, name it after the client, and skip the website-code steps — we deliver events server-side.

Copy the Dataset ID (a long number, shown under the dataset name and in Settings).

Generate the access token dataset Settings

Open the dataset's Settings tab and scroll to Conversions API. Under "Set up direct integration", click Generate access token. Copy it — this token can send events to this dataset and nothing else, which is exactly the least privilege you want.

Treat it like a password: paste it straight into the app's Connect Meta form and nowhere else — not documents, not chat threads, not tickets.

Grab the test event code optional but worth it

On the dataset's Test events tab, copy the code that looks like TEST12345. With it in place, the app fires a ConnectionTest event the moment you connect — visible in that tab within seconds.

Connect & verify in the app

Open the location in Pipeline Signals → Connect Meta → paste Dataset ID, token, and test code → save. The app validates against Meta before storing anything, so a bad paste fails loudly here instead of silently later.

Verify: keep the Test events tab open while connecting. It's a live feed — it only shows events that arrive while the tab is open, which is the single most common "nothing is showing up" confusion. Your ConnectionTest should appear within ~10 seconds.