Yes, MarfeelPass’s no-code notice and custom notice can coexist. The no-code notice is a quick and easy solution for implementing a standard consent notice. If you wish to add a custom touch or tailor the notice further, you can integrate a custom notice alongside the no-code solution.
Once you enable a the experience and disable Didomi’s consent layer, the no-code notice won’t be applied, and only the custom notice will be visible.
Yes, if you have multiple subdomains, you’ll need to upload the merchant file to each of them individually.
In the MarfeelPass setup process, specifically in the Didomi integration step, you have the option to specify your preferred reject duration. For instance, if you want to switch from 24 hours to 7 days, you can make the adjustment by changing the code from:
window.didomiConfig.app.deniedConsentDuration = 86400;
window.didomiConfig.app.deniedConsentDuration = 604800;
Yes, you can customize the text of your CMP notice from the MarfeelPass experience details. This allows you to set it in any language preferred.
Absolutely. You can create separate CMP notices tailored to different languages. Indicate the preferred language within the notice settings, and ensure the pre-targeting language matches the one you’ve set in the text customization.
The system can base this decision on the language settings of the user’s browser or the html language of the webpage being viewed. Make sure your pre-targeting settings align with the languages you have chosen for your varying CMP notices.
You can modify both the HTML and CSS of the MarfeelPass notice, as well as the custom fields to include specific information. Follow these steps to create a custom layout.
Yes, you can conduct AB tests using custom experiment variables as pre-targeting and showing different notices to each variant group.
- Add a new Experiment group on Experiences Settings
- Create 2 MarfeelPass experiences
- Use the newly created experiment group as a pre-targeting condition on each experience. One with value
1and the other with value
No, users do not need to repeat the consent process. MarfeelPass ensures consistent user consent behavior by seamlessly connecting with Didomi in the AMP environment. When users return to the web, MarfeelPass maintains the same consent status, providing a seamless and continuous experience. Additional details on MarfeelPass integration with CMPs can be found here.
You can modify the size and position as needed in the amp-consent configuration:
This adjustment is made following the AMP documentation on consent position, available at: AMP User Consent Modal UI.
initialHeightis a string that represents the viewport height that the iframe should take. A viewport height between 30 and 60, inclusive, will tell amp-consent to style the iframe in a bottom sheet. A viewport height greater than 60 and less than or equal to 80 will tell amp-consent to style the iframe as a centered modal.
Yes, MarfeelPass offers two convenient ways to preview your changes before activating them on your website:
- You can see the preview in Experience Manage. Bear in mind the inline preview is loaded via the
playground.mrf.ioproxy. The proxy makes possible loading your content in an iframe, changing relative paths to absolute. There can be certain cases where the preview is not accurate.
- You can Open the previewed url directly on your browser clicking on
Preview in browser. It will adds
#mrfdebug=followed by the ID of the MarfeelPass you want to see to the url.