Omeda Client Knowledge Base

Using Omeda Cookies with a Consent Management Platform

Knowledge Base Home

When using a third-party consent management platform (CMP), such as OneTrust or CookiePro, it is important to consider how Omeda’s cookies should be categorized based on the functionality they support.

The following Omeda cookies should be configured within your CMP:

  • oly_enc_id

  • oly_anon_id

  • oly_fire_id

oly_enc_id and oly_anon_id

The oly_enc_id and oly_anon_id cookies are required to support Omeda CDP functionality on your website. These cookies allow Omeda to identify site visitors and support experiences that depend on that identification.

If these cookies are blocked, some Omeda functionality may no longer work as expected, including:

  • Personalizations

  • Meter Messages

  • Certain login-related functionality

When determining how to categorize these cookies within your CMP, consider whether visitors should be permitted to disable them and the impact doing so may have on these site experiences.

oly_fire_id

The oly_fire_id cookie is used as part of Olytics behavioral tracking. It allows page visits and other tracked activity to be associated with a site visitor so that their behavior can be understood and used within Omeda.

If the oly_fire_id cookie or the olytics.fire script is blocked, page activity will not be associated with that visitor.

This may also affect Meter functionality. If Olytics behavioral criteria are used to target or exclude audiences from a Meter, both the oly_fire_id cookie and the olytics.fire script must be allowed for that targeting to work correctly.

The appropriate category for each cookie will depend on your organization’s consent policies and implementation. When configuring Omeda cookies in your CMP, consider both the purpose of each cookie and the Omeda functionality that will be unavailable if a visitor chooses to block it.

Table of Contents