How do we go about mapping segments from Krux to AAM.
I understand that a S2S destination can be set up in Krux to map the segments. But is that how we ingest data from Krux to AAM: from S2S destination in krux to a cookie based data source in AAM?
In order to onboard segments from Krux, you will need to set up a data source with id-type based on data being ingested (cookie, cross-device or device id for android/ios). The data source id needs to be shared back with the Krux client. Krux may refer to this Data Source ID as "DPID_TARGET_DATA_OWNER" since that is how it is referenced in the AAM onboarding documentation. Prior to ingestion of data, you will need to create traits for segment ids provided by Krux, so that the data can be collected.
Hope this helps.
Here's what I did and it worked.
The idea was, AAM treats Krux Ids as customer ids like any other batch file upload.
You can also create a cookie/device id based data source. Make sure that you select the right id in the 'inbound' section if you are choosing cookie as id type.
Thanks Harish !
Does the type of data source need to be just cross device & ID type "Customer ID"? The krux data that I'm trying to ingest does not have much authenticated users. So is it OK to create a cookie based data source to ingest the data?