we have our emails in design studio, but heard I should keep all assets in each program. what are the advantages to keep everything local?
There are a many benefits of keeping local assets within Marketing Activity programs—here are a few:
The exception I use is that we generally have global forms that we repeatedly use in the Design Studio and a Universal Fulfillment Email that resides within the Design studio. We tokenize both of these and reference them within the actual Marketing Activities programs, because they're kind of ghost-assets that can inherit token values even when they're not within an actual program itself. With the Universal Fulfillment Email that is tokenized, you won't be able to run separate email performance reports by the triggers, so that's a little bit of a nuance, but pays off overall.
Edward Unthank | Founder, Etumos
Hey Edward Unthank! You mention being able to use Design Studio assets that can refer to program tokens. Can you provide more detail on how you're able to do this? Specifically, I'm trying to have a generic Webinar Confirm page that lives in Design Studio, that pulls in the particular program webinar date/time. However, when I test out the flow, the tokens don't show up. Do the tokens have to live in a particular location? Do I need to use a specific form that lives in the program? thank you!
Allison Sparrow Only in emails! Emails in the Design Studio take the tokens from the smart campaign's program that's casting the email. Not the case for landing pages, unfortunately.
Edward Unthank do you recommend creating custom webinar reg followups for each webinar? Or do you have a generic lp that doesn't have any tokens in it as followup? Also, do you have one webinar form, and does it live in design studio? thank you!! hope you're doing well
I would suggest to avoid having lists local to an Engagement program. By default the leads in the list are added to the first stream.
Retrieving data ...