ÃÛ¶¹ÊÓƵ

Documentation

AEP - RT-CDP activation (LinkedIn, Google Customer Match, Facebook) - Supported identities and what to send

Last update: Thu Sep 05 2024 00:00:00 GMT+0000 (Coordinated Universal Time)

This article discusses the combination of identities you can send for the documentation pages below. You can send one or more of the following identities to the respective destinations: LinkedIn, Google Customer Match, and Facebook.

Description description

Environment

ÃÛ¶¹ÊÓƵ Experience Platform (AEP)

Issue

Learn about while the documentation pages below list support identities per integration, whether you have to send all identities, a combination of them, or just a single one.

  1. LinkedIn Matched Audiences Connection

    • GAID
    • IDFA
    • Hashed Email

  2. Google Customer Matched Connection

    • GAID
    • IDFA
    • Hashed phone
    • Hashed email
    • User ID

  3. Facebook Connection

    • GAID
    • IDFA
    • Hashed phone
    • Hashed email
    • Extern ID

Resolution resolution

You can send one or more of the above identities to the respective destinations.
For example, you can only send GAIDs and IDFAs to activate these destinations (in other terms, hashed email or phone isn’t necessarily required if you send GAIDs and IDFAs.

NB: known (hashed) identifiers might achieve a better match rate since the typical use case is Audience targeting for known audiences on social and advertising destinations.

See more information at Activation to social and advertising destinations from RTCDP.

recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f