Product Documents

**This video was re-uploaded in July 2024   In this video you'll learn from Adobe Marketo Engage Champions Amit Jain & Corey Bayless how to generate authentication tokens using APIs.   This is a quick tip from our On-Demand Webinar: Getting Started with Marketo Engage APIs.    

*This video was re-uploaded in July 2024 **JULY 2024 EDIT: The drag and drop capability for moving content into Engagement Program Streams (mentioned at 4:03) is no longer available. Adding content to streams is now done using an 'Add Content' button visible on each individual stream in the Streams tab. For more information, please review this documentation on Experience League.   In this video you'll learn engagement program set up best practices from Adobe Marketo Engage Champion Andy Caron.    This is a quick tip from our On-Demand Webinar: The Nitty Gritty of Next Level Nurtures.     

**This video was re-uploaded in July 2024   In this video you'll learn from Adobe Marketo Engage Champions Amanda Thomas & Julz James how to build an Adobe Marketo Engage nested nurture program.   This is a quick tip from our On-Demand Webinar: Behavioral-based advanced nurtures.     

**This video was re-uploaded in July 2024   In this video you'll learn from Adobe Marketo Engage Champion Courtney Tobe how to track and report on the ROI and revenue impact of your Adobe Marketo Engage programs.   This is a quick tip from our On-Demand Webinar: Beyond the Basics: Marketo Reporting.    

If you are an authorized support contact for multiple different accounts with the same email address and Marketo login name (typically we see this with consultant profiles) you will need to follow a different process to submit a support ticket. Typically these profiles will have Universal ID for several different Marketo instances across different accounts.   You will need to submit your support ticket through the support portal by following the instructions below:   1. Log into your Marketo instance, click on the community tile from the 'My Marketo' page, navigate to the support tab, and click on the 'My Case Management' button. IMPORTANT NOTE: You want to make sure you do NOT click on 'Open New Case' from the main support page because you will not be able to select which account you would like to submit a support ticket for.   2. On the Case Management page, select the account you would like to submit a support ticket for by clicking on the dropdown next to the 'Create a Case' button.    3. Select the 'Create a Case' button and submit a support ticket.   You should now be all set to submit support tickets as an authorized support contact for multiple different accounts! If you have any issues or questions with this process, please reach out to the Customer eXperience and Identity team by emailing marketocares@marketo.com.    

Hello Nation!   Based on the feedback from you, we have released a couple of interesting updates to the Filtering email bot activity. If you haven't had a chance to look at updates from the last release, here is the link: https://nation.marketo.com/t5/product-blogs/filtering-email-bot-activity-feature-v2/ba-p/322774   In the latest release, the focus was on improving the sophistication in capturing activities by bots. We are launching a new method to identify bot activities "Match with Proximity pattern". So, now we have a total of 2 methods that will be used to filter every email open or email link click activity.   The 2 methods are: Match with IAB bot list: Activities that match with the list UA/IPs from IAB will be marked as bots Proximity pattern: When 2 or more activities happen at the same time i.e under 0 seconds, they are identified as bots too. This pattern should identify activities generated by the link scanners. In the future this method will be enhanced to consider clicks coming from hidden links as an additional data point   So, if you enable the email filtering feature on your subscription, every email open or email click activity will go through the bot identification filtering i.e through the 2 methods in the order mentioned above.    Note: You will have the option to filter out i.e not log activities that are identified by the IAB list but not for proximity pattern in this current release.   If you wish to have all activities, whether they are by a bot or not, then choose the "log activity" option. This way, all activities will still go through identifications using the above-mentioned methods but will be logged into your Marketo subscription. Any email open or click activity matches with any of the 2 methods, it will be labeled as bot activities using the 2 new attributes we introduced in the last release. So, Activities that are identified as bots will have "Bot Activity" as "True" and Bot Activity Pattern as "Match with IAB list"  or "Match with proximity pattern" Activities that are identified as not bots will have "Bot Activity" as "False" and Bot Activity Pattern as "N/A" Activities that happened before we introduced these attributes will have "Bot Activity" as " " (empty) and Bot Activity Pattern as " " (empty) As you might already know, you can use these attributes as constrains in filters and triggers   To know the impact or to know what type of bots spamming your email engagement, we have added the ability to view the number of bot activities that are identified against each pattern to the admin page   Continuing on the feedback themes:   Themes Description Status More Transparency The current version identifies the bot and doesn't log activities identified as bots. Almost every customer and community expressed they would like to log the activities and do their own analysis Released (Added option to opt for logging and flag activities that are identified as bots) More Robust filtering The current version completely relies on the IAB list and we need to introduce more sophisticated filtering to identify bot activities Released (Added a new methods to identify if an activity is by a bot or not)  More Control We find a few user-agents/IPs that are creating bot activities and would like to include them in the bot activity filtering criteria Gathering requirements (If you have any feedback on this please share it in the comments) Reporting (new feedback item) In the Email performance report, we want an option to filter out bot activities so that we can see the metrics with and without bot activities  Gathering requirements (If you have any feedback on this please share it in the comments)  

