Stravax Engage sends conversion signals to Meta and TikTok whenever a lead in your pipeline is created, marked qualified, or converted. Each of those ad platforms you connect receives its own signal, matched to the click or ad that started the WhatsApp conversation, so the platform's algorithm learns which campaigns actually produce real customers, not just clicks.
Stravax Engage reports eligible CRM outcomes to connected ad platforms. A recorded outcome, a provider-accepted request, a matched person, campaign attribution and optimization eligibility are separate facts. Provider receipt alone does not prove the remaining steps. The attribution update below is pending release.
Most WhatsApp inboxes stop at the reply: an ad platform sees a click, then nothing else. Without a conversion signal, ad platforms can only optimize toward clicks or messages started, which rewards volume over quality. For Meta and TikTok, Stravax Engage closes that loop by reporting what actually happened after the click: whether a lead came in, was qualified, and whether it converted into a paying customer. The ad platform's algorithm uses that signal to find more people who look like your real customers, not just more clicks.
Reporting sales outcomes back to Meta and TikTok ad accounts, not just tracking that a click happened, is what separates ad conversion sync from ordinary pixel tracking.
Sending results to Google Ads is not switched on yet.
| Platform | What it receives |
|---|---|
| Meta | New-lead, qualified and converted events, matched to the ad's click token when the conversation started from a click-to-WhatsApp ad |
| Connect your account and receive Google lead forms today. Choose which of the three Engage events to add; each chosen event is added switched on. Sending new-lead, qualified and won results to Google Ads is not switched on yet. | |
| TikTok | New-lead, qualified and converted events, matched to a TikTok click id when available |
When a click identifier is unavailable, any alternative matching depends on the destination, available data and permission. Hashing does not make personal data anonymous.
In the pending attribution update, available matching data and permission are checked for the actual destination. A missing click ID does not authorize every fallback. Meta leads of unknown origin stay held unless a verified compatible route exists. Unsupported TikTok website/CRM flows remain held; native lead-form delivery keeps its own route. Hashing does not make personal data anonymous.
In the earlier look, connect Google Ads or TikTok from the Connections dialog on the CRM page. Facebook and Instagram cannot be connected there after the Facebook connection change; see Connect Facebook and Instagram, or contact support.
No. Connecting an ad account is opt-in, per platform, per organization. If you only run Meta ads, connect Meta and leave Google and TikTok alone: no signal is ever sent to a platform you haven't connected. See Connecting your ad accounts for how to set one up.
The attribution update saves an outcome receipt atomically, then evaluates delivery separately. Native Meta forms use the CRM dataset; genuine CTWA outcomes use the messaging dataset. Website journeys use a separately verified website dataset by default. Later website/thread outcomes require route evidence, and the alternative CRM trial route requires a controlled comparison authorization. A missing website branch does not disable an eligible native branch. New flows remain off until their privacy, notice, pilot and release gates are complete.
Verified acquisition evidence pins the journey. A later click does not switch a native or website journey to another destination. Campaign alignment remains not checked until the destination, goal and selected event are confirmed externally. See Click-to-WhatsApp attribution: how it works.