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 example audience using user id & email as mentioned here , s ome 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; b y using the cdp blended user id, audiences can be created for both users and visitors using the same id 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 help\@chord co 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 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 help\@chord co 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 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 ) facebook's 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 configuring the tiktok pixel destination in chord cdp will facilitate flow of event specific attributes 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 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 value will be collected (if available) in the storefront and sent through to google to be used as another attribute for matching purposes note as always, please reach out to help\@chord co for assistance