Search the Omeda Knowledge Base
Consent Management Overview
Omeda’s Consent Management Platform builds on functionality from our existing CDP products, Olytics and Personalization, to deliver Consent Management to your audience. This tool provides your users with the ability to decline or accept cookies on your site, as well as the information they need to make an informed decision. The cookie descriptions, categories, and opt-out settings are all customizable so your Consent Manager best describes your cookie usage to your audience.
Configuring a Consent Manager
To begin creating a new Consent Manager for your site domain, you’ll first need to navigate to the Consent Management portal. You can do this by selecting ‘Integrations’ in the menu under ‘Activate’.
Note: You need permission for the Consent Management widget to appear on your Integrations page. Reach out to your Omeda representative if you need assistance.
Within the Consent Management portal, you can add a new site domain or select the desired domain from the Sites table.
After your site domain has been added, click ‘View Consent Manager’ to begin configuring the Consent Manager for your site.
There are six sections available within the Consent Manager as you configure your site domain.
- Cookie Management
- Cookie Blocking Settings
- Design Your Consent Manager Modal
- Build Your Personalization
- Stand Alone Usage
Within the General tab, you can review the status of the Consent Manager as well as how the Consent Manager will be made available to your site users. In most cases, the Consent Manager will be made available through the Personalization set up in the ‘Build Your Personalization’ tab, but for some use cases, a stand alone Personalization or another banner may deliver the Consent Manager modal.
You can also review the Cookie Blocking Settings for the Consent Manager.
The General tab is also where you will ‘Activate’ your Consent Manager after it has been configured.
Within the Cookie Management tab, you can scan your site for cookies and categorize them appropriately. The category you assign here will be used to describe the purpose of each cookie within the Consent Manager modal. If the category is not required, the user will be able to opt out of the category from the modal.
The steps below describe how this tab can be used to configure the cookies that will be displayed within the Consent Manager.
- Click ‘Scan My Site’, provide a URL for your site, and click Save and Scan to begin the cookie scan. It may take a couple minutes to scan your site for first and third party cookies. When the scan is complete, another modal will popup containing the number of new and previously scanned cookies found on your site. You may want to scan multiple URLs from your site to ensure that the cookies used across your domain are found.
- You can also manually add a cookie by clicking, ‘Add a Cookie’. A modal will appear for you to provide the necessary cookie information.
- Each cookie will now be listed in the table below. In the column to the far right, ‘Omeda Information’, suggested Company and Category values for your cookies may be listed. This information is available via Omeda’s Cookie Library which stores suggested Companies and Categories for frequently used cookies. To assign the suggested values, click ‘Assign Using Omeda Information’.
- To assign Categories and Companies for the remaining cookies, click the cookie name. Here you can select from the available Cookie Categories and Source Companies. If necessary, you can also edit the other cookie values that were populated during the scan or delete cookies.
- If a cookie’s company has not been created, add the company by clicking Manage Source Companies. The company name, description, and url will be available to site users when the review the cookie details from the Consent Manager modal.
- If you’d like to create a custom category for your cookies, click the Manage Categories button. The category name and description will display within the Consent Manager modal.
- NOTE: Your users will opt out of the cookie Categories, not individual cookies. For this reason, all cookies created by the same script, should have the same Category applied.
Cookie Blocking Settings
In the ‘Cookie Blocking Settings’ tab, you can specify the desired blocking functionality for users based on their IP address location.
By default, all users will be blocked after opt out. This setting can be changed by selecting the alternate option, “Cookies Blocked until Opt In” from the drop-down in the Blocking Behavior column.
You can also add a new User Group by location in the drop down at the top of the screen then set the desired blocking behavior for this User Group.
Design Your Consent Manager Modal
In the ‘Design Your Consent Manager Modal’ tab, you can provide the text and primary color that should be used when the modal displays. The following fields are available
- Title: the text provided here will display as the Title of the modal
- Footer: the text provided here will display at the bottom of the modal.
- Primary Color: the color provided here will be used for the Title, Category and Cookie names, and buttons.
After editing, you can click ‘Save and Quick Test’ to preview the modal or ‘Save and Test on My Site’ to preview how the modal will display on your site.
Build Your Personalization
Within the ‘Build Your Personalization’ tab, you can configure the pop up bar that will display on your site and will be used to launch the Consent Manager modal. The following settings are available:
- Top Bar / Bottom Bar: choose where you’d like the popup bar to display.
- Is Persistent: choose whether the bar should continue to display as the user navigates across the page.
- Display Frequency – Known Preferences: choose how frequently the pop up bar should display after a user has provided their Consent Management preferences.
- Display Frequency – Unknown Preferences: choose how frequently the pop up bar should display for users who have not provided any preferences.
- Text Color: provide the color that should be used for the text within the pop up.
- Background Color: provide the color that should be used for the background of the pop up.
- ‘Manage Preferences’ Text: provide the text for the button that launches the Consent Management modal.
- ‘Accept All’ Text: provide the text for the button which accepts all cookies.
- ‘Decline All’ Text: provide the text for the button which declines all cookies.
- Button Color: provide the color that should be used for the buttons in the popup.
- Button Text Color: provide the color that should be used for the button text in the popup.
- Button Inline: if this field is checked, buttons will display beside the popup text. If unchecked, buttons will display underneath the popup text.
- Consent Message: provide the text that should display on the popup.
To save your changes, click ‘Save and Enable’. After enabling, this popup will display for activated Consent Managers. Your popup can be previewed by clicking, ‘Generate and Test’ or ‘Save and Test on My Site’.
If you are using another method to launch the modal like a stand alone personalization job. You can disable the personalization within this tab and use the stand alone script provided in the next tab.
Stand Alone Usage
Activating and Implementing a Consent Manager
After you have finished configuring your Consent Manager, navigate to the ‘General’ tab and click ‘Activate’. If you are using the provided Personalization popup, it will now begin displaying on all sites within your domain that have our Olytics script implemented.
The Consent Manager will now begin collecting preferences from your users but will not block declined cookie categories until implementation is completed on your sites.
Each cookie script tag will need to be modified so that it contains the Category Attribute and Value snippet for the specified category and the script type is set to”text/plain”. For example, if your site contains the _fbp cookie from Facebook, your script will need to be edited to look like the below example:
For more examples of how frequently used cookies will need to be modified, read our article here.
Blocking Cookies via Google Tag Manager
To block cookies using Google Tag Manager (GTM), you’ll first need to create a trigger in GTM for each category that you’ve allowed users to opt out of.
- In your workspace for the domain, click ‘Triggers’ and ‘New’ to create a new trigger.
- Select ‘Custom Event’ as your Trigger Type.
- In the Event Name field, provide the Category Attribute and Value from the Cookie Management tab within your Omeda Consent Manager. The trigger should fire on Some Custom Events.
- In the fields that appear, the Event should equal the Category Attribute and Value.
- Provide a name for your trigger and Save.
After creating a trigger for each Category, you will need to identify the Tags that fire each cookie script within the category. These triggers for each category will need to be added to your Tags.
- Navigate to the Tags section within GTM.
- Select the Tag and, in the Triggering section, click the + icon and select the trigger for the appropriate category.
- Click Save.
After applying the triggers to the necessary Tags, be sure to submit the changes to your workspace.
When this method is implemented and the Consent Manager is active, Omeda’s Consent Manager will fire an action to trigger the tags for cookies whose categories have not been declined.
Testing your GTM Triggers
After your triggers have been added to your GTM tags, you can use the the GTM preview functionality to test that your triggers are firing appropriately. Using a URL from the domain you are looking to test, click Preview from the Tag section of GTM.
In Omeda, you can use the Save and Test on My Site button to view the Personalization and modal. Use the link generated by the GTM preview. It should look something like this, https://yourdomain.com/article/?gtm_debug=x.
Omeda will generate a test link for you which you can use to test the blocking and triggering behavior after accepting and declining different categories.
You may need to reconnect the GTM debugger after the test link is generated by clicking ‘reconnect’ from the GTM popup. Once this is done, you should see the cookie, __TAG_ASSISTANT, in your browser. Before each test it is best to start fresh by deleting all cookies except the __TAG_ASSISTANT cookie. This way you can be sure the cookies are firing as expected without any lingering cookie values.
Note: if a category is declined, Omeda will no longer fire the the trigger for the category, however it will not delete the cookie value. This means to test that a declined cookie script no longer fires, you will need to delete the cookie and refresh the page. The cookie should no longer appear on reload.