This article contains information on a legacy performance enhancement project that has rolled out to all customers and, in some circumstances, has been superseded by other performance enhancements. It will remain posted for historical purposes but should not be referred to.   What is “Project Orion"?   As the number of customer touchpoints expands, and the volume of digital signals from customers increases exponentially, modern marketers need a way to harness this data to deliver the personalized experiences that customers expect.   Project Orion is about big data ingestion and processing at speed and scale.   Marketo has spent the past year building a new big data architecture that allows Marketo to ingest and process trillions of customer behaviors. “Project Orion” is the code name of the development project to build a big-data infrastructure and first set of services that take advantage of it.   This platform is built using technologies that were pioneered first at Google, Linkedin or Facebook, such as Apache hadoop, an open framework for distributed storage and processing of high volume data and other scale technologies.   What are the benefits to customers?   The platform innovations include 6 specific scale and performance improvements: Track web events (via Munchkin) on any pages of your site without traffic volume restrictions Find People instantly when searching in the Marketo database Get up-to-date Smart Lists instantly with real-time membership updates and faster loading time Import People lists into the Market database in a fraction of the time Accelerate the import of Custom Activities into Marketo Generate Web Page Activity and Company Web Activity reports in less time   Plus, by establishing Marketo’s big data architecture, it creates the foundation for other next-generation platform services for performance and scale in the future.   Does Project Orion solve issues not on the list above?   Project Orion improves scalability and performance for the use cases listed above. Performance for use cases not on the list above are not expected to improve with Project Orion.   Customers with large data sets often experience the most significant performance gains in these areas. The new architecture doesn’t degrade these or other areas in any way.   When is it available? What’s the roll out plan?   The Project Orion development effort is GA and Marketo’s global data centers have been upgraded to our high-scale infrastructure. The roll out to customers started in Q3 2016.   Project Orion consists platform components/services that each have their own roll out plan and are currently being deployed to customers. Priority is based on customer need - Marketo’s Support Team is proactively monitoring customer instances for performance improvement opportunities related to Project Orion.   What's next for performance and scalability in 2017?   With our new big data architecture, we plan to continue building new platform services to further improve performance and scalability.   To learn more about what we have planned this year, come to the Marketing Nation Summit, April 23rd-26th.   Who can I contact for more information on Project Orion?   For more information on Project Orion, please reach out to your Customer Success Manager. If you’re experiencing specific scenarios where you feel that migrating to the new big data architecture will be beneficial, please have your authorized support contact open a case with our Support Team.

