This guide assumes you have an Identity Cloud implementation, a contract to use Integration Bus, and access to the SnapLogic platform through Akamai. If this is not the case but you are interested in enabling this integration pattern, please reach out to your Akamai representative to get started.
The following tasks/items must be completed and available for this integration:
Let’s step through each of these.
Create a package in Marketing Cloud which this integration will use to sync data. For general steps on how to create a package, see Marketing Cloud Packages: Create and Install Packages.
IMPORTANT GUIDANCE:
Once your package is created, you’ll see the following values which will be needed later in this guide:
For this data sync, you’ll map basic subscriber information like email and subscriber key to Marketing Cloud. You can map additional data from the Identity Cloud profile to Marketing Cloud using data extensions.
Note that you must create a separate data extension in Marketing Cloud for each plural you want to map from Identity Cloud. See more details below.
For general steps on how to create a data extension, see Create a Data Extension in Marketing Cloud.
IMPORTANT GUIDANCE:
email
or uuid
) to the Subscriber Key. Make sure to include this identifier as a field and set it as the Primary Key.
Important Note! With this integration you can optionally sync profile deletions in Identity Cloud with Marketing Cloud. In order to sync deletes with data extensions, you MUST map the uuid
to the Subscriber Key (in a later step), and you MUST have the following Send Relationship: “uuid” relates to Subscribers on “Subscriber Key”
For more info, see Sync deletes.
Specific to plurals:
email
or uuid
) as a field, marked as a Primary Key.id
(or another locally-unique attribute in the plural) should be included as a field and also marked as a Primary Key.
The combination of the user identifier and the plural entry identifier as primay keys is necessary to store plural entries properly in Marketing Cloud.
Example that stores data from the legalAcceptances
plural:
The actual mapping of Identity Cloud profile data to Marketing Cloud data extensions will be configured later.
Once your data extension(s) is created, you’ll see the following values which will be needed later in this guide:
In order to grant access for the integration to pull data from Identity Cloud, please create an API client (a.k.a. “Property”) in Identity Cloud Console. This client must have the direct_access
feature only, and must be dedicated for this integration.
This needs to be direct_access
rather than direct_read_access
because the integration needs to both read data from Identity Cloud AND write metadata into the user records for syncing.
To create this client:
You will need the Client Id and Secret later in this guide.
In order to properly sync user data, the integration writes metadata into the Identity Cloud user record. This requires an object called janrain
containing specific attributes be present in the schema. In Identity Cloud Console, it looks like this:
If you are a long-time customer of Identity Cloud (formerly known as Janrain), you may already have this object in your schema(s). If this is the case, and if it contains all the attributes encircled in the above screenshot, you can skip to Next Steps.
To add the required object and attributes to the schema, make the following API call to the /entityType.addAttribute endpoint using the POST method.
The base URL for this call is your Registration Domain.
You can find the Registration Domain in the Identity Cloud Console:
Registration Domain(s)
in the top section of the page
This call requires Basic Authorization. To create the authorization code for this call, your application owner Client Id
and Secret
must be combined with a colon in between (id:secret) and then base64 encoded.
You can find the application owner Client Id and Secret in the Identity Cloud Console:
Client Id
and Secret
in the Credentials section. Click the copy icon to left of each to quickly copy and paste them where needed.
Postman will create the authorization code for you. All you need to do is:
Client Id
as the Username and Secret
as the Password
When you Send the call, Postman will generate the Authorization header for you, and this will override the Authorization template from the imported call.
curl -X POST \
https://my-registration-domain.janraincapture.com/entityType.addAttribute \
-H 'Authorization: Basic AUTHORIZATION CODE' \
-H 'Content-Type: application/x-www-form-urlencoded' \
-d 'type_name=user' \
-d 'attr_def={"name":"janrain","type":"object","attr_defs":[{"name":"etSubscriber","type":"object","attr_defs":[{"name":"syncUpdated","type":"dateTime"},{"name":"syncAttempts","type":"integer"},{"name":"remoteIds","type":"plural","attr_defs":[{"name":"remote_id","type":"string"},{"name":"service","type":"string","constraints":["locally-unique"]}]}]}]}'
If you have multiple Entity Types, you will need to make this call for each one you want to sync with Marketing Cloud. Make sure to update the type_name
for each call.
Remaining steps will be completed in the SnapLogic UI. Please login to SnapLogic with the account Akamai created for you, then come back to this tab to continue.
Supported browsers: Chrome and Firefox
Don’t have a SnapLogic account? When Akamai deployed the Integration Bus for you, you should have received a welcome email from SnapLogic with your login ID, a temporary password, and a link to access your account and set a new password. If you have not received this email, please check your spam folder and/or reach out to your Akamai Identity Cloud representative.
Using a SnapLogic account that predates your Akamai Integration Bus deployment? If so, you can log in normally, then you’ll need to switch to the AkamaiProd environment. If you have multiple environments, you can check or select this in the top-right corner of the SnapLogic UI.