Product Documents

Sort by:
April 2021 Update   In November 2020, we announced that we will forbid programmatic Form POST submissions to our /save and /save2 endpoints beginning May 7, 2021. The reason for this change is to reject methods of unsupported form submissions used by bots to fill customer databases with spam data.   We understand that many customers may need more time to update the integrations to use a supported method such as the Forms2.JS API or the Submit Form REST API endpoint. We have decided to extend the deadline in which we will begin blocking all programmatic Form submissions to take place on October 15, 2021. Programmatic FORM submissions continue to be unsupported and while we are temporarily delaying enabling validation to reject these submissions, we cannot ensure uninterrupted submission following  upcoming product and infrastructure changes.   For customers that still wish to block this method of form submission to address bot attacks,   will allow you to opt-in to form submission validation on your subscription. This validation will check that form submissions are coming from Marketo Forms, Forms2.js API, or the Submit Form REST API and will reject it otherwise. This is expected to block many common sources of bot attacks.   However, if you have a form integration that currently uses programmatic Form POST to submit lead data, enabling this feature will also block your Form submissions. We encourage all customers to migrate to a supported method of form submissions as soon as possible to protect their subscriptions from bot attacks.   The original announcement is below for reference. The details remain the same aside from the schedule to block programmatic form POST submissions.   What’s changing? In our May 7, 2021 release, Marketo Engage will be making changes to our form platform to protect the stability and security of our infrastructure:   Forms 1.0 will be fully deprecated, resulting in loss of functionality of any remaining Forms 1.0 assets still in use. Marketo Engage will begin rejecting form submissions made through unsupported methods, such as programmatic form POSTs to the leadCapture/save and leadCapture/save2 endpoints.   Why is this change being made? On August 1, 2017, Marketo Engage deprecated the Forms 1.0 editor, removing the ability to create or edit Forms 1.0 assets. This change will complete our end of life efforts for Forms 1.0.   In addition, we have found that our Form endpoints “leadCapture/save” and “leadCapture/save2” are common targets for bot attacks. To protect the stability of the Marketo Engage infrastructure, and to aid customers in maintaining a clean database, we are completely disabling the “leadCapture/save” endpoint and enforcing checksum validation on the “leadCapture/save2” endpoint.   What customer action is required? Forms 1.0 deprecation Provisioning of Marketo Engage subscriptions with the ability to create Forms 1.0 assets ended December 31, 2014. If your subscription was provisioned after this date, then it will not have Form 1.0 assets. Forms 2.0 assets will be unaffected by this change.   Marketo Engage subscriptions provisioned before December 31, 2014 may still  be utilizing Forms 1.0 assets on their landing pages and website. These forms will need to be remade in our Forms 2.0 editor and replaced wherever they are still being used.   Programmatic Form POST deprecation Some integrations may be performing programmatic form POSTs to “leadCapture/save" or “leadCapture/save2” to submit data into Marketo Engage databases. This method of data ingestion has always been unsupported and will cease to work as part of this deprecation. All integrations using programmatic form POSTs must be updated to use our Forms 2.0 API, Push Lead REST API, or the Submit Form REST API endpoint releasing in the January 2021 release.   Customers using native Forms 2.0 assets on pages and/or the Forms 2.0 API do not need to take any action. Checksum validation will work natively with these supported methods.   What happens if customers don’t act? Customers that fail to replace any in-use Forms 1.0 asset with a Form 2.0 asset will find that their customers will be unable to submit to their 1.0 Forms.   Customers using integrations that perform programmatic Form POSTs to the “leadCapture/save” or “leadCapture/save2” endpoints will see these integrations fail, resulting in loss of form submission data.   Is my Form 1.0 or 2.0? Forms 1.0 and Forms 2.0 have different look and feel:   Forms 1.0 Forms 2.0 Marketo subscriptions provisioned after December 31, 2014 will only have Forms 2.0 assets.
View full article
In late 2020, Apple announced their intent to  add a new feature to their Intelligent Tracking Prevention implementation  in Safari  called  CNAME Cloaking Defense , to be rolled out with the release of Safari and IOS 14 .   Like  many of the other efforts in Apple’s Intelligent Tracking Prevention schemes, t his feature is designed to  limit  the lifespan of cookies set by hosts which have a CNAME  pointing to a domain name which does not match the visited page’s domain name  to seven days .    Since Munchkin JS  uses  cookies  set by  a CNAME, and the underlying host to which the CNAME  ({your instance }.mktoweb.com )  points   will never match the  domain name of a visited  page ,  cookies set by Munchkin in Safari 14  browsers  will be capped to a  seven-day  lifespan.    While the reduction in cookie lifespan will have some effect on tracking known leads , traffic from Safari generally  represents  less than 10% of requests handled by Munchkin.        T he re are no apparent easy solutions to this  issue,  and each would require  significant intervention  both  on the part of  Adobe engineering and  subscribers .    Adobe will continue to explore long-term options for improving consistency and accuracy of web tracking behaviors, but at this time we have decided not to t ake any extraordinary measures to try to circumvent this change and restore  long lifespans for Munchkin cookies.  Instead,  we have decided to  focus  on  our efforts  to  integrate  Marketo  web tracking with the  Adobe Web SDK   so that all Adobe  Marketo  En gage  customers  can benefit from our best-in-class web tracking solution.   We will have more information to share when we are closer to release of this solution.  
View full article
In 2021, Marketo Engage will be making changes to the URL structure for Landing Pages, Forms, and Images & Files assets.   Why is this change being made? Technical Details Landing Pages Images & Files Forms What customer action is required?   When is this change being made? Starting January 21, 2021, we will begin gradually provisioning new Marketo Engage subscriptions with the new URL structure. On March 5, 2021, all new Marketo Engage subscriptions will be provisioned with the new URL structure in place.   For existing Marketo Engage subscriptions, we will begin gradually rolling this change out beginning April 1, 2021. More details on our rollout timeline will be released in March, 2021.   April 2021 update Starting in March 2021, a subset of new Marketo subscriptions will be provisioned with the new Design Studio URL structure. Beginning with our May 7th release, all new subscriptions will be provisioned with the new Design Studio URL structure.   Existing subscriptions will be gradually migrated through a rollout beginning May 20th.    Why is this change being made? When a Marketo Engage subscription is not configured with a branded CNAME, Design Studio assets use a common hostname shared among all customers on the same pod. This behavior can be exploited in a phishing attack where a user cannot be sure a link to a Marketo Engage hosted asset belongs to the business they expect it to belong to. By updating each instance to use its own unique hostname, it is clearer to users the destination of URLs they are accessing.   Technical Details Landing Pages, Form embed code, and resources stored in Images & Files will have URLs updated from a hostname shared among all subscriptions on the pod to a hostname unique to each Marketo Engage subscription. Subscriptions configured to use a custom CNAME for their landing pages will be minimally affected by this change.   Landing Pages Subscriptions without a configured landing page domain Landing page paths will change to a unique hostname for your subscription. Before: http://na-sj01.marketo.com/lp/123-ABC-456/unsubscribePage.html After: http://123-ABC-456.mktoweb.com/lp/123-ABC-456/unsubscribePage.html   Subscriptions with a configured landing page domain Landing pages will continue to load from your configured landing page domain. No changes will be made. Before: http://example.marketo.com/unsubscribePage.html After: http://example.marketo.com/unsubscribePage.html   Images & Files Subscriptions without a configured landing page domain Paths to resources stored in Images & Files will change to a unique hostname for your subscription. Before: http://na-sj01.marketo.com/rs/123-ABC-456/images/cuteKitten.png After: http://123-ABC-456.mktoweb.com/rs/123-ABC-456/images/cuteKitten.png   Subscriptions with a configured landing page domain Resources stored in Images & Files will continue to load from your configured landing page domain. No changes will be made. Before: http://example.marketo.com/rs/123-ABC-456/images/cuteKitten.png After: http://example.marketo.com/rs/123-ABC-456/images/cuteKitten.png   Forms Subscriptions without a configured landing page domain OR subscriptions without landing pages secured by SSL Before:         <script src="//app-sj01.marketo.com/js/forms2/js/forms2.min.js"></script> <form id="mktoForm_1"></form> <script>MktoForms2.loadForm("//app-sj01.marketo.com", "123-ABC-456", 1);</script>         After:         <script src="//123-ABC-456.mktoweb.com/js/forms2/js/forms2.min.js"></script> <form id="mktoForm_1"></form> <script>MktoForms2.loadForm("//123-ABC-456.mktoweb.com", "123-ABC-456", 1);</script>           Subscriptions with a configured landing page domain secured by SSL In our October 2020 release, we updated our form embed code to load from the landing page domain when it is secured by SSL. No further changes will be made. Before:         <script src="//example.marketo.com/js/forms2/js/forms2.min.js"></script> <form id="mktoForm_1"></form> <script>MktoForms2.loadForm("//example.marketo.com", "123-ABC-456", 1);</script>         After:         <script src="//example.marketo.com/js/forms2/js/forms2.min.js"></script> <form id="mktoForm_1"></form> <script>MktoForms2.loadForm("//example.marketo.com", "123-ABC-456", 1);</script>           What customer action is required? Marketo Engage subscriptions provisioned after May 7, 2021 will have the new URL structure already in place for all Design Studio assets.   Existing Marketo Engage subscriptions will be migrated in a staggered rollout to the new URL structure during nightly maintenance cycles beginning on May 20th. There will be no downtime, but landing pages may experience a short period of degraded performance during migration.   Existing URLs and references will continue to work after the migration to the new URL structure. However, in 2022, we will deprecate the old URLs structure in use today. More details on our deprecation timeline will be provided in March 2021.   To begin preparing for this change, we suggest doing the following: Configure your Landing Page URLs with a CNAME https://docs.marketo.com/display/public/DOCS/Customize+Your+Landing+Page+URLs+with+a+CNAME Secure your Landing Pages with SSL https://docs.marketo.com/display/public/DOCS/Add+SSL+to+Your+Landing+Pages Begin updating pages where you embed Marketo Engage forms with the new embed code introduced in our October 2020 release (requires secured landing pages) Begin an audit of where you reference Design Studio assets on the web. This will help you begin a plan to update any existing references to our older URL structure before we begin deprecation in 2022. Generally this will be on non-Marketo pages, as our Landing Page editor will automatically format embedded images and forms in a compatible manner. Only references hardcoded to the old URL structure need to be updated, e.g.   http:// na-sj01.marketo.com /rs/123-ABC-456/images/cuteKitten.png. Relative references will continue to work without need changes e.g.  /rs/123-ABC-456/images/cuteKitten.png. Please work with your web developer to determine where you may need to make updates.
View full article
Deprecation of Email V1 began  almost  two years ago  and beginning with the  March  maintenance   release to London & Netherlands subscriptions on  March 17 th , 2021  and all other subscriptions on March 19 th , 2021 , all API support for V1  e mails will b e ended.  A fter this release,  any attempts to interact with V1 emails via the Asset APIs will result in errors and no actions taken .  All known remaining users since  February 24 th , 2021  have been notified ,  but  it is possible  that there are still integrations which may attempt to interact with these assets.  The most common types of affected integrations are services  which  offer digital  asset management, translation, and localization .     If you do observe integration failures as a result of this change,  you will still be able to upgrade problematic assets  by editing and approving them .  Once an email asset is upgraded to V2, you should be able to resume using it with integrated services.  
View full article
How does Marketo Engage define a Sales Insight “Active User”? If a sales rep has interacted with the Sales Insight panel in the last 30 days, we consider him//her to be an active user once we remove duplicates user.  Every week, we look at our logs over the last 30 days for certain types of activities that a unique user would do within our Sales Insight panel. Here is the list of activities that are considered as product usage: Marketo tab: Clicking on Best Bets tab and the following actions within the tab Clicking on Edit & Create New View Clicking on “Hide” option Clicking on My Watch List tab and the following actions with the tab Clicking on Edit & Create New View Clicking on “Remove” option Clicking on Web Activity tab and the following actions with the tab Clicking on Edit & Create New View Choosing time frame option from drop down Clicking on Anonymous Web Activity tab and the following actions with the tab Clicking on Edit & Create New View Choosing time frame option from drop down Clicking on My Email tab and the following actions with the tab Clicking on Edit & Create New View Clicking on email link to preview email Clicking on Lead feed and the following actions with the tab Subscribe to an Interesting Moment from lead feed Visualforce panel on Contact/Lead/Account/Opportunity: Clicking on 4 tabs: Interesting Moment, Web Activity, Email, Score Clicking on “Full List” hyperlink at the bottom of the visual force page to access full list Marketo tab Top Nav (only on lead/contact) Choosing “Add/Remove to watch list” from actions drop down, clicking on “Go” button Choosing “Add to Marketo campaign” from actions drop down, clicking on “Go” button Choosing “Send Marketo email” from actions drop down, clicking on “Go” button Clicking on Interesting Moment tab and the following actions with the tab Clicking on “Subscribe” option Clicking on Web Activity tab and the following actions with the tab Clicking on Web page link Clicking on page/referrer link Clicking on Email tab and the following actions with the tab Clicking on email link to preview email When a sales user navigates to any CRM layout that has Sales Insight, the panel loads automatically. The loading of panel is not considered as actual usage. We only consider users who actively interact with the panel.    How does Marketo Engage determine how many Sales Insight (MSI) users I have? We generate a report that logs certain types of activities that an “active user” would do and then remove duplicate users. If there has been one or more of these activities in the last 30 days, we consider this to an individual active user   How do I pull a list of my Sales Insight users? Please reach out to your CSM. He/she will be able to provide your usage report for you.   How do I limit Sales Insight usage? You can monitor Sales Insight seats by creating a Sales Insight profile and assigning it to a Sales Insight Layout or to any existing layout you would like to use. Detailed instruction can be found here - https://docs.marketo.com/display/public/DOCS/Setting+up+Sales+Insight+for+your+Team   How do I start monitoring Sales Insight seats as an existing user? The next time you upgrade your package, rather than installing upgrade for all users you can install it only for admins or for specific profiles you’ve created for Sales Insight. Detailed instruction can be found here https://docs.marketo.com/display/public/DOCS/Upgrading+Your+MSI+Package   How do I determine which version of MSI we are on? In your Salesforce CRM. Click on Set Up > Search for “Installed Packages” in Quick Find search field > Look for “Marketo Sales Insight” under Package Name column > Look for corresponding version number under “Version Number” column  
View full article
Support for Formula fields in batch campaigns was deprecated in 2013 and a notification was added to the product documentation here: Formula Fields. Currently, if a user attempts to schedule a batch campaign with an email that contains a formula field token WITHOUT spaces in the field name, the UI will show an error message saying this is not supported. However, due to an anomaly in the UI, if a user attempts to schedule a batch campaign with an email with a formula field token WITH spaces in the field name, the batch campaign will run. This UI issue was addressed in the January 2021 release of the product.   After March 19, 2021, these unsupported Formula Field tokens WITH spaces will no longer render correctly. Consequently, the tokens, and not the expected replacement strings, will appear in the final email. The deprecation is necessary to place all clients on a new, faster campaign processing platform.  To avoid further issues we recommend migrating the Formula Field tokens to Email Script Tokens immediately. Please refer to the following article which discusses how to use this option: https://docs.marketo.com/display/public/DOCS/Create+an+Email+Script+Token   If you have further questions about this issue, and/or best practices on migrating to Email Script Tokens, please contact Technical Support.  We want to ensure you have all the information you need to address the issue.   Kind Regards, The team at Adobe
View full article
Here are a few helpful tips regarding assigning a record to a queue when using the Sync Person to SFDC flow step:     If the record flowing through the flow step is a Marketo only record a new SFDC lead will be created SFDC Lead any field updates will be synced from Marketo to SFDC and the owner will change to the Queue SFDC Contact a new SFDC lead will be created The value in Marketo for Lead Owner for any records assigned to a SFDC Queue will be empty   Additional  resources   for learning about the Marketo integration with SFDC.
View full article
  The SFDC is Deleted field can be used to identify a SFDC Lead or Contact which used to be in SFDC but was deleted and now only lives in Marketo. Typically the record is deleted from SFDC for a specific reason and most customers will honor the deletion in SFDC by also setting up a smart campaign to also delete the record from Marketo.    If you decide to keep the deleted record (SFDC Lead or Contact) in Marketo to nurture it, the next time the record flows through the SYNC Person to SFDC flow step Marketo will insert it into SFDC as a new lead record. A strategy should be in place to make sure you're not syncing/inserting records you really don't want.   If you decide to delete a SFDC Lead or Contact in Marketo only you should only do it if you have a custom sync rule set-up. Otherwise the next time the record is updated in SFDC it will sync again to Marketo with a new Marketo ID.    Here are the steps to delete a SFDC record which is syncing to Marketo: Create Smart Campaign Set Smart List Set Flow Change Data Value of the "Sync to Marketo" field to False Wait 1 hour Delete record from Marketo only Schedule Run once     Additional  resources   for learning about the Marketo integration with SFDC.
