Ad conversions, without the patient attached.
Conversion Relay moves your pixels server-side. Each ad network receives the click ID from its own ad and an opaque code for the conversion. The page, the form and the person stay with you.
// uploadClickConversions { "gclid": "Cj0KCQiA8x7Q", "conversionAction": "c_7f3a", "conversionDateTime": "2026-11-14 09:42:00-05:00" } // removed before sending page_url (removed) email (removed) ip_address (removed) user_agent (removed)
Field names follow the Google Ads conversion upload API. [VERIFY]
A browser pixel sends more than a conversion.
When a pixel fires in the visitor's browser, the ad platform receives whatever the browser knows. On a treatment site, that says a lot.
The URL names the service
A path like /detox/insurance-check tells the platform what care the visitor looked for.
Form fields travel along
Auto-capture and enhanced matching can pick up names, emails and phone numbers as the form is sent.
Identifiers link it to a person
IP address, cookies and device data connect the visit to a profile the platform already holds.
From conversion to ad network in four stops.
A call, form or chat completes on your site, after the visitor opted in to Advertising.
The event reaches our servers, not the ad platform. No pixel runs in the browser.
URL, form fields, IP and device data are removed. An opaque code replaces the conversion name.
Each network's conversion API receives the click ID and the code. The delivery is logged.
What Conversion Relay does.
Server-side delivery
Conversions go to Google Ads, Meta, Microsoft Advertising, TikTok, LinkedIn, Reddit, Snapchat and Pinterest through their APIs.
Opaque conversion codes
Ad networks see c_7f3a, never "Detox admission". The mapping lives only in your dashboard.
Click ID matching
We keep the click ID from the ad so the network can attribute the conversion to the right campaign.
Calls and chats count
Qualified calls from CallTrackingMetrics and chat starts relay the same way as forms.
Consent-aware
If a visitor declines Advertising, nothing is sent for that visit. Consent Gateway records the choice.
Delivery log
Every payload sent is logged, so you can show exactly what left your site and when.
You name the conversion. We send the code.
Event mapping turns each conversion you care about into a code per destination.
Sample dataEvent mapping
site_0000 · example.org- Admissions inquiry · DetoxAllowed
- Insurance verification formAllowed
- Chat startedAllowed
- Call over 90 secondsNeeds review
- gclid
- Cj0KCQiA8x7Qkept
- conversionAction
- c_7f3a
- page_url · email · ip
- removed
One snippet. Nothing on your server.
Add the gateway first in your site's head. Conversion Relay is configured in the dashboard; there is no server code to deploy.
WordPress and Webflow guides<!-- First in <head>, before any other script -->
<script src="https://gateway.compli3d.ai/v1/gateway.js" data-site="site_0000"></script>Fictional site ID shown. Your dashboard gives you the snippet with your own site ID. [VERIFY SNIPPET]
About Conversion Relay.
Which ad networks does it support?
Google Ads, Meta, Microsoft Advertising, TikTok, LinkedIn, Reddit, Snapchat and Pinterest, through each network's conversion API.
Will the ad network still optimize my campaigns?
Yes. The click ID lets the network tie each conversion to the ad that earned it. Because we send no email or phone, match rates can be lower than with browser pixels; we show you delivery per network so you can judge.
What happens if a visitor declines advertising?
Nothing is sent for that visit. The conversion still appears in your dashboard.
Do I need to remove my existing pixels?
Consent Gateway holds them from the moment the snippet is live. We help you remove them from the page as each network moves to the relay.
Where is conversion data processed?
On our servers, under a business associate agreement. [VERIFY HOSTING REGION]