Google Ads Conversion 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.

Requirements

You must have a Growth plan or higher to connect Google Ads destinations. Server-side CAPI forwarding also requires conversion events to be available in your workspace.

For server-side Google Ads forwarding, Nimriz manages the OAuth app. You authorize the Google Ads account, then choose the customer and conversion action settings Nimriz should use.

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. Go to Integrations›Destinations›Browse catalog in the Nimriz dashboard.
2. Choose Ad Pixel Interstitial.
3. Set Platform to Google and enter your Pixel ID (e.g., AW-123456789).
4. Leave the Tracking interstitial toggle on only after confirming your campaign disclosure and consent flow where required, then click Test connection.
5. Continue through the Filter events and Review steps, then click Connect 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 attribution identifier such as GCLID, WBRAID, or GBRAID, which Nimriz captures and forwards when available.

1. Go to Integrations›Destinations›Browse catalog in the Nimriz dashboard.
2. Choose Google Ads Conversions API.
3. Enter your Customer ID and Conversion Action ID. Optionally add a Conversion Label for a specific conversion action and a Login Customer ID if you operate through a manager account.
4. Continue through the Filter events and Review steps, then click Connect destination.
5. Open the destination detail page, click Connect provider, sign in to Google, and authorize Nimriz. Before saving the connection, Nimriz verifies that the authorized account can access the configured customer and conversion action.
6. After the provider status is connected, use Send test event. Nimriz rechecks the configured Google Ads resources, then asks the Data Manager API to validate the event without ingesting a conversion.

When Nimriz logs a conversion event (either via the API or a post-back webhook), it formats the event and sends it through the Google Data Manager API as an offline conversion, referencing the original Google attribution identifier captured during the redirect. Nimriz does not forward raw IP addresses or full User-Agent strings.

Existing Google Ads destinations that were configured with a manually supplied access token continue to run during the transition. New dashboard setup uses managed provider authorization instead of pasted provider tokens.

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.