AdTech & Programmatic

Cookie Matching & User Sync

No cookie matching yet? We configure the backends and databases and build the applications you need to run cookie matching on your side — so your partners can recognize users and bid on your traffic.

Capabilities

What we deliver

Sync Endpoints

Pixel and redirect endpoints that exchange user IDs with SSPs, DSPs and exchanges, with partner-specific macros and redirects.

Match Tables & Storage

Fast key-value storage for ID pairs with TTLs and eviction, sized for your traffic — plus a warehouse for analytics.

Bid Request Enrichment

Matched partner IDs added to OpenRTB bid requests (user.buyeruid, user.ext.eids) and Prebid user sync configuration.

Consent & Monitoring

TCF and GPP consent handling, opt-outs, match-rate dashboards per partner and alerts when a sync breaks.

Business outcomes

Engineering tied to measurable results

Revenue

Higher bid rates

Demand partners recognize more of your users, so they bid more often and at better prices.

Control

Your own ID layer

Match tables and sync logic run on your infrastructure, under your rules and retention.

Operations

Visible match rates

Per-partner match rates and sync health instead of guesswork.

Delivery

From discovery to production

Discover

Clarify business goals, traffic, partners, constraints and success metrics.

Design

Define architecture, interfaces, data flows, rollout and observability.

Build

Implement incrementally with integration and load testing.

Operate

Launch, monitor, optimize and transfer production knowledge.

Overview

Cookie matching when you do not have it yet

In programmatic advertising every platform identifies a user with its own ID. Cookie matching (cookie sync, user sync) links these IDs so a DSP can recognize the user behind your bid request. Without it, partners see anonymous traffic and bid less often or not at all.

If you have no cookie matching, we set it up end to end: sync endpoints, the database for match tables, the services that read and write them, and the changes in your bid requests. We work on SSP, DSP and publisher sides and connect to your existing ad server, Prebid or OpenRTB stack.

What we set up

  • User sync endpoints and partner redirect chains
  • ID match tables in a fast key-value store with TTLs
  • Bid request enrichment: buyeruid and extended IDs (eids)
  • Prebid.js and Prebid Server user sync configuration
  • Consent handling: TCF, GPP, opt-out
  • Match-rate reporting per partner and sync monitoring

Set Up Cookie Matching →

FAQ

Frequently asked questions

What is cookie matching?

Cookie matching, also called cookie sync or user sync, links the user IDs that different ad platforms assign to the same browser. After a sync, a DSP can recognize the user behind an SSP's bid request and use its own data to decide on the bid.

We do not have cookie matching. What do we need?

Sync endpoints that exchange IDs with partners, a database to store the ID pairs, services that read them at auction time and add them to bid requests, and consent handling. We configure the backends and databases and build these applications for you.

Where do matched IDs go in the bid request?

In OpenRTB the partner's own ID is usually sent in user.buyeruid, and additional IDs in user.ext.eids or user.eids depending on the protocol version and partner requirements.

Which database do you use for match tables?

A fast key-value store with TTLs for real-time lookups, for example Redis or Aerospike, sized to your traffic, and optionally a warehouse such as ClickHouse for match-rate analytics. We choose based on volume, latency and your existing stack.

How do you handle privacy and consent?

Syncs run only when consent allows it: we read TCF and GPP signals, respect opt-outs and keep IDs only for the agreed retention period.

Does cookie matching still matter as third-party cookies decline?

Yes, where third-party cookies are still available it remains a key revenue driver. In parallel we can add first-party and universal ID solutions so matching keeps working in environments without third-party cookies.

Have an AdTech challenge?

Tell us what needs to work better

Share your current architecture, integration problem or growth target. We will suggest a practical next step.