Knowledgebase

Sort by:
Overview Marketo launched the new Email Editor 2.0 with the Spring ’16 release. Email Editor 2.0 is fully backward compatible with Email 1.0 emails and Email 1.0 email templates and also provides a large number of added capabilities. For this reason, after June 18th Email Editor 1.0 and Email Template Editor 1.0 will no longer be available within the Marketo application. All Marketo subscriptions that have yet to enable Email Editor 2.0 will be seamlessly transitioned to Email 2.0 on this date. Note: This change is not tied to a Marketo Release. What are some benefits of using Email Editor 2.0? With Email 2.0, you will enjoy a more modern experience and even more capabilities when editing emails in Marketo. Here’s what you’ll see in your Marketo Engagement Platform: Modules: Defined at the template level, modules are sections that group content elements (images, text, etc.) you can add to your email assets. You can also clone the modules within your email asset, or place them in the most convenient location. Learn more about modules here: Add Modules to Your Email Variables: Email Editor 2.0 allows you to define variables within the email templates that you can reuse within the template or within email assets built based on the template. If necessary, users can modify the variable’s value when building emails. Variables come in several types like String, Color, Image, etc. We are confident variables will help you reduce errors and easily customize emails. Visit: Email Template Syntax - Variables for an in-depth review of email variables. Enhanced Editing Experience: The new Email Editor 2.0 also comes with an improved Email Previewer, which will allow you to see how your email would look like on a desktop and on a mobile device; a new Email Template Picker, so you can easily identify and select the template to start building emails, and a collection of fully responsive “Starter Templates” free of charge. For more information, please see our Email 2.0 Spring '16: Overview recorded session. Deprecation Details The ability to use the Legacy Email Editor 1.0 will be removed from the UI on June 18, 2019. Any emails created or edited after June 18, 2019 will automatically open the new Email Editor 2.0 version. Note that the Marketo APIs (Direct Writes & Clone Programs) will issue warning notifications to help you identify assets still needing to be upgraded to Email 2.0. Any 1.0 assets will still be usable in campaigns! They will simply be converted to the New 2.0 version the next time they are edited and approved (steps on how to do this are outlined below). While the UI will remove the option for users to create templates in the legacy editor, the APIs supporting the Legacy editors will not be removed from Marketo until the January 2020 release. Any assets that are not converted to the New Editor after January will not be usable and unavailable for conversion.  After deprecation, attempts to write to or clone Email 1.0 assets will result in errors instead of warnings. Recommendation We recommend that your team enables 2.0 and gets familiar with the newest email editor prior to the June 18, 2019 UI deprecation date, to not only ensure they’re comfortable continuing to build and edit assets in Marketo, but also take advantage of the enhancements and added features mentioned above.  Frequently Asked Questions (FAQ) How do I know which email editor I’m using? There are 2 ways to figure that out: 1. In the Email section within Admin, select the ‘Edit Email Editor Settings’ option. The application will display a dialog window and indicate the email editor configured for your Marketo subscription, as in the image below: 2. Edit an email asset and see what the editor looks like: Here’s the Legacy Email Editor: Here’s Email Editor 2.0: As a reminder, after June 18, 2019, any emails you created in Email Editor 1.0 will remain in your subscription and still function. However, you won’t be able to create any new emails with Email Editor 1.0. How do I convert my assets from using Email Editor 1.0 to 2.0? These steps below will guide you through converting any assets using Email Editor 1.0 to 2.0: 1. Confirm that you have enabled the New Editor (2.0) in your admin settings by navigating to the Admin Panel > Emails > Email Editor Settings > Select “New” > Save If you already are using the New Email Editor (2.0), then disregard this step 2. After identifying which assets require the conversion, please navigate to the asset in the Tree in Design Studio (or Marketing Activities if the asset lives in a program) 3. Right-Click on the Email and click on “Edit Draft” 4. The screen should now display the editor in the New Editor (2.0) 5. Make changes, if any are needed, and click “Approve and Close” 6. Now this email has been converted and you are free to use this email with Editor 2.0!
View full article
**Nov. 11, 2019 update: In a continued effort to integrate with Adobe's release structure, we are shifting the deprecation of TLS 1.0 and TLS 1.1 to January 13, 2020. To align with Adobe’s world-class standard for security, we will be deprecating support for Transport Layer Security (TLS) 1.0 and 1.1 starting December 13, 2019 January 13,2020.  Systems integrating with Marketo that are not compliant with 1.2 protocol could potentially lose access to Marketo Engage services.  To maintain your Marketo Engage access, please ensure that all client systems are TLS 1.2 compliant before January 13, 2020. For a list of TLS 1.2 compliant browsers and frameworks, see the tables at the bottom of this communication.   What is Transport Layer Security (TLS)?  Transport Layer Security (TLS) is a security protocol that provides privacy and data integrity between two communicating applications. It is deployed widely for web browsers and other applications that require data to be securely exchanged over a network. TLS includes two layers: the TLS Record protocol and the TLS Handshake protocol. The Record protocol provides connection security. The Handshake protocol enables the server and client to authenticate each other and negotiate encryption algorithms and cryptographic keys before data exchange.    Why is Marketo Engage making this change?  Most requests for Marketo Engage web services originate from TLS 1.2 compliant systems, with low traffic from TLS 1.0 and 1.1 systems. TLS 1.0 was first published in 1999, with newer versions 1.1 in 2006, and 1.2 in 2008. As technologies age, security threats evolve, and so must industry standards. To stay aligned and protect our systems from security risks identified with older TLS versions, we are mandating a minimum TLS 1.2 supported connection to ensure secure connections. There have been documented attacks against TLS 1.0 using an older encryption method and the older versions are more vulnerable than TLS 1.2. For more information, see Attacks Against TLS/SSL.   When will this change happen?  TLS 1.0 and TLS 1.1 deprecation will take place on January 13, 2020.  After the date of deprecation, you will not be able to connect to Marketo Engage services using browsers or applications not compatible with TLS 1.2.    Marketo Engage encourages users to quickly abandon older versions of TLS to avoid exposure to security vulnerabilities.      How does TLS affect you?  Marketo Engage services are web-based and can only be engaged through a secure network connection.  TLS helps ensure a secure and reliable connection between your browser or server and Marketo web services, which includes anything that uses Marketo’s API, such as REST, SOAP, Munchkin, RTP, Mobile, and more.   As technology evolves, security standards are upgraded to ensure higher levels of privacy and data integrity.  However, older applications are not updated to include the latest standards.  As the acceptable level of security rises, these older, less secure applications are left behind.    To be able to connect to Marketo Engage services, update your browsers and application frameworks to a version that supports TLS 1.2.    How does TLS affect your customers?  Marketo Engage landing pages will be served to your visitors through TLS 1.2 secured connections.  Any browser updated since late 2013 (except Chrome, updated since 2017) will be TLS 1.2 compliant; further, Apple, Google, Microsoft, and Mozilla have all announced their plan to completely disable TLS 1.0 & 1.1 support by the first half of 2020, so we expect very minimal impact to visitors. If visitors report a loss of connectivity to Marketo Engage hosted landing pages as a result of this change, they will need to update to a compatible browser version.    What error message will return to a non-compliant connection?  The exact error messaging returned depends on the browser or application framework being used to connect to Marketo Engage web services.  Some examples include but are not limited to:  Unable to connect to the service  Service not available  Error in connection  To resolve these errors, the browser or application framework must be updated to a version compatible with TLS 1.2.    TLS 1.2 Compatibility  Desktop Browsers  Desktop Browser  Compatible Versions  Release Date Google Chrome  V30+  March 20, 2017 Mozilla Firefox  V25+  October 29, 2013 Internet Explorer  IE 11  October 17, 2013 Microsoft Edge  All versions    Opera  V17+  October 8, 2013 Apple Safari  V7+  October 22, 2013   Mobile Browsers  Mobile Browser  Compatible Versions  Google Android OS Browser Android 5.0+  Chrome for Android  V30+  Firefox for mobile  V27+  Opera Mobile  V57+  Apple Safari  IOS 5+    Application Frameworks  Java  .NET  OpenSSL  Java 8, or later  .NET 4.6, or later  OpenSSL 1.01, or later  Java 7, with TLS 1.2 enabled in app  .NET 4.5, with TLS 1.2 enabled in app       
View full article
  Marketo's Email Delivery & Compliance Team often recommends that our customers send a reconfirmation message to a set of their inactive leads. This process is used as both a proactive strategy to ensure good delivery rates and as a response to blocklisting issues. For more information on this overall strategy search our Resource Articles for Blocklist Remediation. At its most basic a reconfirmation message request a lead takes an action to stay on your mailing list.  If they don't take that action they will be automatically removed from the mailing list. These types of messages don't usually get a high response rate because you are sending the reconfirmation message to people who have already shown to be disengaged from your marketing. However there are instances where some reconfirmation messages get a more enthusiastic response than others so we've put together some tips for making the most out of reconfirmation. Instead of marketing your company itself think of it as though you are marketing ENGAGEMENT with your company. While these ideas are similar, they aren’t quite the same. You want to frame this message with a sense of urgency to click a link. You also want to make it as easy as possible for someone to open the message and just click a link so they continue to stay engaged with your marketing.   Subject Line We recommend that you frame the subject line very clearly with something about “not missing out” or “staying informed”. The subject should create a compelling and specific call to action.  Some senders use an offer in the reconfirmation message to encourage action. Highlight this in the subject line if this is your approach. Examples We’ve Missed You!  Take Action continue receiving our offers! Last Opportunity to Stay Informed (Action Required) Free shipping plus save 15% on next purchase   From Address While you can use any From Address, we recommend that your From: label clearly identifies your company rather than using a lead owner name. A disengaged recipient is more likely to recognize “Your Company” than “Bob Smith”.   Email Content In the body of the message your call to action should be immediate and clear. Put the reconfirmation at the top of the message content. Some usability studies have suggested that two choices may be more successful than a single choice so consider a bolder reconfirmation link at the top and a smaller link or button lower to unsubscribe. The main priority is getting someone to stick around for more of your mailings. You may also wish to make a short value statement about the fantastic information that someone can expect to receive by staying on your list! There are a couple of reasons for these recommendations. The first has to do with making things easy for the blocklist operator. If during the resolution process they can look at the mail received by their spamtraps and immediately tell from the subject line that the message is a reconfirmation pass it will make it much easier for them to consider the data quality issue resolved because their spamtraps will not activate the reconfirmation link. Some of the less automated blocklists will not list a sender for a reconfirmation message that hits their traps so it's important that your cleanup action look like what it is. The second reason behind this advice is that many people just scan their messages and don’t read all the way to the bottom; if someone has to read through a long value proposition before realizing that they must click a link to continue to be subscribed to your email program you may lose more subscribers than intended. The faster and easier it is to click that link the more people you’ll retain! A lot of people scan over marketing offers and think about them for a while before taking an action. You want to interrupt that process and make it clear that action is required now whether or not they’re ready to make a purchase!   Examples of simple reconfirmation email templates More examples can be found in this other Community Resource “A Creative Re-Engagement Email Campaign” Email #1 Subject Line: Action Required to stay subscribed to COMPANY   [First Name]:   You previously expressed interest in receiving valuable information and/or offers from COMPANY that are specific to your field.  We’d like your permission to continue sending you relevant information via email so that you can stay up-to-date on the latest industry trends/topics of interest.   Please click “YES” below to continue receiving research and trends in your area of interest.  COMPANY subscribers receive exclusive benefits, including the latest research briefs, white papers and/or compelling offers or discounts for future purchases.   Please update your Communication Preference by [DATE/TIME] or this could be your last chance to receive any future research.  It only takes a moment to click one of the choices below.   YES, I would like to stay subscribed to the valuable information from COMPANY.   NO, I no longer wish to receive valuable and insightful offers from COMPANY.   Sincerely, COMPANY   ————–   Email #2   Subject Line: Your Subscription to COMPANY Industry Newsletter Expires Soon   [First Name]:   Our records show that you expressed interest in receiving industry information from COMPANY on [INSERT DATE].  Records indicate you have not read an email in [variable time frame], we do not want to bother you with emails you do no wish to receive so we want to confirm that you would like to remain subscribed to the COMPANY email program.   If you wish to be removed, you don’t have to do anything further.  However, if you do want to continue receiving email from COMPANY, please click the link to let us know:   YES, I would like to stay informed and continue receiving email from COMPANY.   Sincerely, COMPANY   ————–   Email #3   Subject Line: Your Subscription to COMPANY Has Expired   [First Name]:   Thank you for your previous interest in receiving valuable content from COMPANY.  Your subscription has now expired and you will no longer receive any future emails.   If in the future you would like to continue to receive email from COMPANY please click the link to sign up:   YES, I would like to receive email from COMPANY.   Sincerely, COMPANY     Other Resources Marketo Community Resource “A Creative Re-Engagement Email Campaign” http://www.spamhaus.org/whitepapers/permissionpass/ http://blog.deliverability.com/2013/07/do-you-know-whats-lurking-in-your-database-know-thy-data.html http://blog.marketo.com/2010/05/key-to-email-deliverability-is-reputation.html http://www.marketo.com/email-deliverability/    
