ACS - Delivery and tracking logs of Transactional message | Community
Skip to main content
eveline8
eveline8
Level 4
February 21, 2019
Solved

ACS - Delivery and tracking logs of Transactional message

  • February 21, 2019
  • 1 reply
  • 3965 views

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.

    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 Garima_Gakhar

    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.

    1 reply

    Garima_Gakhar
    Adobe Employee
    Garima_GakharAdobe EmployeeAccepted solution
    Adobe Employee
    February 26, 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.

      jedaiah
      jedaiah
      July 17, 2020
      Hi, is this feature something that would be developed in the roadmap/has already been developed?
      Terms & ConditionsAccessibility statement

      Loading footer...