MarfeelPass CMP notice integrates with the webpage underlying configured CMP. It replaces the UI notice popup from your CMP and delegates to it the consent management using generic TCF or vendor specific APIs.
Learn more on:
- When does MarfeelPass CMP notice show?
- What does MarfeelPass do when a user accepts the consent?
- What does MarfeelPass do when a user pays to reject the consent?
- What happens when a user rejects some specific purposes
- Where does MarfeelPass get information about vendors?
- How do MarfeelPass previews work?
When does MarfeelPass CMP notice show?
MarfeelPass CMP notice shows in two scenarios:
- When the standard TCF API notifies that there’s no valid consent string for the user. The most common situations are that GDPR applies and TC data is not present or needs renewal:
window.__tcfapi?.('ping', TCF_VERSION, ({ displayStatus }: PingData) => cb(displayStatus !== 'disabled'));
- When the user selectively rejects any of the Purposes 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 or 11 as defined on Appendix A: Definitions Of Purposes, Features And Categories Of Data of IAB Europe Transparency & Consent Framework Policies. When the user revokes the consent through any of the mechanisms provided by the publisher Marfeel will show the CMP notice based on standard TCF events for
tcloadedanduseractioncomplete
What does MarfeelPass do when a user accepts the consent?
When a user clicks on an Accept button defined by the mrf:userAgreeToAll role element, MarfeelPass invokes a vendor specific method:
- Didomi
Didomi.setUserAgreeToAll()
What does MarfeelPass do when a user pays to reject the consent?
When a user clicks on a Pay & Reject button defined by the mrf:userPayToReject role element, MarfeelPass executes the payment flow and invokes a CMP vendor specific method:
- Didomi
Didomi.setUserDisagreeToAll()
What happens when a user rejects some specific purposes
Where does MarfeelPass get information about vendors?
MarfeelPass displays the number of vendors on elements configured with the mrf:numRequiredVendors role element and opens the configuration screen based on:
- Didomi
Didomi.getRequiredVendors()Didomi.preferences.show('vendors')
Why do positive consent rates on Didomi drop when activating MarfeelPass?
When activating MarfeelPass on the Didomi platform, you might notice a decrease in your positive consent rate. This is because Didomi’s interface is designed to work with the default consent notice and doesn’t integrate analytics of custom notices.
The perceived drop in positive consent rates might be alarming, but it’s a tracking issue, not a decrease in user engagement.
Didomi tracks consent through its pre-built templates. However, custom CMP like MarfeelPass introduces different user journeys that can bypass Didomi’s tracking methods, causing them to display inaccurate statistics.
MarfeelPass triggers eventStatus = cmpuishown __tcf events that Didomi doesn’t track as type:consent.asked on https://api.privacy-center.org/v1/events.