Product Documents

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.               

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)  

In January 2021, we released the Submit Form API endpoint to give Marketo Engage integrators the ability to submit to Marketo Forms through a supported and authenticated REST endpoint. Thanks to customer feedback we were able to identify a lack of parity for critical functionality such as correct handling of duplicate records and support for Program Member Custom Fields. These issues blocked some integrators from successfully onboarding onto the Submit Form API endpoint.   In our August release, we have enhanced the Submit Form endpoint to handle duplicate records the same way as Marketo forms. When there are duplicate records that match an email address submitted to the form, the endpoint will update the record with the most recent Last Modified Date.   In our October 22, 2021 release, we plan to release support for Program Member Custom Fields for the Submit Form REST API endpoint. We understand that integrators will need time to update and test these new changes before they can fully onboard onto the Submit Form endpoint. To allow additional time for migration, we are delaying blocking programmatic POSTs to the /save2 endpoint to our January 21, 2022 release. This will be the final extension.   Programmatic submissions to our form endpoints remain unsupported despite this delay. Please work to update integrations submitting via this method to one that is supported: Marketo Engage forms on Landing Pages or using the embed code, our Forms2.js API, or the Submit Form API endpoint.   Previous announcement: https://nation.marketo.com/t5/product-documents/updated-april-2021-upcoming-changes-to-the-marketo-engage-form/ta-p/306631

One of the biggest gains to productivity you can employ with Executable Campaigns is the ability to pass the token context of the parent campaign to child campaigns.  This allows you to template your campaigns to use contextual data from the parent and then put it into practice within reusable executable campaigns.  It also allows you to set up My Token values as defaults, and then override them by setting them in the calling campaign.  Let’s take a look at an example: Evaluating activity scores   Evaluate Activity Score   Most Marketo subscriptions use activity or behavioral scoring to some extent, and executable campaigns make it easier than ever to create an effective activity scoring model.  By using the same My Token keys in the parent and child campaigns we can craft an activity scoring campaign that can be used by any triggered activity in a single workspace.  This is what a basic templated scoring flow looks like.  The interesting moment is configured to stamp that activity log with the parent campaign name and ID for debugging purposes, and should be omitted for performance reasons in production.   Note how the Change Score step has a Change value of {{My.Activity Score}}.  This is defined as +0 in the Evaluate Activity Score program, so if executed with overriding the token context, or if the value is not defined in a calling campaign, then that will be the value used:   Calling the Campaign   Suppose you want to score when someone fills out a particular form, but you also want to apply a score when they are created by filling out that same form.  In this case you would need two campaigns, each with their own parent program.  Our New Lead campaign needs to listen to the “Person is Created” activity, needs to execute the Evaluate Activity Score campaign, and needs {{My.Activity Score}} to be defined:       Configured this way, our New Lead campaign will call the child campaign with the parent campaign’s context and increment the score by +15 and then move on to the rest of the flow. For our campaign that’s listening for a form fill, but not creation, we only need to configure the trigger and My Tokens differently:     When a lead qualifies for a run through our Evaluate Activity Score campaign, we see that the Person Score is correctly incremented by +15 when it goes through our campaign:   Working with this pattern   This pattern can be applied and modified to work with many different scoring and lead lifecycles.  There are a few things to keep in mind, though: If you are nesting executable campaigns, I.e., using the Execute Campaign step within an executable campaign, you need to set Use Parent Token Context to true through each layer where you need to use token context in the child campaign.  Using folder-based My Token inheritance can help ensure a value is set in all of your relevant folders.  For example, if all of your scoring listener programs and campaigns live in a single folder tree, you can set a {{My.Activity Score}} at the top level folder, which can then be overridden at the local program level. My Tokens that you want to override in an executable campaign should be set in both the child and the calling campaign, as well as any campaigns between the initial caller and the ultimate child. As designed, each campaign that wants to call the Evaluate Activity Score campaign, needs to be in its own program (or Campaign Folder) in order to have its own specific {{My.Activity Score}} token.  More than one score per program needs either multiple “Change Score” steps in your evaluator campaign, each with a distinct score token, e.g. {{My.New Lead Score}} = +15 vs. {{My.Form Fill Score}} = +5 vs {{My.Unsubscribe Score}} = -10, or a distinct campaign for each score-activity pair that you want to score distinctly Pair this with the suggested categorization model for Executable Campaigns for best results.

*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.     

