Skip to content

Google Ads

Prism delivers conversions to Google Ads server-side by uploading click conversions matched on the gclid (Google's click ID), which the snippet captures automatically into a 90-day first-party cookie.

What you need

Unlike Meta, Google has no paste-a-token option — conversion uploads go through the Google Ads API, which requires a one-time OAuth consent from someone with access to the Google Ads account (Standard access or above; a manager/MCC login works too).

Connecting

In the Adsidian dashboard, open the client → Connect Google Ads. The wizard:

  1. OAuth — redirects to Google's consent screen; approve with an account that can access the client's Google Ads account.
  2. Pick the account — choose the customer account (MCC-aware: pick the manager and then the child account if applicable).
  3. Map events to conversion actions — e.g. site event Lead → the "Website lead" conversion action. Only mapped events are uploaded. You can also create a dedicated "Prism" conversion action in Google Ads first, so server-side conversions are distinguishable.
  4. Test conversion — sends a zero-value synthetic conversion to confirm the pipeline end-to-end.

Timing is forgiving

Conversions are matched to clicks, not to sessions:

  • The gclid is captured from the moment the snippet is installed — even before Google is connected.
  • Google accepts conversion uploads up to 90 days after the click.

So if the OAuth step can't happen during onboarding, nothing is lost: connect Google a day (or week) later and conversions attribute retroactively from stored click IDs.

Requirements on the Google side

  • Auto-tagging enabled on the Google Ads account (it is by default) — that's what appends gclid to your ad URLs.
  • Don't strip query parameters in redirects between the ad click and the landing page (a redirect that drops gclid breaks attribution).

Ongoing behavior

Mapped events are uploaded as they happen, with value and currency when your events carry them (data-prism-value or the value property). Delivery counts appear in the client's delivery dashboard alongside Meta.

Adsidian Prism — first-party server-side tracking.