Extended User IDs (EIDs)

What are Extended User IDs (EIDs)?

EIDs are privacy‑safe user identifiers provided by approved identity partners (ex. Liveramp, ID5) to help improve ad addressability when user consent is present.

The Dailymotion Player can automatically detect, read and forward EIDs that already exist in your site or app to eligible ad requests.

Here more details how EIDs are sent in OpenRTB 2.6 - Object: EID.


EIDs prerequisit

  • Ensure EIDs are already present on your page or app (for example via your identity partners or the Prebid User ID module).
  • The Player reads existing EIDs and propagates them to monetization.
  • Activate EIDs in Studio. If you don’t see the toggle, contact Dailymotion Support.
  • Confirm that the EIDs you use are supported by the Dailymotion Player (see the compatibility table below).
  • Verify user consent. The Player forwards EIDs only when your CMP indicates valid consent for the relevant vendors in alignment with IAB TCF, IAB GPP and applicable regulations.

How it works

After you activate EIDs in Studio, the Player detects EIDs already present on your site or app (for example, from your identity partners or the Prebid User ID module).

📘

Consent matters

Make sure your CMP (Consent Management Platform) gives the right signals for each vendor.
Without valid consent, EIDs may not be passed to the Player.

When your CMP indicates valid user consent for the relevant vendors, the Player forwards EIDs in eligible ad requests. No additional Player‑side integration is required.


EIDs compatibility with Dailymotion player

Support varies by EID and integration method.

EIDsWebAppsStorage key
Criteo ID✅❌cto_bundle (Cookie or LocalStorage)
cto_bidid (Cookie or LocalStorage)
EUID✅❌__euid_advertising_token
(1P Cookie or LocalStorage)
First-ID✅❌firstid (1P Cookie)
ID5✅❌id5id
(1P Cookie or LocalStorage)
LiveRamp ATS✅❌_lr_env (Cookie)
UID2✅❌__uid2_advertising_token
(1P Cookie or LocalStorage)
Utiq✅❌utiq_openrtb_eids (LocalStorage)
📘

Understand “Storage key"

The storage key is the cookie name or localStorage key where the Player expects to find each EID. Make sure your identity partner is correctly writing this value to your users' browsers before the Player initialises.


Demand support

Demand typeSupported
OpenRTB 2.5✅
GAM via Secure Signals❌

Did this page help you?