SOLVED

Recurring email -- incomplete stats showing in email performance report?

Go to solution
Dory_Viscoglio
Level 10
We have a recurring (daily, M-F) email for our subscribers that has custom recommendations that are populated by a company called Certona and presented as images in the email. The email itself works great, but I'm having some issues with email performance reports.

So that we would be able to look at a week's reporting as a whole I have set this up as a Monday email, a Tuesday email, etc, each with their own respective smart campaign for sending. Then I set up an email performance report to report on the past week Sunday-Saturday since we have some Monday sends that start on Sunday due to time zones. Week one our reporting worked fine and showed all of the emails that were sent. Week two, however, the actual send numbers are similar (confirmed in the email send campaigns) but the email performance report is only displaying about 2% of the total recipients -- which I'm thinking are our new people who are receiving the report this week.

I've looked through all of the settings of the report, but can't find any reason why it wouldn't be displaying all sends for the timeframe specified. Has anyone seen this before? Or have any suggestions on how to get all of the send information to appear in this weekly report? Technically I can get someone to pull the daily information from our daily send smart campaigns, but that's the point of report subscriptions! 

Thanks in advance for the help!
1 ACCEPTED SOLUTION
Dory_Viscoglio
Level 10
Hey Dan, interesting use case for engagement programs! I'll have to think of that for next time 🙂 

Our final solution was to create a template program that we clone once a week (we're doing this a couple of weeks in advance so it isn't exactly a weekly process) that contains local assets for the emails, smart lists for reporting and also email performance reports, and they all reference to local smart campaigns. So the only thing that we need to do is update a unique daily identifier token, and then schedule the sends. 

It's still slightly more work than I would have wanted, but it's about as "automated" as we could get it given the constraints.

View solution in original post

15 REPLIES 15