View full article
Issue Issue Description You want to invite one user to your two (or more) Marketo instances.     Solution Issue Resolution All Marketo subscriptions come with the optional Universal ID feature. To setup users with the same "login" in both production and sandbox subscriptions (or Prod and Prod, or Sandbox and Sandbox) we will want to take these steps:  1. Create a new user in the "1st instance" (first is arbitrary, it is whichever instance you want to start with, and if a user already exists in this instance you can jump to step 3)  2. User is created: lets say for example the user "login" is: demouser@adobe.com with "email": user@adobe.com and password: 12345GoodPassword  3. We will then want to go into the second instance and invite a user with the same "login": demouser@adobe.com (you can use a different email or the same)  4. When that user receives the second invite they will want to set their password to be exactly the same as the password in the first instance: 12345GoodPassword  Please note: If after following these steps you want to reset your password, you can do so and would want to do so for both instances. To do so, you would want to input your "Login" after selecting the forgot password option. That will initiate the sending of an email to the email address you specified as your "email".  Who This Solution Applies To Marketo Users with Universal ID active  
View full article
In offering a premium email delivery platform to our customers we carefully monitor our IPs for listings on significant blocklists. When we find that one of our customers was responsible for a blacklisting we contact that customer and request some actions be taken to re-mediate the issue. The goal is to isolate potential spamtrap addresses and remove them. The group of addresses you select should be broad enough to capture those potentially bad addresses but small enough not to suppress a huge portion of your database. Step 1 Build an inactive Smart List using ALL filters Was sent email the day of and day before the spam trap hit (please contact support@marketo.com for the date of the trap hit if you do not have this information already.) Lead “was created” date is at least 6 months ago   Inactivity Filters  Not visited web page is “any”; constraint date of activity “in past 3 months” Not filled out form is “any”, constraint date of activity “in past 6 months” Not clicked link in email is “any”, constraint date of activity “in past 6 months” Not opened email is “any”, constraint date of activity “in past 6 months” If you have custom database fields that would show other forms of activity feel free to add this into your inactive Smart List to exclude active leads.   Step 2 Once you have created a smart list to identify these suspect leads remove them from your database. [Leads Tab > Lead Actions > Flow Actions] You’re Done!      
View full article
*Updated in September 2024   Quick points: Spamtraps are addresses owned by antispam organizations Emailing a spamtrap can result in your sending domain or IP to be blocklisted Maintain current, direct opt-in with an active lead database to avoid this Spamtraps are usually functional email addresses that can successfully receive a message.    What is a spam trap or spamtrap?   A spam trap, or spamtrap is an email address secretly owned by an antispam organization that is used to detect spam. Antispam organizations do not sign up for mailing lists, so they consider any email sent to these addresses to be spam. Once an email is sent to the spamtrap, the antispam organization that owns this address can/will blocklist the IP and/or domain that sent the email.   Email administrators purchase subscriptions to the data offered by blocklist providers and may use the lists to block all incoming email from listed IPs or containing listed domains. From the marketer’s perspective, this can mean a high number of bounced emails leading to low lead engagement, and ultimately to weak revenue performance.   There are three types of spamtraps – pristine traps, typo, and repurposed/recycled traps. A pristine trap is an email address that was never used by a person. A repurposed trap is an email address that once belonged to someone but is no longer a valid address; these addresses will bounce as bad addresses for at least six months before an antispam organization will turn them into live traps. A typo trap will contain a misspelled domain.   How can a spamtrap get into my Marketo lead database?   Purchased data Purchased data is unreliable and is high risk for your brand’s sender reputation.  The antispam community does not like the use of purchased data, so antispam administrators have made a concerted effort to get spamtrap addresses into the databases of data vendors. While data vendors may claim they provide opt-in data, you risk inadvertently purchasing spam trap addresses when using a data vendor.  A foundational strategy to maintaining healthy sender reputation is to gather email addresses directly from individuals alongside their consent to be enrolled in bulk email communication.   Sending unsolicited email is prohibited by the Adobe’s Acceptable Use Policy because this practice has a high risk of causing deliverability problems for your brand and the Adobe network.  To avoid spam traps, get direct opt-in before sending email. If you have purchased data in the past, we recommend setting any inactive purchased leads to marketing suspended or simply removing them from your database.   Old data Repurposed traps are email addresses that were once valid but are now owned by an antispam organization. This can happen when a company goes out of business; expired domains are often purchased by antispam organizations. Sometimes a company that has a direct partnership with an antispam organization will allow email addresses of former employees or users to become spamtraps. Because antispam organizations will generally make sure future spam traps return a bounce as bad addresses for at least six months before they become spam traps you can prevent repurposed traps in your database by emailing remaining engaged with everyone in your database at least once every six months.   To safeguard your sender reputation, avoid reengagement campaigns to addresses you have not contacted in more than six months.   Unconfirmed form entries People can unintentionally enter spamtrap addresses into forms either by mistyping their email or by intentionally using a fake email address that happens to be a spamtrap. If you use single opt-in, you risk adding spamtraps to your mailing list. This is more likely to happen if you are a B2C company or through the offer of gated content that requires an email address.   How can I identify spamtrap addresses?   Spamtrap addresses are considered trade secrets by the antispam organizations, and they are obscured by design. They do not share these addresses because their goal is for senders to change their mailing practices rather than to simply remove spamtraps from their mailing lists.   That said, one thing we do know about spamtraps is that they tend to be automated processes and do not engage. Spamtraps do not click links. You can use smart list filters to identify inactive leads in Marketo.   How can I prevent spamtraps in my database?   Maintain active, direct opt-in for all leads Don’t purchase data Email engaged contacts least once every six months Don’t add old data directly to your mailing list Suppress perpetually disengaged contacts Grant access to assets such as free trials and whitepapers as email links to discourage intentional use of fake email addresses on forms Use scripting on your forms to identify potential typos  
View full article
When trying to sync updates to your salesforce.com instance from Marketo you see the following error in the activity log : "Failed: INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITY" This is an error sent to Marketo from salesforce.com. There are a number of reasons why this error could occur but the root cause is always linked to the permissions of the Marketo user that you have set up in salesforce.com. INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITY means that the user who is trying to make the update does not have access to a related element that is required for the record to be updated and saved in SFDC. There are a number of specific examples of what might be the cause but these will vary from organisation to organization depending on the configuration of your salesforce.com. If you were to connect to sfdc as the Marketo user and try manually updating the same record that Marketo is trying to update then you will get the same error in the salesforce.com UI. Here are a list of some elements that you should check in SFDC if you see this error: Do you use record types? If so make sure that the the Marketo user has access to all required record types. Are there any look-up or master detail fields on the object in question? If these types of fields are being updated then make sure that the Marketo user has access this object/ these records. Do you use Apex? If so you may have trigger that fire on the the update of a record, you will need to make sure that the Marketo user has profile access to the relevant Apex classes. If you have any workflow rules or assignment rules that send an email when the record is saved then you will need to make sure that the Marketo user has the send email permission and has access to the email folder that contains the mails that are sent rules are triggered. Make sure "Convert Leads" is turned-on within SFDC.  If it is not, you will get this error message when trying to merge leads that exist within Marketo and SFDC. Is this article helpful ? YesNo
View full article
Included in this article: Overview To provide world class product support, Marketo occasionally disables old areas of the product that have been replaced by newer, improved versions. As previously announced with the Winter ’17 release, we’re updating the way you’ll edit text and create new forms in Marketo. After August 1st, our legacy text editor will be retired and we’re deprecating the Form Editor 1.0. Here’s what you’ll see in your Marketo Engagement Platform: New Rich Text Editor: Enjoy a more modern experience and even more capabilities when editing text in Marketo. We’re retiring the Legacy Text Editor and transitioning all Marketo customers to the new editor – no action is required and your existing assets will not be impacted. Form Editor 2.0: Create all your new web forms with the Form Editor 2.0, giving you an improved WYSISYG editor, the ability to create draft forms and more. We’re deprecating the older Form Editor 1.0, making Form Editor 2.0 the way you’ll create all new forms in Marketo. Any forms previously created in Form Editor 1.0 will remain functional and editable, however these v1.0 Forms will no longer be officially supported by Marketo. To continue receiving support for your Marketo forms, we encourage you to create new forms in Form Editor 2.0 to replace your v1.0 forms. Email Editor: There are no changes to the Email Editor experience. The changes above do not impact the Email Editors. Rest assured, both Email Editor 1.0 and Email Editor 2.0 remain available for your use. For more information, please see our Innovations Update: New Text Editor & Form Editor 2.0 recorded session. Note: This change is not tied to a Marketo Release. Legacy Rich Text Editor On August 1, 2017, we’re switching all subscriptions to the new text editor. This change won’t have any impact on your day-to-day work. The new editor can do everything the old one can—and more. See Using the Rich Text Editor for details. After the change, nothing will happen to your existing assets, but you’ll see the new editor whenever you edit text in Marketo. How do I know which text editor I’m using? Open an editable text section in any Marketo editor to see which one you’re currently using. Here’s the old editor: Here’s the new one: Note: The legacy text editor used default root block settings of <p> for email/snippets and <div> for landing pages. If you’re upgrading for the first time to the new text editor, it will continue to have those settings. Click here to learn more about the root block setting. Form Editor 1.0 When creating a new form, some older Marketo customers have a choice of using the original Form Editor 1.0 or the newer Form Editor 2.0, which is the default selection. After August 1, all customers will only be able to create new forms using Form Editor 2.0, which contains additional functionality. After the change, any forms you created in Form Editor 1.0 will remain in your subscription and still function. However, you won’t be able to create any new forms with Form Editor 1.0. Recommendation We recommend that before the sunset date (August 1, 2017), you make sure that your team is up to speed on the newest text editor and form editor, to be sure they’re comfortable continuing to build new assets in Marketo.
View full article
  When a new lead enters Marketo from a form fillout or List Import, Marketo automatically searches for a lead with the same email address.  If that lead exists, the existing lead is updated instead of creating a duplicate. However, Marketo does not automatically de-duplicate leads who are already in your database. This is especially a problem for new customers who often have many duplicate leads in their database. Also, if you add a new lead directly into Salesforce (through the Salesforce import process or web-to-lead forms) Salesforce will create a duplicate lead that gets synced into Marketo. When this happens, you can use Marketo to find and fix those duplicates.   How Marketo handles duplicates   The primary consequence of duplicates is that one lead record could have the most relevant information about that lead while your sales rep is looking at the incomplete duplicate.   For example, say that you have a duplicate lead in your database and that lead fills out a form on your website. Marketo generally updates the lead record that was most recently updated. In another case, say you run a campaign to email your lead database and two duplicates are included in your campaign run. Marketo automatically detects the duplicate email address and ensures that only one email is sent to that lead. That Email send and subsequent activity will be attributed to the Lowest Lead ID.   When you merge leads, their entire history is combined, and you can control which fields are kept in the final lead. You won't lose any information or tracking.   Most customers have many duplicates when they start with Marketo. After initially de-duplicating your database, the work to keep your database de-duplicated is usually very small. You should work to stop the sources of duplicate leads and make Marketo your single point of entry for all new leads.   Finding Duplicates   Go to the Lead Database section of the app. Then click on the Possible Duplicates list in the tree. Click the grid header that says Email.  You can sort by email address to see the duplicates next to each other. Selecting multiple leads Select two leads that have matching email addresses.  You can do this by holding the "control" key down while clicking on the two different leads.  (You can merge more than two at a time, but start with two.) Tip: Sometimes clicking too fast will make the grid select incorrectly.  Clicking a little slower usually helps. When you have two rows selected or highlighted, click the Merge Leads button in the toolbar.   The Merge Dialog A dialog will appear showing you all the fields that differ between the two leads.  You need to pick which values to keep in the merged lead.  Not every field is displayed -- just the ones that you need determine appear. By default, the values from the most recently updated lead will be selected (with a check and highlighed yellow). To pick a different value for the merged lead, click the checkbox next to that value. If you want to enter your own values for the merged lead, click the Custom field for that row then type in your own value: When you're done, click Merge.  The winning values will be kept in the merged lead; the other values will be discarded. Important: Clicking merge will instruct Salesforce to merge the records properly.  All Salesforce and Marketo activities are merged into the remaining lead.  Nothing is lost.  Campaign History is also kept.   Duplicate pattern matching You will notice that the Possible Duplicates list has a Smart List tab.  Click on the Smart List and you will see it's using the "Possible Duplicates" filter on the "Email Address" field. You can change this filter to search other fields for duplicates. Click the little green plus in the definition. Note: You should use only one Duplicate Fields filter in your Smart Lists.  If you want to check multiple fields, always use the green plus button to add multiple fields; don't drag in a second filter. When you change the Duplicate Fields filter, you should sort the Leads grid by the column you're checking to put the duplicates next to each other. Marketo Merge Program Marketo offers a service for mass-merging of duplicates.  Please contact your Customer Success Manager to inquire about this service. What happens when I merge two leads in Salesforce? When you merge leads or contacts in Salesforce, Marketo will also merge the matching leads in your lead database. See this article to learn more about how that works: https://docs.marketo.com/display/public/DOCS/Find+and+Merge+Duplicate+People#FindandMergeDuplicatePeople-EffectinSalesforce      
