Which cookies does Omea Consent set?

Omea Consent stores the visitor’s choice so it can be respected on every page. Nothing is stored before the visitor chooses – a missing choice simply means denied everywhere.

Cookies

Name	Purpose	Set when	Lifetime
omea_consent_state	The visitor’s choice per category, when it was made and for which banner version	After a choice	As long as a choice is valid – 180 days by default (Settings › Policies)
omea_consent_id	A random consent ID that links the browser to its record in your consent log	When a choice is logged	Same as above
wp_consent_functional, wp_consent_statistics, wp_consent_marketing	The choice shared with other plugins through the WP Consent API	When a choice is made or changed	30 days (the API’s own default)

All of them are first-party cookies, set for your site’s path / with SameSite=Lax. With One choice across subdomains on, omea_consent_state and omea_consent_id are set for the whole domain (for example .example.com) and marked Secure.

Browser storage

Key	Purpose
omeaConsent.consentState	The same choice as the cookie, kept in local storage
omeaConsent.consent.<category>, omeaConsent.hasConsented	Per-category state and the time and version of the choice

Expired or outdated choices are ignored, even if they’re still in storage.

Cookies set by Omea Consent Pro

Only if you use these Pro features:

Name	Feature	Set when
omea_age_gate_ok	Age gate – remembers that the visitor passed	After passing the age gate
omea_conv_pending	Carries a server-side conversion (such as an add-to-cart) to the next page so the ad pixels can send it	Only with Marketing consent, for 10 minutes

In your cookie policy

Omea’s own consent cookie is always listed in the cookie table, even before your first scan.