Introduction    As a Flow Step, the Compute Formula service takes an Excel-style formula, computes it, and returns the resulting value to the selected field.  This facilitates many different types of data transformations and use cases, including date math, text replacement, and composite scoring, among many others.  You can find the repository on Adobe Github.     Prerequisites    To deploy and use the Compute Formula Flow Step Service you will need:  Experience using a command line.  Have git installed and have basic experience in its usage.  Install NodeJS, Node Package Manager (NPM), and the Adobe IO command line tool.  Have an Adobe IO Runtime Account, and permissions to retrieve credentials for Runtime workspaces.  A Marketo Account with Admin Credentials.  An Adobe IO Runtime account.  IO Runtime is currently available as an add-on to subscribers of AEP, AEM, Commerce, or Analytics    Support    While the Self-Service Flow Steps framework is fully supported, Compute Flow is an open-source application built on the framework using Adobe IO Runtime.  Issues specific to the Compute Flow application should be logged on the github repository or on nation.marketo.com.      Deployment    Clone the Repository    In a command line, navigate to the folder where you want to clone the code from the Git Repository for AIO Compute Formula.  From there use the following command to clone to repo:    git clone git@github.com:adobe/aio-compute-formula.git    Obtain IO Runtime Credentials    Make a new project in the Adobe Developer Console, selecting the “Project from Template” option:      Select the App Builder Template and save your project:      Select a workspace, either Production or Stage, that you want to deploy the application to and use the Download All option to download the credentials to the folder where you cloned the repository in the previous step:      Once you’ve downloaded the file locally, from your command line use the following command to use the downloaded credentials for your application deployment:    aio app use <file location>    Render Manifest from Template    Now you’ll need to use the render-manifest script to create a manifest yaml file including your desired API key (this is the API key which you will use later in the installation phase) and log level (info, warn, error, or debug).  Use the following command to render your manifest:  npm run render-manifest <path:'./manifest.yml'> <apiKey> <logLevel>        Install NPM Packages    Now you will need to locally install the dependencies for this project using the following command in your command line:  npm install  Deploy Application and Obtain Service URL    To deploy your application, use the following command:  aio app deploy  Once finished the command line will list out the endpoint URLs of the application.  Copy the URL ending in ‘serviceSwagger’ for use in the next step.      Install and Configure Service    In Marketo, navigate to the Admin->Service Providers menu and use the Add New Service button.  In the dialog box, enter the URL you copied from the previous section:      Then follow the instructions for entering your API key:      In the Incoming Fields section, select the fields which you want the service to be able to write data back to:       You can always come back to change the field mappings later if you are not sure about what fields you want to be eligible for writes at this time.  Follow the rest of the installation guide and then your service will be ready to use in Smart Campaigns  Usage    Flow Step Fields    Formula    The Formula field accepts Excel-style formulas, and supports all of the functions that are supported by FormulaJS.  Lookup and other column-related functions are not available.  Your formula should not include a leading = sign as you would when entering the formula in a cell of a spreadsheet application.  While standalone mathematical statements are supported to some extent, complicated cases should be implemented as Excel functions, as some standard mathematical operators, like ^, have behaviors distinct from the mathematical operation that they represent outside of a JavaScript context.  Strings embedded into the formula field, including tokens for string-like fields, e.g. dates, should be surrounded by quotation marks for functions to behave as they are expected to.  Return String    When returning a value to a string or string-like field, such as a Date or a Datetime, you should select the field you wish to return in the Return String field.  Each field configured as an inbound field for your service will be listed in this field*.  Return Number    When returning a value to a number-type field, like Integer, or Float, you should select the field you wish to return in the Return Number field.  Each field configured as an inbound field for your service will be listed in this field*.    *If the picklist of either Return String or Return Number is empty, or does not include choices which were recently added, you should refresh your picklist choices, either via the refresh button on the flow step card or from the Admin->Service Providers menu.  Example Use Cases    Composite Scoring    A common scoring use case is to create a weighted composite score from two or more other scores.  The Compute Formula Flow Step makes this simple to do.  For this example, you will use two source scores, Behavior Score and Demographic Score, and return the value to a field called Composite Score.  To build our formula, you need to decide how to weight the source scores.  Our hypothetical marketing organization values Behavior scores at 30% and Demographic scores at 100%.  Our formula would then look something like this*:    SUM(PRODUCT({{lead.Behavior Score}}, 0.3), {{lead.Demographic Score}})    *When using numbers between -1 and 1 which have a decimal place, you will need to include a leading Zero (0) when embedding the number into your formula, e.g. 0.8.    If a person record has a Behavior Score of 3 and a Demographic Score of 20, then the resulting composite score would be 20.9.  Scores in Marketo Engage are integers, however, so you should be sure to return a round number.  Use the ROUND() function to make the output an integer.  Now our Formula will look like this:    ROUND(SUM(PRODUCT({{lead.Behavior Score}}, 0.3), {{lead.Demographic Score}}))    Now that you’ve defined your formula, you’ll want to make sure that you’ve configured the fields which you want to write back to, in this case “Composite Score.”  Go to Admin->Service Providers, drill down into the service, and edit the Incoming Fields section to enable the Composite Score field.  Composite Score is a custom field for this example, so if you do not have this field in your instance, you’ll need to create a new one, or use a different score field.      Now let’s put this into practice.  Since this is a composite score, in order for the score to be kept up to date, you need to listen for changes to the source scores to update the composite score when they change.  That means you need a triggered Smart Campaign with Data Value Changes Triggers for both Behavior Score and Demographic Score.        Insert the flow step, populate your formula, and select your desired field to return to using the Return Number field.      Now when you activate this campaign and a person’s Behavior Score changes, then your campaign will activate and return the result to your selected field.              Date Differential/Time in Stage    To measure the efficiency of marketing and sales funnels it is common to measure the amount of time that a person spends in a Marketing Stage.  In particular, the number of days a lead spends in the Marketing Qualified or Sales Qualified stages before the lead is acted upon is a significant indicator of how well aligned the marketing and sales processes are functioning.  While this information is easy to synthesize with a business intelligence application, bringing that same data into Marketo and acting upon it has required complicated API integrations to populate back to person records in Marketo.  With Compute Formula, the process is as simple as defining a formula and your return field.  The DAYS() function counts the number of days between and end date and a beginning date.    DAYS(“{{lead.SQL Date}}”, “{{lead.MQL Date}}”)            Round Robin Lead Assignment    While Marketo provides Random Sample functionality to obtain a percentage-based sample of an audience, some Sales Owner assignment use cases benefit from more fine-grained control over lead assignment.  One example of this is to take the modulus (remainder) of a lead id, using the number of potential owners that you can assign leads to.  Suppose you have 55 potential lead owners, and you want to get an approximately even distribution of leads assigned to a given owner.  One of doing this is to assign each of your owners a number from 1 to 55, and then to take the modulus of the integer lead id.  Our formula would then look like this, where the Number is the lead ID, and the Divisor is the number of potential owners:    MOD({{lead.id}}, 55)    Given an id of 117, the resulting value would be 7.  Our campaign flow would have a Compute Formula step with our formula, and Return Number set to a Sales Owner Seed field, followed by a Change Owner step configured with choices corresponding to each sales owner.               

