Permission: Campaign entities
The ad-free reading model (also known as the Pur model) is a CMP set-up that provides end-users with a choice to pay a fee to access ad-free content or provide consent to a list of vendors and purposes the publisher has defined.
In this article, we will cover two different methods your organization can employ to support ad-free reading (Pur model) in your privacy manager:
- Single consent/reject action for all vendors and/or purposes (bucketed approach)
- Granular consent/reject actions for each vendor or purpose
Note: Please speak with your Account Manager to activate ad-free reading (Pur model) functionality for your organization's Sourcepoint account.
To start, click Messages on the left-hand panel and select GDPR Messages.
Select Web/Webview (TCF) or Web/Webview Standard from the subsequent menu.
Use the property field in the upper right-hand corner to select a property for which you will utilize the Pur model.
Single consent/reject action for all vendors and/or purposes (bucketed approach)
The bucketed approach to the Pur model is a message configuration that allows for a single consent/reject action for all vendors and/or purposes within the privacy manager and a subscribe button in the first layer message.
- Privacy manager configuration (bucketed approach)
- First layer message configuration (bucketed approach)
Privacy manager configuration (bucketed approach)
Customize the privacy manager. Click here for more information on how to navigate the privacy manager builder.
While on the Home page in the privacy manager builder, expand the Privacy Manager Settings tab and enable the toggle for Use Pur model?
Click Save Message when finished.
Toggles will no longer appear for end-users to opt out of purposes and/or vendors who use consent as a legal basis.
First layer message configuration (bucketed approach)
In order to fulfill the conditions of a Pur model experience, your organization will need to give end-users the option to provide some other monetary alternative and not give consent. There are two methods by which you can create a button that provides this option:
- Custom JavaScript
- Redirect (will open redirected page in new browser tab)
Either method can send your end-user to your shop, subscription URL, payment provider, etc...
Note: If the end-user has elected to pay instead of providing consent, your organization will need to "mark" the end-user in your system so that it is noted that the end-user has subscribed.
Create a button in your first layer message that end-users will use to subscribe to your service. Once created, select the button and navigate to the Settings panel on the right-hand panel.
Expand the Action accordion and select Custom JavaScript from the Choice Option dropdown menu.
Use the provided space to input your organization's javascript to allow end-users to pay money instead of providing consent.
Note: The Redirect action will open the input URL in a new browser tab. Please utilize the Custom JavaScript action if this behavior is not desired.
Create a button in your first layer message that end-users will use to subscribe to your service. Once created, select the button and navigate to the Settings panel on the right-hand panel.
Expand the Action accordion and select Redirect from the Choice Option dropdown menu.
Use the provided space to input your organization's URL to allow end-users to pay money instead of providing consent. The URL will open in a new browser tab.
Granular consent/reject actions for each vendor or purpose
The granular conset/reject action approach to the Pur model is a message configuration that allows the end-user to make individual selections for each purpose and/or vendor within the privacy manager (where some purposes can be marked as required for consent) and a subscribe button in the first layer message.
- Vendor list configuration (granular consent/reject actions)
- Privacy manager configuration (granular consent/reject actions)
- First layer message configuration (granular consent/reject actions)
Vendor list configuration (granular consent/reject actions)
The granular consent/reject actions approach to the Pur model allows you to configure specific purposes or stacks as required (and therefore accepted by the end-user) as a condition of their consent. While this information is surfaced to the end-user via the privacy manager, configuring required purposes or stacks is set up in the vendor list for the property.
Navigate to the GDPR TCF vendor list associated with your property and select either a purpose or stack that must be accepted as a condition of the end-user's consent.
Note: Individual purposes not included in a stack can be set as required for consent. If a purpose is included in a stack then the requirement for consent will need to be set for the entire stack instead of the purpose.
Click the checkbox to the right of Required for Consent for the purpose or stack and click Apply Changes when finished.
Repeat as necessary for other purposes or stacks.
Purposes or stacks that are configured as required for consent will have a red asterisk beside their name in the vendor list builder. Click Save in the vendor list builder to confirm your changes.
Note: Please be aware that the required for consent setting will only apply to properties who use the PMTCFv2InlineNeutral component in their privacy managers. If your property does not use this component then the require for consent setting will be ignored.
Privacy manager configuration (granular consent/reject actions)
Customize the privacy manager for the property. Click here for more information on how to navigate the privacy manager builder.
Click the + symbol in the privacy manager builder toolbar.
Select the PMTCFv2InlineNeutral component in the subsequent modal.
The neutral consent privacy manager component will be added to your privacy manager.
The component will have individual accept and reject button for each purpose and vendor. Additionally, purposes or stacks that you have configured in the vendor list as required for consent will also be demarcated in the component.
Note: If your organization utilizes stacks in the vendor list associated with the property and have enabled the stacks feature in your privacy manager builder, the accept/reject buttons and the required for consent demarcation will appear for each stack.
Select the neutral consent privacy manager component and use the Settings panel on the right-hand rail to configure settings and style (including the colors of the accept and reject buttons, require consent icon, etc...).
Your organization will also need to add buttons to Save and Exit the privacy manager once selections are made, and to return to the first layer message.
- Click the + symbol in the privacy manager builder toolbar and select the PMButton component in the subsequent modal.
- Select the newly added button and use the Settings panel on the right-hand rail to edit the Content, Style, and Action for each button.
| Button | Action |
| Save & Exit | Save & Exit |
| Return/Go Back | Cancel |
Repeat as necessary for other buttons in your privacy manager.
The Save and Exit button you create is inactive/non-clickable (indicated by the button's opacity) until the end-user makes a selection for each accept/reject action. Once all necessary selections are made the button will be active/clickable.
Note: The opacity for an inactive/non-clickable Save and Exit button is not configurable.
First layer message configuration (granular consent/reject actions)
In order to fulfill the conditions of a Pur model experience, your organization will need to give end-users the option to provide some other monetary alternative and not give consent. There are two methods by which you can create a button that provides this option:
- Custom JavaScript
- Redirect (will open redirected page in new browser tab)
Either method can send your end-user to your shop, subscription URL, payment provider, etc...
Note: If the end-user has elected to pay instead of providing consent, your organization will need to "mark" the end-user in your system so that it is noted that the end-user has subscribed.
Create a button in your first layer message that end-users will use to subscribe to your service. Once created, select the button and navigate to the Settings panel on the right-hand panel.
Expand the Action accordion and select Custom JavaScript from the Choice Option dropdown menu.
Use the provided space to input your organization's javascript to allow end-users to pay money instead of providing consent.
Note: The Redirect action will open the input URL in a new browser tab. Please utilize the Custom JavaScript action if this behavior is not desired.
Create a button in your first layer message that end-users will use to subscribe to your service. Once created, select the button and navigate to the Settings panel on the right-hand panel.
Expand the Action accordion and select Redirect from the Choice Option dropdown menu.
Use the provided space to input your organization's URL to allow end-users to pay money instead of providing consent. The URL will open in a new browser tab.
Comments
0 comments