Tracking Email users in DMP | Community
Skip to main content
New Participant
May 13, 2019
Solved

Tracking Email users in DMP

  • May 13, 2019
  • 13 replies
  • 15198 views

Hi Team,

I am trying to add users into a trait when they open our email newsletters in the DMP. However, the challenge here is that, email is a non java-script environment and I'm restricted to only using image version of the pixels in the email newsletters. As there is no java-script I suspect there is no cookie that is placed or verified and thereby I suspect that this approach is tracking no one. Can you please correct me if I am wrong and if I've misunderstood how the pixels work?

Also, is there any other way I can use to get users into the DMP from the non java-script environment like email platforms?

Best,
Akshat

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Ankita_Sodhi

Hello akshatganja​,

In the given scenario, turn of events should be as follow:

1. Users click on the link mentioned in the email campaign.

2. Above action will make an declaredID call to AAM and get one UUID assigned to the given customerID.

3. Capture those customerIds who have clicked on the email campaign(this is upto you  how you want to achieve this).

4. Now upload data for those users only who have clicked on the email campaign.

This way you will get assiciation of UUID to customerID and while uploading data, just provide the customerID used in the declaredID call and data will be binded to customerID.

I hope this answers you query. Please feel free to revert with any doubt which you might have.

13 replies

Ankita_Sodhi
Employee
May 16, 2019

Thank akshatganja​ for writing us back.

I understand your concern with respect to device level activity and I am happy to highlight this great thing of AAM i.e. with these declaredID calls, AAM will create on UUID automatically and align it with customer present in d_cid_ic parameter.

Here, you need to create Profile Merge Rules which uses only Authenticated Profile option without device profile so that everything gets written to CustomerID and not device, by this I mean, trait and segment qualifications will be associated to CustomerID only.

I hope this helps, please let me know for any additional question.

New Participant
May 14, 2019

Hi Asodhi,

Thanks for sharing this information. When I think of going this way the only potential issue I see is, how do I associate the online activity of these users to their respective customer IDs. As Adobe uses a cookie to identify a user's online presence / activity with this solution we wouldn't be able to associate that activity to these users as they are defined based on customer ID that doesn't have an online presence.

Is there any way we can sync up the cookies of the users to these customer IDs?

Ankita_Sodhi
Employee
May 14, 2019

Hello Akshat,

I understand that you want to send data to AAM via img click from the email newletters.

You may want to re-check on the pixels/declaredId calls. For AAM to capture one particular user, we need to have either AAMID or CustomerID, so if you can pass customerID(hased or as required) along with a datasourceID then you can utilize declaredID calls.

You can use d_cid parameter or d_cid_ic parameter depending upon the need and create a call similar to below:

http://domain name/event?d_cid=123%01987&Key-value-pairs

In above example: 123 is the integration code of datasource and 987 is the customerID

OR

http://domain name/event?d_cid=123%01987%011&Key-value-pairs

In above example: 123 is the integration code of datasource, 987 is the customerID and 1 at the end is the Authentication State Identifier.

Note: %01 is encoded form of colon (:) and is required in declaredID calls.

You can embed these pixels in img so that they can fire on the click of these images.

Apart from these, you may want to check on the Media Pixels if they solves the purpose. Please check this link for more information.

I hope this helps, please let me know for any additional question.