A conversion event only reaches Meta Events Manager if three things line up: the platform is connected, the lead reached a stage your mapping sends (created, qualified, or converted), and enough time has passed for the platform to reflect it in its own reporting. Check the connection status and the lead's stage first.
Stravax Engage only sends a conversion event to a platform you've connected, Meta, Google, or TikTok, each connected separately and independently of the others. If you haven't connected a platform, or its connection has stopped working (for example a revoked token that can no longer refresh), no event goes to it at all, and the connection's own status will show it needs attention. See Connecting your ad accounts.
A conversion event fires automatically the moment a lead is created, or its stage changes to qualified or converted, as long as your connection's mapping covers that stage. Nothing is sent manually, and nothing is sent for a lead sitting in an unqualified or rejected stage. If the lead hasn't reached one of the synced stages yet, there's nothing to send. See Moving a lead through stages and What is a conversion event?.
It's worth checking timing too. Ad platforms can take a little while to display a freshly received event in their own reporting, so if the stage change happened very recently, waiting and refreshing the platform's dashboard is worth trying before assuming something's wrong.
Each conversion event is deduplicated per lead, stage, and platform, so moving a lead back and forth, or a retried delivery, never produces a duplicate event, and the first one sent is always the one that counts. A failed send retries automatically, and an hourly pass catches anything still stuck, which is also when expired Google and TikTok tokens get refreshed automatically. If nothing changes after that, recheck the connection itself: a platform-side permission or token issue is a common cause.
| Possible cause | Where to check | What to do |
|---|---|---|
| Platform not connected, or its token was revoked | Connection status in Connections | Connect, or reconnect, the platform |
| Lead hasn't reached a synced stage yet | The lead's stage in the pipeline | Move the lead into a stage your mapping covers |
| Event was just sent | The platform's own reporting UI | Wait and refresh; this usually resolves itself |
| Event is still retrying | The automatic hourly retry pass | No action needed; it retries and self-heals within the hour |