View full article
Issue You have been receiving form submissions that appear to have bogus/nonsensical data in the fields, such as "kjsag@sm4.to" for email address, or "111-111-1111" for phone number, or in a Comment field other random nonsensical text.     Solution Currently, there are no default settings in Marketo that prohibit a form submission if the required fields are filled out. A great workaround for addressing these bogus form submissions in Marketo is to implement a 'honeypot' field on the form. To do this, you will need to create a custom Marketo field, string type, and name it something distinctive (such as "spam" or "honeypot"). After creating this field in Marketo Admin > Field Management, place this new field on the form as a hidden field. Real live end-users do not see hidden fields, but spam bots will see them and fill out all available fields. So now when we see form fills with this honeypot field "not empty," we know that it was a bot fillout.   Setting up the Honeypot Field Say that you have a Trigger Campaign that's having some issue with these spam/bogus form fills. In the flow of this campaign, you can add a flow step at the top: Remove from Flow, with a Choice.   Choice: If Honeypot field Is not empty, then remove from flow Default: do nothing   This way, the lead record is removed from the flow. You can also have other campaigns to handle these bogus form fills, such as a daily recurring batch to delete the record.   Other Options Another method of dealing with bot fillouts is to enable a reCaptcha. In fact, a very prolific Marketo user has written custom code that you feasibly could use to enable a reCaptcha on the form! Check this out: https://codepen.io/figureone/pen/meybqN?editors=0110    
View full article
What’s changing? On February 21, 2019, Webkit announced the new release of Safari’s Intelligent Tracking Prevention (ITP), known as ITP 2.1 and ITP 2.2 shortly thereafter. With ITP 2.x, all persistent client-side cookies, i.e., non-session cookies created via JavaScript through document.cookie, are capped to a seven-day or one-day expiry.  Mozilla Firefox and Google Chrome have also announced their intent to conform to these new policies, though no details or dates have been released.   How does this impact Web Personalization? As a result of these changes to the cookie policy, 7 days after their initial tracked visit to your domain, the RTP cookies of visitors using Safari (or future affected browser versions) created with the existing versions of RTP JavaScript will expire, and on subsequent visits, they will be tracked as a new visitor.   How does RTP operate? On a person’s first visit to a page where rtp.js is loaded, a new anonymous person record is created in Marketo Web Personalization. The primary key for this record is the trwv.uid which is created in the user’s browser. All subsequent activities on Campaigns, Rich media and Recommendation bars are recorded against this anonymous record. In order to be associated with a known record in Web Personalization Marketo, one of the following methods should be used: The person may visit a Munchkin-tracked page with a mkt_tok parameter in the query string from a tracked Marketo email link. The person may fill out a Marketo Form. REST Associate Lead call must be sent.   Once one of these actions is completed, the cookie and all its associated web activity will be associated with the known record.   How is Marketo planning to address ITP concerns? Marketo will implement a new web service to allow RTP cookies to be set with a Set-Cookie header via HTTP response, so that they may bypass the 7-day expiry cap imposed when setting cookies via JavaScript.   Do I need to do anything to take advantage of these updates? If you have incorporated the changes as part of the Munchkin update for ITP (which was rolled out in the last release) then you do not have to take any action. Please refer to this link for details : https://nation.marketo.com/t5/Knowledgebase/Browser-Cookie-Updates-How-Marketo-Munchkin-Is-Affected/ta-p/251524   If not please follow the below steps: In order to leverage the new behavior and take advantage of the greater expiry period and tracking capabilities, ensure that you have configured the following: A Landing Page CNAME Secured Landing Pages (i.e. HTTPS) For external pages, you must have configured a Landing Page Domain or Domain Alias with a Top-Level Domain (TLD) matching the external domains which you wish to track For example, if you have pages on the domain www.example.com which are tracked, you must have configured an LP Domain or Alias which is a subdomain of example.com, like munchkin.example.com   What happens if I do nothing? RTP’s ability to track users across sessions on the same domain will remain limited by ITP to either 1 or 7 days based on the browser and browser version used by the visitor. As of this posting, this only affects visitors using the Safari browser, although Chrome & Firefox may follow suit with their own versions.   When will the solution be launched? All customers should expect to have the solution with the Jun 2020 Marketo release.   Note: Please feel free to refer the link for the munchkin update for ITP which was part of the earlier release: https://nation.marketo.com/t5/Knowledgebase/Browser-Cookie-Updates-How-Marketo-Munchkin-Is-Affected/ta-p/251524    Google Chrome Update (Feb. 2020): Google recently announced that the Chrome browser will block all third-party cookies within two years; however, since Marketo uses 1st party cookies, this update regarding 3rd party cookies will NOT affect your Marketo tracking efforts. For further context about 3rd party cookies in general, and the industry shift away from using them, please see the following article for Adobe's stance across the Experience Cloud Solutions: https://medium.com/adobetech/an-adobe-perspective-google-chromes-announcement-on-the-future-limits-o...        
View full article
  So you’ve now used the previous document (Getting Started With Guided Landing Pages:) to download a template from our library and set it up in your Marketo instance, you have even used it to make a landing page or two and you’ve customized those landing pages, AND you’ve even gone the extra mile and customized your template and modified some elements! (Editing Marketo Guided Landing Page Templates, Pt. 1 - Elements:) All of which is fantastic news! Good job!   But if you recall from the article that showed you how to edit Elements on the template, I skipped right over the section on Variables. This is the piece that this document is designed to tackle.   So what is a variable? If you edit a Guided Landing Page you will see a panel on the right hand side that displays both Elements and Variables. In this instance, the variables do everything from assigning a gradient color, to deciding if you want to display or hide different sections of the landing page.   Modifying a variable in the landing page editor is designed to be really simple, just click the variable you want to change and give it a new value. Here I changed the Primary Gradient 1 and 2 from 1DA083 and 0F3450 to A00E35 and F2F2F2 respectively and the landing page changes:   At its easiest to understand, a variable works a lot like a token in an email. It’s a placeholder for actual code to be used later. So if I create an email that starts with “Hello, {{lead.firstname:default=Friend}}!” you can tell right away what that’s going to do. Pull the first name from the lead record, if none exists use the word “Friend”.   Think of a Variable as a token that you get to define as well as use. The first step is to define it and the second step is to actually call back to the variable you defined.   While it’s easy for a non-technical user to use a variable (as it should be!), setting one up in the template does require a fair amount of HTML knowledge. As stated before, if you are not comfortable editing HTML and do not have a resource available to you, please reach out to services@marketo.com, they are able to assist with any sort of coding needs.   So as before, let’s dive into the template, this time we’re going straight for the Variable code.       <!-- Marketo Variable Definitions -->     <meta class="mktoColor" id="gradient1" mktoName="Primary Gradient 1" default="#1da083">     <meta class="mktoColor" id="gradient2" mktoName="Primary Gradient 2" default="#0f3450">   So right at the start of the template, we’re off to the races defining variables. As you can see with the Gradient 1 and Gradient 2, these are both marked with a class of “mktoColor”.   As with the Elements, the full list of Variable types can be found here: https://docs.marketo.com/display/public/DOCS/Create+a+Guided+Landing+Page+Template        class : "mktoString"      class : "mktoColor"      class : "mktoBoolean"   A string is a variable that contains a value, Color should be obvious what that does and Boolean is a yes or no choice.   In addition to the class, each variable has to have a unique ID. This is critical and used when the variable is called later on down the page. When you call a variable it’s always with the syntax of ${id name}. So in this case ${gradient1} and ${gradient2}. As you can see it looks a LOT like a token but it’s a token you can name whatever you want.   The mktoName is how it displays the variable in the Landing Page editor.   The default value is what it starts out with.   So let’s take a look and see how these Gradients are applied now that they’re defined at the top of the template.   Color is typically used in the CSS portion of the header. As defined in the previous document, CSS stands for “Cascading Style Sheets” and is a way of formatting the same thing over and over again, kind of like setting a font in a word processor.       /* Header Gradient */     #is {         top: 0;         width: 100%;         min-height: 620px;         position: relative;         z-index: 1;         color: #fff; padding-top: 10%;                 background-image: linear-gradient(${gradient1},${gradient2});     }   Now normally in CSS, the linear-gradient option would have two colors listed, the top color and the bottom color and it provides a gradual transition from one to the other.   We could just as easily change this in the template to        background-image: linear-gradient(red,white);   But the problem doing that is that an end user, who is only using the Landing Page Editor, would not be able to change it. The gradient would be defined in the template and inaccessible to the Editor.   Changing these values to the variables defined before allows the user to change the first and second colors in the Landing Page editor interface.   In Summary:   The Meta Tags define what the variables mean:     <meta class="mktoColor" id="gradient1" mktoName="Primary Gradient 1" default="#1da083">     <meta class="mktoColor" id="gradient2" mktoName="Primary Gradient 2" default="#0f3450">   The ID= is then used to call the variable and put it into action:       background-image: linear-gradient(${gradient1},${gradient2});   The other benefit to doing it this way is you can re-use the same variable over and over again. Look at this piece of CSS:   body {                 background: ${gradient2};         margin: 0;         color: #696E74;     }   That’s the same ID as the gradient we used before, only applied to a different section. This ensures that the bottom color of the gradient and the background of this section will always be the same color.   Any item in the CSS that contains a text value, a color value or a yes/no choice can be converted to a Variable.   Here’s another common usage:   You’re using a form on your landing page, but you want the end user to be able to change the text on the submit button.   As before you define the variable:        <meta class="mktoString" id="section4ButtonLabel" mktoName="Sec. 4 Button Label" default="More Questions?">   Then farther down the page where the button appears you call the variable you defined before:        <div class="centered mtb">           <a href="${section4ButtonLink}"><button class="btn btn-lg btn-green mt">           ${section4ButtonLabel}</button></a>      </div>   The <a href= is pulling a http link that the user can define in the editor, the button class is setting up a green button as defined in the CSS, and there is our Variable to display the label which reads “More Questions?” Here’s what it looks like in the editor:   So this is great, and it makes sense because you can see this was all set up and defined by a professional. What if you wanted to add your own? Is that even possible?   Naturally it is!   First, figure out what you want to convert to a Variable. Is it a piece of text like a button name or a link? Is it a color? Is it a yes/no choice?   Let’s say we want to add a variable that controls the color of the buttons. We have two, both using the same color green, and we want whoever is running the landing page editor to change that without having to go to the template:   Step 1: Define your variable:        <meta class="mktoColor" id="ButtonColor" mktoName="Button Color" default="#1DA083">   We’re talking about colors so the class will be “mktoColor”. The ID can be anything we want it to be as can be the mktoName. The default is the same lovely green shade as was used before.   Now we need to call this color.  Looking at the CSS, we can see the .btn-green is defined as this:        .btn-green {           border: 4px solid #1da083;           border-radius: 60px;           color: #fff;           background: #1da083;           -webkit-transition: none;           -moz-transition: none;           transition: none;      }   The background is the color we want to change to a Variable so it can be edited without having to access the template.   Change the code to this:        .btn-green {           border: 4px solid #1da083;           border-radius: 60px;           color: #fff;           background: ${ButtonColor};           -webkit-transition: none;           -moz-transition: none;           transition: none;      }     Approve the template and check out the landing page in the editor:     Well that’s fantastic, but there’s a separate color for the border, we could just as easily add a variable for it as well:        border: 4px solid #1da083;   We don’t want to HAVE to add another new variable for just the border. We could change the border at the same time as the button. By changing #1da083; to ${ButtonColor};   The trick now becomes what if you change your mind? What if you have a variable in the template that is no longer desired? How do you get rid of it?   Remember each variable is two pieces, the definition and the call. You have to remove BOTH pieces. Technically removing the call would be enough to prevent the change from being made on the page, but the definition is what makes the variable appear in the Landing Page Editor, if you only removed the call then there would be a non-functional Variable in the landing page editor.   So in the case of our button color:   Step 1 would be to strip out the meta tag containing the definition:     Step 2 would be changing the variable name where it’s being used to some fixed value:        .btn-green {           border: 4px solid #1da083;           border-radius: 60px;           color: #fff;           background: ${ButtonColor}; -> change this to some other fixed color. #00FF33; or the original #1da083;.           -webkit-transition: none;           -moz-transition: none;           transition: none;      }   Doing both pieces will prevent the Variable from being listed in the Landing Page Editor and prevent it from having any effect on the page.  