Apple recently announced new features in their upcoming iOS and macOS releases which are designed to protect data from third parties. A broad set of FAQs on the potential impact can be found on Adobe Experience League. We have provided an additional set of Marketo Engage-specific FAQs below. Since the new features have not yet been released by Apple, much of the information below is speculative. We plan to post updates as we learn more, so please stay tuned.  UPDATE: iOS 15 is now generally available on both iPhone and iPad.  We have conducted tests using iPhones running iOS 15 with Mail Privacy Protection enabled.  Please see updates to this FAQ below (in red).    Will this impact email open-tracking in Marketo Engage?  Highly likely. Early reports suggest that the open-tracking pixel contained in Marketo emails may be obscured and downloaded as a background process, irrespective of how you interact with the email. It is possible that an email open could occur without opening the email, which could artificially inflate the number of email opens. Also, the timing of when an email open activity is generated could be impacted since it may be decoupled from the actual open.  UPDATE: Yes, we confirmed that unopened emails can trigger an email open activity.   Test Methodology We used a batch campaign to send a test email to 5 testers with Mail Privacy Protection enabled on their iPhones.  We instructed each tester to not open the email and then waited 1 week before checking results.  Create a static list of test leads Create a batch campaign to send an email to members of static list Run campaign once Wait for 7 days and inspect campaign results   Observations After the 7 day wait, we found that 3 of the 5 unopened emails had open email activities logged in Marketo.  These activities were “machine-generated” due to a background load of the open-tracking pixel that occurs when Mail Privacy Protection is enabled.  For the 3 machine-generated opens, we found that 1 occurred within minutes of delivery, and the other 2 occurred several hours after delivery.    We then had testers go ahead and open the delivered emails.  For the 2 emails that did not machine-generate an open,  we found 2 email open activities were logged as usual.  For 3 emails that did machine-generate opens, no additional open activities were observed as expected.  This is because Marketo only ever records a single email open activity for any given campaign/mailing/lead combination.   We ran same test with Mail Privacy Protection disabled and did not observe any machine-generated opens.   To summarize: When Mail Privacy Protection is enabled, some delivered emails will have machine-generated opens, and the timing of when machine-opens occur is unpredictable. When Mail Privacy Protection is disabled, no machine-generated opens occur. Will this impact email link click tracking in Marketo Engage?  It is unlikely that tracked links will be impacted.  UPDATE: No, we confirmed that click email activities are logged as expected.  No change here.   Which product areas within Marketo Engage might be affected?  While there is no immediate impact right now, here is a quick look at the potential areas of impact within Marketo Engage.   Assuming that email opens may not be accurately trackable in the native Mail app, and that a user’s IP address will be altered by the native Email app and the Safari browser, we have identified the following areas of potential impact.  Activities It is hard to predict what the impact will be on the “Open Email” activity. For example, if the open-tracking pixel request is generated even though the email is not actually opened, then email opens could be overcounted. Also, the time of the open-tracking pixel request could differ from the time of the actual email open. Finally, there are activities that contain a “Client IP Address” attribute which may not be as accurate as before (Visit Web Page, Fill Out Form, Click Link, Unsubscribe Email).  UPDATE: There is no way to identify which open email activities are machine-generated, and which are not.  Machine-generated opens will likely increase the overall number of opens, but by how much is hard to know.   The User Agent on iOS15 has changed to simply “Mozilla/5.0”.  Since some activities contain metadata that is derived from User Agent, some of this metadata has changed (Platform, Device, User Agent, Is Mobile Device).   Open Email Activity - Before iOS15 Open Email Activity - After iOS15   This could impact your smart lists should they leverage these attributes as constraints.   Here is an idea that could help provide insight into iOS15 adoption.    First, build a smart list that looks for leads that have opened email using an earlier version of iOS. Since at the time of writing, iOS15 is only available on iPhone/iPad, we limit results to those devices only. Click on the People tab and record the number of list members (in lower righthand corner). Next, add another filter to smart list for leads that have opened email using iOS15. Since at the time of writing, iOS15 user agent is "Mozilla/5.0", we limit results to that browser only.  This provides the list of leads that have opened email using a prior version of iOS and using iOS15 in past 30 days.  Click on the People tab again and record the number of list members. You can then compare the two results and gain insight into iOS15 adoption.     Here are some of our test results over the past 30, 60, and 90 days. Date of Activity (in Past) 30 Days 60 Days 90 Days Device iPhone/iPad 23,723 38,901 52,964 Device iPhone/iPad & Browser Mozilla/5.0 1,160 2,621 3,444 iOS 15 Adoption Rate 4.9% 6.7% 6.5%   From this list, you can inspect the lead activity history and identify when a lead switched over to iOS15. Your mileage may vary!   Reporting Email opens can be inferred through email link clicks without the open-tracking pixel being activated, but reporting may be impacted. The “Opened”, “% Opened”, and “Clicked to Opened Ratio” columns in Email Performance Report columns may contain less accurate data. Also, any open-related measures or fields in Revenue Cycle Analytics Email Analysis Report may contain less accurate data.   UPDATE: There is no way to identify which open email activities are machine-generated, and which are not.  Machine-generated opens will likely increase the overall number of opens, but by how much is hard to know.   A/B Testing If you use Opens as Winner Criteria, then test results may be impacted since this criteria relies on accurate email open tracking.  UPDATE: See Reporting (above).   Web Personalization The “Location” and “Industry” firmographic Web Segments may not match as they had before. This is because the segment attributes are derived by doing a lookup using the client IP address.  UPDATE: See Inferred Fields (below).   Inferred Fields Since client IP address may not be as accurate, Inferred Fields may be impacted. Send In Recipient Time Zone can use inferred fields to calculate time zone (as a fallback when known location fields are not populated). Lead to Account Matching can also use inferred company name field in matching logic. UPDATE: The client IP address behavior on iOS15 has changed.  To allow users to hide their IP addresses from websites and network service providers, requests now go through an Apple proxy server. The proxy server assigns an IP address from a pool of users grouped by their approximate location.  As a result, the location information stored in Marketo inferred fields will be less precise.  Best practices for using inferred data can be found here.   As a Marketo Engage user, what can I do now to prepare for this change?  Review your usage of product areas described above and assess potential impact. Reduce dependency on email open rates. Look for activities from the click onward to measure engagement. Think about how you measure success of your email campaigns and how email opens fit into your overall methodology. Gather device and OS data to understand potential impact. This can be done using either Email Insights or Smart Lists as described here.  UPDATE: Reduce dependency on email open rates.   As a Marketo Engage user, what should I be thinking about in the future?  Email opens are not the most important indicator for measuring success of your email campaigns. Email is the vehicle by which you drive your customers to a landing page to convert via filling out a form or other action. Web page visits, link clicks, and form fills are the high value activities that you should concentrate on.    Geographic and firmographic data based on client IP address lookup is not entirely accurate since many IP addresses return data for the Internet Service Provider instead of the actual user. In some cases, an IP address lookup will return no data at all. An alternative could be to use a third-party data enrichment service.    Privacy changes are transforming email as we know it. Changes to proxies, location data, and blocked email opens present new challenges to email measurement. Here are Deliverability resources that may prove useful to address those challenges:  Optimizing Marketo Engage Email Deliverability  Email Deliverability 101: 4 Tips to Inbox Success 

