Ad conversions
LiveCapture the gclid on ad-driven link clicks and forward offline conversions to Google Ads server-side, with value, currency, and your conversion action attached.
Bot traffic is excluded by default. Delivery runs off the redirect path with automatic retries.
Why Google Ads Conversions API with Nimriz
When Google Ads auto-tagging appends a gclid to your ad clicks, Nimriz captures it at the redirect, keeps it with the click, and attaches it to the conversion your backend later reports. The result is offline conversion uploads that actually match ad clicks, without you building gclid plumbing yourself.
Most link platforms throw away ad click identifiers at the redirect. Nimriz extracts the gclid from auto-tagged clicks automatically, with wbraid supported where present, so conversions arrive with the identifiers Google Ads needs.
Conversions carry type, monetary value, and currency. Refunds, cancellations, and reversals reference the original sale instead of overwriting it, so downstream reporting stays truthful.
Stable event identifiers and idempotency keys keep retried callbacks from becoming duplicate conversions, even when your backend sends the same outcome twice.
Conversion bridge
Conversions carry type, value, and currency, with deduplication through stable event identifiers and idempotency keys. Refunds, cancellations, and reversals reference the original sale instead of overwriting it.
Nimriz records the touch with campaign context and, where enabled, appends the nim_ct click token to the destination URL.
Send lead, sale, refund, cancellation, or reversal events to the signed Nimriz Conversion API using the click token or your own customer identifier.
The conversion joins the original click, inherits campaign and link context, and is formatted into a destination-ready payload.
The attributed conversion uploads with the captured gclid, your conversion action, and value details. Delivery runs asynchronously with retries.
Under the hood
Forward eligible conversion events to Google Ads using the setup guide.
Connector access, mapping controls, and event volume depend on plan. Use pricing and setup docs to confirm the right path before configuring production delivery.
Guided setup
Add the platform credentials in the destination catalog and run Test connection before anything is saved.
Enable conversion tracking on your links and report outcomes from your backend through the signed Conversion API.
Scope which conversion events this destination receives by domain, space, tag, country, or field conditions.
Review the configuration, confirm test results, then enable the action for live server-side delivery.
Nimriz uses destination-aware payloads and privacy-aware analytics language. Do not send secrets, raw personal data, or provider credentials in public links.
Nimriz never forwards raw IP addresses or complete User-Agent strings in integration payloads. Strict privacy mode omits visitor hashes and selected granular fields such as city.
Analytics privacy docsMore in Ad conversions
Turn branded link clicks into attributed, server-side Meta conversion events with value and currency attached, without slowing the redirect or relying on browser pixels alone.
Report B2B outcomes from branded campaign links to LinkedIn server-side, mapped to the conversion rules you manage in Campaign Manager.
Connect creator and campaign link outcomes to TikTok server-side, so short-link and QR-driven conversions feed paid social reporting with value and currency attached.