View full article
Included in this article Overview Marketo uses a set of fields to capture certain kinds of marketing related information. If you would like this data in Salesforce, please follow the instructions below. Create three custom fields in Salesforce on the lead and contact objects: Lead Score, Acquisition Program, and Acquisition Date. Map these custom fields between leads and contacts so that on conversion in Salesforce, the values carry over. You can create other additional fields, if necessary (see the table below). All of these custom fields are optional and are not required to sync Marketo and Salesforce. As a best practice, we recommend that you do create fields for Lead Score, Acquisition Program, and Acquisition Date. Add Marketo Fields to Salesforce Add three custom fields on the lead and contact objects in Salesforce listed above. If you want to add more, see the table of available fields at the end of this section. Perform the following steps for each of the three custom fields to add them. Start with Lead Score. 1. Log into Salesforce and click Setup. 2. In the Build menu on the left, click Customize and select Leads. Click Fields. 3. Click New in the Custom Fields & Relationships section at the bottom of the page. 4. Choose the appropriate field type (for Lead Score — number; Acquisition Program — text; Acquisition Date — Date/Time). 5. Click Next. 6. Enter the Field Label, Length, and Field Name for the field, as shown in the table below. Field Label Field Name Data Type Field Attributes Lead Score mkto71_Lead_Score Number Length 10 Decimal Places 0 Acquisition Date mkto71_Acquisition_Date Date/Time Acquisition Program mkto71_Acquisition_Program Text Length 255 7. Click Next. 8. Specify the access settings and click Next: Set all profiles to Visible and "Read-Only". Uncheck "Read Only" for the profile of your sync user. Often customers have a user with the profile of a System Administrator as the sync user. If that's the case with you, then uncheck “Read Only” for the System Administrator profile as shown in the picture below. If you have created a custom profile for the sync user, then uncheck "Read-Only" for that custom profile 9. Choose the page layouts that should display the field. 10. Click Save & New to go back and create each of the other two custom fields. Click Save when you're done with all three. 11. In the Build menu on the left, click Customize and select Contacts. Click Fields. 12. Perform steps 3 through 10 for the Lead Score, Acquisition Date, and Acquisition Program fields on the contact object, just as you did for the lead object. 13. Optionally, use the above procedure for any additional custom fields from this table.      NOTE: These fields are additional optional fields you may choose to add as well. The Lead Score, Acquisition Date and Acquisition Program fields      are detailed above Field Label Field Name Data Type Field Attributes Acquisition Program Id mkto71_Acquisition_Program_Id Number Length 18 Decimal Places 0 Original Referrer mkto71_Original_Referrer Text Length 255 Original Search Engine mkto71_Original_Search_Engine Text Length 255 Original Search Phrase mkto71_Original_Search_Phrase Text Length 255 Original Source Info mkto71_Original_Source_Info Text Length 255 Original Source Type mkto71_Original_Source_Type Text Length 255 Inferred City mkto71_Inferred_City Text Length 255 Inferred Company mkto71_Inferred_Company Text Length 255 Inferred Country mkto71_Inferred_Country Text Length 255 Inferred Metropolitan Area mkto71_Inferred_Metropolitan_Area Text Length 255 Inferred Phone Area Code mkto71_Inferred_Phone_Area_Code Text Length 255 Inferred Postal Code mkto71_Inferred_Postal_Code Text Length 255 Inferred State Region mkto71_Inferred_State_Region Text Length 255 Map Custom Fields for Conversions A custom field on the lead object in Salesforce should be mapped to a contact field on the contact object so that data is carried over when a conversion occurs.  1. In the top right corner, click Setup. 2. Type "Fields" into the Nav Search without pressing Enter. Fields appears under different objects; Click Fields under Leads. 3. Go to the Lead Custom Fields & Relationships section and click Map Lead Fields. 4. Click the drop-down next to the field you want to map. 5. Select the corresponding contact custom field. 6. Repeat the above steps for any other fields you've created. 7. Click Save when you're done. Here's a video of the entire process that should make it easy to follow along: Salesforce Connector Setup
View full article
Issue Customers on Shared or Trusted IPs are able to set up additional branding within the Marketo sending infrastructure.  You are able to set up a branded 'envelope_from' so the From Domain used by the Marketo sending servers is associated with your brand instead of with Marketo. This enables you to further isolate your sending reputation to your own brand and email activity.  This can improve delivery rates to email networks looking for this level of alignment (generally smaller B2B domains but this can also help with AOL and Gmail).  Branded 'envelope_from' is also key for authentication using DMARC, as it will allow you to align the domains in your email headers.     Solution Issue Resolution Marketo's default envelope_from (also known as return-path) domains include: San Jose datacenter - @em-sj-77.mktomail.com London datacenter -  @eu-lon-188.mktomail.com Ashburn datacenter - @potomac1050.mktomail.com Sydney datacenter -  @snsmtp.mktomail.com   Process: To implement this, first reach out to your CSM to confirm that branded return path addresses are included in your Marketo package.  Branded return path for instances on a Shared IP would be a paid addition to your Marketo Subscription.  There is no charge for instances on the Trusted IP range. Then you will need to chose a sub-domain of your choice for this branding, and set up 2 DNS entries depending on which datacenter your Marketo instance is on:   -If your Marketo instance is on the shared range in San Jose, the configs would be:    IN MX (your subdomain):  em-sj-77.mktomail.com    IN TXT (your subdomain) “v=spf1 include:mktomail.com -all”   -If your Marketo instance is on the shared range in Ashburn, the configs would be:    IN MX (your subdomain):  potomac1050.mktomail.com    IN TXT (your subdomain) “v=spf1 include:mktomail.com -all”   -If your Marketo instance is on the shared range in London, the configs would be:    IN MX (your subdomain):  eu-lon-188.mktomail.com    IN TXT (your subdomain) “v=spf1 include:mktomail.com -all”   -If your Marketo instance is on the shared range in Sydney, the configs would be:    IN MX (your subdomain):  snsmtp.mktomail.com    IN TXT (your subdomain) “v=spf1 include:mktomail.com -all” Once that DNS setup is completed, submit a case to Marketo Support with those details and we can complete the process by implementing that branding for your instance's emails.  
View full article
  Welcome to Marketo Support This guide provides individual links that covers the following topics: Marketo Support Policies Service Level Agreement How to Contact Marketo Support How to Submit a Case Tips on Effective Case Submission Managing Authorized Support Contacts (Support Admins) Managing Your Cases How to Escalate    
