Marketo token reference
Personalizing your emails is a great way to engage and connect with your subscribers. FeedOtter allows you to personalize your emails with Marketo tokens directly in the app using custom fields. Here’s how you can use Marketo personalization tokens in FeedOtter.
Most Common Marketo Personalizations
These are the most commonly used tokens we see in our FeedOtter emails for Marketo that are the perfect way to add some customization and uniqueness to your emails.
Person Marketo Personalization Tokens
Person Marketo personalization tokens refer to the information associated with the subscriber receiving your email. These tokens are great for inserting unique, personal touches to your email to reach your subscriber.
Company Marketo Personalization Tokens
These tokens look at the company details of the subscriber receiving the email. You can use these for personalization in the header and footer of your emails as well.
Other Marketo Personalization Tokens
Marketo has plenty of personalization tokens for your emails and allows for specific tokens for smart campaigns such as system update tokens, trigger tokens, program tokens and campaign tokens.
For example:
Custom Marketo Personalization Tokens
Marketo also has options for custom personalization throughout your Marketo instance. Custom Marketo personalization allows you to get creative and make your email communications extra unique and engaging for your subscribers.
Custom Field Tokens
Marketo allows you to add custom fields to subscriber information which can later be used in your email communications.
If you have a custom person field, the token will read:
If you have a custom company field, the token will read:
My Tokens
My tokens are created in Marketo programs or campaign folders and are custom variables anyone with access to your Marketo account to create and use.
My tokens will look like this:
Member Tokens
Member tokens are used to add unique information from integrated service partners; most commonly used for unique webinar URLs for attendees.
For example:
The token above automatically resolves the person’s unique confirmation URL generated by the service provider.
NOTE: It’s important to remember these tokens will only populate if the smart campaign that sends the email is a child asset of the Event Program.
Last updated