How to use retroactive data in destination publishing?

Avatar

Avatar

harshit_a_pande

Avatar

harshit_a_pande

harshit_a_pande

25-04-2018

Hello,

I wanted to understand how retroactive data can be used in destination publishing via AAM? We have imported a large chunk of our data when we decided to go ahead with AAM.

Please help me understand if the imported data can be used for destination publishing without the users having to do actions again which will qualify them to be populated in a trait/segment and then later being sent for some destination.

I basically want to use the data set which I already have to be used for targeting. This data is dated years back so chances of those users to visit again and do actions again is bleak thus I wanted to know if there is a way around.

Adding to it, how is the offline data stored in AAM? Is there any MCID created in AAM after the upload is done and when the id sync happens the new MCIDs are mapped to the corresponding CRM-ID? Can we create traits in AAM solely depending upon the values which we passed in the file and it would start showing numbers?

Thank you in advance.

-Harshit

View Entire Topic

Avatar

Avatar

harshit_a_pande

Avatar

harshit_a_pande

harshit_a_pande

27-04-2018

Hello,

Thank you for your answer. Adding to it, what will happen if I upload the data (which was never synced in past) and I create traits based upon those signals?

Will the trait only populate when the person with same CRM ID visits and id syncs happens? What will happen to the uploaded data against whom no future id sync happens? Will the data still reside in AAM or will it be discarded? Let's say the same person visits but a month later, will the id sync now populate the traits which was created long back against the signals passed in the old upload file?

Thank,

Harshit Pandey