> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/activate/audiences/anonymous-audiences.md). # Anonymous audiences ## Overview As is often the case in audience generation and identification, customer identifying details can be limited. Customer attributes like email address, phone number or User ID are easy to retrieve for customers who have *already* transacted, but not as easy to pull for *anonymous* customers that have yet to be identified. Chord's "blended user ID", along with a few additional configuration steps, helps to solve this and allows for audience building of yet to be identified customers. ### Example audience using Chord blended ID ![](https://2938842758-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5Oy2IAsu7IvAGAlWgC36%2Fuploads%2Fgit-blob-9927eb4737d3b06c161db8920315cf8df159b67c%2Fanonymous-audiences-1.png?alt=media) ### Example audience using user ID & email ![](https://2938842758-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5Oy2IAsu7IvAGAlWgC36%2Fuploads%2Fgit-blob-48cb97d2a01f313d7daa17d7fff333e4bc12688d%2Fanonymous-audiences-2.png?alt=media) As [mentioned here](/reference/apis/audiences-api.md#Yrz_M), some audiences may contain what Chord calls a “blended user ID,” which is derived from the Chord data models to contain the **CDP User ID** - if one exists - else the **Anonymous ID**. This use case is particularly useful when mixing users that may or may not have a known CDP User ID; by using the CDP Blended User ID, audiences can be created for both users and visitors using the same ID. {% hint style="info" %} **Note:** Pre-built audiences like `At-Risk Customers`, `Brand Champions` and `Product Loyalists` are examples of audiences containing user-specific identifiable properties like user name, user ID and user email (which is a property that can be used downstream in most configured data activation destinations to identify and link customer activity). Should you have any questions, please reach out to . {% endhint %} ## How to pass along blended ID For anonymous/unidentified audiences to be effectively used, \***Chord's blended user ID** \*must be sent downstream to all relevant destinations where the audience is to be activated. This passage requires that the Data Activation destination has a ***corresponding destination configured within Chord CDP.*** In other words, if you are looking to leverage blended IDs in audiences activated to downstream destinations, you **must** configure the corresponding pixel and/or device mode destination in the Chord CDP which is receiving events from a front-end source. {% hint style="info" %} **Note:** Pixel and device mode destinations in the Chord CDP typically reflect destinations receiving events from your store *front-end*. **Examples include:** * Facebook Pixel * Google Analytics (Device Mode) * TikTok Pixel Should you have any questions, please reach out to . {% endhint %} ## Examples ### Facebook Ads To help better connect unidentified audiences in your Facebook Ads accounts with their corresponding front-end user events and behavior, it is recommended that the ***Facebook Pixel*** destination be configured in Chord CDP to receive front-end events from your storefront: ![](https://2938842758-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5Oy2IAsu7IvAGAlWgC36%2Fuploads%2Fgit-blob-880c29ae3587a4c94a10418f2f919b4c7658bde9%2Fanonymous-audiences-3.gif?alt=media) Configuring the Facebook Pixel destination in Chord CDP will help facilitate flow of user-specific identifiers downstream into your configured Facebook Ads account (via [Chord Data Activations](/activate/data-activations/data-activations.md)). [Facebook's customer information parameters](https://developers.facebook.com/docs/marketing-api/conversions-api/parameters/customer-information-parameters) define which attributes can be sent and in which format they are required. The more customer information parameters passed along, the higher likelihood of profile match and identification. ### TikTok Ads To help better connect unidentified audiences in your TikTok Ads accounts with their corresponding front-end user events and behavior, it is recommended that the \***TikTok Pixel** \*destination be configured in Chord CDP to receive front-end events from your storefront: ![](https://2938842758-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5Oy2IAsu7IvAGAlWgC36%2Fuploads%2Fgit-blob-9d91cb0d3437ddeff1aa2dc17cdd0b83de4c705f%2Fanonymous-audiences-4.gif?alt=media) Configuring the TikTok Pixel destination in Chord CDP will facilitate flow of [event-specific attributes ](https://ads.tiktok.com/help/article/how-to-set-up-matching-events-with-events-api?lang=en)like Click ID, Email and Phone, and External ID. This ***External ID*** is mapped to the "blended User ID" captured on the Chord side. Events with an included external ID will increase match rates for improved measurement and audience creation downstream in TikTok Ads. ### Google Ads To help better connect unidentified audiences in your Google Ads accounts with their corresponding front-end user events and behavior, it is recommended that the \***Google Analytics (Device Mode)** \*destination be configured in Chord CDP to receive front-end events from your storefront: ![](https://2938842758-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5Oy2IAsu7IvAGAlWgC36%2Fuploads%2Fgit-blob-bb58f9d8871fbdebd8eb9fe3578e758e337a8021%2Fanonymous-audiences-5.gif?alt=media) Similar to the destinations above, configuring the Google Analytics (Device Mode) destination in Chord CDP allows for passage of client-side user-specific attributes that can aid in user identification downstream in Google Ads. When the destination is configured, [Google Analytic's user\_id](https://developers.google.com/analytics/devguides/collection/ga4/user-id?client_type=gtag) value will be collected (if available) in the storefront and sent through to Google to be used as another attribute for matching purposes. {% hint style="info" %} **Note:** As always, please reach out to for assistance. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.chord.co/activate/audiences/anonymous-audiences.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.