Documentation · Prynt Reveal · Install

WordPress

Three ways, from no-code to a child theme. All of them load the same one-line snippet on every front-end page.

Option A — a header/footer plugin (no code)

  1. Install **WPCode** (formerly *Insert Headers and Footers*) or the header-code feature of your theme / SEO plugin.
  2. Copy the snippet from the console (Websites → your site → Install).
  3. Paste it in the **Header** box, save. Done — WPCode prints it in <head> on every page.
<script src="https://api.pryntid.com/cdn/prynt-reveal.umd.js" async
  onload="PryntReveal.reveal({publicKey:'pk_live_YOUR_PUBLIC_KEY',website:'example.com'})"></script>

Option B — the theme's custom code field

Astra, GeneratePress, Kadence, Divi, Elementor and most premium themes have a *Header scripts* / *Custom code* field under Appearance → Customize or the theme options. Paste the same snippet there.

Option C — functions.php of a child theme

// functions.php of a child theme (or a small mu-plugin). Loads on every front-end page.
add_action('wp_head', function () {
  if (is_admin()) return;
  echo '<script src="https://api.pryntid.com/cdn/prynt-reveal.umd.js" async '
     . 'onload="PryntReveal.reveal({publicKey:\'pk_live_YOUR_PUBLIC_KEY\',website:\'example.com\'})"></script>';
}, 5);

Use a child theme or a mu-plugin so a theme update does not remove it.

Notes

  • Caching/optimisation plugins (WP Rocket, LiteSpeed, Autoptimize): exclude prynt-reveal.umd.js from *delay JavaScript* so the first pageview is not postponed until the visitor interacts; async is already there.
  • Consent plugins: CookieYes, Cookiebot, Complianz (which can emit Google Consent Mode) and Klaro are detected automatically — see Consent.
  • Contact Form 7, WPForms, Gravity Forms: add forms: true to the options (or the form selector) to capture the email on submit with consent.
  • WooCommerce: the snippet also runs on checkout pages; logged-in customers can be identified with identify({ email }) from a small snippet that reads the current user.

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: Google Tag Manager

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