This example illustrates how to import a file containing profiles and subscribe them to an existing service. After importing the file, a reconciliation needs to be carried out so that the data imported can be identified as being profiles. To ensure that the file does not contain any duplicates, a deduplication activity will be executed on the data.
The workflow is presented as follows:
A Load file activity loads the profile file and defines the structure of the imported columns.
For this example, the file loaded is in the .csv format and contains the following data:
lastname;firstname;email;birthdate;subdate jackman;megan;firstname.lastname@example.org;07/08/1975;10/08/2017 phillips;edward;email@example.com;09/03/1986;10/08/2017 weaver;justin;firstname.lastname@example.org;11/15/1990;10/08/2017 martin;babeth;email@example.com;11/25/1964;10/08/2017 reese;richard;firstname.lastname@example.org;02/08/1987;11/08/2017 cage;nathalie;email@example.com;07/03/1989;11/08/2017 xiuxiu;andrea;firstname.lastname@example.org;09/12/1992;11/08/2017 grimes;daryl;email@example.com;12/06/1979;12/08/2017 tycoon;tyreese;firstname.lastname@example.org;10/08/1971;12/08/2017
A Reconciliation activity identifies the data from the file as belonging to the profile dimension of the Adobe Campaign database. Only the Identification tab is configured. It identifies the file data according to the email addresses of the profiles.
A Deduplication based on the email field of the temporary resource (resulting from the reconciliation) identifies any duplicates. If the data imported from the file contains any duplicates, the subscription to a service will fail for all data.
A Subscription Services activity lets you select the service to which the profiles must be subscribed, the field corresponding to the subscription date, and the origin of the subscription.