Contentpass Integration

Contentpass is a privacy-focused monthly subscription for readers. With one registration, Contentpass users visit participating websites ad-free and without being tracked, while publishers receive subscription revenue that matches lost ad revenue at ad market rates.

The Contentpass Integration plugin integrates Contentpass with your site so you can combine consent management, script control, and Contentpass configuration from the WordPress admin.

Features

• Integration – Configure your Contentpass property (base URL, ID), set up Consentmanager (CMP), and manage staging vs production behaviour.
• CMP support – Consentmanager in the admin UI. Choose whether Consentmanager is already on your site or should be loaded by the plugin (validated snippet paste).
• Blocking Rules – Define patterns to scan for or exclude, with admin UI for script blocking aligned with your consent setup.
• Request Contract – Quick link to the Contentpass publisher contact flow with tracking parameters for support context.
• Staging mode – During onboarding, Contentpass is limited to logged-in editors and administrators (or an authorized URL debug flag). Production for all visitors begins automatically once your property is approved and live in the Contentpass publisher dashboard.

Admin screens require the manage_options capability by default (filterable via cp4wp_required_capability).

External services

This plugin connects to third-party services so you can integrate Contentpass and Consentmanager (CMP) with WordPress. Only the services that match your plugin settings are used (Consentmanager plus Contentpass when configured and not in a disabled/staging-only state). No data is sent to services you have not configured.

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; verifying that your property CNAME and config.json are reachable during setup and admin saves.
• now.js (mandatory): The plugin always loads now.js from the publisher’s configured Contentpass base URL when Contentpass is active. This is part of the official Contentpass integration contract, not user-supplied executable code. The URL is derived from the validated base URL setting (not a free-text script field).
• What data is sent and when:
  • From the WordPress server (admin/setup): HTTP GET requests to https://{your-contentpass-base-url}/properties/{property-id}/config.json when you save settings, use “Check again”, 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/… to connect Contentpass with the selected CMP. 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 Consentmanager is selected as the CMP in plugin settings.

• 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.