📘

This integration requires activation of additional services. Contact your MetaRouter representative for assistance.

What is CEEId?

CEEId is a privacy-focused identity solution designed to generate pseudonymous user identifiers from consented first-party data. It enables advertisers and publishers to create durable, privacy-compliant identifiers based on hashed email or phone inputs. The service validates user consent using IAB TCF standards before issuing an identifier, ensuring compliance with European privacy frameworks. CEEId is commonly used to support addressability, audience matching, and attribution in cookieless environments.

Product Type: Advertising

Integration Type: Starter Kit & ID Sync

Capabilities

• Captures hashed email or phone identifiers from identify() traits and sends them to CEEId’s API to generate an encrypted identifier.
• Stores the returned identifier in first-party storage for use in downstream event enrichment.
• Validates user consent via IAB TCF v2 before generating an identifier.
• Supports identity enrichment within the Wirtualna Polska Starter Kit by providing an additional identifier for downstream matching and activation.

Considerations

• Important Activation Details: This integration requires activation of additional MetaRouter services to enable the identity sync functionality. For assistance activating these services, please contact your MetaRouter representative.
  • The CEEId API key is managed and configured by MetaRouter and is not user-configurable within the UI.
• The sync reads the IAB TCF v2 consent string and requires vendor ID 676 to be consented for successful ID generation.

Sync Details

• IDs:

  • data – An encrypted identifier returned by CEEId based on hashed email or phone inputs, used for attribution and identity resolution.

• Description:

  • The sync captures hashed email or phone values from identify() traits.
  • A request is sent to CEEId’s endpoint at https://ceeid.eu/api/xid/generate.
  • The request includes a SHA-256 hex hash of the identifier and the user’s TCF consent string.
  • Each value is stored in first-party storage for the duration defined by the Cookie Lifetime (days) setting.
  • Values retrieved by this fetch-based sync refresh after the storage marker expires and can also re-trigger on identify().
  • A failure marker is stored when the request fails. This marker typically remains for 1 day, after which the sync retries.
  • The identifier is added to server-side event payloads in the Wirtualna Polska Starter Kit for attribution and targeting.

• Response Example:

{
  "value": "AABIYW4TSKC7SE7R"
}

• Server-side Event Payload:

Server-side Event Payload: Upon completion of all vendor's sync, the server-side events will incorporate all resolved identifiers as described above. The following object will be appended to the context.providers property within the event's JSON payload.

{
   "ceeId": {
     "encrypted": {
       "data": {
         "value": "AABIYW4TSKC7SE7R"
       }
     }
   }
}

• Cookie Name:
  • Cookie: _meta_ceeId_data, _meta_ceeId_data_failure
  • IndexedDB: [your storage prefix]_ceeId_data, [your storage prefix]_ceeId_data_failure
  • For a general guide on ID Sync validation, see here.

Sync Setup Guide

1. Gather Credentials

Please reached out to your CEEId representative to obtain an API token.

2. Add a CEEId Sync in MetaRouter

• Submit Integration Request Ticket
  • Submit a request through our support portal to enable enrichment services and set up your CEEId token. MetaRouter will handle the implementation of the token on your behalf. You may attach a file containing your API token securely during this step.
  • Example ticket description:
    • Ticket Name: Enable CEEId Enrichment and API Token Implementation
    • Ticket Description: Please enable enrichment services for our CEEId integration and implement our provided API token (attached).
• Add the CEEId Sync - To gather the data, you must add a CEEId sync.

1. From the Pipelines page, find the pipeline associated with the web property you’d like to add a sync to. Hover over the three dot dropdown and select “Build AJS File.”
2. In the Identity Syncs section, select the CEEId sync.
3. Fill out the following fields:
   1. MetaRouter Ingestor URL – Base domain for your MetaRouter ingestor. Exclude https:// and anything after .com. Typical format: mr.[ORGANIZATION].com.
   2. Cookie Lifetime (days) – How long a synced identifier remains in first-party storage. When expired or no longer detected, the sync will re-trigger. Example: 1.
   3. API Timeout (ms) – Maximum time the Sync Injector waits for a response from the vendor’s API. Example: 300.
4. Scroll down and click the Save and Build File button.
5. Deploy your AJS file to propagate changes to your web property.