Integrations overview
Which ad platforms Convultra connects to today, what each connection does, how the setup wizard works, and how to read the card states.
On this page · 8 sections
Convultra connects to your ad platforms and sends conversions through their server-side APIs, so nothing is lost to ad blockers, cookie limits or iOS privacy changes. It also pulls ad spend back in, so the dashboard can show blended ROAS and CPA. Open Integrations in the sidebar to see every integration and its current state.
What is live and what is coming
| Platform | Conversion forwarding | Ad spend sync | Notes |
|---|---|---|---|
| Google Ads | Live, with enhanced conversions | Live | Setup guide |
| OpenAI Ads | Live | Live | Connects with an Ads API key; forwarding needs a Conversions API key as well (below) |
| Microsoft Ads | Coming soon | Live | Setup guide |
| Meta | Coming soon | No | Setup guide describes the setup that will apply |
| TikTok | Coming soon | No | Events API |
| Google Search Console | Read-only organic search data | Setup guide |
Audience Sync is live for Google Ads Customer Match and OpenAI Ads Custom Audiences. See the Audience Sync guide. Meta and Microsoft audience destinations are coming soon.
Also coming soon: LinkedIn, Pinterest and Snapchat conversion forwarding, a Shopify app, and Stripe and CRM revenue. Every coming-soon feature is tagged wherever it appears on this site.
Connecting a platform
Google Ads, Microsoft Ads and Google Search Console connect with an OAuth sign-in: click Connect on the card and sign in with the account that has access. Google Ads asks for the Google Ads, Data Manager and basic profile permissions. Tokens refresh automatically in the background; you do not need to sign in again unless you revoke Convultra’s access from the platform side.
OpenAI Ads connects by pasting an Ads API key from your OpenAI Ads account. That key covers spend sync and audiences. Sending conversions needs a second credential, a Conversions API key, created in Ads Manager under Settings → Manage conversion keys; the card asks for it before the forwarding wizard opens. The account key will not work in its place.
The setup wizard
Once connected, each ad platform card opens the same four-step wizard, and each step saves as you complete it:
- Account. Pick the ad account (or accounts) to connect. Selecting an account starts spend sync.
- Conversion action. Choose the conversion action or goal in the ad account that receives your conversions. Only the seven conversion types (
purchase,lead,signup,subscription,download,contact,schedule) are forwarded. - Value and matching. Decide where the conversion value comes from, and switch Enhanced conversions on to send SHA-256 hashed customer data alongside each conversion.
- Confirm. Review and confirm. Forwarding starts.
Then click Send a test conversion on the card to open the Conversion Test Center and push one conversion through the full pipeline.
Card states
| State | Meaning |
|---|---|
| Connected | The account is linked and setup is complete, but nothing has been sent in the last seven days yet. |
| Healthy | Conversions are being delivered. Underneath, Some failures or Failing appears instead if recent uploads have failed, Setup unfinished if a step of the wizard is still open, and Needs reconnecting if the platform revoked the token. |
| Script missing | The tracking script has not sent any events, so there is nothing to forward. See Tracking health. |
| Paused | The chosen conversion action is paused in the ad account. Conversions are not counted until you unpause it there. |
| Stale | The chosen conversion action has not recorded a conversion for months in the ad account. Check it is the one you meant. |
| Unavailable | The conversion action cannot take uploads (for example it is a call or app action, or forwarding is not live for that platform yet). Choose a different action. |
Delivery
Every attempt to send a conversion is on the Conversion delivery page in the sidebar, with its status (pending, retrying, success or failed) and the reason for any failure in plain English. A failed upload is retried automatically up to 3 times, then waits for a manual retry. See Events show as pending and never send.
Consent
When a visitor has declined tracking, through a consent banner that records the denial, a cookies_declined cookie or Do Not Track, the Convultra script does not run, so nothing is recorded or forwarded for them. See Does Convultra work with a consent management platform?
Reading delivery programmatically
The REST API and MCP server expose the delivery log through list_deliveries and get_delivery_summary, and get_project reports which platforms are connected, with status and timing only, never credentials.
Next steps
Pick a platform above, or go to Integrations and click Connect on the Google Ads card.