GDPR Consent Management

Owned by Bettina Lippisch
Last updated: May 30, 2024
5 min read

Knowledge Base Home

Search the Omeda Knowledge Base

GDPR and Personalization

Building a GDPR Personalization allows you to track your site users’ consent using messages or popup modals that you create. This tool also allows you to store the consent within your database and target the audience that will see your message.  

How it works

  1. Design a personalized message for your visitors with verbiage and style of your choosing.

  2. Review and modify your message html – utilizing our olytics.consentYes() and olytics.consentNo() javascript functions (shown below).

  3. When a visitor clicks a link or button with the appropriate onclick function attached – that consent (Yes or No) is stored in your Omeda database and the message will automatically close. NOTE: to store consent the olytics.fire script must also be executed on the page.

  4. Consent is stored at the site domain level.

  5. GDPR consent messages will display according to overall priority against both regular and GDPR-type messages.

  6. Once a visitor has seen a GDPR message, they will not be shown another message for a minimum of 5 minutes.

  7. Under “Location Settings” you can choose to target or exclude visitors from countries in the European Union.

Things to consider

  1. The Consent is stored at the site domain level so you may want to create individual personalization messages for each site.

  2. GDPR consent messages will display according to overall priority against both regular and GDPR messages.

  3. After a user declines to give consent, Omeda will no longer track their site behaviors but this does not necessarily mean that any additional tools you may use to track behavior will no longer do so. We are working on enhancements to our API suite to allow you or your vendors to access this field.

Once a visitor has seen a GDPR message – they will not be shown another message for a minimum of 5 minutes.

How to find it

  1. You can find the GDPR option for Personalization under the “Administer” section of Omeda’s menu. If you don’t have permission for this, please contact your Audience Services manager.

 

image-20240425-123945.png

  1. You can also find this within the Personalization tool.

image-20240425-124011.png

Instructions to create a GDPR consent message

  1. When creating a GDPR consent message within the personalization tool, you will need to make sure the first box, “This is a GDPR Consent Message”, in the GDPR section of the tool is checked.

  1. Create or add your content. You can create and edit your message using the wysiwig editor or copy/paste your html by clicking Tools > Source Code or clicking the <> symbol.

  1. Add the olytics.consentYes() and olytics.consentNo() javascript functions to your html by clicking Tools > Source Code or clicking the <> symbol. It is best to add this to a link or button within your html.

  1. Select “Quick Test”, to confirm that your message displays the way you’d like it to.

  2. Specify whether the user must click consent yes or decline in order to close the modal.

  3. Specify whether users should not see the modal if they have already consented.

  4. Select your audience.  

    1. You can choose to target a specific audience query you’ve created in Audience Builder (OnQ).

    2. Limit your audience to exclude only EU site users or include only EU site users.

    3. Target Anonymous Visitors Only or Known Visitors Only.Or, do not select any of the above and display your consent popup to all site users.

    4. Specify how often you would like to show your message.

  5. Specify which display option you would like to use.

  6. There are a few more options available to you when targeting or displaying your content. Feel free to use these fields if you find them necessary.

  7. Set your domain restrictions. Because consent is stored on the domain level, you will want to make sure you are showing a unique personalization modal for each domain. The content can be the same, but you will set your domain here so the modal only shows on sites with that specified domain.

  8. Name your personalization and save. Make sure to test on your site to make sure your content works with the css on your site.

  1. Set the priority for your personalization by clicking the arrows in the Priority column.

  1. Activate your personalization.

Reporting and Analytics

  1. You can find a report for each GDPR Personalization in the column labeled Actions, there are several reports available:  

    1. Impressions by Day (Known Customers)

    2. Impressions by Day (Anonymous Traffic)

    3. Impressions per Url (Top 20 Shown – Known Customers)

    4. Impressions per Url (Top 20 Shown – Anonymous Traffic)

    5. Impressions per Entry Point (Top 20 Shown – Known Customers)

    6. Impressions per Entry Point (Top 20 Shown – Anonymous Traffic)

  2. In Audience Builder (OnQ), you can select all those who have seen your GDPR Personalizations under the Personalized Content Impressions skittle. Search for the name of your personalization in the field “Personalized Content Search”.

 

  1. You can select those who have consented or declined on each domain using the field labeled “GDPR Consent”.

For any other questions, please review our GDPR Overview within our Knowledge Base or contact us at privacy@omeda.com.