You connect Meta, Google Ads, Microsoft Advertising, Snapchat and TikTok separately, one platform at a time, from Settings > Connections, subject to availability. In the earlier look, connect Google Ads or TikTok from the Connections dialog on the CRM page. After the Facebook connection change, Facebook and Instagram cannot be connected there. See Connect Facebook and Instagram. Connecting or disconnecting one platform never touches the others. Your credentials are encrypted before they're stored, and Stravax Engage refreshes Google and TikTok connections automatically so you rarely need to reconnect.
Connect an ad platform to pull its lead-form submissions into your pipeline. Conversion sync starts in Test mode until you turn it live; sending results to Google Ads is not switched on yet.
Open Connections and choose the platform you want to add. Each connection is scoped to your organization only: a connection you create is never visible to, or usable by, another tenant on Stravax Engage. Once connected, the platform shows a status so you can see at a glance whether it's active and sending, or still pending.
The new-look Facebook and Instagram connection and reconnection controls are held. Contact support; the following describes earlier connection behavior and does not establish that a new connection can be made now.
A new Meta connection starts in Test mode. Test and Live are explained below.
A dataset is where Meta receives the conversion events Stravax Engage sends for your ads. There are two kinds:
The list shows the datasets Stravax Engage finds for your Page. A dataset you enter with Enter a dataset id must belong to the business portfolio of your Facebook Page, and Stravax Engage reads it back from Meta before saving it. If the list is empty or the dataset you need is missing, use Enter a dataset id and paste the ID. For the WhatsApp dataset, enter both the dataset ID and your WhatsApp Business Account ID. The account must be one of the WhatsApp numbers connected to this workspace, and the dataset is checked with Meta against the Page's business portfolio.
While click-to-WhatsApp events are waiting for a dataset, Stravax Engage also attempts discovery once an hour. This needs an active Meta connection, exactly one WhatsApp account in your workspace with usable credentials, and a dataset that Meta returns as linked to that account. When it finds one, it saves the link. This is a best-effort check with no delivery-time promise, so entering the dataset yourself stays the quick alternative. Stravax Engage never creates a dataset in your Meta business. Creating one is a deliberate step you take in Meta.
A click-to-WhatsApp event for a connection that is Live but has no WhatsApp dataset cannot be sent yet. It waits instead of failing, and shows Waiting for dataset. A Live connection that has only the WhatsApp pair and no main dataset also makes main-path events wait. When a dataset is saved, or Meta starts returning a linked one, the eligible waiting events resume with their original time, subject to Ad Sync being on and the connection being active and Live. Delivery keeps its other checks and has no promised time.
A Meta event is checked against a 7-day age limit counted from the conversion time. An event older than that is too old for Meta to accept. It shows Too old to send and is not sent. Snapchat and Microsoft apply the same limit.
New connections start in Test. Google Ads result sending is not switched on yet. You turn a Meta connection Live with Go Live, which needs a dataset to be picked first, and go back with Use Test.
If you reconnect Meta and the connection ends up with no destination dataset, Stravax Engage switches it to Test and shows a warning on the card: "Reconnecting switched this connection to Test. Conversion events are not being sent." A reconnect that keeps its dataset stays Live. Choosing None for now when you finish connecting also switches a Live connection to Test. Stravax Engage never turns Live back on by itself. Pick a dataset again, then press Go Live.
A reconnect or a save can also be refused when the connection changed while you were editing it. Nothing is overwritten. Reload the card and try again.
Connect your Meta ad account to create click-to-WhatsApp ads from the CTWA report. Everything is created paused. Going live is always a separate, confirmed step. The daily budget cap is entered in minor units (for example fils or cents). Campaign creation above the cap is refused on the server, and new campaigns always start paused.
Before connecting, all three creation switches start on:
Leave on at least one. Connecting adds the conversion actions you leave on to your Google Ads account and switches them on. Once result sending is switched on, Google may use them to steer your ads. You can switch them off in Google Ads. Conversion actions already added stay in Google Ads. An action left off can be added later: connect again with it switched on. Existing compatible actions are reused without changing them.
An already-added action is locked on in Engage. If you remove it in Google Ads, the next explicit setup adds it again switched on. To leave it out, disconnect and reconnect with its switch off. If adding an action fails, the connection stays in error until setup succeeds; existing actions create no result rows during that time. A stage whose action was left out creates no Google result row, retry, error or charge, and adding it later does not replay past transitions.
Results are not sent to Google yet: nothing is sent, counted or charged, so these conversion actions have no effect on your ads until sending is switched on.
You can set an expected value for a qualified lead under Lead quality in the same Connections window. It applies on every connected ad platform. When no value is set, qualified leads carry no value. A won lead uses the deal's own amount and currency.
Microsoft does not document how long the token lasts. If sending starts failing with a 401 error, copy the token again from the same place and save it in Connections.
Snapchat does not document whether validated events are recorded or discarded. Clear the validation box only when you want the connection to use the live events endpoint.
The junk gate flags honeypot hits, disposable email addresses, implausible phone numbers and rapid duplicate submissions. Flagged leads are kept under the Junk filter and never send a conversion.
You can set an expected value on qualified leads. When set, qualified leads carry this value on connected ad platforms when sending is enabled, so those platforms can bid toward value, not just volume. A lead's own converted value always wins.
Customer list audiences build a Meta Customer List from your own customers, for targeting, exclusions and lookalike seeds. Unlike conversion events, a customer list has no freshness window, so historical customers count too. Every sync replaces the audience, so churned customers drop out. Nothing is uploaded until you press Upload to Meta and confirm Upload and replace.
Yes. Your ad account credentials are encrypted at rest (AES-GCM) before they ever touch the database, with a fresh random value used on every encryption. If a stored credential were ever tampered with, decrypting it would fail loudly rather than silently returning garbage. When you view a connection afterward, Stravax Engage never shows the credential back to you or anyone else, not even in a redacted form beyond confirming that a credential is on file.
Google and TikTok connections use tokens that Stravax Engage refreshes automatically on a regular schedule, so the connection keeps working without you needing to re-authenticate. If access is revoked on the platform's side and a token can no longer be refreshed, the connection shows an error status until you reconnect it.
You can update or replace a connection's credentials at any time from Connections, without disconnecting the other platforms you've set up.
Meta's CRM dataset, verified website dataset and messaging dataset/WABA are independent roles. Selecting a website dataset does not replace an established CRM destination. The website selection uses the same business-ownership check as the existing validated dataset setup. Sharing an ID across roles requires a collision review.
An authenticated workspace admin can inspect basic Ad Sync readiness independently of the advanced lead-quality entitlement. Advanced quality diagnostics stay under that entitlement. Basic readiness separates Test/Live, mapping, origin/identity/permission/route holds, budget, oldest unsent occurrence and actual attempt disposition. Matching, attribution and optimization remain unknown without platform evidence.
A connection can support one branch while another stays held. An eligible native-form branch need not wait for website setup. Switching to Live or repairing a destination does not replay historical outcomes automatically: an admin previews a bounded eligible set and confirms those existing delivery IDs. Stravax admin approval still controls paid Ad Sync activation. These backend contracts do not enable collection or introduce new controls before the separate UI and release gates.
Ad conversion sync: Meta, Google and TikTok explains why connecting a platform improves ad performance. What is a conversion event? explains the conversion stages. Sending results to Google Ads is not switched on yet.