Link Search Menu Expand Document

PDF

Enabling External Identifiers

Demand Partners


To enable receiving an external identifier (EID) in the ad request, go to your account settings, and then select the appropriate IDs from the list:

NOTE

You can select as many EIDs you want to receive.


Supported Prebid-Based Identifiers

The Prebid-based identifiers supported by OpenX are as follows:

  • Ramp ID
  • Unified ID 1.0
  • PubCommon ID
  • Criteo ID
  • LiveIntent ID
  • ID5 Universal ID
  • BritePool
  • Parrable ID
  • Merkle ID
  • Shared ID
  • Halo ID from Audigent
  • Quantcast ID
  • Intent IQ ID
  • Verizon Media Connect ID
  • Lotame Panorama ID
  • Fabrick ID by Neustar
  • NetID
  • ZeoTap ID+
  • IDx
  • Tapad ID
  • LiveRamp Envelope
  • Unified ID 2.0
  • Floc ID
  • Admixer ID
  • DeepIntent ID
  • DMD ID
  • Nextroll ID
  • Novatiq Snowflake ID
  • MediaWallah OpenLink ID
  • Akamai DAP ID
  • AMX ID

Traffic Filtering with External Identifiers

There are several options you can utilize to filter the traffic with EIDs.

  1. In your account settings, select the appropriate EIDs available on the list.

  2. In the traffic set Select Audience section, select Matched Users from the list.

    NOTE

    If you don’t need to filter the traffic based on user data regardless of synced cookies or received EIDs, do not add Matched Users.

  3. Select a Matched Users = option as needed:

    Matched Users = {option}Description
    Matched UsersAllows to filter the traffic to receive only cookie synced users or with the user’s identity EIDs.

    Users Matched by Cookie OnlyAllows to filter the traffic to receive only cookie synced users. Requests with EIDs and cookie synced users are filtered out.

    Users Matched by EIDs OnlyAllows to filter the traffic to receive only ad requests with EIDs. Requests with EIDs and cookie synced users are filtered out.

    You can select a subset of account EIDs to be used for traffic filtering.

    Unmatched UsersAllows to filter the traffic to receive only ad requests without EIDs and cookie synced users.


Use Cases

The following are some use cases on how to filter traffic.

You want toDo thisResult
Get traffic with cookie-matched users only.1. If the cookie-matched users setting in the traffic set is Off, enable the setting.

2. Select Users Matched by Cookie Only.

Note: There is no need to perform any EIDs configuration.
Traffic with cookie-matched users only.
Get all the traffic but enriched with the EIDs of your choice.1. Go to the account level and select the appropriate EIDs.

2. If the cookie-matched users setting in the traffic set is On, disable the setting.
All the traffic:
   • Cookie matched users
   • Unmatched users
   • Unmatched users with selected EIDs
Get unmatched traffic with Unified ID.1. Go to the account settings and select Unified ID from the list. If there are other EIDs selected but you only need to filter requests with Unified ID, make sure Unified ID is on the list and then proceed to the next step.

2. If the cookie-matched users setting in the traffic set is Off, enable the setting.

3. Select Users Matched by EIDs Only. If you don’t want to filter requests with EIDs set on the account level other than Unified ID, select only Unified ID from the list.
Traffic with unmatched users with selected EIDs.

For more about traffic sets, see Creating Traffic Sets.