View full article
If you create a multi-select field in SFDC, let's say it called "Product of Interest," it syncs as a string field in Marketo. If multiple values have been selected in SFDC, they will be separated by a semicolon, e.g. Frosted Flakes;Cheerios;Wheaties. If you use this field on a form, you will need to change the field type to Select to allow for multiple selections. If someone fills out the form and chooses Frosted Flakes and Cheerios, this will overwrite the existing values in the field and the field will now only say Frosted Flakes;Cheerios. These will resolve correctly in the SFDC multi-select field. If you don’t want to overwrite existing data create a Marketo custom field for your forms. Call It “Product of Interest for Web Forms” and set it up on the form exactly as you would have set up the multi-select field. Next create a smart campaign like the following in Marketo: Smart List: Trigger, Data Values Changes, Attribute – Product of Interest for Web Forms Flow: Change Data Value, Attribute – Product, New Value – {{lead.Product of Interest}};{{lead.Product of Interest for Web Forms}}. Now, if you fill out the form and choose Frosted Flakes and Cheerios on the form, the "Product of Interest for Web Forms" field will say Frosted Flakes;Cheerios and the Product field will say Frosted Flakes;Wheaties;Cheerios. This will resolve to the correct values in the multi-select list in SFDC.   Additional resources for learning about the Marketo integration with SFDC.
View full article
What’s changing?   Beginning i n  January 2021, we will  be  rolling out  two e mail tracking-related  security  improvements  over the course of several months .   In Q 3  of  2020 ,  a new  version of the Outlook Plugin will be available that also contains a security improvement.    This document serves to provide a high-level overview of the changes that are coming.  We will follow up with additional information as th ose  date s  draw near.     Background: Email Link Tracking   By default, links in emails have tracking embedded  which  allow s  you to see who clicked which link, how many total links were clicked, etc.   Link tracking is  configured  via the Insert/Edit Link dialog box  from within the email editor .     Predictive Image Tracking   When using Content AI, you can configure email images to be predictive.   Predictive image s have an URL and are   configured via the  “Make Predictive”  menu item within the email editor . Alternatively, you can  select  “Enable Content API” menu item within the email editor. Changes:   Tracking Link  Length   When link tracking  or predictive image  is enabled, the  original  URL specified is  converted into a “tracking link ”   that points  to a Marketo tracking server.  The format of  a  tracking link looks something like this:   http://mkto-q1234.com/Y0b020YU00000001NPR0wR0  After this change, the identifier  at the end of the URL will be slightly  longer .   Tracking Parameter Expiration   When a tracked link  or predictive image  is clicke d   from  within an email , the Marketo tracking server  logs a  “Click Email”  or “Click Predictive Content”  activity  and then  redirects  user  to the original URL  specified.   The tracking server appends   the “mkt_tok”  query parameter  which is  used  in conjunction with  Munchkin JS   to associate  the  Munchkin cookie with the   known lead that  clicked on the email link , and with the  campaign  that  sent  the email .    After  this change, mkt_tok  will expire  6 months after the email was sent.    As a result, if  a  lead  clicks on a link  in an email that is older than 6 months,  the webpage visit activity will be anonymous, and campaign  association will not occur.   This is  the same behavior as  when  tracking  is  disabled.   Outlook Plugin   With these changes a new upgrade of the Outlook plugin will be released. The new plugin will no longer support offline mode, and users will be required to have an active connection to the internet when sending emails. Users who do not have an active connection will see the following message when clicking the Marketo Send and Track button:       Why is this change being made?   The t racking parameter e xpiration  and tracking link change   are  additional step s   in providing a  more consistent and more secure experience with  Marketo’s  forms.   This change is a continuation of the work done last year when we released  Form Pre-Fill Feature Upgrade .   The  Outlook Plugin   update  was  made  to  standardize on using common  email  tracking-related  functionality  across  our  products.     What customer action is required?   Aside from the Outlook Plugin upgrade, no additional action is required.   The new plugin will be available as part of the Q3  2020  release so customers can upgrade. As part of the Q4  2020  release users will receive a message in Outlook asking them to upgrade before continuing to use the plugin.      How does this impact customers?   Tracking Links and Predictive Image s   If a tracked email link or  a  predictive image is clicked  by an anonymous lead  in an email that is over 6 months old,   the known lead will not be associated with user’s Munchkin cookie .  This is the same behavior  when  tracking  is  disabled.   Form Pre-Fill   If  a  tracked  email link or  a  predictive image  i s clicked  i n an email that is over 6 months old ,   and the  click   sen d s  user to a landing page  containing  a form with pre-fill enabled,  the form will not pre-fill.   This is the same behavior as  when  tracking  is  disabled .   Outlook Plugin   All users must  update  the Outlook Plugin   by  Q1 2021.  
View full article
The  Duplicate Fields  filter  can be used  t o identify duplicate person records based on a field.  Typically, the  E mail field is used for this purpose, but other fields may be used as well (Full Name, Last Name, SFDC Type, UpdatedAt).   In Q1 2021 we will be making a change to the  comparison  behavior of the Duplicate Fields filter.  The comparison will be case - sensitive for all fields except for Email.   Legacy Behavior Match was case-insensitive for all supported fields.   New Behavior Match remains  case-insensitive for Email field, but changes to  case - sensitive for  remaining  supported fields.   Example Here is a smart list named  “ Duplicates ”  that uses Duplicate Fields filter with Full Name filter.   Since l egacy behavior is case - insensitive,   the  two person record s below  qualify for the list .    This is because a case- in sensitive comparison between “ wilma  flintstone” and “Wilma Flintstone” is  true .   The n ew behavior is  that neither of the two person records above qualify for the list.   This is because a case-sensitive comparison between “ wilma  flintstone” and “Wilma Flintstone” is false.   Customer Impact If using  only the  Email field in Duplicate Fields filter, then no   impact .  If using any  of the  other  supported  fields , then fewer persons are likely to  match the filter .
View full article
During  2020, Marketo deployed infrastructure updates to improve batch campaign performance as described here.  As a result, there was a slight change in behavior when using Head Start for Email Programs.   Legacy Behavior The “Send Email” activity was generated when a campaign started executing at its scheduled time followed shortly thereafter by generation of the “Delivered Email” activity.    New Behavior  The “Send Email” activity is now generated when head start starts executing 12 hours ahead of scheduled time.  As a result, the “Send Email” activity is logged 12 hours earlier than it had been.  There is no change to the timing of the “Delivered Email” activity.   Example    Before Email Delivery - Email program scheduled time on Nov 6, 2020 at 1:30am EST with head start enabled - Initial status is “Waiting to run”  - Status changes to “Processing started, waiting to run” at Nov 5th, 2020 at 1:30pm EST   - Activity log “Send Email” at Nov 5th, 2020 at 1:29pm EST   - Email Performance Report shows Sent and Pending count    After Email Delivery  - Email Performance Report shows Delivered count and no emails in Pending   - Activity log “Email Delivered” is as expected at scheduled time   Customer Impact - Smart List Filters - If using “Was sent email” filter, this should be changed to “Was delivered email” filter - Communication Limits - Communication limits are calculated using "Send Email" activities so scheduling can be impacted - Email Performance Report - Emails remain in “Sent/Pending” state for 12 hours - Activity Log - "Send Email" and "Delivered Email" entries are now 12 hours apart
View full article
Forms serve as a valuable point of entry to your Marketo Engage database for your prospective and existing customers to express interest in your business. They also serve as a portal for malicious actors to flood your database with junk data, hoping to trigger emails to use in phishing attacks, to overwhelm your business services, or to DDoS our platform. We are rolling out enhancements to strengthen the security of Marketo Engage forms to address this growing problem in the industry.   These features are releasing throughout Q3 2020 and will be available to all Secured Domains for Landing Pages customers. No changes to your forms or landing pages are needed to take advantage of these enhancements.   EDIT: We have delayed the rollout of our form field validation to Q1 2021 to ensure a high level of quality.   Bot Spam Blocking We have identified bot patterns common among most spam attacks on Marketo Engage forms. These patterns were identified by examining form data captured in bot attacks for values that were impossible to have been submitted by a human submitter. This new feature will introduce server-side validation on standard Marketo Engage form fields that will reject submissions of illegitimate values that match these bot patterns.   Sever-side form field validation Today, Marketo Engage forms enforce field data rules with client-side Javascript validation that is easily circumvented by bots or users that disable scripting in their browsers. To address this, we are enhancing forms with server-side validation of form field rules. These include: • Validation of field type. For example, checkbox form fields must be submitted with boolean values; numerical form fields cannot contain alphabetical characters, etc. • Presence of required fields • Values in Select type fields must match the configured list of values • Configured max length of field value is not exceeded • Numerical values fall within the configured minimum and maximum values Submissions to Marketo Engage forms that fail validation will return an error with the offending field highlighted with an error message.    Frequently Asked Questions:   Can my business define its own custom logic for rejecting form submissions based on submitted field values? Unfortunately, not at this time.   Should my business continue to use CAPTCHA, honeypots, or Javascript validation on our forms? We anticipate these enhancements will reduce the need for solutions such as CAPTCHA or honeypots, but they can still serve as an additional layer of security against bots for your forms. Custom Javascript validation will continue to give your business granular control over form field validation on your landing pages and web pages.   Will you block specific IP addresses we commonly see associated with spam? IP addresses on the internet are often dynamic and are recycled by ISPs to be used by multiple devices. Blocking an IP address could result in legitimate visitors unable to fill out your forms. It is also trivial for an attacker to switch to a different IP address or use a distributed network of IP addresses to spam your forms, which makes IP address blocking an ineffective long-term strategy.
View full article
What’s changing?   On  October 16, 2020 ,  Marketo will deploy new versions of  line, bar, column and pie charts  throughout the  Marketo  Engage Application .  This includes all reporting features, as well as data visualizations that appear in the Marketing Activities screen.     How will this change impact customers?   Customer impact will be minimal.   The  content   of the new visualizations will be identical to  that of  the previous ones ,  with some impro vements to axis labels and legend positioning to maximize use of the plot area.     Why is this change being made?   The previous visualizations were implemented using Adobe Flash, which will reach its official end-of-life on December 31 st , 2020 , and as a result the charts needed to be rebuilt using a different charting library.     What customer action is required?   No customer action is required.  The new visualizations will automatically appear in the  Marketo  application following  Marketo’s  product release on  October 16, 2020 .  
View full article
What chang ed ?   Operators are used within Filters ,  Triggers , or Flow Steps   t o define selection criteria.    The list of operators  available  for  use  for  a  given  field  depends on  the field  type  (e.g. Integer, String, Date) .   A list of field types and their operators can be found  here .     In  the  June 2020 release, we removed both the “is” and “is not” operators for Float field types.  As a result, these two operators are  no longer  available in filters ,  triggers , or flow steps   that  use the  Float field .   Filter Trigger Flow  Step Wh at didn’t change (yet) ?   The “is” and “is not” operators still exist in Marketo Sky , but w e will be removing  them  as soon as possible.   Until the se operators  are removed ,  please  refrain from  selecting  them  within  the  Marketo Sky  interface .  Otherwise,  you  run the risk of adversely impacting your campaigns.   Why is this change being made?   Float fields store an approximation of a value, not the literal value.    For example, a float field could store  “ 10.5 ”  as  “ 10.5995485730481245 ”  or something similar.    So "is 10.5"  would not  qualify .    As a result, comparisons using “is” and “is not” were  not consistent .  In  some  cases,   comparisons  worked as expected, in others they did not.  To eliminate this  ambiguity , we removed these operators as choices.   What action is required?   If you are currently using “is” or “is not” operator for Float field in a filter  you must  change  your fi lter  to use  a  different  operator .   We recommen d  using either “between”  operator .   For example,  suppose  you  are  using   a filter with  “is” operator  to match  the number “10.5”. To correct, r eplace   ”is” with “between” and supply a range  that encloses  the number.  In this example we use the range  from  “10. 5 ” to “10.6” to enclose the number ”10.5”. How can I  determine if I am using “is” or  “is not”  operator with Float field?   1. G ather  a  list of Float fields  using  the Marketo REST API.  The  Describe  endpoint returns a list of all person fields  with their  data type s .  Search  the response  body  for “float” to identify  all  Float fields  in your instance.   2. I dentify places where a given field is used  by going to  Admin > Field Management  and search ing  for the  given  field name.  Select the field and  see  “Field Used  By” for a list of places where used. What if we don’t take this action?   Since  results  can be  inconsistent, you may not be identifying audiences  correctly .   Some persons could be  erroneous l y  included or excluded  from a campaign or smart list .    In addition, s ome trigger campaigns  could execute or not  execute  based on an inconsistent comparison.
View full article
[FAQ attached below this article]   What's Changing? On August 31, 2020, Marketo Engage will implement a new retention policy specifically for Sent & Delivered Email activities. Under this policy, data for these two activity types will be stored for a rolling 90-day period from the activity date for use in Smart Lists. This is a change from the current default retention period of 25 months, and from the current  Extended Data Retention subscription option period  of 37 months.   Upon the policy taking effect, data older than 90 days for these two activities will be deleted and no longer available for export. Any Smart List with the “Was Sent Email” and “Was Delivered Email” filters (including NOT Was Sent and NOT Was Delivered) should be updated to ensure the maximum lookback date is 90 days.  If the lookback date is greater than 90 days, the Smart List will continue to function, but only activities that are 90 days old or less will qualify.   Why? In 2020, we are improving critical parts of the underlying Marketo Engage infrastructure, including Batch campaign processing, similar to the Trigger campaign improvements made in 2019. This new infrastructure, in combination with the new retention policy, is expected to result in shorter lead time with large email sends and faster segmentation processing to deliver significantly faster processing to our customers. Note, the revised retention policy is one, among several, aspects that come together to deliver this improved performance, but broadly speaking reduced retention helps with faster database look ups and search across the run-time infrastructure.     What's NOT Changing? Aggregated data – including Reports, Dashboards, and Analytics – will not be affected by this change (unless they reference a Smart List with these activities).  The new policy will not affect any activity type other than Sent and Delivered (for example, Was Opened activity data is not affected). Further, this change does NOT affect Engagement Program casts.   What Customer Actions Are Needed? First, you'll want revisit where and how you're using these two activity types. Audit your Smart Lists and ensure the date ranges for these two activity types are less than 90 days - if you must use a date greater than 90 days, we suggest running a process to export to an external system. You will need to create this before the new retention policy takes effect on August 31, 2020.  Information on how to export activities using APIs can be found on our Developers Documentation website.   We appreciate you understanding as we move toward an enhanced Marketo Engage experience for all customers. Please download and review the FAQ attached below for further suggestions, workarounds and additional information.  
View full article
If you have not heard or seen it yet, in the Fall 2016 Release, we were super excited to launch our Content AI (Predictive Content) for Email. This included a revamp of the Content AI App (previously known as Predictive Content).   Content AI i s an Application Marketo offers that helps you auto-discover your content, engage your web visitors and email recipients with the most relevant, recommended content powered by machine learning and predictive analytics. See more in Docs here:Predictive Content - Marketo Docs - Product Docs   Here are regular FAQs on Content AI we hear from customers and those interested in the App:   General   Where do I learn more about Predictive Content? Marketo.com Website Product Page: Content AI Recommendations - Marketo Customer Success Story using Content AI : Case Study​ / Webinar Video​ Webinar: Behold the magic of Predictive Content​ Marketing Nation Summit 2016: Predictive Content: Amplify your content through machine learning Request a demo from your Account Manager   How do I find the Content AI App? Is it the same as Web Personalization? Content AI is a paid for stand alone App offered by Marketo. It is a separate product to Web Personalization. If you have purchased the Content AI App, you will see a Content AI icon on your My Marketo page. If you are interested in hearing more about the App, speak to your Account Manager.   Setup   Do I need the RTP Javascript tag to enable Content AI on my website and landing pages? The set up process for Content AI (See Getting Started Docs​) includes adding the RTP Javascript Code onto all pages of your website, including landing pages. This helps us to "listen" to your web activity, to auto-discover your content and display it on your web or email channels as Content AI outputs.   A re there any restrictions on where the content resides? Does that content have to reside in Marketo or can it be in any CMS? The RTP Javascript tag is agnostic to CMS platforms, meaning it works on all types of CMS platforms. Once the tag is on your site, we can discover and track all your content (PDF, embedded video, HTML pages) and use it for Content AI . So, the content does not have to reside on Marketo or Landing Pages or Design Studio. The Content AI part that the marketer prepares based on the discovered content and the part that is shown Predictive on your website or within an email is managed and controlled within the Marketo Content AI App.   Content Discovery   How does Content AI discover my website content? Marketo Content AI "listens" to your website activity, and when any web visitor clicks and views a specific content piece (HTML, PDF, Embedded Video, PPT) on your domain, we capture and discover the content title and content URL and start tracking the content's views and engagements. This  discovered content piece is then displayed under the All Content page. For set up details of Content Discovery see: Getting Started with Predictive Content.   Does the Content AI reporting also show which content has the highest engagement? Yes, the All Content page shows all web content (html pages, videos, pdf, etc...) on your domain that web visitors viewed. These results can be displayed from highest views to lowest.   On the Content AI page, the reporting shows how many web visitors or email recipients clicked on the Content AI piece and can also be sorted to see which was the most engaged piece of Content AI per channel (web or email) or overall.   Tracking Content   How many contacts or content do I need to start using Content AI ? Content AI relates to web content. Content Discovery will find in most cases, we have seen hundreds of content pieces on your domain. The marketer can then go ahead and approve and enable these discovered content pieces for Predictive Content. You can also manually add content pieces to the collection. It is recommend you have 10-15 pieces of content enabled for Predictive (for any channel) to start and keep adding more to this.   Can you create your own Conversion Criteria ? We track and display the views on content and also clicks on Content AI . In addition, the metrics we show are conversions (direct and assisted) per content piece, which shows attribution to the content piece in bringing in new People. Conversions : The number of visitors who clicked on recommended content and completed a form in the same visit Assisted Conversion : Visitors who clicked on recommended content in a past visit and completed a form later Currently, you cannot create your own conversion criteria.   Content AI Algorithm   Can you clarify on how the algorithms predict the content? The Content AI algorithms use machine learning and predictive analytics to decide and recommend which pieces of content are relevant for each visitor or email recipient individually. We use a mixture of algorithms that are constantly optimized and improved for best performance and results analyzing clicks and conversions. The algorithms are based on trending, popular content viewed on your website, new pieces of content added to your site, and also takes into account URL paths and user behavior clicks and visits.   Will Content AI show content the visitor or email has already received? There are certain checks and validations in place in order to provide the best experience for the end user receiving Content AI . These include: The Recommendation Bar will not recommend a piece of content the web visitor is currently browsing The Rich Media Recommendation will not show repeat predictive content on the same page and if the user clicks on a piece, we will not recommend the same piece of content they clicked on during that visitor's session. In Predictive Content for Email, a email recipient will not see the same Predictive Content more than once in follow up emails sent with Predictive Content in them.   Does Predictive Content now take into consideration any type of segmentation? So predictive content for segment A versus segment B? No, it is not related to segments, and this would be more of a rule-based style Web Personalization campaign. Instead, Predictive Content takes into account many variables to calculate before producing the Predictive outcome result for each visitor. Predictive Content can also be categorized and shown per category in the Rich Media and Email. See more here: Set Up Categories in Predictive Content   Is the Predictive Content picked at random, or is it based on customer criteria? The Predictive Content is prepared and approved by you. You also select the look and feel of the outcome and where it will appear on your site or in your email body. However, in the end it's the Algorithm that decides which of the approved Predictive Content pieces is best to show the current web visitor or email recipient.   Displaying Predictive Content on Web or Email   What are the Character Limits (Char limits) for predictive content on Web and Email?   Content Name: 255 Chars Bar Title: 110 Chars Rich Media Title: 50 Chars Rich Media Description: 215 Chars Email Title: 50 Chars Button Label: 17 Chars   The char limits are in place in order for the text to fit into the defined styling and look for the bar, rich media and email layout.   Can you see which pieces will be promoted in the email before sending the email? As the marketer, you can prepare and approve the piece of content for each source (email, web). In the end, the Predictive Algorithm decides what the end user will receive. For Predictive in Email, you can preview the layout and category of the Predictive Content, however the Predictive image is not seen until the recipient opens the email, so what you see in the preview is just an example, and will not necessarily be the image the recipient sees. See the process for setting it up and previewing Predictive Content in Email here.​   Can we use only Marketo landing pages, or anything under our company webpage domain? Yes, you can define all html pages, including landing pages, as content pieces to use in predictive. You can also manually add new pieces of content to the application.   Do you recommend Predictive Content for Marketo landing pages? Particularly Thank you pages? Predictive Content for web in the form of the Recommendation Bar or Rich Media is suited for all types of pages. We have customers using rich media on their home page (3 pieces of Predictive Content in horizontal format) below the fold of the home page. We have the Bar running on Blogs or Resources pages. A Thank You page or Thank You email is a great use case to add Predictive Content as these pages or email, usually do not have any call to action, and adding Predictive Content can help create more clicks and engagement by the viewer. You can categorize your predictive content for Rich Media and Email so it would be recommended to show on that Thank You page Predictive Content related to the thank you submission (eg. white paper, case study, webinar, blog post).   Can you alter the code of the predictive content to be flush with a font style/coloring? Predictive Content Rich Media for Web can be styled accordingly with font and colors. See here: http://developers.marketo.com/javascript-api/web-personalization/rich-media-recommendation/​. Predictive Content for Email is a Predictive image generated upon email open, so it is offered as 8 different fixed layouts and the Marketo user selects one. See documentation here: Enable Predictive Content in Emails.   Can you use categories in the "web" or "rec bar" versions like you can in emails? You can use Categories in Rich Media for Web and in Predictive for Emails. Currently, the Recommendation Bar does not support categories. Categories allow you to group your content and present predictive outcomes on web (rich media) or email. For example, you can work only with blogs, or with content in a particular language.
View full article
  Beginning on  2020-05-07 ,  Marketo  will start to roll out version 159 of the Munchkin  JavaScript  Client.   Subscriptions which have the  Munchkin Beta f lag enabled  will see changes from this release first, after which deployment will begin on a rolling basis to subscriptions which  do not have this flag enabled.    The  most significant change in this re lease is the  deprecation of Munchkin Associate Lead.       Changes     Deprecation of Associate Lead       Beginning with this release, when the  Associate Lead method  is invoked, a warning will be issued to the browser console, indicating that the method will be removed in a future release.  For more details on what to expect from this deprecation  process   read this announcement .     Reversion of Domain Selector V2       Despite best efforts to offer an improved the selection of the domain for the munchkin cookie, the change proved disruptive in certain cases.  We will be reverting the mainlining of this change, and the f unctionality will be  hidden behind a configuration flag  as it was prior to version 158 .     Fixing Undefined Referrer when Calling Visits Web Page       Previously when calling the  Munchkin API to submit a Visits Web Page event , the referrer would be submitted with a value of ‘undefined’.  With version 159, the referrer will now be cor rectly recorded.  This bug did not  affect  normal web visit tracking.       Rollout     As with all Munchkin releases, this version will be a phased rollout,  initiallity  to customers who have enabled  Munchkin Beta  for their subscriptions, and later for all  Marketo  subscriptions.  Th is schedule is subject to change.   Customers who need early access to these features in their subscriptions should consider enabling Munchkin Beta.   Date   Release Type   Percentage   2020-05-07   Beta   10%   2020-05- 21   Beta   50%   2020-0 6-05   Beta   100%   2020-06-19   General Availability   10%   2020-07-10   General Availability   50%   2020-08-04   General Availability   100%    
