This capability is currently in beta, and subject to frequent updates and modifications without notice.
Please reach out to Adobe Customer Support if you plan to implement this capability.
Learn how to map different data types between Adobe Campaign Standard and Adobe Experience Platform.
In this tutorial we will see how to map custom resources which already exist in ECS. I am in custom resources and here we see two custom fields have been added to the profile dimension. These two fields at business designation, business ID. One of them is of the type long text and other of the type integer. Since these are custom fields created, we need to create custom schema as well for each of these fields in platform. So I am at the platform UI now and profile underscore, campaign underscore at post 78. This kind of schema which will always be available in AD. So, by default, whenever you get a campaign instance alongside an AEP instance, you will always see some schema which exists from campaign and one that you just created on top of the schema. Even you can choose to reuse this or you can create your own. We would encourage you to use the schema and your own extensions mixing exception although you can choose to create your own data set or use the existing data set as well. The format to locate your own schema is profile underscore campaign, underscore name of the URL your instance name. So, when you see this is the campaign instance named which we are seeing here, which is at post 78 dot QA dot campaign dot adobe dot com. And, on the basis of this, the schema names has been generated automatically. So we see a profile underscore campaign, underscore is the name of the instance you are at self. Once you go and create more custom fields you will see your custom fields are created under the spot organized already. Here, you see ee-to-ee center, so ee-to-ee center is the name of the archived excel which you see here. So, as a customer you will have multiple instances and these multiple instances might be mapped with the same archiving. Since you want all of your data from these multiple instances, just blow in a single archived in AD. You will see a common center name here, so you can use the same schema as here, and all of the data from different instances will flow in this. So, this is the schema for this particular instance which is at post 78. Now, we go back to platform data mappings. In campaign to create these mappings. So, as you know that we can access the platform data mappings menu from the platform menu, under development and administration. You will see these two out of the box mappings already created. You will duplicate one of the out of the box mapping which was been created under targeted dimension profile. It is always best to duplicate the mappings in case you are going to use the box mapping itself. Or even if you’re going to change your own mapping. You can either create your own mapping of fresh from here. Or, duplicate it and then make changes in the same one. So, we are going to make changes in the same duplicated mapping, just copy your profile and platform data model mapping. We can rename it to something more meaningful and useful, such as customer profile table mapping. We can keep the ID as is, or have our own meaningful ID generated. I choose to keep the same targeting dimension here, but in case your targeting dimension is different you can choose your different targeting dimension. We will quickly add it to custom field which we have here. So one of the custom fields which we have created is business designation.
So, this particular value is the ACS field and the other field is the XDM field. So we will map from one platform, one product to another platform, which is ACS to XDM. This is an explorer, and this is basically an expression editor. We will use this expression editor to map more complex mapping, such as mapping in ah-deo, and mapping in ee-nom. These are simple mappings, so we don’t need expression editor right now. We will see usage of these expression editors in another tutorial. Similarly, I can look for XDM fills using this explorer itself, which is an XDM fill explorer. And we will see that all the XDM schemas which we have created in AD will be listed here. Since they are fetched from AD, takes a few seconds for this particular list to complete. We can either type out the name…
So we can simply go and select the name as well business underscore designation.
So, designation filling or X-treel has been mapped to stream field. And some ID field which is basically and en-digit. We will map with doing en-digit itself.
So business ID, you will add these mappings, once these mappings have been added, we can save it.
And once we have saved these mappings, we will quickly refresh the URL to see and check whether the mappings which we have saved are reflected in this mapping list or not. So we see business ID exists, and then we can go and see…
Okay, business underscore designation also exists. So now, we can go ahead and publish the mapping. Since we are already sending the records from the beginning it doesn’t matter whether we choose yes or no. But, if we had already ingested some records and then we were making some changes to the schema, and if the schema changes when not disruptive we will choose no because it will not impact our performance. Mapping has been published. And we can use these three dots at the bottom of this particular widget to access the mapping logs. In case a mapping fails, we can again use the same logs to see where the mapping has failed. It might be because of some expression being incorrect or some thought being incorrect to access the XDM field or some generic problems itself. And, with export jobs under this particular tab you can see how your batches have been created and how others have been ingested in AD. It takes a couple of minutes, two or three minutes, for these export jobs to appear, so by the time we wrap up our video we will not be able to see it. But there’s another tutorial to cover how to see these export jobs and test whether your data has been ingested or not.
So, in this video we have seen that we are able to map two custom fields one of them right data, the other data type endangered and the other data type stream mapped and ingested in AD.
See the product documentation for more information on the Mapping definition