Skip to main content

Google Ads retargeting

Connecting your Google Ads account to POK turns every visit to one of your organization's credentials into a remarketing audience inside that same Google Ads account. There is nothing to install on your own site: POK loads Google's tag on the credential's public page for you, scoped to the Google Ads ID you connect.

Google Ads retargeting is a premium feature, enabled per organization. To turn it on, talk to your account executive or write to contact@pok.tech.

Where do I find my Google Ads ID?​

POK asks for your organization's Google Ads ID, in the format the field's own hint shows, "Ex: AW-123456789". It is the ID tied to the Google Ads account that should receive the remarketing audiences POK builds for you, so use the one for the account your team actually runs campaigns from.

Connect your Google Ads account​

You need an administrator or operator role. The "Organization Settings" item only appears in the menu for those two roles.

  1. In the top navigation bar, click your organization's name, then click "Organization Settings".

  2. Open the "Connected accounts" tab.

  3. On the Google Ads card, "Turn visits to your credentials into opportunities", click "Configure Google Ads".

  4. In the "Google Ads Integration" dialog, paste your ID into the "Google Ads ID" field.

  5. Check "I accept the data processing agreement". "Confirm" stays disabled until both the field is filled in and this box is checked.

  6. Click "Confirm".

The card then shows a green "Connected" badge and your ID in a pill with an edit icon, in place of the "Configure Google Ads" button.

What gets tracked, and what does not​

When someone opens one of your organization's public credentials, POK checks whether your organization has a Google Ads ID configured, and if it does, loads Google's own tag on that page.

Before anything else, that tag tells Google its consent defaults: ad storage, ad user data, ad personalization and analytics storage all start out denied. Every credential page also shows a cookie consent banner, so advertising data is stored for a given visit only once that visitor accepts it.

Once consent allows it, POK sends a single event, view_pok_credential, to your connected Google Ads ID. It carries the credential's title, its template name and your organization's name, plus, when they apply, the custom page the credential was viewed on and the learning path step it belongs to. It fires once per page view, the first time the certificate, your organization's profile and its template have all finished loading. Nothing about the visitor travels with it: no name, email or identification number, only the credential context above.

Change or remove your Google Ads ID​

To change it, open "Connected accounts" again and click the edit icon on the pill next to your current ID. It reopens the "Google Ads Integration" dialog pre-filled with that ID; edit it and click "Confirm" again.

To remove it, click the delete icon on the same pill. POK asks "Delete Google Ads ID?", "This action will stop collecting remarketing events and audiences for this organization." Click "Delete" to confirm, or "Cancel" to back out. Once removed, the card reverts to the "Configure Google Ads" button.

Your remarketing audiences are not growing​

Work through these in order:

  1. Nobody has opened one of your organization's credentials yet. Tracking only fires when a visitor opens one of your own credentials, once per page view, and only once the page finishes loading the certificate, your organization's profile and its template.

  2. The visitor did not accept the cookie consent banner. Until they do, the default POK sends to Google keeps ad storage and personalization denied, so nothing is stored for that visit.

  3. Google Ads retargeting is no longer enabled for your organization. If your premium access lapsed, the public credential page cannot fetch your ID at all, even if one is still saved under "Connected accounts", so no tag loads and nothing is tracked.

The Google Ads card does not show your ID as connected​

  1. You are signed in as Operator, not Administrator. Only Administrators can see whether Google Ads is already connected on this card; an Operator sees "Configure Google Ads" regardless of whether an ID is stored.

  2. Google Ads retargeting was turned off after you connected an ID. The card only shows the connected pill while the premium feature is on and an ID is stored. If the feature is turned off, the card falls back to the button even though the ID is still saved underneath.