ACS - Delivery and tracking logs of Transactional message

Avatar

Avatar
Boost 25
Level 3
eveline8
Level 3

Likes

24 likes

Total Posts

70 posts

Correct reply

5 solutions
Top badges earned
Boost 25
Validate 10
Validate 1
Boost 5
Boost 3
View profile

Avatar
Boost 25
Level 3
eveline8
Level 3

Likes

24 likes

Total Posts

70 posts

Correct reply

5 solutions
Top badges earned
Boost 25
Validate 10
Validate 1
Boost 5
Boost 3
View profile
eveline8
Level 3

21-02-2019

Hi,

I need to export delivery and tracking logs of a specific transactional message.

We have created this campaign to send mail with API input.

So the same profile can receive different messages with the same transactional template.

I tried to export delivery and tracking log of this transactional message but the delivery ID and label are always the same.

Is there a field that allows me to distinguish the different mailings?

For example:

Delivery ID DM2

Status: sent

mail xxx@gmail.it

event date: 14/02/2019

Delivery ID DM2

Status: sent

mail xxx@gmail.it

event date: 16/02/2019

Delivery ID DM2

Status: Open

mail xxx@gmail.it

event date: 17/02/2019

I want to know if the open is associated at the first or the second send.

thanks,

E.

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Boost 5
Employee
Garima_Gakhar
Employee

Likes

44 likes

Total Posts

77 posts

Correct reply

38 solutions
Top badges earned
Boost 5
Boost 3
Boost 25
Boost 10
Boost 1
View profile

Avatar
Boost 5
Employee
Garima_Gakhar
Employee

Likes

44 likes

Total Posts

77 posts

Correct reply

38 solutions
Top badges earned
Boost 5
Boost 3
Boost 25
Boost 10
Boost 1
View profile
Garima_Gakhar
Employee

26-02-2019

Hi eveline8​,

BroadLog ID is the field/Schema which is actually responsible for identifying Delivery success to Recipients.

If the recipient is being targeted multiple times for same Delivery, there is no out of the box field (corresponding to Deliveries) which could identify the specific 'Send' of that Delivery leading to an Open/Click.

Even a comparison of Event Date (within Sending Logs) with approximate time of API Calls won't give a fair idea as to which API Call is responsible for the Open/Click.

No User Session (end-recipient identification) values would match with any detail of API Call as well.

Answers (0)