Real time transactional messages logs | Community
Skip to main content
G
GiustaMa
Level 2
July 7, 2022
Solved

Real time transactional messages logs

  • July 7, 2022
  • 1 reply
  • 1758 views

Hi, 

 

I have few questions about delivery and tracking logs of real time transactional messages on campaign standard.

Querying the delivery logs and tracking logs tables, it seems that delivery and tracking logs are not available to extract for this kind of transactional messages, but if I look punctually in each real time transactional message in the execution list I can see the delivery logs.

Whereas, in the tracking logs recipients are not available.

What are the policies on this? 

Which is the differences between the profile based and the real time based transactional messages logs availability?

Is it possible to extract the raw data of the real time transactional messages logs?

 

Thanks!

    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 costa_n11

    Hi @giustama 

    Profile logs as it name infers are delivery and tracking logs for deliveries sent to a Profile.

    When creating a transactional event, you select which type it would be:

    1. Profile: the delivery will be sent to a Profile and you would have to ensure to pass the reconciliation field in the event to map it to Profile. HOWEVER, there is a catch using Profile for transactional event. the profile record MUST exist in Campaign prior the invocation of the transactional event. This allow you to use Profile information to personalise the delivery, for instance profile.firstName (a classic of course 🙂 )
    2. Real-Time: the event has no knowledge of a Profile when it is invoked, meaning that the information the delivery has is self-contained by the information provided by the event itself, in our sample above, you would have a field firstName in the event context itself and you will use this field in your delivery, event.ctx.firstName.
    3. You also have the possibility to create a follow up delivery when creating the events, this allows you to have a multi-wave journey based on the original transactional event.

    When you create a Real-Time event, it does create a resource under the hood that you can query this object delivery and tracking logs as opposed querying the Profile delivery and tracking logs.

    When you create a Query activity, go to Resource and search your event using EVT, you will see a Resource representing your event and you can query the delivery and tracking logs of this resource...

     

    That's how it works in Campaign Standard.

     

    Hope this helps,

     

    thanks

    Denis

    1 reply

    C
    Adobe Employee
    costa_n11Adobe EmployeeAccepted solution
    Adobe Employee
    July 7, 2022

    Hi @giustama 

    Profile logs as it name infers are delivery and tracking logs for deliveries sent to a Profile.

    When creating a transactional event, you select which type it would be:

    1. Profile: the delivery will be sent to a Profile and you would have to ensure to pass the reconciliation field in the event to map it to Profile. HOWEVER, there is a catch using Profile for transactional event. the profile record MUST exist in Campaign prior the invocation of the transactional event. This allow you to use Profile information to personalise the delivery, for instance profile.firstName (a classic of course 🙂 )
    2. Real-Time: the event has no knowledge of a Profile when it is invoked, meaning that the information the delivery has is self-contained by the information provided by the event itself, in our sample above, you would have a field firstName in the event context itself and you will use this field in your delivery, event.ctx.firstName.
    3. You also have the possibility to create a follow up delivery when creating the events, this allows you to have a multi-wave journey based on the original transactional event.

    When you create a Real-Time event, it does create a resource under the hood that you can query this object delivery and tracking logs as opposed querying the Profile delivery and tracking logs.

    When you create a Query activity, go to Resource and search your event using EVT, you will see a Resource representing your event and you can query the delivery and tracking logs of this resource...

     

    That's how it works in Campaign Standard.

     

    Hope this helps,

     

    thanks

    Denis

      A
      ABr86
      Level 2
      July 11, 2022

      Hi @costa_n11 

      when you said "When you create a Real-Time event, it does create a resource under the hood that you can query this object delivery and tracking logs as opposed querying the Profile delivery and tracking logs.".

       

      I think I can find Delivery logs but I can't see Tracking logs. Can you give me an example of tracking logs for a real time transactional event?

       

      Thanks

       

       

      C
      Adobe Employee
      costa_n11Adobe Employee
      Adobe Employee
      July 11, 2022

      Hi @abr86 

      Sure, let say you have a event call EVTSampleEmail as shown below

      When you go to the Properties tab of a Query activity, you will search EvtSampleEmail as a Resource and you can extend the list of entities you can use as a Resource

       

      That's how you can query Real-Time Event... 

      Hope this helps,

      Thanks a lot

      Denis

        Terms & ConditionsAccessibility statement

        Loading footer...