Hi William,   Folder-level tokens are great for providing consistency across programs - in usage and/or values.    Since the tokens will be inherited in all the programs inside the folder, a campaign creator doesn't need to think about creating each necessary token from scratch on a new program, but merely updating the token values. You can use a placeholder value to prompt the campaign creator to update the token value and follow any guidelines. For example, if your organization's analytics needs require that each program has a unique tracking code appended onto all link urls, you could create a folder-level Text token with the value "enter the tracking code in the format xyz".   Consistency in the names of the tokens - because they're inherited from the folder- can make it easier to document and understand how they're used. If program tokens (not just system or person tokens) are leveraged in the email templates or snippets, the exact naming is critical - the token will not work if it says {{my.awesometoken}} in the template and {{my.supertoken}} in the program.   Sometimes the format of system tokens doesn't quite meet your needs, and you can use top-level folder tokens as a workaround. For example, if you want an auto-updating copyright year, the system token has only the full date. On the top-level folder, use an Email Script token type with this value (and then do not edit the value on the program - just leave the inherited value): ## replace "CST" with your timezone to capture exact New Year's Day changes! #set( $timeZoneObject = $date.getCalendar().getTimeZone() ) #set( $currentYear = $date.format("yyyy", $date.getDate(), $date.getLocale(), $timeZoneObject.getTimeZone("CST") ) ) ${currentYear}   When a token is inherited, you can change the value on the original (e.g. folder-level) token and the new value will flow down to the programs. Keep in mind that once you override or delete an inherited token, you can't re-inherit it. This means that any updates to the value of the original (higher-level) token will no longer flow down to it, even if you recreate the token with the value it had originally inherited.   While (inherited or local) tokens can exist on a program without actually being used/referenced within the email asset, I would caution against adding too many inherited tokens. It could create confusion about the use cases and be messy to manage.   Hope this gives you some ideas! ... View more

So true that MOPs folks end up as the translators/bridges between departments!   How did you come about developing the mentoring relationship with the data scientist? ... View more

Hi Jen, have you always sent the the emails at the same time/day and to the same audience criteria? It could potentially be the processing load in your instance at that moment (e.g. if there are other emails sending or trigger/batch campaigns processing) or possibly even the data center your instance is on. You might want to try using the Head Start setting to pre-process the audience, which may help the send go faster and more in line with your selected time.   Generally, I've found that emails can take 24 hrs to deliver, especially to folks overseas.   Hope this helps! ... View more

Hi Suzy, depending on how many duplicates there are and the criteria are for what field values "win", manual merges one by one may be an option. This is what I had to do in the past, as the Marketo Easy Merge didn't allow for complex criteria, such as "if the value of (field name) is true for one of the duplicate records, then keep all the field values from that record." ... View more

Hi, you would need an API developer to leverage the  Bulk Lead Extract API; unfortunately it isn't beginner-friendly and requires technical expertise. You might want to consider working with a Launchpoint partner or Marketo professional services in order to complete your one-time export. ... View more

Hi Nancy, I haven't tested it with this particular issue, but I've used OpenOffice (free and open source) on my Mac for spreadsheets. It offers many selections for importing CSVs, such as character set (e.g. Unicode UTF-8) and separator options. ... View more

Hi Ivan, it looks like you're missing a "container". You need to define a container that contains any and all modules for the template (and the container can have only modules inside it, nothing else)   See https://docs.marketo.com/display/public/DOCS/Email+Template+Syntax#EmailTemplateSyntax-Containers   Specified using either <table>, <tbody>, <thead>, <tfoot> or <td> with class=”mktoContainer”   Hope this helps! ... View more

Totally agree about the mutual benefits of sharing with the Marketo community - others learn from you, and you learn from others! ... View more

Tips & tricks are my favorite! I'd like to request captions/transcripts on the videos for accessibility (and for folks who forget headphones). ... View more

It's helpful to get a quick and easy description of what the Launchpoint partners do and an example use case. There is a lot of info to sift through on Launchpoint! ... View more

So nice to see names and faces; it makes it easier to connect! I'd like to meet some of the folks behind the Community redesign. ... View more

