One-to-One Personalization Feature Overview

Digesto One-to-One Personalization allows for a single email to go out with personalized content matching a given person’s preferences. When Digesto runs on your chosen schedule, emails will be tailored to subscribers’ specific categories and/or authors selected, meaning each subscriber only receives updates on the posts that they are interested in.

On this page, you'll find all the technical specifications, requirements, and more.

Digest Processing Steps

	Digest Test (Test button)	Digest Schedule (Prod)
1. Get Content	Digesto gets the most recent content on your feed up to the "Max Posts" that you have configured on your Digest and proceed to #2.	Digesto looks for newly published content on your RSS feed. If new content is detected since the last scheduled run, it will retrieve it, up to the "Max Posts" that you have configured on your Digest and proceed to #2. If no new content was published, it will stop here until the next scheduled run.
2. Build Recipients List	Not applicable during test. Digesto will send the test to all recipients in your test smart campaign.	Digesto will fetch all subscribers and identify leads that have at least 1 preferences that matches the newly-published content (from #1). This step involves: a) Import the list of all blog subscribers from the relevant Marketo list into Digesto. b) Verify the match of preferences on each person record against the newly-published content for this particular run. c) If a minimum of one person in the list has at least one article that matches preferences Digesto Imports the recipients list in Marketo - the “Qualified” subscribers Static List, the logs will indicate "No Lead Matching Criteria".
3.Build (Clone) Program	Not applicable during test. Digest will schedule the test campaign in your original\template program.	Digesto will clone the Marketo Template Program
4.Build Content	Digesto converts the RSS feed into proprietary scripts and passes is to the template program tokens.	Digesto converts the RSS feed into a proprietary scripts and passes is to the cloned program tokens.
5.Schedule Delivery	Digesto will schedule the "Test" smart campaign to get your email delivered to your test recipients.	Digesto will schedule the "production" smart campaign to get your email delivered to qualified subscribers.
6.Content Personalization	if the recipient has preferences matching any article(s), only these articles will be displayed. If no match ifs found, all articles will be displayed.	As the email is compiled, if the recipient has preferences matching any article(s) only these articles will be displayed. If no match ifs found, the recipients should not receive an email.

Client-Side Requirements

A dedicated Marketo API Role, User and Web service must be configured with the following permissions:
Access API
- Activate Campaign
- Approve Assets
- Execute Campaign
- Read-Only Campaign
- Read-Write Assets
- Read-Write Person
A dedicated MERGE user with email [yourcompany@mergeworld.com] - Exact email to be confirmed - must be created for our consultants to be able to access your Marketo Instance and perform all the following tasks (permissions) - Typically this requires a "Marketer" Role :

Access Marketing Activities
- Edit Marketing Asset (Create and Edit Folders Create and Edit Programs)
- Activate Trigger Campaign
Access Design Studio
- Access Email
  - Edit Email - Gives users permission to edit, create, and clone emails
    Approve Email - Enables users to approve emails.
- Access Email Template
  - Edit Email Template - Edit, create, and clone email templates
  - Approve Email Template
Access Database
- Create and Edit Static Lists
Blog/News Feed Articles to be distributed must be “tagged” or “categorized” in your Content Management System (CMS) - Ex: WordPress - with the required dimensions for personalization (Categories and/or Authors) and your RSS/Atom feed must contain these elements in the designated feed elements: - For Categories, this corresponds to “<category>” in RSS feeds and “<category term>” in Atom. Learn more about feed elements supported by Digesto here.
- For Authors, this corresponds to “<author>” or “<dc:creator>” in RSS and “<name>” as sub element of “<author>” in Atom.
Subscription preferences for each of Categories and Authors must be stored on the Person record, each in a dedicated field. Values must be stored in a Marketo field (“Text Area” is recommended) and be formatted semi-colon separated value (standard format for multi-select Marketo form fields). Ex: Account-Based Marketing; Data Management; Data Quality
The values stored in person record and it's equivalent rss feed for Categories or Authors cannot use semicolon characters ";" nor pipe characters (|). These characters are reserved to be use as delimiters.
For the email to display personalized content, the values stored on the Person record field (for Categories or Authors) must exactly match the Categories identified in RSS/atom feed element (case sensitive). The articles will display if ANY of the values on the Person record date matches ANY of the corresponding values in the feed elements.

Limitations

Marketo API limits and fees may apply including the following:
- Daily Marketo API calls: this is typically set to 10 000 calls per day by default. This limit is shared across all web services - increase is available to purchase from Marketo.
- Digesto uses bulk lead export to get all subscribers. Daily Lead Export is Maxed to 500mb. This limit is shared across all web services. Increase is available on purchase from Marketo. (Note: for a Digesto export, 500mb would represent approximately 5 million records.)
- Digesto uses bulk lead import to identify qualified subscribers for each email delivery. Lead Import is Maxed to 10MB size. Digesto is currently limited to using this function with a maximum of approximately 250 000 subscribers.
You may contact your Marketo Account Manager for more details or to request an increase to these limits.

Personalization is limited to a single dimension (or single level of category values). Therefore, if you need to use two or more dimensions (Ex: Content Type and Category) - all related values must be stored as a string of unique value on the Person record field, as well as on your RSS\Atom Feed.
For example, if possible values are:
Content Type: Webinar; Whitepaper; Video
Categories: Artificial Intelligence; Internet of Things; Robotics,

If an article can be displayed to a person that has ANY dimensions matching preferences, the data on Person record and your RSS/Atom must be stored as semi-colon separated values:
Webinar; Internet of things; Robotics

But If an article must be displayed only to a person that has BOTH dimensions, the data on Person record and your RSS/Atom Feed must be stored as combined values:

Webinar - Artificial Intelligence
Webinar - Internet of Things
Webinar - Robotics
Whitepaper - Artificial Intelligence
Whitepaper - Internet of Things
Etc.

Digesto is currently limited to sending a Max of 100KB of content for each email. This typically results in a maximum that varies between 8-25 posts that can be distributed in a single email, depending on the length of the content included for each post.
Marketo native A/B Testing functionality cannot be used. Legacy A/B Testing should be supported. Learn more about using A/B Testing with Digesto here.
General Digesto Known Limitations:
- Your Digest (feed content) design is setup once and will repeat for every post with the same formatting.
The feature to “Disable Clone” is not supported with One-to-One, therefore each email will be sent from a cloned version of your original Marketo Program.

Resources

Book a Demo