Stravax Engage records verified referral and tracked-link evidence when it is available. Missing or ambiguous evidence remains unknown. Opening a link does not create a CRM lead or prove ad attribution. The website identity update described at the end of this page is not available yet.
When a verified Meta message carries a genuine CTWA referral, its click identifier can support the messaging route. The acquisition journey remains distinct from each outcome's channel. A later CTWA touch cannot turn an established website or native-form journey into a CTWA journey, and a missing CTWA identifier does not authorize a messaging fallback.
For wa.me links, website buttons, or Google and TikTok message ads, create a tracked link in Stravax Engage instead of a plain wa.me link. When someone clicks it, Stravax Engage records the click id (Google gclid/gbraid/wbraid, Meta fbclid, TikTok ttclid, or Microsoft msclkid) and any UTM parameters, then redirects the visitor to WhatsApp with a short reference code pre-filled into the message. When that first message arrives, Stravax Engage matches the reference code back to the recorded click and attributes the conversation to it.
Add this snippet to your website. On the page a visitor arrives on, it reads ad click ids and UTM parameters from the page address and, when your account has a tracked link, adds them to your WhatsApp links on that page. Unless the newer website identity collection described below is set up for your account, it sets no cookies and stores nothing in the visitor's browser, so a click id is not carried to other pages or later visits.
<script src="https://app.stravax.ai/t.js?k=YOUR_WEB_FORM_KEY" async></script>
Replace YOUR_WEB_FORM_KEY only as part of an authorized installation. A script's presence does not establish advertising permission. The newer website identity collection, which keeps data in the visitor's browser only after your site records the visitor's consent, is not available yet. A failed widget request followed by a plain WhatsApp link is not proven attribution.
Unknown origin remains unknown for measurement. Historical probable matches are not upgraded into deterministic evidence. The pending admission flow requires a real inbound message and the tenant's explicit enablement; multiple open deals require a human choice. A click alone creates nothing, no unrelated click is borrowed, and admission does not enable AI.
The messaging route requires a real sale closed in the thread, a recorded positive value and currency, Purchase opt-in and confirmation that Engage owns reporting for that business. A human CRM decision also needs the business's recorded thread-closing attestation. Shopify, browser pixels, other connectors and offline uploaders must be checked for duplicate reporting. A generic Won label is insufficient. Event upload age and identifier observation age are separate; an unconfirmed old messaging window remains held rather than being given a new timestamp.
Importing ad names is separate from sending eligible outcomes to ad platforms. Admin Ad Sync controls on the new-look CRM page are held; no refresh frequency is promised.
Ad conversion sync: Meta, Google and TikTok explains what this attribution feeds into. The CTWA per-ad report shows the results per ad.
The new website bridge is pending release. Its reference is an opaque random token with a seven-day service lifetime, bound to the intended WhatsApp number and one contact. Keep it intact in the message. An edited, expired or wrong-number token supplies no paid identity. A token cannot be reassigned after its first valid claim; a copied decorated URL gets a fresh receipt with unknown permission. The new path never assigns credit from a nearby unmatched website click.
A site-authorized collector preserves exact supplied IDs and their original observation times. It decorates only the configured destination or an explicit matching tracked-link anchor. Two different WhatsApp numbers on a page retain their own destinations. Dynamic and keyboard-activated links use fresh evidence at interaction. Re-paste the script-loader snippet when the rollout instructs you to replace an older inline snippet.
Opening a link alone creates no CRM deal. A tenant can separately enable new plain-inbound admission after the required notice about Ad Sync quota and legacy overage effects. Those deals have unknown origin. Enabling admission does not enable AI. Returning customers and ambiguous open deals need a staff choice; the matching interface is held for its separately approved UI release.
Preserved evidence is not a promise that an advertising platform attributes or optimizes a campaign. Redirect-only derived Meta evidence remains held without the required platform confirmation, and installations need their own pilot proof.