Included in this article Summary How Leads Become Known Anonymous Web Activity Logging Triggered Smart Campaigns   Revised 9/15/2023 Clarified Qualification Rules Behavior with regard to the date of a triggering activity   Summary When a person visits a web page with your Munchkin tracking code on it, that web activity is tracked for that anonymous lead. When a lead takes action to become known, a lead record is created in your Marketo lead database and the anonymous web activity that lead had prior to becoming known is included in that new lead record. Any smart campaigns that would have triggered off of that web activity will then fire in the order of when the web activity occurred.   How Leads Become Known There are three main ways that an anonymous web activity record can be converted into a known lead in your Marketo lead database.           1. Fills out form. If the anonymous lead fills out a Marketo form, that will create a new known lead record. The anonymous web activity that lead had before becoming known will be associated to that new known lead record.        2. Clicks a link in an email. Hyperlinks in emails are automatically decorated with a tracking code that is used to associate an anonymous record back to a known lead record. If you have a lead in your database that hasn’t had any web activity yet (like a lead that was added from a list import), when the lead clicks the hyperlink in the email, that tracking code in the hyperlink will associate their Munchkin cookie to your known lead record and all of that anonymous web activity will be logged into that known lead record.        3. API call. You can use an API call to associate an anonymous web activity record to a known lead record. This can be done through a SOAP API syncLead call​, or by a REST API Associate Lead call.   Anonymous Web Activity Logging Anonymous lead activity is housed in a different database. This doesn’t create a lead record until the lead is promoted to a known lead. All activity a lead had prior to becoming known will be logged chronologically in the new lead record with the correct corresponding date/time stamps once the lead becomes known.                  Triggered Smart Campaigns Anonymous leads can’t trigger smart campaigns. However, when a lead becomes known, the active smart campaigns that would have triggered from the anonymous activity will be triggered. All trigger campaigns currently active at the time the lead becomes known will be triggered if the lead took the action being triggered on while anonymous. Only campaigns currently active at the time the lead becomes known will be triggered.                The campaign definition at the time it is triggered is what will be executed. For example, if the campaign has a Score Change of +10 but is changed to +5 just before the lead becomes known, the new lead created will be given a score of 5, not 10. The campaigns that are triggered by the anonymous activity will be processed in order of the activities that occurred, oldest to newest. In the lead’s activity log, all campaign activities (with one exception below) will be logged with the time stamp of when the lead becomes known, right before the New Lead activity. Interesting Moment flow step activities will be backdated to the date and time when the corresponding anonymous activity occurred.                  Not all flow actions in the campaign will be executed. When leads flow through campaigns as a result of the promotion to known lead, only specific flow actions will be processed. All other flow actions will be ignored. The flow actions executed will be:           1. Change Score           2. Interesting Moment           3. Change Data Value           4. Add to List           5. Remove from List Secondary campaigns (campaigns triggered off of activities performed by the campaigns triggered by the lead promotion) will not be triggered.                Pruned activities will not trigger campaigns. Anonymous web activity is not stored forever—it gets pruned over time, so any activity that has been pruned is no longer there to be triggered off of. When determining whether a person will qualify for a replayed trigger campaign, the time that the activity occurred is used.  For example, if you have a campaign listening for Visits Web Page events, and qualification rules set to let leads run through once per hour, each event that is more than one hour apart will qualify the lead for the campaign.  This may lead to several instances of the same campaign running for a person upon promotion to known.

Apple iOS 17 and Apple OSX Sonoma will introduce changes to how Safari opens URLs with tracking parameters in order to protect user privacy. Details on these privacy changes can be found on Apple’s website https://www.apple.com/newsroom/2023/06/apple-announces-powerful-new-privacy-and-security-features/   Our teams have tested the beta versions of these operating systems to learn how these changes will impact Adobe Marketo Engage emails. We have found that URLs containing our tracking parameter mkt_tok will be impacted in some scenarios by these changes. The mkt_tok parameter is used to help associate browsers to known leads using Munchkin and to render the correct email with the View As Webpage link.   Impact on links in emails The impact these changes have on links in emails will be dependent on whether your links have tracking enabled. Tracked links go through our redirection service which preserves URL parameters when browsing Safari in non-private browsing mode. Links that are not tracked are more susceptible to URL parameters being stripped by Safari. For more information on how to enable or disable link tracking please refer to this documentation https://experienceleague.adobe.com/docs/marketo/using/product-docs/email-marketing/general/functions-in-the-editor/disable-tracking-for-an-email-link.html     Action Track Link Include mkt_tok Resulting URL Impact Open link from Mail or copy/paste link from Mail into Safari ✓ ✓ URL resolves at destination with mkt_tok and third-party parameters intact. Click is tracked. Parameters not stripped. Open link from Mail or copy/paste link from Mail into Safari ✓ X URL resolves at destination with third-party parameters intact. Click is tracked. Parameters not stripped. Open link from Mail or copy/paste link from Mail into Safari X X URL resolves at destination. Third-party parameters may be stripped. Third party solutions may be impacted by stripped parameters. Open link from Mail or copy/paste link from Mail into Safari Private Browsing ✓ ✓ URL resolves at destination with mkt_tok and third-party parameters stripped Click is tracked. Browser is not associated to known lead via Munchkin. Third party solutions may be impacted by stripped parameters. Open link from Mail or copy/paste link from Mail into Safari Private Browsing ✓ X URL resolves at destination with third-party parameters stripped. Click is tracked. Third party solutions may be impacted by stripped parameters. Open link from Mail or copy/paste link from Mail into Safari Private Browsing X X URL resolves at destination. Third-party parameters may be stripped. Third party solutions may be impacted by stripped parameters.   In general, tracked links in emails will not be impacted by these changes in non-private Safari browsing as our redirection service will retain the URL parameters. If the link in the email is not tracked, then URL parameters may be stripped by Safari. If the link is opened in Safari Private browsing, then mkt_tok and some third-party parameters will be stripped regardless of whether the link is tracked and goes through our redirection service. Impact on View As Webpage links Testing has shown some impact on View As Web Page links. Action Method of inserting link Resulting URL Impact Open link from Mail or copy/paste link from Mail into Safari "Include View as Web Page" option in Email Settings URL resolves through tracking service and mkt_tok not stripped No change. Open link from Mail or copy/paste link from Mail into Safari {{system.viewAsWebpageLink}} URL has mkt_tok value stripped View As Web Page does not load and returns an error page Open link from Mail or copy/paste link from Mail into Safari Private Browsing "Include View as Web Page" option in Email Settings URL has mkt_tok value stripped View As Web Page does not load and returns an error page Open link from Mail or copy/paste link from Mail into Safari Private Browsing {{system.viewAsWebpageLink}} URL has mkt_tok value stripped View As Web Page does not load and returns an error page   Our service requires the mkt_tok parameter in the URL to render the personalized version of the email; when this parameter is stripped by Safari it will result in an error page being returned instead.   View As Webpage links that are inserted by the token {{system.viewAsWebpageLink}} are not decorated with CNAMEs and do not navigate through our tracking service and will see their mkt_tok values stripped when opened in Safari as a result. This will result in the user getting an error page.   The change will also affect all View As Webpage Links opened in Safari Private Browsing on iOS 17 and Sonoma regardless of how the links were generated. This also includes View As Webpage links in emails sent before the release of these new operating systems.   Our team has identified a solution to build our View As Web Page links in a way that will not be affected by these privacy changes. This change is currently scheduled for our October 24, 2023 release. View As Web Page links generated by {{system.viewAsWebpageLink}} and View as Web Page links opened in Safari Private Browsing on iOS 17 or OSX Sonoma will not function between when the device is updated to one of those operating systems and our October 24, 2023 release.   To lessen the impact on users opening links in Safari, please use the “Include View As Web Page” option in Email Settings instead of the {{system.viewAsWebpageLink}}. Unfortunately there is no workaround that can be offered in the interim for users using Safari Private Browsing.   As we continue to learn more about these changes, we will continue to update this post.   FAQ Q: Will click tracking be impacted by these changes? A: No, click tracking that create Clicked Link in Email activities will not be impacted by these changes.    

