Documentation · Prynt Reveal · Install

Google Tag Manager

A Custom HTML tag fired on every page. GTM's consent settings and Google Consent Mode are picked up automatically.

Create the tag

  1. Tags → New → **Custom HTML**. Paste the loader below with your public key and domain (copy them from the console's Install page).
  2. Trigger: **Initialization – All Pages** (or *All Pages*). Reveal follows SPA navigations itself, so no History Change trigger is needed.
  3. Advanced Settings → Consent Settings: *No additional consent required* is fine — the script reads analytics_storage from the data layer itself and sends only minimal pageviews until it is granted. If you prefer GTM to gate the tag, require analytics_storage here instead.
  4. Submit and publish the container.
<script>
  (function () {
    var s = document.createElement('script');
    s.src = 'https://api.pryntid.com/cdn/prynt-reveal.umd.js';
    s.async = true;
    s.onload = function () { PryntReveal.reveal({ publicKey: 'pk_live_YOUR_PUBLIC_KEY', website: 'example.com' }); };
    document.head.appendChild(s);
  })();
</script>

Notes

  • The tag must not be set to *Fire once per page*: single-page apps keep the page alive and PryntReveal.reveal() must run exactly once per page load — it does, because the loader is idempotent per load.
  • Server-side GTM is not needed; the beacon goes straight to api.pryntid.com (see CSP and storage if you run a CSP).
  • Google Consent Mode (gtag('consent', 'update', …)) and the CMPs that implement it (Cookiebot, CookieYes, OneTrust, Usercentrics via GCM) are read every second — a late acceptance is honoured without reloading.

Run the Test Script

  1. In the console go to Websites → your site → **Test Script**. It fetches your page from our side and runs the seven checks: snippet present, public key, website match, CSP script-src, CSP connect-src, consent manager, script position and www redirect.
  2. Open your site with ?prynt_debug=1 to see the live panel from the browser's point of view (consent, CMP, storage, cspBlocked, last send).
  3. Visit two or three pages. The pulse in the console shows the last event within seconds; the first companies appear as soon as a business network visits.

A cspBlocked: true or a failed CSP check means your Content-Security-Policy needs the two lines from CSP and storage. Running a consent manager? Consent explains what is detected and what is sent before the visitor decides.

Next: Webflow

Last updated 2026-11-03 · Limits · Visitor opt-out