Great tip about the ways to set the acquisition program! Reminder for folks that if you're using a Marketo form embedded on a web page (vs. in a Marketo landing page), you must use the flow step to capture acquisition program. ... View more

So important! You don't want to have an agency create "email templates" for you that aren't actually editable in Marketo, or to propose a solution that would work only in a totally different industry/business case from that of your organization. Just creates more work for you and you'll have to hire another consultant to fix the situation. ... View more

Haha; of course Kevin couldn't miss an opportunity to talk about Funko Pops! I like that people talked about being outdoors - it can be hard to balance that with our line of work. ... View more

I haven't used the request campaign flow step before so this was super helpful to have some examples! ... View more

Awesome! It might be helpful to offer definitions for some of the filters. Like what's the difference between "Marketo documentation" and "Knowledgebase". Or that "Ideas" is suggestions for the product development team. ... View more

Love it! Especially about archiving folders from past time periods that you no longer need cluttering up the instance. One of the challenges is making sure everyone is using the same abbreviations and order in the naming conventions. (e.g. CM-19F not Fall2019-CMkt). Using a spreadsheet formula like you shared is a great way to keep it consistent. We saved a naming convention/abbreviation guide on the staff intranet, but it would be awesome if this info could be displayed within Marketo itself... But you can save programs/assets in the center of excellence that follow the naming conventions and hopefully they will be good examples for people to follow as they clone. ... View more

Super helpful to know! We had been using Qualtrics surveys quite a bit, and used a reusable custom field in Marketo to import PURLs generated by Qualtrics. And then to send reminders to those who hadn't taken the survey, we had to do a static list import for the contacts who did fill out the survey as an exclusion list. Sounds like this integration would save some of these steps and enable additional communications in Marketo based on the responses. ... View more

Great tips, Chloe & crew! I would note that it's often helpful to dig a little if the underlying marketing strategy isn't very clear, such as a directive that seems more like a tactic than a strategy (e.g. we need to send 5 emails! we need to add "favorite color" to the form!) Then you'll know what you're actually aiming for and can apply the right Marketo tip! ... View more

That's a great use case for dynamic snippets; thank you for sharing! ... View more

You're spot on about the https:// in tokens and putting the UTM as a separate one! Thank you for sharing! ... View more

Why and when do you move assets from one workspace to another?   Item was accidentally created in wrong workspace Plans changed and another group will be managing/editing the program/assets Cloning to mimic a past program that was originally created in another workspace Wishful thinking: While it currently isn't possible to move a program that has members (i.e. email send program that already went out), as we create/retire workspaces based on org structure changes (we pretty much have a workspace for each separate department) it would be nice to be able to move programs into the relevant workspace. Note: We create some things in the default workspace (so we can better manage centrally) and then share out to the other workspaces - so it isn't moving them, but still making them available to the other workspaces Why and when do you move assets between marketing activities and the design studio?  I don't think we have ever done this. I can't imagine a reason to do so - we only put things in design studio because they can't currently be built in Marketing Activities (e.g. images and email templates). Why and when do you move assets  between  marketing activities and the lead database?   I don't think we have ever done this. We try to build any lists/smart lists that would be referenced by multiple programs in the Lead Database from the get-go. ... View more

Thanks, Kevin! Good point about not adding another tool for them to use. ... View more

Hi Cat, Grace is spot on about the spam traps once being real email addresses. Like us, you probably have alumni who forget to update their contact information. (I've seen Compuserve email addresses!) In addition those who opened and clicked the few emails you have sent out from Marketo, you may be able to rule out potential culprits if you have any records of recent alumni interaction (e.g. donations, event registrations and/or email replies using the email address that's in Marketo). If you have the email reputation powerpack (add-on with Marketo), a trick we've used is to include first name in the subject line, as subject line is listed in the spam trap hits - if they have an unusual name, it's easier to pinpoint. In the absence of these options, you could also try sending emails in small batches to help narrow down to the spam trap. Recipients of an email that didn't hit a spam trap could be eliminated as potential culprits...at least for now. ... View more

Saving for reference! That's a good point about refreshing the CoE periodically to match what is needed/used at the present time. ... View more