title: "Google Ads Conversions API" description: "Send click data and offline conversions to Google Ads for better campaign attribution."

Google Ads Conversions API

Nimriz supports forwarding conversion events directly to Google Ads using the server-side Conversions API, as well as firing client-side tracking pixels via the tracking interstitial.

Review your Google Ads setup, notices, legal basis, and consent requirements before enabling either path.

Setup Google Ads Pixel (Tracking Interstitial)

If you rely on the client-side Google tag (gtag.js), you can use the tracking interstitial to fire the tag before the user reaches their destination.

1. Navigate to Settings > Integrations in the Nimriz dashboard.
2. Click Add Integration Destination and select Ad Pixel (Interstitial).
3. Set the Platform Type to Google.
4. Enter your Measurement ID or Conversion ID (e.g., AW-123456789).
5. Enable the tracking interstitial only after confirming your campaign disclosure and consent flow where required.
6. Click Create Destination.

Setup Google Ads Conversions API

For higher fidelity tracking without redirect latency, you can send conversion events server-side to Google Ads. This requires the click to include a Google Click ID (GCLID) which Nimriz will capture and forward.

1. Navigate to Settings > Integrations in the Nimriz dashboard.
2. Click Add Integration Destination and select Google Ads Conversions API.
3. Enter your Conversion ID.
4. (Optional) Enter your Conversion Label if you are targeting a specific conversion action.
5. Click Create Destination.

When Nimriz logs a conversion event (either via the API or a post-back webhook), it formats the event and dispatches it to Google Ads as an offline conversion, referencing the original GCLID captured during the redirect when available. Nimriz does not forward raw IP addresses or full User-Agent strings.

Nimriz does not forward original IP addresses or complete User-Agent strings in the canonical server-side payload. Standard privacy may include daily-salted pseudonymous hashes where supported. Strict privacy omits visitor hashes and selected granular fields such as city.

Frequently Asked Questions

Does the interstitial affect redirect speed?

Yes. The tracking interstitial serves a brief HTML page to load the Google tag, adding approximately 1.5 seconds of latency before the user is redirected to the final destination.

Do I need to append gclid manually?

If you run Google Ads with auto-tagging enabled, Google automatically appends the gclid parameter to your URLs. Nimriz automatically extracts this from the request and includes it in server-side conversion payloads.

Treat gclid and similar click IDs as purpose-bound attribution identifiers. Do not place personal data, secrets, access tokens, or sensitive data in destination URLs, short-link paths, UTM fields, custom query parameters, pixel settings, or conversion payloads unless you have an appropriate basis and understand downstream processing.