XeroWP
Contentpass Integration
Contentpass Integration

Contentpass Integration

0/5 (0 ratings) — active installs Updated Oct 29, 2026
CMPconsentGDPRpaywallsubscription
Download v1.4.7 Plugin Website
Contentpass admin – Integration settings (Consentmanager, URLs, staging).

Contentpass admin – Integration settings (Consentmanager, URLs, staging).

Contentpass is a privacy-focused monthly subscription for readers. With one registration, Contentpass users visit participating websites ad-free and without being tracked.

For you as a publisher, that means revenue from visitors who reject advertising consent. Contentpass pays out at ad market rates, so you earn the same from these visitors as you do from advertising.

This plugin adds Contentpass to your WordPress site. You set everything up in the WordPress admin, without editing your theme.

What your readers get

  • A fair choice. Your consent layer offers two options: agree to personalized advertising, or subscribe to Contentpass and visit ad-free and without being tracked.
  • One subscription for many websites. A single registration covers every participating website.

What you get

  • Revenue when visitors reject consent. Contentpass pays out at ad market rates for visits from Contentpass users.
  • Less work for your team. Contentpass handles payment processing and customer service for its users.
  • Reporting without profiles. You receive aggregated page-view counts from Contentpass users, not personal profiles.
  • Consent in one place. The plugin connects Contentpass with Consentmanager and holds back third-party scripts and embeds until visitors consent.
  • A safe start. Try Contentpass with your own editors first. It goes live for all visitors once your property is approved.

You need a Contentpass publisher account to use the plugin. Don’t have one yet? Get in touch through Request Contract in the plugin menu, or visit the Contentpass publisher page.

For site administrators

Requirements

  • WordPress 6.3 or later and PHP 7.4 or later.
  • A Contentpass publisher account with a Property ID.
  • Consentmanager as your consent management platform (CMP). Consentmanager is the only supported CMP.

What the plugin does

  • Integration: Enter your Property ID. The plugin loads your property configuration from Contentpass, including the host that Contentpass loads from.
  • Consentmanager: The plugin can load Consentmanager for you from the script tag you copy in Consentmanager. If Consentmanager already runs on your site (through your theme, a tag manager, or another plugin), the plugin works alongside it.
  • Blocking Rules: Block scripts and iframes by URL until visitors consent, and set exceptions that always load. Blocked content shows a placeholder with your own text, styling, and privacy link. A rule can also hand its content to Consentmanager Dynamic Content Blocking, using the vendor ID from Consentmanager. Rules can be exported and imported as JSON or CSV.
  • Scripts after consent: Load external scripts, such as ad tags, only after visitors give full consent.
  • Staging mode: Until your property is approved and live, the Contentpass consent layer appears only to logged-in Editors and Administrators, or to anyone who opens a page with ?cpdebug=staging. Consentmanager and script blocking run for every visitor. Staging ends on its own once the property is approved and live in the publisher dashboard (this can take up to 10 minutes).
  • Access control: The admin screens require the manage_options capability. Developers can change it with the cp4wp_required_capability filter.

External services

This plugin connects to third-party services so you can integrate Contentpass and Consentmanager (CMP) with WordPress. Only Contentpass and Consentmanager are used, and only when those features are configured. Staging limits who sees the Contentpass consent layer. Consentmanager and script blocking still run for every visitor.

Contentpass (API and CDN)

Used to load the Contentpass integration (now.js), CMP-specific JavaScript stubs, and property configuration.

  • What it is used for: Subscription and consent integration on the front end; loading your property config.json and verifying that now.js is reachable during setup and admin saves.
  • now.js (mandatory): The plugin always loads now.js from the publisher’s Contentpass host when Contentpass is active. This is part of the official Contentpass integration contract, not user-supplied executable code. The host is taken from the hostname field of your property config.json (not a free-text script field).
  • What data is sent and when:
    • From the WordPress server (admin/setup): HTTP GET requests to https://static.contentpass.net/properties/{property-id}/config.json when you save settings, enter a Property ID, or when the plugin refreshes cached configuration. These requests include the plugin User-Agent (Contentpass-WP/{version}) and your configured property ID. They do not include front-end visitor form input.
    • From the visitor browser (front end, when Contentpass loading is active): Scripts from your Contentpass base URL (for example {base-url}/now.js) and from https://static.contentpass.net/stubs/consentmanager/latest.js. The browser may send standard web request metadata (IP address, User-Agent, cookies, consent/subscription signals) to Contentpass as described in their documentation.
  • Service provider: Content Pass GmbH (Contentpass)
  • Terms of service: https://www.contentpass.net/en/terms
  • Privacy policy: https://www.contentpass.net/en/privacy

Consentmanager

Loaded when Plugin should also load the CMP is selected. Consentmanager is the only supported CMP.

  • What it is used for: Displaying the Consentmanager cookie/consent banner and passing consent signals to ads and tags.
  • Third-party script: The plugin loads Consentmanager’s semi-automatic CMP loader from the validated src URL in your pasted snippet (typically https://cdn.consentmanager.net/delivery/js/semiautomatic.min.js). Only allowlisted data-cmp-* attributes are used; pasted markup is parsed and not echoed raw. Paste the external semi-automatic script from Consentmanager Get Code in the plugin settings when Plugin should also load the CMP is selected.
  • What data is sent and when: From the visitor browser to Consentmanager hosts (cdn.consentmanager.net, delivery.consentmanager.net, and related endpoints) when the CMP script loads and when visitors interact with the banner. Data typically includes the configured Code-ID, page URL, consent choices, and standard request metadata (IP address, User-Agent, cookies). The WordPress server does not proxy visitor consent to Consentmanager.
  • Service provider: consentmanager AB (consentmanager.net)
  • Terms of service: https://www.consentmanager.net/en/general-terms-and-conditions/
  • Privacy policy: https://www.consentmanager.net/en/privacy/

Post-consent ad / tag URLs (optional publisher setting)

Some publishers need specific third-party ad or analytics scripts to load only after consent (for example GPT, Prebid, or network tags). The plugin provides optional URL fields for this purpose.

  • What it is used for: Loading external JavaScript files by URL after the CMP reports full consent, alongside the plugin’s script-blocking unblock flow.
  • What publishers can enter: Only http:// or https:// script source URLs in structured admin fields (max 20). No inline JavaScript, HTML, PHP, or CSS can be saved.
  • How the plugin outputs scripts: It builds <script src="…" async defer class="cpnotblocked"> tags programmatically from validated URLs. javascript:, data:, and other non-URL schemes are rejected at save time.
  • What data is sent and when: From the visitor browser to the hosts in the configured URLs, only after consent, when those tags are injected.

Optional admin links

The plugin admin may link to Contentpass documentation and the publisher dashboard (for example https://docs.contentpass.net/ and https://publisher.contentpass.net/). These open in the browser when an administrator clicks them; they are not automatic background requests to third parties.