Event Forwarding Logs

Hi ​@tyrese,

Yes, Adobe Event Forwarding provides built-in logging through the Adobe Experience Platform Debugger and 
via the Event Delivery monitoring in the UI.

Here are the ways to view Event Forwarding logs:

1. Event Delivery Monitoring (UI)
  - Go to Data Collection > Event Forwarding
  - Open your Event Forwarding property
  - Navigate to Monitoring tab
  - Here you can see event delivery status, success 
    and failure rates per rule/extension

2. Adobe Experience Platform Debugger
  - Install the AEP Debugger Chrome extension
  - Enable Event Forwarding trace in the debugger
  - This gives you real-time logs of events being forwarded including request/response payloads

3. Audit Logs (Admin level)
  - In AEP go to: Admin > Audit Logs
  - Filter by Event Forwarding to see configuration change history

4. Extension-specific logging
  - Some Event Forwarding extensions (like Meta Conversions API, Google Analytics) have their own dashboards where you can verify received events on the destination side

Important note: Detailed payload-level logging for every forwarded event is not stored long-term in AEP by default, the Debugger trace is the best tool for real-time troubleshooting of individual events.

Are you looking for real-time debugging of a specific event, or historical logs for auditing purposes? That will help narrow down the best approach.
 

You could set up the Assurance logs to audit the logs.

Hey ​@silpasurapaneni  and ​@akhil_merupula 

Thanks for both of you reaching out, and apologies on the late reply.

I was more so trying to understand if there was a way to see historic logs - I understand how to use the debugger and assurance for personal testing.

Thanks,
Ty

Unfortunately you will have to start the assurance session to get the traffic in the timeframe the session is set up for.

Thanks ​@silpasurapaneni - that was my thought and its not ideal because its makes it difficult to 

​@bjoern__koth - do you know of any way to do this? Maybe an API call? Or will this have to be a product enhancement request

Thanks,

Ty