Re: New Email Program Reporting Issues

Anonymous
Not applicable

New Email Program Reporting Issues

I used the email program for the first time over the weekend and have two questions that I cant seem to figure out:

1. I have activities sync with Salesforce.com and for some reaon both the the activities and interesting moments that show up in Marketo Sales Insight the emails aren't labeled properly with the name and subject line. It is either blank or names the email test name instead of the subject line or name of the actual email. 

2. When I try to add this program to an email performance report the statistics on the email blast arent showing up in the report. 

Any ideas/suggestions?

Thanks!
Tags (1)
6 REPLIES 6
Josh_Hill13
Level 10 - Champion Alumni

Re: New Email Program Reporting Issues

I'd check with Support. There are still some features that could be buggy. I'm pretty sure #2 should work. Try a local Report instead.


Anonymous
Not applicable

Re: New Email Program Reporting Issues

I believe that the Emails sent via an email program are not currently selectable in a email performance report - looking into this internally . In the meantime you should be able to get all the stats you need from the dashboard.
Anonymous
Not applicable

Re: New Email Program Reporting Issues

Thanks for the suggestions. We'll probably wait till these bugs are worked out before we use the program again – it’s alarming when the email information synchronized with Salesforce.com isn't what you expect, even if it is incorrect. 
 
 
Anonymous
Not applicable

Re: New Email Program Reporting Issues

I haven't been able to run email performance reports off my Email Program A/B Subject tests, so I am in the same boat. I'll probably be sticking with my good ol' smart campaigns until the next patch.
Anonymous
Not applicable

Re: New Email Program Reporting Issues

Hey all, is there any update on this?  It looks like we still cannot run performance reports.
Anonymous
Not applicable

Re: New Email Program Reporting Issues

This looks like it was never solved. Does anyone know of a workaround for this? It seems to work at the program level, but not in an aggregate report that we're trying to run.