Activation to social and advertising destinations from RTCDP

Configure Identity Namespaces to be used in Profile data sources.

• Use out of the box namespaces such as Email, Email SHA256 Hash, where available.
• Facebook has a list of supported identities. In order to activate to Facebook custom audiences, one of the supported identities must be present in the profiles to be activated.
• The following identities are currently supported by Facebook: GAID, IDFA, phone_sha256, email_lc_sha256, extern_id.
• For additional details see the Facebook Destination Guide.
• Google Customer Match has a list of supported identities. In order to activate to Google Customer Match, one of the supported identities must be present in the profiles to be activated.
• The following identities are currently supported by Google Customer Match: GAID, IDFA, phone_sha256_e.164, email_lc_sha256, user_id.
• For additional details see the Google Customer Match Destination Guide.
• Create custom namespaces where out of the box namespaces are not available for the applicable identities.

Configure Profile data source schemas and datasets.

• Create Profile Record schemas for all profile record source data.

  • Specify the primary identity and secondary identities for each schema.
  • Enable the schema for profile ingestion.

• Create Profile Record datasets for all profile record source data, assigning the associated schema.

  • Enable the dataset for profile ingestion.

• Create Profile Experience Event schemas for all profile time series based source data.

  • Specify the primary identity and secondary identities for the schema.

• Enable the schema for profile ingestion.

• Create Profile Experience Event datasets for all profile experience event source data, assigning the associated schema.

  • Enable the dataset for profile ingestion.

Ingest the source data using a source connector into the associated dataset configured above.

• Configure the source connector account with credentials.

• Configure a dataflow to ingest the data from the source file or folder location at a specified schedule to the specified dataset.

• Map any fields from the source data to the target schema.

• Transform any fields to the correct format for ingestion into Experience Platform.

  • Date transformations
  • Transform to lowercase where appropriate - such as email address
  • Pattern transformations (phone number for example)
  • Add unique records IDs for experience event records if not present in the source data.
  • Transform arrays and map type fields to ensure correct mapping and modeling of arrays and maps for segmentation in Experience Platform.

Configure the Profile Merge Policy to ensure the correct configuration of the identity graph and which datasets should be included in the merging of profiles.

After dataflows have executed, ensure the profile data ingestion was successful with no errors.

• Inspect the identity graph of several profiles to ensure correct processing of identity relationships.
• Inspect the attributes and events of several profile to ensure correct ingestion of attributes and events to the profiles.

Author segments to create profile audiences

• Build segments in the segment builder using rules against attributes and events.
• Save the segment for evaluation. Segments will evaluate at the specified schedule once a day.
  • If the segment rules are eligible for streaming segmentation the segment will be evaluated as new streaming data is ingested for the profiles. Streaming segments will also be evaluated once per day during the scheduled batch segmentation.

Ensure the segment results are as expected.

• Review the segment results count for the given segments.
• Investigate the profile that should be included in the segment to verify the segment membership is included in the segment membership portion of the profile.

Configure the delivery of the audience to the destination in the Destination configuration.

• See the Facebook Destination Guide for further details on configuring the Facebook Destination.

• See the Google Customer Match Destination Guide for further details on configuring the Google Destination.

• When configuring a destination, select which audience you would like to activate to the destination.

• Determine the scheduled start date you would like the destination dataflow to begin delivering the audience to the destination.

• Each destination has required and optional attributes that will be sent.

  • For Facebook one of the required identities must be included and is used to match the profiles in the audiences within Experience Platform to a profile that is targetable by Facebook.
  • For Google Customer Match one of the required identities must be included and is used to match the profiles in the audiences within Experience Platform to a profile that is targetable by Google Customer Match.

• Each destination also has a specified delivery type, whether streaming or batch, file based or JSON payload.

  • For Facebook, audience memberships are delivered in streaming fashion to a Facebook endpoint in JSON format.
  • For Google Customer Match, audience memberships are delivered in streaming fashion to a Google Customer Match endpoint in JSON format.
  • Audience memberships will be delivered in streaming fashion subsequent to the streaming or batch segmentation evaluation in Experience Platform.

Ensure the destination flow has delivered the audience to the destination as expected.

• Check the monitoring interface to confirm the audience was delivered with the number of profiles expected. The audience size should be reflective of the expected number of profiles activated, noting that specific destination such as Facebook and Google will require certain fields, such as an email hash identity, and if not present in the profile that is a member of the audience, it will not be activated to the destination.
• Check for any skipped profiles for profile identities missing or attributes missing that were mandatory.
• Check for any other errors that may need to be resolved.

Verify the audience was activated to the end destination with the expected number of audience memberships.

• Login to Facebook Custom Audience portal to verify the audience from Real-time Customer Data Platform was delivered and that the match rate of profiles in the audience in Facebook reasonably matches the number of profiles in the audience from Real-time Customer Data Platform.
• After completing the activation flow, switch to your Google Ads account. The activated segments are shown in your Google account as customer lists. Please note that depending on your segment size, some audiences do not populate unless there are over 100 active users to serve.