Product Documents

Sort by:
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.    
View full article
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 will be making changes to the URL structure for Landing Pages, Forms, and Images & Files assets.   Why is this change being made? Technical Details Landing Pages Images & Files Forms What customer action is required?   When is this change being made? Starting January 21, 2021, we will begin gradually provisioning new Marketo Engage subscriptions with the new URL structure. On March 5, 2021, all new Marketo Engage subscriptions will be provisioned with the new URL structure in place.   For existing Marketo Engage subscriptions, we will begin gradually rolling this change out beginning April 1, 2021. More details on our rollout timeline will be released in March, 2021.   April 2021 update Starting in March 2021, a subset of new Marketo subscriptions will be provisioned with the new Design Studio URL structure. Beginning with our May 7th release, all new subscriptions will be provisioned with the new Design Studio URL structure.   Existing subscriptions will be gradually migrated through a rollout beginning May 20th.    Why is this change being made? When a Marketo Engage subscription is not configured with a branded CNAME, Design Studio assets use a common hostname shared among all customers on the same pod. This behavior can be exploited in a phishing attack where a user cannot be sure a link to a Marketo Engage hosted asset belongs to the business they expect it to belong to. By updating each instance to use its own unique hostname, it is clearer to users the destination of URLs they are accessing.   Technical Details Landing Pages, Form embed code, and resources stored in Images & Files will have URLs updated from a hostname shared among all subscriptions on the pod to a hostname unique to each Marketo Engage subscription. Subscriptions configured to use a custom CNAME for their landing pages will be minimally affected by this change.   Landing Pages Subscriptions without a configured landing page domain Landing page paths will change to a unique hostname for your subscription. Before: http://na-sj01.marketo.com/lp/123-ABC-456/unsubscribePage.html After: http://123-ABC-456.mktoweb.com/lp/123-ABC-456/unsubscribePage.html   Subscriptions with a configured landing page domain Landing pages will continue to load from your configured landing page domain. No changes will be made. Before: http://example.marketo.com/unsubscribePage.html After: http://example.marketo.com/unsubscribePage.html   Images & Files Subscriptions without a configured landing page domain Paths to resources stored in Images & Files will change to a unique hostname for your subscription. Before: http://na-sj01.marketo.com/rs/123-ABC-456/images/cuteKitten.png After: http://123-ABC-456.mktoweb.com/rs/123-ABC-456/images/cuteKitten.png   Subscriptions with a configured landing page domain Resources stored in Images & Files will continue to load from your configured landing page domain. No changes will be made. Before: http://example.marketo.com/rs/123-ABC-456/images/cuteKitten.png After: http://example.marketo.com/rs/123-ABC-456/images/cuteKitten.png   Forms Subscriptions without a configured landing page domain OR subscriptions without landing pages secured by SSL Before:               <script src="//app-sj01.marketo.com/js/forms2/js/forms2.min.js"></script> <form id="mktoForm_1"></form> <script>MktoForms2.loadForm("//app-sj01.marketo.com", "123-ABC-456", 1);</script>               After:               <script src="//123-ABC-456.mktoweb.com/js/forms2/js/forms2.min.js"></script> <form id="mktoForm_1"></form> <script>MktoForms2.loadForm("//123-ABC-456.mktoweb.com", "123-ABC-456", 1);</script>                 Subscriptions with a configured landing page domain secured by SSL In our October 2020 release, we updated our form embed code to load from the landing page domain when it is secured by SSL. No further changes will be made. Before:               <script src="//example.marketo.com/js/forms2/js/forms2.min.js"></script> <form id="mktoForm_1"></form> <script>MktoForms2.loadForm("//example.marketo.com", "123-ABC-456", 1);</script>               After:               <script src="//example.marketo.com/js/forms2/js/forms2.min.js"></script> <form id="mktoForm_1"></form> <script>MktoForms2.loadForm("//example.marketo.com", "123-ABC-456", 1);</script>                 What customer action is required? Marketo Engage subscriptions provisioned after May 7, 2021 will have the new URL structure already in place for all Design Studio assets.   Existing Marketo Engage subscriptions will be migrated in a staggered rollout to the new URL structure during nightly maintenance cycles beginning on May 20th. There will be no downtime, but landing pages may experience a short period of degraded performance during migration.   Existing URLs and references will continue to work after the migration to the new URL structure until June 30, 2022. 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.   To begin preparing for this change, we suggest doing the following: Configure your Landing Page URLs with a CNAME https://docs.marketo.com/display/public/DOCS/Customize+Your+Landing+Page+URLs+with+a+CNAME Secure your Landing Pages with SSL https://docs.marketo.com/display/public/DOCS/Add+SSL+to+Your+Landing+Pages Begin updating pages where you embed Marketo Engage forms with the new embed code introduced in our October 2020 release (requires secured landing pages) Begin an audit of where you reference Design Studio assets on the web. This will help you begin a plan to update any existing references to our older URL structure before we begin deprecation in 2022. Generally this will be on non-Marketo pages, as our Landing Page editor will automatically format embedded images and forms in a compatible manner. Only references hardcoded to the old URL structure need to be updated, e.g.   http:// na-sj01.marketo.com /rs/123-ABC-456/images/cuteKitten.png. Relative references will continue to work without need changes e.g.  /rs/123-ABC-456/images/cuteKitten.png. Please work with your web developer to determine where you may need to make updates.
View full article
IMPORTANT UPDATE "Match with Hidden link UA/IPs" filtering method has been too aggressive and resulted in many false positives. So the new patterns were rolled back in May. For now, we plan to launch back only the "Match with proximity pattern" filtering method in the 3rd week of July. The following blog has been updated accordingly to reflect the upcoming release changes   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   For May 2022 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 total 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 more than 2 activities happen at the same time i.e under 2 seconds, they are identified as bots too. This pattern should identify activities generated by the link scanners. Going forward 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 above-mentioned order.    Note: You will have the option to filter out i.e not log activities that are identified by IAB list but for not for proximity pattern in this current release.   If you wish to have all activities even if they are by a bot or not, then choose the "log activity" option, this way all activities will still go through identifications using 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)  
View full article
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  
View full article
October 2021 Update https://nation.marketo.com/t5/product-documents/update-to-deprecation-of-programmatic-form-submission-methods/ta-p/317522#M1062 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. April 2021 Update   In November 2020, we announced that we will forbid programmatic Form POST submissions to our /save and /save2 endpoints beginning May 7, 2021. The reason for this change is to reject methods of unsupported form submissions used by bots to fill customer databases with spam data.   We understand that many customers may need more time to update the integrations to use a supported method such as the Forms2.JS API or the Submit Form REST API endpoint. We have decided to extend the deadline in which we will begin blocking all programmatic Form submissions to take place on October 15, 2021. Programmatic FORM submissions continue to be unsupported and while we are temporarily delaying enabling validation to reject these submissions, we cannot ensure uninterrupted submission following  upcoming product and infrastructure changes.   For customers that still wish to block this method of form submission to address bot attacks,   will allow you to opt-in to form submission validation on your subscription. This validation will check that form submissions are coming from Marketo Forms, Forms2.js API, or the Submit Form REST API and will reject it otherwise. This is expected to block many common sources of bot attacks.   However, if you have a form integration that currently uses programmatic Form POST to submit lead data, enabling this feature will also block your Form submissions. We encourage all customers to migrate to a supported method of form submissions as soon as possible to protect their subscriptions from bot attacks.   The original announcement is below for reference. The details remain the same aside from the schedule to block programmatic form POST submissions.   What’s changing? In our May 7, 2021 release, Marketo Engage will be making changes to our form platform to protect the stability and security of our infrastructure:   Forms 1.0 will be fully deprecated, resulting in loss of functionality of any remaining Forms 1.0 assets still in use. Marketo Engage will begin rejecting form submissions made through unsupported methods, such as programmatic form POSTs to the leadCapture/save and leadCapture/save2 endpoints.   Why is this change being made? On August 1, 2017, Marketo Engage deprecated the Forms 1.0 editor, removing the ability to create or edit Forms 1.0 assets. This change will complete our end of life efforts for Forms 1.0.   In addition, we have found that our Form endpoints “leadCapture/save” and “leadCapture/save2” are common targets for bot attacks. To protect the stability of the Marketo Engage infrastructure, and to aid customers in maintaining a clean database, we are completely disabling the “leadCapture/save” endpoint and enforcing checksum validation on the “leadCapture/save2” endpoint.   What customer action is required? Forms 1.0 deprecation Provisioning of Marketo Engage subscriptions with the ability to create Forms 1.0 assets ended December 31, 2014. If your subscription was provisioned after this date, then it will not have Form 1.0 assets. Forms 2.0 assets will be unaffected by this change.   Marketo Engage subscriptions provisioned before December 31, 2014 may still  be utilizing Forms 1.0 assets on their landing pages and website. These forms will need to be remade in our Forms 2.0 editor and replaced wherever they are still being used.   Programmatic Form POST deprecation Some integrations may be performing programmatic form POSTs to “leadCapture/save" or “leadCapture/save2” to submit data into Marketo Engage databases. This method of data ingestion has always been unsupported and will cease to work as part of this deprecation. All integrations using programmatic form POSTs must be updated to use our Forms 2.0 API, Push Lead REST API, or the Submit Form REST API endpoint releasing in the January 2021 release.   Customers using native Forms 2.0 assets on pages and/or the Forms 2.0 API do not need to take any action. Checksum validation will work natively with these supported methods.   What happens if customers don’t act? Customers that fail to replace any in-use Forms 1.0 asset with a Form 2.0 asset will find that their customers will be unable to submit to their 1.0 Forms.   Customers using integrations that perform programmatic Form POSTs to the “leadCapture/save” or “leadCapture/save2” endpoints will see these integrations fail, resulting in loss of form submission data.   Is my Form 1.0 or 2.0? Forms 1.0 and Forms 2.0 have different look and feel:   Forms 1.0 Forms 2.0 Marketo subscriptions provisioned after December 31, 2014 will only have Forms 2.0 assets.
View full article
In 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
View full article
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.
View full article
Executable campaigns are a powerful new feature designed to allow you to make your campaign logic modular, reusable and maintainable.  However, staying within the limit of three nested executables can be difficult when your campaign trees get complicated.  This article describes a simple method of classifying your executables into three categories to help you stay within the nesting limits while also remaining productive.     Three Categories for Executable Campaigns   This classification system has three categories with simple definitions:   Tier 1: These campaigns may not be executed by other executable campaigns   Tier 2: These campaigns may not execute other Tier 2 campaigns   Tier 3: These campaigns may not execute any other campaigns       By classifying your campaigns in this way, and abiding by their restrictions, you can avoid bumping up against the nesting limit.   Now we have a way to avoid the nesting limit, but how should you map your existing campaign logic and lifecycles into these categories? Let’s look at Tier 3 first, as it is the foundation of this model     Tier 3 – Task/Unit - May Not Execute Any Other Campaigns   Tier 3 cannot execute any other campaigns, and this is where individual tasks should be implemented.  Your organization can define what a task is in this context, but I think that it is useful to borrow the definition of  unit  from software development: A unit is the smallest testable part of any software.  In the context of Marketo, a unit is the smallest testable part of any campaign.   Let’s look at a common example for lead lifecycles: Taking a country input and outputting a country code to a different field.       The above is an abbreviated example using flow-step choices to match the value of Country to a particular country code.  Supposing we wrote a test for this, we would expect a lead who enters the flow with an empty value of “United States of America” to receive a Country Code value of “US”.   This or similar steps could be a unit for your business, but you do not need to limit your units to single steps.  Your Tier 3 task campaigns should tend to be short sequences of work which are used in multiple contexts     Tier 2 – Orchestration – May Not Execute Other Tier 2 Campaigns   Tier 2 (as well as Tier 1) are more flexible than Tier 3 campaigns as they can execute other campaigns themselves.  These executables can be used to string sequences of other campaigns together alongside standalone flow steps.  An example would be a Standard Data Enrichment campaign.  Where normalizing a country code is a unit or task, this is a sequence of one or more data enrichment tasks that can be maintained and modified separately from the logic of the individual tasks themselves     Tier 1 – Last-Mile – May Not Be Executed by Other Executable Campaigns   You may find that your business does not need to use Tier 1 campaigns, and that you can satisfy your organizational needs with just Tier 2 & 3 campaigns.  However, Tier 1 campaigns allow an additional layer of flexibility for you to manage your campaigns.  Typically, one of these campaigns will call a mix of individual flow steps, and Tier 2 & 3 campaigns to assemble a flow for a typical lifecycle event, like a Standard New Lead Flow.  These typically include data enrichment, normalization, scoring, and routing flows, which can be created as tier 2 or 3 campaigns.        
View full article
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.  
View full article
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.   
View full article
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.  
View full article
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. 
View full article
In late 2020, Apple announced their intent to  add a new feature to their Intelligent Tracking Prevention implementation  in Safari  called  CNAME Cloaking Defense , to be rolled out with the release of Safari and IOS 14 .   Like  many of the other efforts in Apple’s Intelligent Tracking Prevention schemes, t his feature is designed to  limit  the lifespan of cookies set by hosts which have a CNAME  pointing to a domain name which does not match the visited page’s domain name  to seven days .    Since Munchkin JS  uses  cookies  set by  a CNAME, and the underlying host to which the CNAME  ({your instance }.mktoweb.com )  points   will never match the  domain name of a visited  page ,  cookies set by Munchkin in Safari 14  browsers  will be capped to a  seven-day  lifespan.    While the reduction in cookie lifespan will have some effect on tracking known leads , traffic from Safari generally  represents  less than 10% of requests handled by Munchkin.        T he re are no apparent easy solutions to this  issue,  and each would require  significant intervention  both  on the part of  Adobe engineering and  subscribers .    Adobe will continue to explore long-term options for improving consistency and accuracy of web tracking behaviors, but at this time we have decided not to t ake any extraordinary measures to try to circumvent this change and restore  long lifespans for Munchkin cookies.  Instead,  we have decided to  focus  on  our efforts  to  integrate  Marketo  web tracking with the  Adobe Web SDK   so that all Adobe  Marketo  En gage  customers  can benefit from our best-in-class web tracking solution.   We will have more information to share when we are closer to release of this solution.  
View full article
Deprecation of Email V1 began  almost  two years ago  and beginning with the  March  maintenance   release to London & Netherlands subscriptions on  March 17 th , 2021  and all other subscriptions on March 19 th , 2021 , all API support for V1  e mails will b e ended.  A fter this release,  any attempts to interact with V1 emails via the Asset APIs will result in errors and no actions taken .  All known remaining users since  February 24 th , 2021  have been notified ,  but  it is possible  that there are still integrations which may attempt to interact with these assets.  The most common types of affected integrations are services  which  offer digital  asset management, translation, and localization .     If you do observe integration failures as a result of this change,  you will still be able to upgrade problematic assets  by editing and approving them .  Once an email asset is upgraded to V2, you should be able to resume using it with integrated services.  
View full article
How does Marketo Engage define a Sales Insight “Active User”? If a sales rep has interacted with the Sales Insight panel in the last 30 days, we consider him//her to be an active user once we remove duplicates user.  Every week, we look at our logs over the last 30 days for certain types of activities that a unique user would do within our Sales Insight panel. Here is the list of activities that are considered as product usage: Marketo tab: Clicking on Best Bets tab and the following actions within the tab Clicking on Edit & Create New View Clicking on “Hide” option Clicking on My Watch List tab and the following actions with the tab Clicking on Edit & Create New View Clicking on “Remove” option Clicking on Web Activity tab and the following actions with the tab Clicking on Edit & Create New View Choosing time frame option from drop down Clicking on Anonymous Web Activity tab and the following actions with the tab Clicking on Edit & Create New View Choosing time frame option from drop down Clicking on My Email tab and the following actions with the tab Clicking on Edit & Create New View Clicking on email link to preview email Clicking on Lead feed and the following actions with the tab Subscribe to an Interesting Moment from lead feed Visualforce panel on Contact/Lead/Account/Opportunity: Clicking on 4 tabs: Interesting Moment, Web Activity, Email, Score Clicking on “Full List” hyperlink at the bottom of the visual force page to access full list Marketo tab Top Nav (only on lead/contact) Choosing “Add/Remove to watch list” from actions drop down, clicking on “Go” button Choosing “Add to Marketo campaign” from actions drop down, clicking on “Go” button Choosing “Send Marketo email” from actions drop down, clicking on “Go” button Clicking on Interesting Moment tab and the following actions with the tab Clicking on “Subscribe” option Clicking on Web Activity tab and the following actions with the tab Clicking on Web page link Clicking on page/referrer link Clicking on Email tab and the following actions with the tab Clicking on email link to preview email When a sales user navigates to any CRM layout that has Sales Insight, the panel loads automatically. The loading of panel is not considered as actual usage. We only consider users who actively interact with the panel.    How does Marketo Engage determine how many Sales Insight (MSI) users I have? We generate a report that logs certain types of activities that an “active user” would do and then remove duplicate users. If there has been one or more of these activities in the last 30 days, we consider this to an individual active user   How do I pull a list of my Sales Insight users? Please reach out to your CSM. He/she will be able to provide your usage report for you.   How do I limit Sales Insight usage? You can monitor Sales Insight seats by creating a Sales Insight profile and assigning it to a Sales Insight Layout or to any existing layout you would like to use. Detailed instruction can be found here - https://docs.marketo.com/display/public/DOCS/Setting+up+Sales+Insight+for+your+Team   How do I start monitoring Sales Insight seats as an existing user? The next time you upgrade your package, rather than installing upgrade for all users you can install it only for admins or for specific profiles you’ve created for Sales Insight. Detailed instruction can be found here https://docs.marketo.com/display/public/DOCS/Upgrading+Your+MSI+Package   How do I determine which version of MSI we are on? In your Salesforce CRM. Click on Set Up > Search for “Installed Packages” in Quick Find search field > Look for “Marketo Sales Insight” under Package Name column > Look for corresponding version number under “Version Number” column  
View full article
Support for Formula fields in batch campaigns was deprecated in 2013 and a notification was added to the product documentation here: Formula Fields. Currently, if a user attempts to schedule a batch campaign with an email that contains a formula field token WITHOUT spaces in the field name, the UI will show an error message saying this is not supported. However, due to an anomaly in the UI, if a user attempts to schedule a batch campaign with an email with a formula field token WITH spaces in the field name, the batch campaign will run. This UI issue was addressed in the January 2021 release of the product.   After March 19, 2021, these unsupported Formula Field tokens WITH spaces will no longer render correctly. Consequently, the tokens, and not the expected replacement strings, will appear in the final email. The deprecation is necessary to place all clients on a new, faster campaign processing platform.  To avoid further issues we recommend migrating the Formula Field tokens to Email Script Tokens immediately. Please refer to the following article which discusses how to use this option: https://docs.marketo.com/display/public/DOCS/Create+an+Email+Script+Token   If you have further questions about this issue, and/or best practices on migrating to Email Script Tokens, please contact Technical Support.  We want to ensure you have all the information you need to address the issue.   Kind Regards, The team at Adobe
View full article
Here are a few helpful tips regarding assigning a record to a queue when using the Sync Person to SFDC flow step:     If the record flowing through the flow step is a Marketo only record a new SFDC lead will be created SFDC Lead any field updates will be synced from Marketo to SFDC and the owner will change to the Queue SFDC Contact a new SFDC lead will be created The value in Marketo for Lead Owner for any records assigned to a SFDC Queue will be empty   Additional  resources   for learning about the Marketo integration with SFDC.
View full article
  The SFDC is Deleted field can be used to identify a SFDC Lead or Contact which used to be in SFDC but was deleted and now only lives in Marketo. Typically the record is deleted from SFDC for a specific reason and most customers will honor the deletion in SFDC by also setting up a smart campaign to also delete the record from Marketo.    If you decide to keep the deleted record (SFDC Lead or Contact) in Marketo to nurture it, the next time the record flows through the SYNC Person to SFDC flow step Marketo will insert it into SFDC as a new lead record. A strategy should be in place to make sure you're not syncing/inserting records you really don't want.   If you decide to delete a SFDC Lead or Contact in Marketo only you should only do it if you have a custom sync rule set-up. Otherwise the next time the record is updated in SFDC it will sync again to Marketo with a new Marketo ID.    Here are the steps to delete a SFDC record which is syncing to Marketo: Create Smart Campaign Set Smart List Set Flow Change Data Value of the "Sync to Marketo" field to False Wait 1 hour Delete record from Marketo only Schedule Run once     Additional  resources   for learning about the Marketo integration with SFDC.
