You are here:
Send Logging Best Practices and Tips
Here’s a list of best practices for send logging in Marketing Cloud Engagement. Follow all general data extension best practices for send logging data extensions as well.
- Use send logging to retain information that can change after a send occurs and can affect reporting. Send logging captures send-time values for reports, extracts, and tracking data.
- Use data retention to limit the amount of data stored. Limit data storage to 10 days.
- Add 10 or fewer custom fields to the send log.
- Minimize the size of the fields used in a send log to the size required for the expected data.
- Limit the number of activities concurrently using a data extension. For example, schedule a query activity or report that is reading from the send log to run at a different time than a send that uses the Send Log. You can also use a query activity to move data from an active send log to an archive data extension, as necessary.
- Dates added are in UTC-6.
- Data is rendered correctly if you use the default settings for the data extension send logs. The send log can fail if you add custom fields for the data extension send logs.
- To record the new send log, ensure that you pause, republish, and restart triggered sends and Journey Builder triggered sends. Consider creating a Journey Builder send depending on the number of email or mobile sends activities and journeys.
- The send log can contain duplicate records of a single message due to sending issues. Design your queries to address these potential duplicate records when you use a send log data extension.
Did this article solve your issue?
Let us know so we can improve!