Deprecation of Email V1 began almost two years ago and beginning with the March maintenance release to London & Netherlands subscriptions on March 17th, 2021 and all other subscriptions on March 19th, 2021, all API support for V1 emails will be ended.  After 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 24th, 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. 

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

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.

What’s changing?  Beginning in January 2021, we will be rolling out two email tracking-related security improvements over the course of several months.  In Q3 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 those dates draw near.    Background: Email Link Tracking  By default, links in emails have tracking embedded which allows 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 images 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 clicked 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 tracking parameter expiration and tracking link change are additional steps 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 Images  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 is clicked in an email that is over 6 months old, and the click sends 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. 

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 improvements 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 31st, 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. 

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.

  Beginning on 2020-05-07, Marketo will start to roll out version 159 of the Munchkin JavaScript Client.  Subscriptions which have the Munchkin Beta flag 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 release 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 functionality 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 correctly 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.  This 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-06-05  Beta  100%  2020-06-19  General Availability  10%  2020-07-10  General Availability  50%  2020-08-04  General Availability  100%   

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!  

Over the last few years all these translations have been gathered together by my colleagues. One of them had kindly gathered them into this beautiful display and I thought it was worth sharing with you all. CTAs English Simplified Chinese (CN-S) Traditional Chinese (CN-T) Portuguese (PT) Japanese (JA) Spanish (ES) Korean (KO) German (DE) View Now 现在就查看 現在就查看 Veja agora 今すぐ見る Vea ahora 지금 보기 Read More 阅读更多 閱讀更多 Leia mais さらに読む Lea más 더 읽기 Watch Video 观看视频 觀看視頻 Assista ao video 動画を観る Vea el video 비디오 보기 Learn More 了解更多 了解更多 Aprenda mais さらに学ぶ Aprenda más 더 알아보기 Read the brochure 查看资料手册 查看資料手冊 Leia o material 小冊子を読む Lea el folleto 브로슈어 읽기 Broschüre lesen Register today 今天就注册 今天就註冊 Inscreva-se agora 今すぐ登録する Regístrese hoy 오늘 등록하기 Explore more opportunities 发掘更多机会 發掘更多機會 Explore mais oportunidades 他の機会も探る Explore más oportunidades 더 많은 기회 알아보기 Read full report 查看完整报告 查看完整報告 Leia o relatório completo 完全レポートを読む Lea el informe completo 보고서 전문 보기 Read article 阅读全文 閱讀全文 Leia o artigo 記事を読む Lea el artículo 기사 보기 Read press release 阅读新闻稿 閱讀新聞稿 Leia o release de imprensa プレスリリースを読む Lea el comunicado de prensa 보도자료 보기 View tool 查看工具 查看工具 Veja a ferramenta ツールを見る Vea la herramienta 도구 보기 View quotes 查看报价 查看報價 Veja as cotações 相場を表示する Vea las cotizaciones 시세 보기 View contract specifications 查看合约规则 查看合約規則 Veja especificações de contrato 商品仕様を見る Vea las especificaciones de contrato 상품 명세 보기 Listen to podcast 收听广播 收聽廣播 Ouça o podcast ポッドキャストを聴く Oiga el podcast 팟캐스트 보기 View presentation 查看 查看 Assista à apresentação プレゼンテーションを見る Vea la presentación 프리젠테이션 보기 Get started 开始 開始 Aprenda 今すぐ始める Comience a aprender 시작하기 View offerings 查看产品及服务 查看產品及服務 Veja ofertas 商品とサービスを表示する Vea las ofertas 제안 보기** View schedule 查看日程安排 查看日程安排 Veja programação 予定を見る Vea el programa 스케줄 보기*** Read white paper 阅读报告 閱讀報告 Leia relatório oficial 白書を読む Lea el libro blanco 백서 읽기 Read fact card 阅读事实卡 閱讀事實卡 Leia o cartão de dados パンフレットを読む lea la tarjeta de datos 팸플릿 읽기**** Download PDF 下载PDF文档 下載PDF文檔 Baixe o PDF PDFをダウンロードする Descargar PDF PDF다운로드 PDF herunterladen Items found on Research Articles English Simplified Chinese (CN-S) Traditional Chinese (CN-T) Portuguese (PT) Japanese (JA) Spanish (ES) Korean (KO) German (DE) View this article in PDF format. Leia este artigo em formato PDF. Ver este artículo en formato pdf. Diesen Artikel als PDF anzeigen. About the Author 关于作者 演说者简介 해설자 소개 Über den Autor Disclaimer Common Headings English Simplified Chinese (CN-S) Traditional Chinese (CN-T) Portuguese (PT) Japanese (JA) Spanish (ES) Korean (KO) German (DE) Resources 资源 資源 関連情報 참고 자료 View in: English 简体中文 (CN-S) 繁體中文 (CN-T) 日本語 (JA) 한국어 (KO) Português (PT) Español (ES) 语言： 語言： Ler em: 使用言語: Ver en: 언어: Key Features 主要特点 主要特點 Principais características 主な特長 Principales características 주요 특징 Key Benefits 主要优势 主要優勢 Principais benefícios 主なメリット Beneficios clave 주요 혜택 Contact Us 联系我们 联系我们 Entre em contato conosco: お問合せ先 Contáctenos: 연락처 In the News 相关新闻 相關新聞 É notícia 関連ニュース Recursos 뉴스 화제 Figure 1 图1 圖 1 Gráfico 1 図１ Figura 1 그림 1 Abb. 1 Getting Started 简介 簡介 Começando ご利用を始めるにあたって Primeros pasos 시작하기 Related Content 相关资料 相關內容 Conteúdo relacionado Contenido relacionado Forms English Simplified Chinese (CN-S) Traditional Chinese (CN-T) Portuguese (PT) Japanese (JA) Spanish (ES) Korean (KO) First Name 氏 氏 Primeiro nome 氏 Nombre 이름 Last Name 姓 姓 Sobrenome 姓 Apellido 성 Business email 电子邮箱 電子郵箱 Email corporativo 業務用メールアドレス Correo electrónico empresarial 이메일 Phone number 电话号码 電話號碼 Telefone 電話番号 Número telefónico 전화번호 Country 国家 國家 País 国 País 국가 Address 地址 地址 Endereço 住所 Domicilio 주소 City 城市 城市 Cidade 市町村 Ciudad 도시명 State 省 省 Estado 州・都道府県 Estado 주 Firm name 公司名称 公司名稱 Nome da empresa 会社名 Nombre de la empresa 회사명 Company Type 公司类型 公司類型 Atividade da empresa 会社の種類 Tipo de empresa 회사 유형 Job Function 工作职能 工作職能 Função 職務権限 Función del cargo 담당 업무 Comments/Specific Interest 评论/咨询 評論/諮詢 Comentários/Interesse específico コメント／質問 Comentarios/Interés específico 건의사항 또는 관심 사항 Submit 提交 提交 Enviar 送信 Enviar 제출 Regulator 监管者 監管者 Regulador レギュレータ Regulador 규제당국 Vendor 供应商 供應商 Fornecedor ベンダー Proveedor 벤더 Other 其他 其他 Outro その他 Otro 기타 Indicates required fields. 必填项 必填項 Indica campos obrigatórios 入力必須の項目です。 Indique los campos requeridos 필수 항목을 가리킴 Contact Us 联系我们 聯繫我們 Entre em contato conosco お問合せ先 Contáctenos 연락처 Must be valid email. Example@yourdomain.com 请填写有效邮箱, Example@yourdomain.com 請填寫有效郵箱, Example@yourdomain.com E-mail válido é necessário. Exemplo@seudominio.com 有効なメールアドレスでなければなりません。例：Example@yourdomain.com Debe ser un correo electrónico válido. Ejemplo@sudominio.com 유효한 이메일이어야 합니다. Example@yourdomain.com This field is required. 该项是必填项 該項是必填項 Este campo é obrigatório. この項目は必須です。 Se requiere este campo. 이 항목은 필수항목입니다. Thank you. Your message has been received. Someone will contact you shortly 您好，您的信息已收到，我们的工作人员会尽快与您联系 您好，您的信息已收到，我們的工作人員會盡快與您聯繫 Obrigado. Sua mensagem foi recebida. Você será contatado em breve. ありがとうございました。メッセージを受信いたしました。こちらよりご返信いたします。 Gracias. Hemos recibido su mensaje. En breve, una persona se pondrá en contacto con usted. 감사합니다. 귀하의 메시지가 접수되었습니다. 곧 연락 드릴 예정입니다. Executive 行政管理 行政管理 Executivo 幹部 Ejecutivo 임원 Finance 金融 金融 Finanças 財務 Finanzas 재무 Marketing 市场营销 市場營銷 Marketing マーケティング Marketing 마케팅 Research 研究 研究 Pesquisa リサーチ Investigación Research Sales 销售 銷售 Vendas 営業 Ventas 영업 Technology 技术 技術 Tecnologia テクノロジー Tecnología 전산 Trading 交易 交易 Negociação トレーディング Operaciones 운용 Other 其他 其他 Outro その他 Otro 기 Select… 选择… 選擇… Selecione... 選択してください…… Seleccionar… 선택… Submit 提交 提交 Enviar 送信 Enviar 제출 First Name: 名： 名： Nombre: 名： Primeiro nome: 이름: Last Name: 姓： 姓： Apellidos: 姓: Sobrenome: 성: Comments/Questions: 评论/问题： 評論/問題： Comentarios/Preguntas: コメント／質問： Comentários/questões: 코멘트/질문： Submit 提交 提交 Enviar 送信 Enviar 제출 Contact Us 联系我们 聯繫我們 Contacto お問合せ先 Entre em contato conosco 연락처 Welcome back, [name] 欢迎回来， [姓名] 歡迎回來，［姓名］ Bem-vindo de volta, [name] 再ログインありがとうございます、 [氏名]様 Bienvenido nuevamente, [nombre] [이름]님 다시 오셔서 환영합니다. Click here if this is not you. 如果您并非所示姓名本人，请点击这里。 如您並非所示姓名本人，請按此。 Clique aqui se não for você. [氏名]様ではない場合は、ここをクリックしてください。 Haga click aquí si éste no es usted 다른 사람이시면 여기를 클릭하십시오 Topic 主题 主題 Tópico トピック 주제 Select One 请选择一个 請選擇一項 Selecione um 一つ選択してください 하나를 선택하십시오 Register for future communications 注册日后接收通讯 登記日後收取通訊 Inscreva-se para contatos futuros 今後の通知を受け取るための登録 향후 커뮤니케이션을 위해 등록하십시오 Thank you for registering. ご登録いただき、ありがとうございます。

I created this as I was studying for the Revenue Cycle Analytics exam. I tried so hard to understand Attributions in Marketo by watching a video about attribution in Marketo University, as well as reading the Product Docs. However, it took me so long until I am able to fill in data for the attribution tables. The Revenue Cycle Analytics Certification may be closed soon, but I do hope my note and explanation would be beneficial, and would complement Marketo's Product Docs in regards to understanding Attributions