How do we set up identity resolution and entity matching within Census before syncing audience segments to our ad platforms?
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
How do we set up identity resolution and entity matching within Census before syncing audience segments to our ad platforms?
2 real searches · 1 real-search pass
Badge and edge weight = share of passes that produced the query. Hover a query for its intent and routing format.
Query classes
Google's semantic query class for every sub-query: what kind of answer each search is after, simulated vs real.
Classifying 2 queries…
Searches and sources
ChatGPT2 real searches · gpt-6
Census identity resolution entity matching audience segments ad platforms documentation Google ↗
Census reverse ETL audience sync identity matching customer data platform docs Google ↗
- Announcing Census Entities: Define business entities once to make your most important data available for everyone · get-census.webflow.io
- Computed Columns · docs.getcensus.com
- One-Click Audiences ⚡ · whatsnew.getcensus.com
- Census changelog · whatsnew.getcensus.com
- Snapchat · docs.getcensus.com
- Sync audiences from Census · docs.rokt.com
- Sync Alerts · docs.getcensus.com
Queries
2 queries · click a column to sort
| Query / type | Search | Intent | Query class | Routing format | Cluster | Freq ↓ | Weight |
|---|---|---|---|---|---|---|---|
Census identity resolution entity matching audience segments ad platforms documentation OBSERVED | Google ↗ AI Mode ↗ | — | — | — | — | 1x of 1 | |
Census reverse ETL audience sync identity matching customer data platform docs OBSERVED | Google ↗ AI Mode ↗ | — | — | — | — | 1x of 1 |