Activate the data you have in Adobe Experience Platform by mapping segments to destinations. To accomplish this, follow the steps below.
To activate data to destinations, you must have successfully connected a destination. If you haven’t done so already, go to the destinations catalog, browse the supported destinations, and set up one or more destinations.
The steps in the activation workflow vary slightly between destination types. The complete workflow for all destination types is outlined below.
Applies to: All destinations
In the Platform user interface, navigate to Destinations > Browse, and select the destination where you want to activate your segments.
Select the name of the destination to navigate to the activation workflow.
Note that if an activation workflow already exists for a destination, you can see the segments that are currently being activated to the destination. Select Edit activation in the right rail and follow the steps below to modify the activation details.
Once you have selected a destination, select Activate.
Applies to: All destinations
In the Activate destination workflow, on the Select Segments page, select one or more segments to activate to the destination. Select Next to proceed to the next step.
Applies to: social destinations and Google Customer Match advertising destination
For social destinations, you can select source attributes to map as target identities in the destination. This step is either optional or mandatory, depending on which primary identity you are using in the schema.
If you are using email address as primary identity in your schema, you can skip the Identity mapping step, as shown below:
If you are using another ID, such as “Rewards ID” or “Loyalty ID”, as primary identity in your schema, you need to manually map the email address from your identity schema as a target identity in the social destination, as shown below:
Select Email_LC_SHA256
as target identity if you hashed customer email addresses on data ingestion into Adobe Experience Platform, according to Facebook email hashing requirements.
Select Email
as target identity if the email addresses you are using are not hashed. Platform will hash the email addresses to comply with Facebook requirements.
Applies to: Email marketing destinations and cloud storage destinations
In the Configure step, you can configure the schedule and the file names for each segment you are exporting. Configuring the schedule is mandatory, but configuring the file name is optional.
To add a schedule for the segment, select Create schedule.
A popover appears, showing options to create the segment schedule.
The default file names consist of destination name, segment ID, and a date and time indicator. For example, you can edit your exported file names to distinguish between different campaigns or to have the data export time appended to the files.
Select the pencil icon to open a modal window and edit the file names. Note that file names are limited to 255 characters.
In the file name editor, you can select different components to add to the file name. The destination name and segment ID cannot be removed from file names. In addition to these, you can add the following:
MMDDYYYY_HHMMSS
format or a Unix 10-digit timestamp of the time when the files are generated. Choose one of these options if you would like your files to have a dynamic file name generated with each incremental export.Select Apply changes to confirm your selection.
If you don’t select the Date and Time component, the file names will be static and the new exported file will overwrite the previous file in your storage location with each export. When running a recurring import job from a storage location into an email marketing platform, this is the recommended option.
Once you have finishing configuring all your segments, select Next to continue.
Applies to: advertising destinations, social destinations
On the Segment schedule page, you can set the start date for sending data to the destination, as well as the frequency of sending data to the destination.
For social destinations, you must select the origin of your audience in this step. You can proceed to the next step only after selecting one of the options in the image below.
Applies to: email marketing destinations and cloud storage destinations
On the Scheduling page, you can see the start date for sending data to the destination as well as the frequency of sending data to the destination. These values cannot be edited.
Applies to: email marketing destinations and cloud storage destinations
On the Select attributes page, select Add new field and choose the attributes that you want to send to the destination.
Platform prefills your selection with four recommended, commonly used attributes from your schema: person.name.firstName
, person.name.lastName
, personalEmail.address
, segmentMembership.status
.
File exports will vary in the following ways, depending on whether segmentMembership.status
is selected:
segmentMembership.status
field is selected, exported files include Active members in the initial full snapshot and Active and Expired members in subsequent incremental exports.segmentMembership.status
field is not selected, exported files include only Active members in the initial full snapshot and in subsequent incremental exports.Additionally, you can mark different attributes as mandatory. Marking an attribute as mandatory makes it so the exported segment must contain that attribute. As a result, it can be used as an additionally form of filtering. Marking an attribute as mandatory is not required.
It is recommended that one of the attributes is a unique identifier from your schema. For more information about mandatory attributes, see the identity section in the Email marketing destinations documentation.
If any data usage labels have been applied to certain fields within a dataset (rather than the entire dataset), enforcement of those field-level labels on activation occurs under the following conditions:
For example, if the field person.name.firstName
has certain data usage labels that conflict with the destination’s marketing use case, you would be shown a data usage policy violation in the review step. For more information, see the data usage policies guide.
Applies to: all destinations
On the Review page, you can see a summary of your selection. Select Cancel to break up the flow, Back to modify your settings, or Finish to confirm your selection and start sending data to the destination.
In this step, Platform checks for data usage policy violations. Shown below is an example where a policy is violated. You cannot complete the segment activation workflow until you have resolved the violation. For information on how to resolve policy violations, see Policy enforcement in the data governance documentation section.
If no policy violations have been detected, select Finish to confirm your selection and start sending data to the destination.
Follow the steps below to edit existing activation flows in Platform:
For email marketing destinations and cloud storage destinations, Platform creates a tab-delimited .csv
or .txt
file in the storage location that you provided. Expect a new file to be created in your storage location every day. The default file format is:
<destinationName>_segment<segmentID>_<timestamp-yyyymmddhhmmss>.csv|txt
Note that you can edit the file format. For more information, go to the Configure step for cloud storage destinations and email marketing destinations.
With the default file format, the files you would receive on three consecutive days could look like this:
Salesforce_Marketing_Cloud_segment12341e18-abcd-49c2-836d-123c88e76c39_20200408061804.csv
Salesforce_Marketing_Cloud_segment12341e18-abcd-49c2-836d-123c88e76c39_20200409052200.csv
Salesforce_Marketing_Cloud_segment12341e18-abcd-49c2-836d-123c88e76c39_20200410061130.csv
The presence of these files in your storage location is confirmation of successful activation. To understand how the exported files are structured, you can download a sample .csv file. This sample file includes the profile attributes person.firstname
, person.lastname
, person.gender
, person.birthyear
, and personalEmail.address
.
Check your account in the respective advertising destination that you are activating your data to. If activation was successful, audiences are populated in your advertising platform.
For Facebook, a successful activation means that a Facebook custom audience would be created programmatically in Facebook Ads Manager. Segment membership in the audience would be added and removed as users are qualified or disqualified for the activated segments.
The integration between Platform and Facebook supports historical audience backfills. All historical segment qualifications get sent to Facebook when you activate the segments to the destination.
To disable an existing activation flow, follow the steps below: