Embeddings: The Next Frontier in Advertising?
Start here — the originating essay.
WritingTopic hubReference
Vector representations are becoming the semantic infrastructure layer for agentic advertising, contextual targeting, lookalikes, clean rooms, and cross-media decisioning.
Embeddings turn words, pages, shows, ads, users, households, products, and behaviors into numerical vectors that can be compared by similarity. In advertising, that means audiences, contexts, creatives, and signals can be matched by meaning — not only by IDs, keywords, or fixed taxonomies.
Embeddings are not a privacy shortcut. They are a semantic matching layer that still needs governance, provenance, consent, evaluation, and standards.
The simplest way to understand embeddings: they turn messy real-world objects into vectors so machines can compare similarity at scale.
Seed essay Embeddings: The Next Frontier in Advertising?
By meaning document embeddings
An embedding is a vector representation of an object — text, an image, an audio signal, a user profile, a content page, a product, a show, a household behavior pattern, or a campaign. Similar objects tend to sit closer together in the embedding space, which makes similarity computable.
Embedding = meaning compressed into numbers.
A learned vector representation where distance or angle can approximate relatedness, similarity, or context — depending on the model and training objective.
Encodes the words that describe an object — a page, a brief, an audience. Strong on meaning; famously lossy on numbers, geography, and time. This is what the advertising stack runs on today.
Encodes the place and the hour themselves, learned from structural data rather than descriptions of it. Google's PDFM is the public exemplar on the spatial axis; the hour-of-week as a native coordinate is the newer frontier — now a live proposal at the W3C . The two families do not share a geometry — see the portability problem below.
Embeddings are not always interpretable dimension by dimension. They are useful because the overall geometry can preserve relationships — not because each coordinate has an obvious human label.
| Concept | Plain meaning | Advertising example |
|---|---|---|
| Vector | list of numbers | household viewing profile encoded as numbers |
| Embedding space | where vectors are compared | sports fans cluster near sports content |
| Cosine similarity | angle-based similarity | creative and page context are close |
| Centroid | average point for a group | seed-audience summary |
| Nearest neighbor | closest items | most similar audiences / contexts |
| Translation layer | maps one vector space to another | publisher vectors to buyer vectors |
They make meaning computable
A buyer can move beyond exact keywords and fixed categories into semantic relationships.
They reduce dependence on brittle IDs
Where identity is limited, embeddings can support contextual, cohort, or signal-based similarity. They do not eliminate privacy obligations.
They connect different media surfaces
Text, video, audio, CTV viewing, app behavior, commerce signals, and creative assets can be represented in comparable forms — if the system is designed properly.
They support agentic workflows
Agents need objects they can discover, compare, activate, and evaluate. Embeddings help agents reason over meaning and similarity.
They improve retrieval and recommendation
Search, ranking, content matching, creative selection, and signal discovery all benefit from vector-based retrieval.
They create new governance questions
Vectors can encode sensitive patterns, inferred traits, and behavioral signals. They need policy, retention, access control, and evaluation.
Lookalike audiences without direct ID matching
Seed a group of converters, watchers, buyers, or high-value users; represent their behavior as vectors; find similar users, contexts, or households where permitted.
Watch-out: Similarity is not consent. Validate data rights and avoid sensitive-inference risk.
Contextual targeting 3.0
Match creative, page, video, app, show, or bid context by semantic similarity rather than only keyword match.
Watch-out: Contextual does not automatically mean low-risk if the context reveals sensitive categories.
Cross-media similarity
Represent web, app, CTV, audio, commerce, and content signals in ways that support comparison across media surfaces.
Watch-out: Vector spaces may not align without common models or translation layers.
Creative-to-context matching
Embed ad creative, landing pages, product metadata, and publisher content to choose better-fit creative or environments.
Watch-out: Creative fit should be evaluated against outcome and brand safety, not just proximity.
Signal discovery
Use embeddings to search signal catalogs by meaning — a natural-language brief can retrieve related audience, content, and contextual signals.
Watch-out: Returned signals need provenance, freshness, and policy metadata.
Suppression and exclusion
Identify users, contexts, or inventory that are semantically misaligned with a campaign or likely to waste budget.
Watch-out: Wrong thresholds can suppress valuable reach or introduce bias.
Clean-room output interpretation
Compare aggregated outputs, audience descriptions, product categories, or campaign cohorts without exposing raw data.
Watch-out: Clean-room governance still applies; embeddings should not become an uncontrolled export channel.
Agentic activation
Agents can use embeddings to compare brief intent with available signals, contexts, inventory, and measurement outputs.
Watch-out: Agents still need permissions, output policy, human approval, and audit.
Embeddings can reduce raw-data movement, but they do not automatically remove privacy risk. A vector can still encode patterns about people, households, content, behavior, or sensitive interests. Whether it is personal data depends on context, identifiability, linkage risk, and how the vector is used. Under EU/UK GDPR concepts, pseudonymized data is still personal data , and anonymization requires that re-identification is no longer reasonably likely — a high, evidence-based bar.
| Claim | Better framing | Why it matters |
|---|---|---|
| Embeddings are anonymous | Embeddings may be lower-risk than raw data, but they are not anonymous by default. | They can still support inference, linkage, or profiling. |
| No IDs means no privacy issue | Privacy risk can exist without direct identifiers. | Behavioral vectors can still describe or single out people or households. |
| Vectors are safe to share | Vector sharing needs purpose limits, access control, retention rules, and re-identification-risk review. | Vectors can leak meaning or enable similarity matching across datasets. |
| Embedding equals pseudonymization | Embedding and pseudonymization are different concepts — and pseudonymized data is still personal data. | Both can still require GDPR / privacy compliance depending on context. |
| Contextual is always safe | Contextual targeting can still be sensitive when context reveals protected or sensitive categories. | Policy and brand safety still apply. |
These are EU/UK GDPR concepts applied to embeddings by analogy; regulators have not ruled on embeddings specifically. US frameworks (CCPA/CPRA) and Apple's ATT are separate regimes — embeddings do not bypass any of them.
Embeddings are powerful inside one system. They get harder when multiple companies need to exchange or compare them: a vector from one model may not mean the same thing as a vector from another. Model choice, dimensionality, training data, normalization, and distance metric all matter — embedding spaces are usually not directly fungible, so translation layers, benchmark sets, and common standards may be needed.
| Problem | What breaks | Possible solution |
|---|---|---|
| Different model | vectors do not align | shared model, adapter, projection |
| Different dimensions | cannot compare directly | transformation / projection layer |
| Different training data | semantic drift | benchmark and calibration |
| Different objectives | similarity means different things | document objective and use case |
| Different privacy rules | unsafe exchange | output policy and governance |
| Different freshness | stale vectors | timestamp and refresh policy |
| Different modality (text vs place-time) | no shared geometry — similarity is undefined across the two spaces | comparison semantics defined at the standards layer, not per-integration |
Agents need more than natural language. They need a way to compare meaning across briefs, signals, contexts, creative, inventory, and outcomes. Embeddings can become the similarity layer that lets agents reason over advertising objects.
Signal containerization packages embeddings with the missing layers: provenance, policy, activation path, allowed outputs, and evaluation logic.
Embeddings only become market infrastructure when systems agree on how they are represented, exchanged, governed, and evaluated.
Agentic Audiences / UCP
IAB Tech Lab's Agentic Audiences, formerly the User Context Protocol, defines how agents exchange identity, contextual, and reinforcement signals. It uses embeddings — officially described as dense vectors of 256–1024 dimensions . As of June 2026 it is an initial proposal / draft; validate the current version against official IAB Tech Lab documentation.
Embeddings connection embeddings as a compact signal representation
AdCP
A separate, non-IAB agentic workflow layer (over MCP): discovery, activation, status, governance, creative, and media buying. Embeddings can support signal discovery and semantic matching inside AdCP-style workflows; AdCP does not mandate embeddings.
Embeddings connection discovery, activation, status, governance
AAMP
IAB Tech Lab's broader agentic-advertising management initiative — foundations (ARTF v1.0, final August 2026), protocols (incl. Agentic Audiences), and trust — built on existing standards (OpenRTB, AdCOM, OpenDirect, Deals API).
Embeddings connection agentic protocols, trust, runtime
Signal containerization
A practical way to package embeddings with semantic meaning, provenance, policy, activation logic, and evaluation.
Embeddings connection packaging vectors with policy and activation
OpenRTB / bidstream
Embeddings may support bidstream scoring, contextual alignment, or signal enrichment — but real-time use requires latency, governance, and protocol design.
Embeddings connection potential bidstream scoring / signal extension
Clean rooms
A governed collaboration environment where vector-safe analysis and governed outputs still sit under clean-room policy.
Embeddings connection governed output and vector-safe analysis
A serious embedding program is not just a model call and a vector database. It needs data rights, model choice, storage, retrieval, governance, evaluation, and business ownership.
Source
content, behavior, CRM, campaign, CTV, app, commerce, creative, product metadata
Embedding
model, dimensionality, normalization, distance metric, version
Storage / retrieval
vector index, metadata, filters, freshness, deletion
Governance
consent, access, retention, sensitive category, output policy, audit
Activation
DSP, SSP, clean room, CDP, BI, agent, recommendation system
Evaluation
precision, recall, lift, relevance, bias, waste reduction, revenue outcome
Start here — the originating essay.
Why agents need shared representations.
How the protocols fit together.
Packaging vectors with policy + activation.
The moment has four dimensions — who, what, where, when.
The agentic workflow layer.
AAMP, ARTF, Agentic Audiences, Agent Registry.
The governed data spine.
Shared meaning across systems.
Embeddings, privacy, and agentic standards evolve quickly. Validate official documentation, standards versions, and legal guidance before implementation.
The originating essay — why vector representations matter for advertising and where they create value and risk. Supports: POV, Use cases.
Why agents need shared representations and protocols to interoperate across the advertising stack. Supports: Agentic framing.
How AdCP, UCP / Agentic Audiences, and related efforts fit together as layers. Supports: Standards map.
Packaging signals (including embeddings) with provenance, policy, activation path, and evaluation. Supports: Operating model, Governance.
The No Fluff reference page for the AdCP agentic workflow layer. Supports: Standards.
The No Fluff reference page for AAMP, ARTF, Agentic Audiences, and the Agent Registry. Supports: Standards.
An embedding is a vector of floating-point numbers; distance measures relatedness; cosine similarity for retrieval; model dimensions (e.g. 1536 / 3072) are vendor-specific and adjustable. Supports: Definition, Cosine similarity, Dimensionality.
Embedding = vector representation in a lower-dimensional space; distance interpreted as relative similarity; word embeddings often 256 / 512 / 1024 dimensions. Supports: Definition, Embedding space, Dimensionality.
A vector of floating-point numbers whose distance correlates with semantic similarity; cosine similarity often used; powers vector similarity search. Supports: Definition, Cosine similarity, Vector search.
Numerical representations of real-world objects learned via neural networks; text, image, and graph embeddings; cross-modal matching (text ↔ image). Supports: Definition, Modalities.
Embeddings learned from data; cosine / Euclidean / dot-product metrics; nearest-neighbor vector search; per-dimension features usually implicit, not human-labeled; text/image/audio + multimodal. Supports: Metrics, Vector search, Interpretability.
Pseudonymised data remains personal data and stays in scope; identifiability assessed on means reasonably likely to be used; singling-out and linkage are re-identification vectors. Supports: Pseudonymisation != anonymisation, Re-identification.
Anonymisation is not automatic and rarely zero-risk; pseudonymisation is not anonymisation; removing direct identifiers is masking only; inference of sensitive traits is possible. Supports: Anonymity bar, Overclaims to avoid.
Pseudonymised data qualifies as personal data under the GDPR; pseudonymisation mitigates risk but does not remove obligations. Supports: Pseudonymisation status.
Formerly UCP; donated by LiveRamp; encodes identity, contextual, and reinforcement signals as dense vectors officially described as 256–1024 dimensions; status is an initial proposal / draft. Supports: Agentic Audiences, Embeddings in standards.
README: "formerly the User Context Protocol"; "initial proposal"; embeddings encode identity/contextual/reinforcement signals; 256–1024 dims vs thousands of raw features. Supports: Status caution, Signal types.
AAMP umbrella across foundations (ARTF v1.0 — final, August 2026), protocols (incl. Agentic Audiences), and trust (Agent Registry), built on OpenRTB / AdCOM / OpenDirect / Deals API + taxonomies. Supports: AAMP framing, Status.
Separate, non-IAB agentic workflow layer over MCP (discovery, media buy, creative, signals activation); can use embeddings for signal discovery but does not mandate them. Supports: AdCP separation.
Graph-learned embeddings for ~28,000 US postal codes (and counties) built from aggregated search trends, busyness, weather, and air quality; benchmarked across 27 geospatial tasks (arXiv 2411.07207); embeddings publicly available. The public exemplar of spatiotemporal (place-based) embeddings, as distinct from semantic text embeddings. Supports: Two-families distinction (semantic vs spatiotemporal), Cross-space portability framing.
July 2026 proposal on the W3C private-advertising list to standardize attribution’s unit of analysis as (H3 hexagonal cell, ~460 m edges at R8) × (ISO 8601 week) × (UTC hour) — place and time as native coordinates rather than metadata; convention-level, no API change. Public marker that the spatial/hour-of-week frontier has reached a standards venue. Supports: Hour-of-week frontier status, Geo-time unit of analysis.
Platform capabilities and naming change quickly. Last validated: September 12, 2026. Check current documentation before implementation.
Embeddings become useful when they are connected to data rights, signal design, activation paths, governance, and outcome measurement. That is where the operating model matters.
Ask about the essays, frameworks, playbooks, or how to work with Evgeny.