Delivery logs

[mmbb110]

Hi,

Where can I query the delivery logs for a real time transactional message in Adobe campaign standard.

I want to check the count of delivery logs generated for my transactional message.

[Denis_Bozonnet · Accepted solution]

Hi,

Transactional Messages delivery and tracking logs are stored in their own event broad and tracking logs. While using a Query activity, go to the Property tab on the activity and in the "Resource" field, search for broadLog, you should see a series of broadlog entities associated to the Profile and then to each of your transacitonal event, starting with EVT, select the event you're interested and you can query it.

Thanks

Denis.

[mmbb110]

@Denis_Bozonnet, I used a query activity and when I search in Resources under the properties tab, I don't see the BroadLog for the transactional event, starting with EVT, I have attached a image for reference.

[Denis_Bozonnet]

Hi,

[Denis_Bozonnet]

Hi,

It is strange, could you try to search with EVT instead. and go on the right side of the return list to click on the arrow?

[JasonSmithDW]

Are transactional deliveryLogs not stored in a single table?

[Denis_Bozonnet]

In ACS, you have a distinction between the physical table (Data Objects) and the representation of an event (Business Object). Since the event is now well organised for its context, you can only query the Business Object and not the underlying Data Object...

you might be able to query the real-time event object however you will not have the context event available in the event itself.

In OO modeling you could say that each event resource is a sub-class of the real-time event resources. 

1. At event level you have the exact context but you have to query event type per event type
2. At real-time event level, you can only query at the top and you lose the context but you can query all logs... 

Sadly you can't have both at same time... unless you query 1st real-time event and then manually split by event type and use an enrichment to bring the context in the Target data.. 

The whole thing was made this way to allow follow up deliveries on transactional messages.