View full article
Wha t’ s  changing? In the June 2020 release,  Marketo  is deploying  an  update to the  infrastructure  that supports  batch campaign processi ng .  Th is  a  necessary  step  to  prepare for  forthcoming performance improvements .  The  updat e  wil l  b e  d ep loy ed   in  a stepwise fashion   across all  subscriptions  over the course of  the next  several months  and  is expected  to  be  complete  by  end of year 2020.   Why is this change being made? As platform demands increase, changes must be  made t o accommodate .   Th is change  is  to lay the foundation for  a n ticipated   p erformance demands  going forward .   In cremental updates to several  services  will  b e  p e rformed   to  r ea dy  the  system for th e   future  improvements .   What customer action is   needed ? None .  This  is a  seamless update   that occurs  behind the scenes .   How does this impact customers? There is no customer impact .
View full article
LinkedIn updated their permissions model on April 1. Marketo already supports the new permissions, so if you have not already done so, all you need to do is re-authorize your LinkedIn LaunchPoints to update your authentication token to ensure continued syncing. If you have both LinkedIn Matched Audiences and LinkedIn Lead Gen, you will need to re-authorize both LaunchPoints.   LinkedIn Matched Audiences LaunchPoint To update the permissions for the LinkedIn Matched Audiences LaunchPoint, a Marketo admin with access to your LinkedIn Business Account(s) will need to go to LaunchPoint in Marketo Admin. Select the LinkedIn Matched Audiences LaunchPoint and click "Edit Service" at the top.     Once in the Edit Service modal, click "Next". This will show you the user that authorized the integration and the date the LaunchPoint will expire.   Click on "Re-Authorize", which will open up a new window with a prompt to log into LinkedIn. You do not require the same user who originally set up the LaunchPoint.   Once you've signed in, the window will close and your LaunchPoint will now have an updated expiration date shown in the modal. Make sure to click "Save" to save the updated permissions.   And now your Matched Audiences LaunchPoint has updated permissions!   LinkedIn Lead Gen LaunchPoint To update the permissions for the LinkedIn Lead Gen LaunchPoint, a Marketo admin with access to your LinkedIn Business Account(s) and either admin or Lead Gen Form Manager permissions on your Company Page will need to go to LaunchPoint in Marketo Admin. Select the LinkedIn Matched Audiences LaunchPoint and click "Edit Service" at the top.   Once in the Edit Service Modal, click "Next". This will show you the user that authorized the integration and its expiration date. Click on the gray "Re-Authorize" button. This will open a new window with a prompt to log into LinkedIn.   Once you've logged in, the window will close and your LaunchPoint modal will show a new expiration date. Click "Next".   You will then see your list of LinkedIn Accounts. You do not need to update this screen. Click "Next" again. The final screen will be your field mappings. You do not need to update any field mappings to update permissions. Click "Save" to save updated permissions.   And now your LinkedIn Lead Gen LaunchPoint has updated permissions!  
View full article