View full article
If you create a multi-select field in SFDC, let's say it called "Product of Interest," it syncs as a string field in Marketo. If multiple values have been selected in SFDC, they will be separated by a semicolon, e.g. Frosted Flakes;Cheerios;Wheaties. If you use this field on a form, you will need to change the field type to Select to allow for multiple selections. If someone fills out the form and chooses Frosted Flakes and Cheerios, this will overwrite the existing values in the field and the field will now only say Frosted Flakes;Cheerios. These will resolve correctly in the SFDC multi-select field. If you don’t want to overwrite existing data create a Marketo custom field for your forms. Call It “Product of Interest for Web Forms” and set it up on the form exactly as you would have set up the multi-select field. Next create a smart campaign like the following in Marketo: Smart List: Trigger, Data Values Changes, Attribute – Product of Interest for Web Forms Flow: Change Data Value, Attribute – Product, New Value – {{lead.Product of Interest}};{{lead.Product of Interest for Web Forms}}. Now, if you fill out the form and choose Frosted Flakes and Cheerios on the form, the "Product of Interest for Web Forms" field will say Frosted Flakes;Cheerios and the Product field will say Frosted Flakes;Wheaties;Cheerios. This will resolve to the correct values in the multi-select list in SFDC.   Additional resources for learning about the Marketo integration with SFDC.
View full article
What’s changing?   Beginning i n  January 2021, we will  be  rolling out  two e mail tracking-related  security  improvements  over the course of several months .   In Q 3  of  2020 ,  a new  version of the Outlook Plugin will be available that also contains a security improvement.    This document serves to provide a high-level overview of the changes that are coming.  We will follow up with additional information as th ose  date s  draw near.     Background: Email Link Tracking   By default, links in emails have tracking embedded  which  allow s  you to see who clicked which link, how many total links were clicked, etc.   Link tracking is  configured  via the Insert/Edit Link dialog box  from within the email editor .     Predictive Image Tracking   When using Content AI, you can configure email images to be predictive.   Predictive image s have an URL and are   configured via the  “Make Predictive”  menu item within the email editor . Alternatively, you can  select  “Enable Content API” menu item within the email editor. Changes:   Tracking Link  Length   When link tracking  or predictive image  is enabled, the  original  URL specified is  converted into a “tracking link ”   that points  to a Marketo tracking server.  The format of  a  tracking link looks something like this:   http://mkto-q1234.com/Y0b020YU00000001NPR0wR0  After this change, the identifier  at the end of the URL will be slightly  longer .   Tracking Parameter Expiration   When a tracked link  or predictive image  is clicke d   from  within an email , the Marketo tracking server  logs a  “Click Email”  or “Click Predictive Content”  activity  and then  redirects  user  to the original URL  specified.   The tracking server appends   the “mkt_tok”  query parameter  which is  used  in conjunction with  Munchkin JS   to associate  the  Munchkin cookie with the   known lead that  clicked on the email link , and with the  campaign  that  sent  the email .    After  this change, mkt_tok  will expire  6 months after the email was sent.    As a result, if  a  lead  clicks on a link  in an email that is older than 6 months,  the webpage visit activity will be anonymous, and campaign  association will not occur.   This is  the same behavior as  when  tracking  is  disabled.   Outlook Plugin   With these changes a new upgrade of the Outlook plugin will be released. The new plugin will no longer support offline mode, and users will be required to have an active connection to the internet when sending emails. Users who do not have an active connection will see the following message when clicking the Marketo Send and Track button:       Why is this change being made?   The t racking parameter e xpiration  and tracking link change   are  additional step s   in providing a  more consistent and more secure experience with  Marketo’s  forms.   This change is a continuation of the work done last year when we released  Form Pre-Fill Feature Upgrade .   The  Outlook Plugin   update  was  made  to  standardize on using common  email  tracking-related  functionality  across  our  products.     What customer action is required?   Aside from the Outlook Plugin upgrade, no additional action is required.   The new plugin will be available as part of the Q3  2020  release so customers can upgrade. As part of the Q4  2020  release users will receive a message in Outlook asking them to upgrade before continuing to use the plugin.      How does this impact customers?   Tracking Links and Predictive Image s   If a tracked email link or  a  predictive image is clicked  by an anonymous lead  in an email that is over 6 months old,   the known lead will not be associated with user’s Munchkin cookie .  This is the same behavior  when  tracking  is  disabled.   Form Pre-Fill   If  a  tracked  email link or  a  predictive image  i s clicked  i n an email that is over 6 months old ,   and the  click   sen d s  user to a landing page  containing  a form with pre-fill enabled,  the form will not pre-fill.   This is the same behavior as  when  tracking  is  disabled .   Outlook Plugin   All users must  update  the Outlook Plugin   by  Q1 2021.  
View full article