should I keep all assets local to a program? if so, why?

[Anonymous]

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?

[Edward_Unthank_ · Accepted solution]

Hey Sherin:

There are a many benefits of keeping local assets within Marketing Activity programs—here are a few:

1. You can create program templates that contain all the right assets for certain types of programs (Content, Online Advertising, Email Blast, Lead Nurture Cast, List Purchase, etc.).
2. You can use program tokens or .my tokens with local assets on landing pages.
3. It's a much cleaner way to structure your Marketo instance where you don't have to repeat names everywhere, and all emails/landing pages/lists are all in nicely organized buckets that everyone can understand at a glance.
4. It makes archiving and deleting entire marketing campaigns and content programs in a few clicks as opposed to spread out many different places.
5. It's much faster to clone programs and not have unique names for everything when you have local assets within programs. Names of assets are concatenated with the program name, so you can name a landing page "LP" within a local asset as opposed to "landing page for webinar on 3/12/2015 with Cisco."
6. Acquisition Program is assigned automatically if you're using local assets such as landing pages and forms. This is a great way to do easy first-touch attribution without the headache because it's automatically assigned.
7. Progression Statuses are easier to assign within programs. You need these for campaign reporting and program reporting to prove that your marketing and sales efforts actually bring in leads, how many, at what cost, and how much revenue they create.

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.

Cheers,

Edward Unthank | Founder, Etumos

[Anonymous]

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!

[Edward_Unthank_]

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.

[Anonymous]

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

[Sanjana_Mohan]

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.