Tracking Matrix
Choose where server-side events go, which triggers fire automatically, and map any element on your site to a custom conversion.
Conversions APIs
Where server-side conversions are sent.
Meta Conversions API (CAPI)
Server events with hashed identifiers
Google Ads Server-Side
Enhanced conversions via edge relay
Signs in once and stores a reusable credential, so conversions keep flowing while you're offline.
LinkedIn Conversions API (CAPI)
B2B lead conversions sent server-side
LinkedIn only counts conversions it is told about. Sending them from the server means ad blockers and cookie limits can't lose them.
Reads your ad accounts and their conversion rules, and streams conversions to the rule you choose. Access renews itself, so there is no token to rotate and nothing to paste.
CRMs
Where closed deals come from, so bidding can follow revenue.
HubSpot CRM → Google Ads
Closed Won deals sent as offline conversions with real revenue
Google optimizes for whatever you send it. Sending closed deals with their real value teaches it to find buyers, not form fills. How this works
Reads deals and contacts. Adds one hidden gclid field to your forms so closed deals can be traced back to the ad click — why we need that.
Salesforce connector
Closed Won opportunities as offline conversions
Test your connections
Sends one sample conversion — with a hashed test email, phone, value and page URL — to every destination you have switched on, then shows exactly what each one said back. Save your settings first.