We are announcing some changes to Adobe Marketo Engage activities that are related to Dynamic Chat. To support new Dynamic Chat offerings announced at Adobe Summit, and to better match standardized naming conventions, we will be updating the names of some existing Marketo Engage activities and attributes and adding additional activity attributes to existing activities. These changes will go into effect in our July release (July 18, 2023 for NLD and LON datacenters, July 21 for AB, SJ, and SN datacenters).   Will these changes impact my business and how? These changes will primarily impact Smart Lists (standalone and in Smart Campaigns), Person Activity Log, and the REST and SOAP APIs:   Smart Lists The names of affected activities and attributes will change in their respective cards. Existing Smart Lists (both standalone and in Smart Campaigns) will continue to evaluate without needing any change in configuration. Filters/triggers referencing the new names of activities or new names of attributes will continue to qualify older activities and attributes with the old naming convention.   Person Activity Logs Newly created activities will use the new naming conventions. Older activities will continue to show the old naming conventions and will not be retroactively renamed. These older activities will still qualify in Smart Lists by referencing them with the new naming conventions.   REST and SOAP APIs Activity ID of affected activities will stay the same. New names of activities and attributes will be returned over the REST API from the Get Activity Types endpoint (/activities/types.json) or SOAP API from the getLeadActivity and getLeadChanges endpoints.   Integrations should be tested to ensure they can support the upcoming changes. If your integration has hardcoded references to activity or attribute names, they must be updated to support both the old naming conventions and the new naming conventions else it will run the risk of interruption.   Updates to the activities are detailed below:   Engaged With Dialogue Activity Name Existing Name New Name Engaged with Dialogue Engaged with A Dialogue   Attributes Existing Attribute Name New Attribute Name Dialogue Name Dialogue Name Page URL Page URL Status Conversation Status Chat Transcript Conversation Transcript   Conversation Summary*   Language*   Workspace* *Denotes new attributes   Reached Dialogue Goal Activity Name Existing Name New Name Reached Dialogue Goal Reached Dialogue Goal   Attributes Existing Attribute Name New Attribute Name Dialogue Name Dialogue Name Goal Name Goal Name Page URL Page URL   Language*   Workspace* *Denotes new attributes   Dialogue Appointment Scheduled Activity Name Existing Name New Name Dialogue Appointment Scheduled Scheduled Meeting in Dialogue   Attribute Names Existing Attribute Name New Attribute Name Dialogue Name Dialogue Name Agent Agent Email Page URL Page URL Status Meeting Status Scheduled For Scheduled For   Agent Name*   Routing Queue ID*   Routing Queue Type*   Routing Queue Name* *Denotes new attributes   Interacted with Document Activity Name Existing Name New Name Interacted with Document Interacted with Document in Dialogue   Attributes Existing Attribute Name New Attribute Name Dialogue Name Dialogue Name Document Name Document Name Document URL Document URL Document Opened Document Opened Document Downloaded Document Downloaded Search Terms Search Terms Page URL Page URL   Language*   Workspace* *Denotes new attributes

March 2023 update: The deprecation of the legacy URL patterns will occur on August 1, 2023.   June 2022 update: We have decided to extend the deadline until the end of 2022 with support of old URL patterns ending in January 2023. More information to be provided once a precise date has been chosen.   In 2021, Marketo Engage made changes to the URL structure for Landing Pages, Forms, and Images & Files assets. On August 1, 2023 we will be deprecating usage of old URL structures and these references will no longer load on the web.   Why is this change being made? Technical Details Landing Pages Images & Files Forms What customer action is required?   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.   Now that all Marketo Engage subscriptions have been migrated to our new URL structure for some time, we will be ending support to the legacy, more vulnerable URL structure.   Technical Details Landing Pages, Form embed code, and resources stored in Images & Files had 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 were minimally affected by this change. Landing Pages Subscriptions without a configured landing page domain Landing page paths will changed to a unique hostname for your subscription. Legacy: http://na-sj01.marketo.com/lp/123-ABC-456/unsubscribePage.html Current: 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 changed to a unique hostname for your subscription.   Legacy: http://na-sj01.marketo.com/rs/123-ABC-456/images/cuteKitten.png Current: 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 Legacy:     <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>     Current:     <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? You will need to audit the source code of your web pages to see if these URL patterns are in use by your business. If you have web pages or form usage that pre-date 2021 it is possible they are using the legacy URL pattern.  Most customers configure a CNAME and secure it via SSL early in the life of their instance, minimizing the impact on Images & Files URLs. Prior to our October 2021 release, all form embed codes used the legacy URL structure. If you have usage of Marketo forms from prior to 2021 it is very likely they will need to be updated to use the new URL pattern, which can be found by copying the form embed code from the Form asset page.   For Marketo Landing Pages and Emails, if you used the Image picker or Form picker that are included in the Landing Page editor or Email editor then no change is necessary. If you hard coded references to images or forms using the legacy URL pattern instead of using the pickers then these references will need to be updated to the new URL pattern.   Customer Support does not have the ability to perform this audit for you.   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 August 2023. 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.

