Connect Meta
- Meta Events Manager → Data sources → the dataset (Pixel) your ads optimise on → Settings. Copy the Dataset ID.
- On the same page, under Conversions API, Generate access token.
- In the dashboard, Settings → Meta → Connect Meta, paste both.
Connect TikTok
- TikTok Events Manager → the pixel your ads use → Settings. Copy the Pixel code.
- Generate Access Token (Events API).
- In the dashboard, Settings → TikTok → Connect TikTok, paste both.
Test before going live
- In Events Manager, open Test events and copy the test event code.
- Enter it as Test event code in the dashboard. While it is set, every event is sent as a test and counts for nothing in reporting or optimisation.
- Send test event sends one install right away. It shows under Test events within a minute.
- Clear the code to go live.
What is sent
Each event can be switched off or renamed per network. Renewals are off by default: they
land long after the click, outside the networks’ attribution windows. Purchase events
carry the price and currency from RevenueCat.
- Only matched installs are sent, and only to the network whose click it was: a tap
with
fbclidgoes to Meta, one withttclidto TikTok. Installs from plain links, ambiguous and unmatched installs are never sent. - Each event carries the tap’s click id, IP address and user agent, as the Pixel would have, and a hashed install id so the network can deduplicate.
- Refunds, cancellations, and sandbox or test purchases are never sent.
- Postbacks start with the first install matched after you connect. Nothing is sent retroactively, and events older than 7 days are skipped because the networks reject them.