View full article
Overview GoToWebinar is changing their authentication protocol used for API access. Their legacy protocol, OAuth v1.0, will no longer be used after January 31, 2019, and all services accessing GoToWebinar (Marketo) will be required to use the new authentication protocol, OAuth v2.0. Marketo has already updated our system to utilize the new OAuth v2.0 authentication protocol for new login authentication. All newly initiated service authentications between Marketo and GoToWebinar will use OAuth v2.0. However, all existing GoToWebinar services currently logged in and in use now must be reauthenticated manually. All customers who use GoToWebinar must reauthenticate each of the logins for these services in your Marketo instance by navigating to Admin > LaunchPoint. Any API calls still using OAuth v1.0 after January 31 will fail. This will result in statuses not being shared between Marketo and GoToWebinar and will prevent users from syncing Event programs with a GoToWebinar event. FAQ Why is this change happening? GoToWebinar is strengthening their security protocols for API login access to their services. This requires using an upgraded version of the login protocols, known as OAuth v2.0. Is this a Marketo change or a GoToWebinar change? This change is being implemented by GoToWebinar to strengthen their security protocols. Marketo has upgraded our system to allow a seamless transition, but the protocol change is being made by GoToWebinar. When does this take effect? The new protocol version OAuth v2.0 is active and in place now. GoToWebinar has placed an announcement on their status page stating that the deprecation of the legacy OAuth v1.0 is scheduled for January 31, 2019. All connections between Marketo and GoToWebinar that are still using the legacy OAuth v1.0 protocol will be refused by GoToWebinar after that date. This includes new access requests as well as those currently active and in use. What do I need to do? Reauthenticate your GoToWebinar services with a fresh login from within your Marketo instance before January 31, 2019. Why do I have to do it myself? Marketo has made the changes necessary to utilize OAuth v2.0 for new authentication logins being made moving forward. However, all logins already in use were initiated on the older protocol, OAuth v1.0. Marketo doesn’t know your personal login credentials, so you need to do the reauthentication directly. Is there a different procedure for how to enter the credentials inside the Marketo UI? No. The update Marketo made was on the back end, so there is nothing different to how you enter the info. The UI is the exact same as it was. What happens if I don’t reauthenticate the login before January 31, 2019? All connections between Marketo and your GoToWebinar services will be refused by GoToWebinar on their end. If I miss the deadline and the connection is shut off, how will I know? You’ll find error messages in your Marketo instance where the services are used. See the section below for “Symptoms of a disconnected service” to know what to look for. If I miss the deadline and the connection is shut off, how do I get it working again? Reauthenticate your login credentials in Admin > LaunchPoint. See the “Customer Action Needed” section below for step by step directions. Customer Action Needed All customers who use GoToWebinar must reauthenticate the login credentials for each user. This must be done before January 31, 2019 to avoid experiencing disruption of your services. 1. Navigate to Admin 2. Click LaunchPoint to open the list of Installed Services 3. Click and open the GoToWebinar service to edit it 4. Click the Log into GoToWebinar button. 5. In the GoToWebinar Sign In pop-up window, enter your GoToWebinar email and password and click Sign In. 6. After the window closes, click Save DONE! By reauthenticating the login, you’ve ensured that the service is using the new OAuth v2.0 protocols. Symptoms of Disconnected Service Here is a list of what to expect if the integration with GoToWebinar is disconnected due to the deprecation of OAuth v1.0 on January 31, 2019. 1. The service listing in Admin > LaunchPoint will have a status of Failed along with a few details. A. Reauthenticating your login credentials will resolve these errors. 2. Event programs that have not yet synced with GoToWebinar will be unable to sync and will return errors. A. Reauthenticating your login credentials will resolve these errors. B. For reference, here is the documentation on how to sync an Event Program to GoToWebinar. 3. Existing programs which were synced with GoToWebinar prior to the deprecation will show no difference. However, if anyone is added to the program with a ‘Registered’ status, Marketo will attempt to push this record to GoToWebinar and will fail due to the deprecation of the OAuth v1.0 protocol. This will give the record a status of ‘Registration Error’. If this occurs, this data is not lost. A. Reauthenticate the GoToWebinar service B. Manually refresh the webinar attendance. Navigate to the Event Actions menu of your Event Program and select Refresh from Webinar Provider 4. Records that were already registered with GoToWebinar before the service stopped will still be able to receive the correct {{member.webinar url}} token. That data for the token will already be in Marketo, so reminder emails will still have the right links to the actual webinar even if the service was stopped after they were registered. The attendee report won’t be able to come down from GoToWebinar with the connection cut off, but at least your leads will still have the link to get to the webinar. 5. If the service is no longer active and an existing webinar completes, normally this would record attendance information and sync this back to Marketo and change the status of program members. However, if the service is inactive, this will fail silently, and no status change will occur. Manually refreshing from webinar provider will also silently fail if done while the service is still inactive. The notification will show that there are no updates. A. Reauthenticate the GoToWebinar service B. Manually refresh the webinar attendance. Navigate to the Event Actions menu of your Event Program and select Refresh from Webinar Provider C. Now that the credentials were reauthenticated and the service is back online, the manual refresh will work properly. How to Get Additional Help Feel free to ask questions in the comments section of this documentation. Our Support team will be monitoring the comments to help answer your questions. You can also Contact Marketo Support at any time.
View full article
Marketo calls to the Salesforce API During a single sync session, Marketo makes 25 API calls to check if your Salesforce objects need updating.  Because your Salesforce sync happens in 5 minute intervals (default setting), each day Marketo makes 7200 API calls to your account to see if any updates are needed. If there are updates, more API calls are used to sync the information.  Leads, Contacts, Accounts, Opportunities, Campaigns, and Activities are synced in batches of 200 per API call. If you use a Sync Lead to SFDC or Add to Campaign flow step in trigger campaigns, each one uses at least one API call per lead; the API call happens when the lead hits that flow step (instead of waiting for the next sync). Batch campaigns can send up to 200 leads to Salesforce with 1 API call for these flow steps. Any activities you've synced from Marketo to Salesforce (like "Filled Out Form" or "Opened Email") use an extra API call per event. You can use these to estimate the number of API calls Marketo makes per day.  For example, if you have 1,000 Lead and Contact updates a day and 100 Account, Opportunity, and Campaign updates, you'll use: 7200 (check for updates) + (1000 Lead updates / 200 per API call) + (1000 Contact updates / 200 per API call) + (100 Account updates / 200 per API call) + (100 Opportunity updates / 200 per API call) + (100 Campaign updates / 200 per API call) + 7200 + 5 + 5 + 1 + 1 + 1 = 7213 API calls When you first sync your Salesforce account to Marketo, you'll use significantly more API calls until Marketo is up to date with your Salesforce instance.  After that, you can expect the API calls to be much lower unless you make large updates to your leads (in Marketo or Salesforce) API Calls and your Salesforce edition Salesforce determines your API call limit based on the edition and licenses you have. This document from Salesforce has information on how they calculate that limit. For many Salesforce users, particularly Enterprise Edition users, the number of API calls made by Marketo is usually not a problem. If you're using a more limited edition of Salesforce or don't have many Salesforce licenses, you may hit the daily limit on your API calls.  In that case, please contact Marketo Support and ask us to decrease your sync interval.  At a 30 minute sync interval, Marketo uses around 1000 API calls per day, well under the limit for nearly every Salesforce edition. To see your API limit (per 24 hour period) and your current usage (for past 24 hours) in SFDC,  navigate to: Setup -> Administration Setup -> Company Profile -> Company Information Look for the field called "API Requests, Last 24 Hours", which will display API usage for the past 24-hour period as well as your current 24-hour limit (in parenthesis). Order of Events during SFDC Sync Marketo will sync your SFDC and Marketo objects in the following order: Lead: synch schema Account: synch schema Contact: synch schema User: synch schema Task: synch schema Opportunity: synch schema Opportunity Contact Role: synch schema Campaign: synch schema Campaign Member: synch schema Campaign Member Status: synch schema Lead: pull conversions Account: pull deletes Account: pull updates User: pull updates Lead Queue: pull updates Lead Status: pull updates Account Type: pull updates Lead: pull deletes Contact: pull deletes Lead: pull updates Contact: pull updates Lead: push updates Contact: push updates Campaign: pull deletes Campaign Member: pull deletes Campaign Member Status: pull deletes Campaign: pull updates Campaign Member: pull updates Campaign Member Status: pull updates Opportunity: pull deletes Opportunity Contact Role: pull deletes Opportunity: pull updates Opportunity Contact Role: pull updates Event: pull updates Task: pull updates Email Template: push new Email Template: push updates Task: push new Task: push updates
View full article
*Updated in September 2024   What is a feedback loop (FBL)? An FBL is an arrangement between an email sender, such as Marketo, and an Internet Service Providers (ISPs) or email hosting service.  The FBL allows the email sender to be automatically notified when the user who receives an email marks it as spam.   When a lead who uses one of these ISPs clicks the spam button for an email, the ISP sends an automated notice to Marketo. Marketo automatically unsubscribes the lead with the unsubscribe cause, "Customer Complaint Received from ISP".  Marketo's Email Compliance Team also logs these complaints for internal compliance monitoring.     What FBLs is Marketo enrolled in? By default, all emails sent by Marketo are covered by an FBL with the following email providers: Bluetie/Excite Comcast Fastmail Gandi.net Italiaonline Lapost.net Liberomail Liberty Global Locaweb Mail.ru* QQ.com* OpenSRS/Tucows Rackspace Seznam.cz SFR SilverSky Swisscom Synacor Telenet Telenor Telstra Terra TIM Unitymedia UPC United Online/Juno/Netzero Virgilio Virgin Yahoo! Ziggo Zoho.com   *The FBLs for Mail.ru and QQ.com can only be set up for customers on dedicated IPs.  Please reach out to Support if these Russian and Chinese ISPs respectively are targets for your email program.   Notably, Gmail does not offer a traditional FBL. They have a similar offering that Marketo has evaluated and determined does not meet the needs of our clients at this time.  Google does offer Postmaster Tools that allow senders to monitor their complaint rate and other reputation information.  Senders can sign up here:  https://gmail.com/postmaster/   
View full article
Marketo campaign queues work like a mall parking lot.  We accommodate average and even above average loads.  But if it's Christmas, you may have to wait a while for a spot.   The campaign execution queue When a flow is launched, Marketo assigns it a priority then queues it for execution.  This priority is based on how the campaign was launched (batch, trigger, resume from Wait) and what's in the flow: Priority level Priority criteria High Send email (triggered) Send alert Medium Request Campaign Interesting Moment Create Task Convert / Delete Lead Add to / Remove from List Change Sales Owner / Progression Status / Revenue Stage / Field in Program Change Member of / Add to / Remove from Sync to SFDC Change Status in SFDC Campaign Low Change data value Change score Wait steps with a wait time > 5 minutes Web hooks Marketo then executes campaigns based on priorities.  High priority campaigns run first in the order they were added to the queue.  Once those are finished, the next highest priority campaigns are executed in time order and so on down until all have completed. If the queue contains only low priority campaigns and a new high priority campaign comes in, the high priority campaign will jump to the head of the line and run next. Batch campaigns and trigger campaigns are run and processed in separate queues.   "Why is my campaign running slow?" Several factors determine how fast and when your campaign will run.  In general, campaign execution time depends on: The campaign's priority The complexity of the smart list filters being used - See Best Practices for Smart Lists The number of records that qualify for the campaign The number of flow steps used in the campaign The complexity of Choices in the flow steps   Even though Marketo can execute many campaigns simultaneously, there are only so many resources available to process smart campaigns. Also, certain campaign flow steps take longer to process, than others.  The flow steps below take longer than most, and you may notice that difference when executing your campaigns: Send Email Delete Lead Sync Lead to Sales Add Lead to SFDC Campaign Call Webhook   Speeding up your campaigns Here are some tips to speed up how and when your campaigns are executed: Do essential flow steps first If this is an auto-response or notification campaign, put the Send Email or Send Alert flow step first.  Absolutely do this if you're using two slow steps in a row (Send Email followed by Sync Lead to Sales) so that the email goes out with the highest priority. Don't start with a "Wait" step If you need to delay the launch of your batch campaign, use the batch campaign scheduler.  Re-think any triggered campaigns that start with a "Wait" step because it will be prioritized lower; you probably don't need to include it anyway. If you have a wait step of longer then 5 minutes this will cause all flows below it have a low priority.
View full article
  What is a Blocklist? Can I Still Send My Emails, or Are You Blocking Me from Sending? What Is a Spamtrap and Why Do They Matter? Can You Give Me the Spam Trap Address That Triggered the Blocklist So I Can Remove It from My Database? Can You Give Me More Information regarding the Blocklist Issue? What Is the Quarantined IP Range? I Sent This Email Campaign a While Ago. Why Am I Only Getting Notification of the Blocklist Issue Now, and Am I Still Blocklisted? The Blocklist Notification Went to the Wrong Email Address. Why Was It Sent to That Address? Which blocklists should I be concerned about? - Top Blocklists – What You Need to Know How do blocklist issues get resolved? What steps do I need to take to resolve the blacklist issue? - Blocklist Remediation      
View full article