Starting in the October 2022 release, we introduced a minor change to Marketo REST API response message.   What is changing? First, let’s begin by looking at the standard defined by the Internet Engineering Task Force (IETF) in RFC 9110.    In particular, the standard for Control Data in response messages: “Response message control data includes a status code, optional reason phrase, and protocol version.”   For example, typical response message control data for a successful HTTP request would be “200” for status code, “OK” for reason phrase, and “HTTP/1.1” for protocol version.   Now, let’s cover what is changing.   The reason phrase will change depending on the deployment of infrastructure.   Why is this change being made? As part of ongoing maintenance, we must update infrastructure components to newer versions to keep pace with industry change.   What customer action is required? Action is required if you use an integration that is built using the Marketo REST API and that integration depends on the reason phrase.  If so, then your integration must be changed to remove dependencies on the reason phrase and instead should rely on the status code.   Note that this is an unlikely scenario as most HTTP libraries and integrations already use the status code.   When must customers make the change? As soon as possible.   What if customers don’t act? Integrations using the Marketo REST API may not function correctly.

In the March 2023 Marketo Engage release, we will be changing several values used to populate the Inferred Country field for new Persons.   What is changing? Several of the values used to populate the Inferred Country field are changing.  More information on inferred fields can be found here. The following table shows the values that will change.   Inferred Country Field Value Changes January 2023 March 2023 Bolivia, Plurinational State of Bolivia (Plurinational State of) Cape Verde Cabo Verde Congo, the Democratic Republic of the Congo (Democratic Republic of the) Czech Republic Czechia Holy See (Vatican City State) Holy See Iran, Islamic Republic of Iran (Islamic Republic of) Korea, Democratic People’s Republic of Korea (Democratic People’s Republic of) Korea, Republic of Korea (Republic of) Micronesia, Federated States of Micronesia (Federated States of) Moldova, Republic of Moldova (Republic of) Swaziland Eswatini Taiwan, Province of China Taiwan (Province of China) United Kingdom United Kingdom of Great Britain and Northern Ireland United States United States of America Venezuela, Bolivarian Republic of Venezuela (Bolivarian Republic of) Virgin Islands, British Virgin Islands (British) Virgin Islands, U.S. Virgin Islands (U.S.)   Why is this change being made? We are updating the 3 rd party data source used to lookup demographic and firmographic information based on client IP address.   What customer action is required? Action may be required if you use an Inferred Country filter in a smart list.  The first step is to identify all smart lists that contain the Inferred Country filter.  Do this by going to Admin > Field Management and selecting Inferred Country field from tree on righthand side.  Then click the Export Used By item from Field Actions menu to export relevant smart lists.   Inferred Country - Export Used By             Inferred Country - Field Used In             The second step is to examine each Inferred Country filter definition for each row in Field Used In column and compare against the January 2023 values in table above (column 1).  If the filter definition matches a value in the table, then action is required to ensure that new Persons will continue to qualify for the smart list.  The action needed depends on which operator is used in the filter definition.    Let’s go through a few examples to help illustrate.   Example 1: “is” Operator Persons with “Inferred Country is United States” qualify with this filter.       In this case we see “United States” in the table, so action must be taken.  To qualify persons with either January 2023 or March 2023 values, add a second filter using “United States of America” as shown below.          This way Persons with either “Inferred Country is United States” OR “Inferred Country is United States of America” will qualify.   Example 2: “starts with” Operator Persons with “Inferred Country starts with United States” qualify with this filter.       No action is needed since “starts with United States” will match either “United States” or “United States of America”.   Example 3: “starts with” Operator Persons with “Inferred Country starts with Cape Verde” qualify with this filter.       In this case we see “Cape Verde” in the table, so action must be taken.  This will not qualify Persons with either January 2023 or March 2023 values since “Cabo Verde” does not “start with Cape Verde”.  The solution here is to replace “starts with” filter with two “is” filters as shown below (like idea shown in Example 1).           This way Persons with either “Inferred Country is Cape Verde” OR “Inferred Country is Cabo Verde” will qualify.   Example 4: “contains” Operator Persons with “Inferred Country contains United States” qualify with this filter.       No action is needed since “contains United States” will match either “United States” or “United States of America”.   Example 5: “is empty” Operator Persons with “Inferred Country is empty” qualify with this filter.       No action is needed because the filter definition does not contain a value and thus cannot match a value in table.   Here is a list of related product documentation: Understanding Smart Lists Define Smart List Filters Inferred Filters Export Used By Data for a Field When must customers make the change? Before the release that is currently scheduled for March 24, 2023.   What if customers don’t act? Persons entering Marketo Engage after this change may not qualify for smart lists that contain Inferred Country filters.  Existing Persons are not impacted so they will continue to qualify as before.

