Building Send Logs for SFMC

Creating the Templated Email Send Log For SFMC

Why follow all of these steps?

Having a Send Log not only helps you to track down errors, tying everything together makes reporting easier and allows you to build things like a decision data extension the give you the ability to do a wait for 7 days or until them open type functionality.

Step 1

Create the Email Send Log Data Extension with the following additional fields:

  • EmailName (Text)

  • EventDate (Date)

  • FromName (Text)

  • FromEmail (Text)

  • SubscriberKey (Text)

  • EmailAddress (Text)

  • ViewLink (Text 500 characters)

  • dataSourceName (Text)

  • AccountID (Text, For when multiple business units)

  • CampaignId (Text)


Step 2

Add Ampscript to capture the data for these fields to every email header. I recommend saving it in a shared folder and adding it to email templates as a "Reference Block". That way if you decide you want to add something to every email it is easy.

Download the AmpScript here.

Step 3

Create a Data Extension for a Send Log you can search with Primary Keys (PK). I like to call this "EmailSendLog_PK". You will want all of the same fields plus a few more:

  • JobID (PK)

  • BatchID (PK)

  • ListId (PK)

  • SubscriberKey (PK)

  • EmailSubject

  • SendClassification

  • TriggeredSendID

  • ErrorCode

  • EmailSubject

  • SendClassification

  • TriggeredSendID

  • ErrorCode

  • JourneyName

  • VersionNumber

  • SentDate

  • OpenDate

  • ClickDate

  • BounceDate

  • BounceType

  • -Plus all of the field listed previously

To be continued...