Badges
Accepted Solutions
Likes Received
Posts
Discussions
Ideas
Blog Posts
This is weird, I'd open a support ticket
You need to do it at the program level. Smart campaigns use the tokens from the campaign they're triggered in.
Make sure you don't have any dynamic content on there, you could have a hidden segment with a different subject line
Coding for email templates, Marketo in particular, is complicated! Unless you have in-house dev experienced in Marketo email syntax, it's usually best to outsource. We've been very happy with Digital Pi's FLEX templates. They have lots of little toggles and adjustments, super easy to work with. Reco...
There was a great San Diego Marketo User Group last year about "hacking" segmentations. Unfortunately it looks like the recording isn't available. But they talked about how some features (like date in past) are not available to be used by a Segmentation, but by changing a field or adding someone to ...
There have been some great presentations at conferences and user groups about Marketo email nurture. Amanda Thomas of Etumos presents on nurture a lot, here's a MUG recording: https://mugs.marketo.com/events/details/marketo-austin-mug-presents-make-scalable-nurture-planning-as-satisfying-as-thanksgi...
To clarify, your Marketo Program is synced to the SFDC campaign, correct? You can run a smart list of people who are in one but not the other, open a person record, look through the activity history and see if you can spot any issues.
I have not used them, but several developers offer tools to revert your Marketo data. I'd look at https://reverto.io/ and digitalpi.com/services/data-services/
I imagine this has to do with the way that Marketo is transitioning into the new UI, and will be fully resolved once the new UI is live across all functions in Marketo.
To confirm, you have the Marketo Program synced to the SFDC campaign? Sometimes this connection is a bit tenuous, especially with list uploads. You can unsync the program from the campaign and use "change status in sfdc campaign" flow step to add everyone to the correct statuses.