If you are invited into a second instance with Universal ID (UID) enabled, you will need to follow the process below to ensure that you are accessing your second instance correctly. IMPORTANT NOTE: When an admin user in Marketo is inviting you into a second instance, in order for Universal ID to work correctly they will need to invite you with the exact same Marketo Login name and Email. Doing this correctly will allow you to toggle between both instances with UID.   1. Open up your Marketo new user invite email with the subject "Marketo Login Information" from no-reply@marketo.com. Click on the "Login to Marketo" hyperlink in the email   2. You will be taken to a 'Login page'. NOTE: When you are invited into your very first instance you are taken to the 'Create a Password' page but since this is your second or third or fourth instance you have been invited into with UID, you will be prompted with the login page below.  You will enter your login credentials for your original Marketo instance, click on the "I accept the terms and conditions" checkbox, and then select the sign-in button.   3. You will be logged into the new Marketo instance and you should see a grey arrow next to the instance name in the upper right-hand corner. You can click on the instance name, and you should see a drop-down with all the instances you have access to (in this case just 2).    You should now be all set! If you have any issues with that process, you can reach out to the Customer eXperience and Identity team (CXI) for further assistance by emailing customercare@marketo.com. 

As of November 2020, Marketo Measure was migrated into the Adobe Admin Console. What this means is that user management for Marketo Measure is now done through the Adobe Admin Console. Because of this, anyone who needs to be a Marketo Measure user will need to be added through the Console. For security reasons, only your organization’s System Admins can manage users.   System Admins can add Marketo Measure users by following these steps:    Navigate to https://adminconsole.adobe.com  Log in with your Adobe ID (select “Company or School” account type)  Click on the “Products” tab  Click on your Marketo Measure product card  Add the desired user to the product card. Once the desired users are added, they can navigate to https://apps.bizible.com/ and log in with their Adobe ID.  If a user needs admin permissions within Marketo Measure they will also need to be added in the 'admin' section of the Marketo Measure product card.   If you or your System Admins are having any issues with this process, please reach out to the Customer eXperience and Identity team (CXI) by emailing marketocares@marketo.com          

As a Marketo Measure only customer, you need to be set up as a Marketo Measure Only Support Contact to submit support tickets for Marketo Measure through the Nation (nation.marketo.com). IMPORTANT NOTE: Although user management for Marketo Measure is done through the Admin Console (adminconsole.adobe.com), support for Marketo Measure is still done through the Marketo Nation support portal.    In order to get set up as a Marketo Measure Only support contact, you will need to reach out to the Customer eXperience and Identity team (CXI), formerly the Customer Care team, by emailing marketocares@marketo.com and request to be added as a "Marketo Measure Only Support Contact". NOTE: The Customer eXperience and Identity team may require approval from your Account Manager (CSM, SAM, VSM, etc.) before setting you up as a Marketo Measure only support contact. If you can copy your account manager on your email or have them submit the request for you, this will move the process forward quicker.   Once the CXI team has confirmed that you need to be added as Marketo Measure only support contact, they can create your support contact profile and provide you with your login credentials.   Once you have your login credentials you can access your support portal by doing the following: 1. Navigate to nation.marketo.com 2. Click on ’Sign In” in the upper right hand corner 3. Click on the ‘I am an Adobe Marketo Measure (Formerly Bizible) ONLY customer or an Adobe Marketo Engage Sales Connect ONLY customer’ button 4. Enter in your credentials 5. Click on the 'Support' tab across the top of the page   You are all set! You can now create and manage your support cases as a Marketo Measure only customer.      

In September 2022, we released two Marketo Engage Performance Tier packages: Performance. Additional performance to meet the needs of high demand marketers. Performance Plus. Highest level of performance to meet the needs of any marketer. When you purchase a performance package, additional infrastructure is allocated to your Marketo Engage subscription. This allows your subscription to scale to meet increased demands.   Each package has a set of defined thresholds for various capabilities as described below. The thresholds represent the highest level of performance that can be achieved when using best practices. Exceeding a threshold may adversely impact performance or cause undesired product behavior. Each threshold falls into one of four categories: Entitlement, Scoping Parameter, Performance Guardrail, or Static Limit. For category definitions, and threshold values, please see the Marketo Engage Product Description here. If you would like to know how your current product usage compares with these product thresholds, please contact your account representative.   Note: Nothing changes in how Marketo has always operated, it still is a multi-tenant system and the mileage one gets is dependent on overall activity level within the subscription as well as within the data center. Published values should not be interpreted as throughputs one should consistently expect. Rather, the values represent the maximum performance thresholds/guardrails beyond which purchasing a performance package would become required.   Activities Marketo Engage supports a wide variety of activity types which are related to Person records. Every data change, action, or flow step is recorded against a Person’s activity log. These activities can be leveraged in Smart List and Smart Campaign filters and triggers. There are two activity-related scoping parameters: Maximum Number of Activities – Rolling 7-day Average Maximum Number of Activities – Peak Per Day The Rolling 7-day Average is the total number of daily activities over a 7-day period divided by 7. The time span goes back several weeks from time of retrieval. The Peak Per Day is simply the largest number of activities observed in a day over that time span.   Campaigns There are two campaign-related performance guardrails: Maximum Trigger Campaign and Segmentation Throughput Maximum Batch Campaign Throughput Campaign performance is highly variable. The type of program, the complexity of the program (smart list filters and triggers, flow steps, etc.), the number of persons that qualify for program all contribute. In addition, environmental factors such as the current load on the system will impact performance. Throughput in the context of campaigns refers to the volume of campaigns that run to completion over a given period. The Standard level of performance represents the base level of performance provided out of the box. The higher levels of performance provided by performance packages are expressed in terms of multiples relative to Standard. Using batch campaigns as an example, a throughput improvement of 8 times greater than Standard can be achieved by using the Performance package (10 times greater when using Performance Plus package).   Email There is one email-related performance guardrail: Peak Batch Email Send Rate Peak Send Rate is the maximum number of emails that can be sent in an hour. Send rates are supported for sustained periods of up to 4 hours per day, and up to 4 days per week. Marketo Engage supports both shared and dedicated IP addresses.  When you use a dedicated IP to send email, your messages are sent from a unique and exclusive IP. As such, you have complete control over your email sender reputation and thus email deliverability. Multiple dedicated IP addresses are used to efficiently distribute large email volumes leading to higher throughput. To achieve the highest send rate available using Performance Plus, you must use 5 dedicated IP addresses (Email Delivery Services and Power Pack are included).   CRM Sync There is one CRM Sync-related performance guardrail: Peak Sync Rate with CRM System Peak Sync Rate is the maximum number of records that can be synchronized in an hour and in a day. Sync rates are supported for periods of up to 10 hours per day. The rates for Salesforce and Veeva are similar due to using the same underlying technology. Sync rate performance is highly variable due to the nature of the sync process. The CRM vendor's API response time, the number of objects and records and fields within each record, whether creating new records versus updating existing records, all these things impact performance.   API There are two API-related static limits: Maximum Purchasable Number of API Calls Maximum Purchasable Size Limit for Bulk Extract Jobs Number of API Calls is the maximum number of calls that can be made: In a day (daily quota) Over the time span of 10 seconds (rate limit) At the same time (concurrency limit) Purchasable means that these limits can be increased by purchasing a Performance, Performance Plus, or in some cases by purchasing an addon. Please contact your account representative for more information. These static limits are strictly enforced. Exceeding a limit will cause the API to return an error.   Data Model There are six Data Model-related static limits: Maximum Number of Custom Object Records Maximum Number of Custom Objects Maximum Number of Fields per Custom Object Maximum Number of Custom Activities Maximum Number of Fields per Custom Activity Maximum Number of Fields per Contact Custom Object Records refers to the number of database rows that have been written for a given custom object. Custom Objects refers to the number of custom object definitions.  Fields per Custom Object refers to the number of fields defined within a custom object definition. Custom Activities refers to the number of custom activity definitions.  Fields per Custom Activity refers to the number of fields defined within a custom activity definition. Fields per Contact refers to the number of custom fields defined for a Person. Custom objects are most efficient if the fields are defined when objects are first created. Fields that are defined afterwards are slower to insert and update. If updates are not needed, then custom activities should be considered as an alternative. In many cases it is better to have several custom objects with fewer fields versus a single monolithic custom object with many fields. Consider your schema carefully before finalizing on usage.   Data Ingestion There are two Data Ingestion-related performance guardrails: Maximum Number of Web Page Visit Activities Processed Maximum Number of Form Submissions Processed There are two web page visit activities: Visit Web Page, Clicked Link on Web Page. Both occur when a person interacts with a web page that has been instrumented with Lead Tracking JavaScript.  Marketers should only instrument web pages that are related to marketing campaigns. Typically, these are landing pages that are placed in the body of an email. When a person submits a Marketo Form, a Fill Out Form activity is generated.  Forms can be hosted on Marketo landing pages or on a customer/external landing page (embedded). Settings for the Standard package are sufficient to handle typical web page visits, and form submission volumes.  If not, you may see a lag between the actual time of activity and time when the activity is available within Marketo. If you have trigger campaigns that leverage either of these activity types, high volumes can cause the trigger campaigns to fall behind.   Segmentations There is one Segmentation-related static limit: Maximum Number of Segmentations This is simply the number of Segmentations that can be created in a subscription.  Segmentations are implemented as a system triggered smart campaign. The campaign is triggered when a field in the Segment Rule is updated.  If the rule references many fields and/or the referenced fields change frequently, this can adversely impact performance.   Engagement Programs There is one Engagement Program-related static limit: Maximum Number of Engagement Programs This is simply the number of Engagement Programs that can be created in a subscription.

In our June 2022 release notes, we have announced that functionality Forms 1.0 assets will be completely removed from Marketo Engage including the ability for form submissions to be made to the leadCapture/save endpoint. This change will irreversibly break Forms 1.0 assets on Marketo Engage Landing Pages or embedded in external websites so that they can no longer accept submissions. Our modern Forms asset, Forms 2.0, will continue to be supported and will face no interruptions.   To aid in identifying which Forms 1.0 assets are in your subscription we have created a tool accessible by users with the Admin role. To use the tool, follow these instructions:   Navigate to Admin -> My Account. Take note of your data center in the “Support Information” panel. In your URL bar, navigate to app-[your data center].marketo.com/supportTools/formIdentification. In the tool, click “Get Form 1.0 List”. Your list of Forms 1.0 assets are returned. Each Form name is a hyperlink that will open in a new tab to the Form Asset page where you can view more information including what Marketo Landing Pages the Form is used on. Only references to Marketo Landing Pages will be of concern; references to these Forms will continue to work in Smart Lists filters.   The Forms 1.0 assets will be disabled on October 14, 2022 with no option for extensions or exceptions. Please complete your review of your form usage beforehand and replace any in-use Forms 1.0 asset with an equivalent Forms 2.0 asset.