Product Documents

A customer who has been using Marketo as a standalone system for the past year asked me recently for some tips for integrating with SFDC. Please note the following tips will also apply if the customer had a custom integration and was not using Marketo's connector for Microsoft Dynamics or SFDC. Check in the Marketo Admin area for the CRM icon Create a strategy for handing the duplicates which will be created in Marketo So if you've been using Marketo for a while you've probably imported a lot of lists Records synced from SFDC are NOT deduped against existing records in Marketo based on email address Any records including duplicates based on email address syncing from SFDC will sync to Marketo, records syncing from SFDC are considered intended behavior The easiest way to handle the issue is to delete all the records in Marketo before syncing with SFDC Unfortunately, you will lose all your activity history Another option is to work with Marketo services or a Launchpoint partner to merge the duplicates together If you have a lot of duplicates, it may take many weeks to merge all the records together Merging records will preserve the activity history but may cause smart campaigns to fire, always test and be prepared to adjust your campaigns accordingly Consider a hybrid approach by deleting the least valuable records Create a strategy for the fields you want to sync from SFDC Marketo will automatically map the most common SFDC fields with your existing fields Consider switching from your Marketo custom fields to your SFDC fields or merging the fields together. Here are some resources about fields Read about implementing a custom sync filter following the best practice Read about how the sync works. If you are using SFDC Lighting, be aware of the unsupported features. Understand how Marketo treats records deleted in SFDC Understand the different ways you can insert/sync a Marketo record to SFDC unintentionally Finally, here are some handy references in case you are wondering about using the SFDC Opportunity Object or a SFDC Custom Object. Feel free to add your own tips. Thanks!

Hi All, I recently inherited a marketo database and am new to administrating the platform in general. I come from a salesforce background and have been spoiled at having the ability to look up what each permission does and exactly what it controls. I've searched out there for something similar with marketo and haven't had a whole lot of luck finding a consolidated document that describes the roles well. I have tried compiling my own and there were a few things I didn't know, but if there is an expert out there, can you take a glance at this and let me know if I've misunderstood any of the permissions? Thank you! Kelly Access Admin Access Admin: Ability to click on ‘Admin’ in the upper right corner of Marketo. Also allows user to see Admin | My Account. Access Channels: Ability to see and manage Admin | Tags | New Channels or Tag Actions. Note this only applies to channel type tags. Access Communication Limit: Ability to see and manage Admin | Communication Limits. Access CRM: Ability to see and manage Admin | Database Management | Salesforce Objects Sync and Admin | Integration | Salesforce. Access Data.com: no current subscription, assuming this assists in downloading leads from data.com Access Email Admin: Ability to see and manage Admin | Email. Access Event Partners: Ability to see and manage Admin | Integration | LaunchPoint. Access Field Management: Ability to see and manage Admin | Database Management | Field Management. Access File Upload: not sure what this does Access Landing Pages: Ability to see and manage Admin | Integration | Landing Pages. Access Location: Ability to see and manage Admin | Location. Access Login Settings: Ability to see and manage Admin | Security | Login Settings. Access MK Denial: no current subscription - not sure what this is Access Munchkin: Ability to see and manage Admin | Integration | Munchkin Access Revenue Cycle Analytics: Ability to see and manage Admin | Revenue Cycle Analytics. Access Roles: Ability to see and manage Admin | Security | Users & Roles | Roles. Access Sales Insight: Ability to see and manage Admin | Integration | Sales Insight. Access Single Sign-on: Ability to see and manage Admin | Single Sign-On. Access Smart Campaign: Ability to see and manage Admin | Smart Campaign. Access SOAP API: Ability to see and manage Admin | Integration | Web Services. Access Tags: Ability to see and manage Admin | Tags | New or Tag Actions. Note this only applies to non-channel tags. Access Treasure Chest: Ability to see and manage Admin | Treasure Chest. Access Users: Ability to see and manage Admin | Security | Users & Roles | Users. Access Webhook: Ability to see and manage Admin | Integration | Webhooks. Access Workspaces and Partitions: Ability to see and manage Admin | Security | Workspaces & Partitions Marketo Custom Objects: only granted to the standard Admin role. Access Analytics Access Analytics: Ability to access the Analytics module. Includes the ability to see all reports, create new reports, and modify existing reports. Can create new folders and archive content. Access Revenue Explorer: Grants full access to the Revenue Explorer module. (Includes export from Revenue Explorer). Delete Report: Ability to delete existing reports in the Analytics module. Export Analytics Data: Ability to export reports to Excel in the Analytics module. Access Calendar Presentations - Requires a Marketing Calendar License Access Calendar Presentations: Ability to access the Calendar module and view the details of calendar events. Can view Calendar Presentations. Can create new Calendar Presentations Edit Calendar Presentations: getting odd behavior, would assume additional permissions required for this to work correctly Access Design Studio Access Design Studio: allows access to the design studio tab and to view the tree. This access alone does not allow the users to see the details of the asset. Access Email Access Email: allows the user to view the details of the email. Approve Email: allows the user to approve the email. Delete Email: allows the user to delete an email. Edit Email: allows the user to create an email and update an existing email. Access Email Template Access Email Template: allows the user to view the details of an email template and use it. Approve Email Template: allows the user to approve the email template. Delete Email Template: allows the user to delete an email template Edit Email Template: allows the user to create an email template and update an existing email template. Access Form Access Form: allows the user to view the details of a form. Delete Form: allows the user to delete a form. Edit Form: allows the user to create and update an existing form. Access Image Access Image: allows the user to view the details of an image or file. Delete Image: allows the user to delete an image or file. Upload Image: allows the user to upload an image, including overwriting existing ones. Access Landing Page Access Landing Page: allows the user to view the details of a landing page. Approve Landing Page: allows the user to approve a landing page. Delete Landing Page: allows the user to delete a landing page. Edit Landing Page: allows the user to create and edit a landing page. Access Landing Page Template Access Landing Page Template: allows the user to view the details and use a landing page template. Approve Landing Page Template: allows the user to approve a landing page template. Delete Landing Page Template: allows the user to delete a landing page template. Edit Landing Page Template: allows the user to edit a landing page template. Access Snippet: snippets are reusable blocks of rich text and graphics that can be used in emails and landing pages. Access Snippet: allows the user to view the details of a snippet and use it. Approve Snippet: allows the user to approve a snippet. Delete Snippet: allows the user to delete a snippet. Edit Snippet: allows the user to create and edit a snippet. Access Social App: these are typically accessed under Marketing activities and not design studio. Access Social App: allows the user to view the details of social buttons and use them. Approve Social App: allows the user to approve social apps/buttons. Delete Social App: allows the user to delete social apps/buttons. Edit Social App: allows the user to edit social apps/buttons. Access Lead Database Access Lead Database: grants access to the Lead Database module Access Segmentation Access Segmentation: grants the user access to view the details of a segment and use them. Approve Segmentation: allows the user to approve a segment. Delete Segmentation: allows the user to delete a segment. Edit Segmentation: allows the user to create or edit a segment. Advanced List Import: Delete Lead: allows the user to be able to delete a lead record from the Lead Actions list. Delete List: allows the user to be able to delete a list (static or smart). Edit Lead: allows the user to be able to edit a lead record by double clicking on a lead. Also allows the user to be able to add to other programs. Export Lead: allows the user to be able to export a list of leads from marketo. Import Custom Object: if there are custom objects in marketo, this allows the user to be able to import the data for custom objects. Import List: allows the user to import data into marketo via right click on group list | Import List. Merge Leads: allows the user to be able to merge lead records from the Lead Actions list. Run Single Flow Actions: extends the edit lead functionality by allowing access to single flow actions that can sync with salesforce. View Opportunity Data: allows the user to see the opportunity tab when viewing a lead record. Access Marketing Activities Access Marketing Activities: grants access to the Marketing Activities module. Requires additional access from the design studio to view the design assets. Requires additional access from the lead database to view smart lists and results. Access Push Notification: requires a webhook to a 3 rd party that uses SMS distribution. Once that’s been established then push notifications can be accessed. Approve Push Notification: allows a user to approve a push notification. Delete Push Notification: allows the user to delete a push notification. Edit Push Notification: allows the user to create and edit a push notification. Access Awards: not sure what this is, possibly requires a subscription Activate Trigger Campaign: allows the user to activate a triggered campaign. Approve Email Program: allows the user to approve an email program. Clone Marketing Asset: allows the user to clone a marketing asset. Delete Marketing Asset: allows the user to delete an individual marketing asset. Edit Marketing Asset: allows the user to create and edit a marketing asset (think programs). Import Program: allows the user to mass clone all assets under a program to create a new one. List Import: allows the user to create a new list and import members into it. Schedule Batch Campaign: allows the user to schedule and run a batch campaign. Access SEO: need to review this more, not sure of all of the differences between the two dashboards. Access SEO: grants access to the SEO module. Requires one of the following two permissions in addition. Administer SEO: grants admin access to the SEO Dashboard. Standard SEO: grants read-only access the SEO Dashboard. Workspace Administration – requires a subscription to workspaces & partitions Workspace Administration – cannot confirm, could be that it grants the user access to all workspaces Move Assets Between Workspaces – if a subscription is active, allows the user to move assets from one workspace to another. Access Mobile Application Access Mobile Application – grants the user to two mobile apps: Event Check-in and Marketo Moments Hi Kelly, First off, thanks for taking the initiative to share this! I feel like Marketo's own documentation is a little weak in this respect, since it only lists permissions without explaining what those permissions actually control. To answer a few of your questions: 1e/1m. For whatever reason, Marketo has the permissions for data.com and MKDenial​ defined even on instances that do not subscribe to either service. 1i. I believe this specifically refers to the ability to upload files other than images in Design Studio, but would love clarification from Marketo. 7a. This specifically refers to the ability to create and administer workspaces themselves; granting a user access to workspaces is actually done when assigning individual users roles (since you may want someone to be an admin of one workspace, but have less permissions on another, for instance.) Also, throwing this one out there: what is "Access/Administer Vespa"? I completely realized I posted this under my test user's account and not my own. *sigh* Is there anyway to change the ownership of the thread? If not, no worries. Wow, this is a great summary!  While I haven't verified every role to be correct, I would highly encourage the Marketo documentation/education team to add this to product docs. Hi Frank Passantino​, Might be interesting to you -Greg Hi: Thanks for publishing this!  As a word of warning: I was recently told by Support that certain rights are not entirely dependent on that check box in the role.  For instance, if you have a user you would like to manage communication limits and the global footer, they need to be the default Admin, despite checking that box when creating a custom role.  I would really like to see an easier way to manage access in the application.  I have users I want to empower for every Marketing-related functionality, but, because we are fully integrated with several other databases within our company, I need to keep tight restraints on mass edits to the database, field creation/additions, etc.  This is the first application I worked with that makes administration this murky. I haven't run full tests on each of the admin functions you outlined, but I know communication limits and the footer are dependent on the user having full admin rights.  Channel Tags are not; you can give a user access to these without granting full admin privileges.  Noted. Thank you for mentioning that. Hi Kelly, Thank you for documenting all of this!  Quick question.. Clone Marketing Asset: allows the user to clone a marketing asset. Does this permission encompass cloning entire programs?  I'm researching the possibility of allowing an international user who works in one work space the ability to clone programs from the US work space. Yes, Anna, when cloning a Program, it will clone all assets/items underneath. The ability to Clone items under Marketing Activities encompasses this as well. Sharing a document page I came across today, as I'm researching what permissions/access each role has. Looks like you got the list covered! Descriptions of Role Permissions - Marketo Docs - Product Docs Access Admin - view and make changes to settings in the Admin section. Access Audit Trail Access Channels - access only to modify the Channel tag, not other custom tags Access Communication Limit Access CRM Access Data.com Access Email Admin Access Event Partners Access Field Management Access File Upload Access Landing Pages Access Location Access Login Settings Access Marketo Custom Activity Access Marketo Custom Object Access MK Denial Access Munchkin Access Revenue Cycle Analytics Access Roles - access to manage and edit roles, but not users Access Sales Insight Access Single Sign-on Access Smart Campaign Access SOAP API Access Tags - access to all custom tags except the Channel tag Access Treasure Chest Access Users - access to edit and manage users, but not roles Access Webhooks Access Workspaces and Partitions Access API Approve Assets Execute Campaign Read-Only Activity Read-Only Activity Metadata Read-Only Assets Read-Only Campaign Read-Only Company Read-Only Custom Object Read-Only Lead Read-Only Opportunity Read-Only Sales Person Read-Write Activity Read-Write Activity Metadata Read-Write Assets Read-Write Campaign Read-Write Company Read-Write Custom Object Read-Write Lead Read-Write Opportunity Read-Write Sales Person Access Analytics - see the Analytics tabs, view and edit reports Access Revenue Explorer Delete Report Export Analytics Data Access Calendar Presentations Edit Calendar Presentations Access Design Studio - see the Design Studio tab Access Email - view Emails Edit Email - edit, create, and clone emails Make Email Operational Approve Email Delete Email Set Branded Domain Access Email Template - view Email Templates Approve Email Template Delete Email Template Edit Email Template - edit, create, and clone email templates Access Form - view Forms Delete Form Edit Form - edit, create, and clone forms Access Image - view Images Delete Image Upload Image Access Landing Page - view Landing Pages Approve Landing Page Delete Landing Page Edit Landing Page - edit, create, and clone landing pages Access Landing Page Template - view Landing Page Templates Approve Landing Page Template Delete Landing Page Template Edit Landing Page Template - edit, create, and clone landing page templates Access Snippet - view Snippets Approve Snippet Delete Snippet Edit Snippet Access Social App - view Social App Approve Social App Delete Social App Edit Social App Access Lead Database - view the Lead Database, view and edit Smart Lists and static lists Access Segmentation Approve Segmentation Delete Segmentation Edit Segmentation Advanced List Import Delete Lead Delete List Edit Lead - prevents manual editing and running single flow actions. You can still edit leads by running campaigns against them Export Lead - export spreadsheets with from your Lead Database lists Import Custom Object Import List Merge Leads Run Single Flow Actions - Enable users to run 'Change Data Value' action on Leads from the Lead Database View Opportunity Data - hides the opportunity info on the lead detail page Access Marketing Activities - view the Marketing Activities tab, campaigns, and campaign folders Access SMS Message Approve SMS Message Delete SMS Message Edit SMS Message Access Push Notification Approve Push Notification Delete Push Notification Edit Push Notification Access Awards Activate Trigger Campaign Approve Email Program Clone Marketing Asset Delete Marketing Asset Edit Campaign Restrictions Edit Marketing Asset Import Program List Import Schedule Batch Campaign Access SEO Administer SEO Standard SEO Targeting and Personalization Administer Web Personalization CRE Campaign Editor CRE Campaign Launcher Web Campaign Editor Web Campaign Launcher Workspace Administration - Admin access for a specific Workspace (only if you have Workspaces enabled) Move Assets between Workspaces - (only if you have Workspaces enabled) Access Mobile Application This document was generated from the following discussion: 

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

In our first post, we discussed the concept of URLs and UTM tracking. Now that those are in place, we will dive into the setup with Marketo. Here are the high-level steps: Create the UTM fields in order to have a place to store the values Add the fields on your form pages as hidden fields, add to a landing page Setup the Marketo programs and/or smart campaigns to process them Test and check to make sure it's working Step 1 - Create UTM fields If you are setting this up for the first time, or you have inherited a Marketo instance, I recommend checking to make sure these fields are not already in place, or they exist, but are named something else. If you have access, go to Admin > Field Management, and search for any fields containing "utm" or "ppc" to see if they are there. In the screenshot below, you'll see that all 5 fields have been created and are currently mapped to the SFDC lead and contact records. *Side note: The mapping is important if you want the values for leads or contacts since SFDC treats them differently. Also, if you are creating them for the first time, make sure to do it in SFDC and wait for the fields to sync to Marketo or you'll have to get it re-mapped. ​ Step 2 - Add fields to your forms Now that you have the fields created, add them to any relevant data forms. There are two main options for this. If your website uses custom non-Marketo forms, ask your web developer to add the extra fields to the forms and make them hidden. In the field management screen, there's an "Export Field Names" button which will export all the necessary fields that you can provide to your developer. The file provides a mapping for the UTM values that need to be written to from the website form field to the Marketo field. There might be other options such as native plugins that might already accomplish this. If you are adding them to a Marketo landing page, drag those new fields onto your forms and make them hidden. In the Autofill property, choose Edit and you'll see options to chose where the field values will populate from. Choose URL Parameter and type in "none" for the default value or anything that you can filter on later to troubleshoot if it's not working. At this point, the landing page is just waiting for a referring visit with UTM values. Consider what happens when someone clicks a link, but does not sign up right away? The values from the URL parameter must be present at the time of submission in order for this to work. So if someone navigates away and the parameters disappear, then the UTM values will not be captured. To solve for this, we have created a tracking script that will store any UTM parameters it finds into a cookie. Now when a visitor fills out a form that contains the hidden UTM values on a form, the cookie will store the UTM value across the main and subdomains. *Technical Stuff: You can upload the extracted file into the images directory or on your web server. Before doing so, take note to make one change to the file and re-save it for it to work. Open the file with any text editor and looking for a line that says "domain=digitalpi.com" and change it to your domain. Once set, it won't expire for another 365 days. The script should be place where your Munchkin script is also placed. It's a simple script that does the following. If UTM parameters are present, store those into a cookie. This means if it comes from a URL and it's the first time seeing it, the script creates the cookie. If the visitor comes back by clicking another link with different UTM parameters, it will replace with the new ones and continue to do so. It's not session specific which means if the visitor closes the browser and comes back at a later date, it will still be in the cookie and keep it for 365 days. Here's a link to the tracking script: dpi-ppc-tracking-script.js.zip So that you can see this process in action, I created a simple form with visible UTM fields on a landing page. When you click on one of the sample links, you should see the UTM values in the UTM fields where they would normally be hidden. If you want to experiment with it, change any of the UTM values after the equal sign and refresh the page. You'll see the new value populated in the field that was changed. Long version: http://info.digitalpi.com/Marketo-UTM-Sample-Page.html?utm_source=blog&utm_medium=email&utm_term=utm&utm_content=utm-tracking-blog-p2&utm_campaign=blog-sub Shortened version: http://goo.gl/O6VyL9 Step 3 - Setup Marketo processing This next part is just ordinary Marketo smart campaign building. Setup the trigger filtering on UTM values. Make sure it's unique enough to process for the individual UTM parameter (campaign, source, medium, etc.). Step 4 - Test and validate Create a few URLs to your landing page and use different combinations of UTM parameters and click on your form submission. Look for the test record and in the custom fields look for the values. If they are there, it's working properly. Keep in mind these values will change each time a new set of UTM values are set. You can run reports on the different campaigns or even down to the add level if programs are setup to track that. This feature is used frequently, so we hope this article saves a lot of time and frustration. Happy Marketing!!

Our sales team is very new to Sales Insight, so I did a training with them last week to show them some of the features and how they can use it to interact with their prospects better. I figured this is probably something a lot of us have to do at some point, so I am attaching my powerpoint that anyone can adapt to use for their own sales teams. Warning: it has many gifs and memes. Our sales team is very young, so I knew this would keep their attention also, my gif game is strong. Some of this is specific to our instance - for example, I created a marketing suspend campaign to allow them to suspend a prospect from marketing for 30 days if they are actively working a deal or about to do a demo - but it can probably be adapted for anyone.

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 Please check out my guide on Understanding Attribution in Understanding Attribution in Marketo This doc is for the exercise file

As part of my role in Marketing Operations is to manage data quality. Data comes form many sources and not always in the optimal state I require it to be for lead routing. Not all Marketers are data savvy and will need some coaching when they hand over a CSV file from an event they have just ran. As we collect data from a variety of regions, not all of it is going to be perfect. Some folks expect Marketo platform to cleanse the data on upload. Some maybe missing mandatory data points in order for them to be routed to the appropriate sales rep for follow up. Bad practices of data collection can leave your data base with gapping holes and will require extra scrutiny at some point. One of the first things I do each Monday morning is check on how many leads we are collecting from our marketing activities with missing data by running a Marketo report. We took advantage of Marketo lead report in Revenue Cycle Analytics with the ability to add custom smart lists to the report. This report can then be subscribed to on a weekly or monthly cadence. Below are the steps to take to build a database health report: First off, we need to build smart lists for every field we need visibility into. Create a new folder in your Smart List section of Marketo Data base, name it ‘Data Base Health Report Smart Lists’ and create a new Smart List and start off with First Name. Make sure to name your Smart Lists the way you want them to be named in your custom columns as they will appear exactly the same. Drag and drop in First Name field into your smart list, select ‘Is empty’. This smart List will group all leads in your DB with a missing First Name. Do the same for Last Name, Company Name, Country, Lead Source, Industry, Phone etc. All the ones you need to monitor. Now go to Analytics section and create a new lead report. Go to set up and add in your custom column smart lists, the first two columns will be your 'Grouping' and 'Total leads', so be sure to add them in the order you want them to appear in the rendered report. Note: can only add up to 10 smart lists as custom columns to the lead report. Now group your report by lead create date and select to view monthly. Go to subscription section and add yourself and pick whatever cadence you want your report to be sent out. In the smart list section of your lead report, add any filters you need to segment your report by, E.g. try to look only for leads created by a certain date or from a large static list etc. Below I'm making sure I don't pull leads with empty email address and a lead type of Corporate. This area helps you to focus your lens to a smaller set of data or leave blank and pull in your whole data base to the report. Now hit report to render, once rendered, you may need to adjust the columns. Your report will now show you your total leads by your chosen create date and grouped by created month. Along side will have columns to show total leads and how many of that total are missing First Name, Last Name, Company Name, Country, Lead Source, Industry, Phone etc. Advanced actions: Using this method of reporting can show many more ways to chop your data up. Try using smart list columns for certain Marketo forms your monitoring for engagement. Filter on lead sources with lead source detail.

March 2023 update: The deprecation of the legacy URL patterns will occur on August 1, 2023.   June 2022 update: We have decided to extend the deadline until the end of 2022 with support of old URL patterns ending in January 2023. More information to be provided once a precise date has been chosen.   In 2021, Marketo Engage made changes to the URL structure for Landing Pages, Forms, and Images & Files assets. On August 1, 2023 we will be deprecating usage of old URL structures and these references will no longer load on the web.   Why is this change being made? Technical Details Landing Pages Images & Files Forms What customer action is required?   Why is this change being made? When a Marketo Engage subscription is not configured with a branded CNAME, Design Studio assets use a common hostname shared among all customers on the same pod. This behavior can be exploited in a phishing attack where a user cannot be sure a link to a Marketo Engage hosted asset belongs to the business they expect it to belong to. By updating each instance to use its own unique hostname, it is clearer to users the destination of URLs they are accessing.   Now that all Marketo Engage subscriptions have been migrated to our new URL structure for some time, we will be ending support to the legacy, more vulnerable URL structure.   Technical Details Landing Pages, Form embed code, and resources stored in Images & Files had URLs updated from a hostname shared among all subscriptions on the pod to a hostname unique to each Marketo Engage subscription. Subscriptions configured to use a custom CNAME for their landing pages were minimally affected by this change. Landing Pages Subscriptions without a configured landing page domain Landing page paths will changed to a unique hostname for your subscription. Legacy: http://na-sj01.marketo.com/lp/123-ABC-456/unsubscribePage.html Current: http://123-ABC-456.mktoweb.com/lp/123-ABC-456/unsubscribePage.html   Subscriptions with a configured landing page domain Landing pages will continue to load from your configured landing page domain. No changes will be made. Before: http://example.marketo.com/unsubscribePage.html After: http://example.marketo.com/unsubscribePage.html   Images & Files Subscriptions without a configured landing page domain Paths to resources stored in Images & Files changed to a unique hostname for your subscription.   Legacy: http://na-sj01.marketo.com/rs/123-ABC-456/images/cuteKitten.png Current: http://123-ABC-456.mktoweb.com/rs/123-ABC-456/images/cuteKitten.png   Subscriptions with a configured landing page domain Resources stored in Images & Files will continue to load from your configured landing page domain. No changes will be made.   Before: http://example.marketo.com/rs/123-ABC-456/images/cuteKitten.png After: http://example.marketo.com/rs/123-ABC-456/images/cuteKitten.png   Forms Subscriptions without a configured landing page domain OR subscriptions without landing pages secured by SSL Legacy:     <script src="//app-sj01.marketo.com/js/forms2/js/forms2.min.js"></script> <form id="mktoForm_1"></form> <script>MktoForms2.loadForm("//app-sj01.marketo.com", "123-ABC-456", 1);</script>     Current:     <script src="//123-ABC-456.mktoweb.com/js/forms2/js/forms2.min.js"></script> <form id="mktoForm_1"></form> <script>MktoForms2.loadForm("//123-ABC-456.mktoweb.com", "123-ABC-456", 1);</script>       Subscriptions with a configured landing page domain secured by SSL In our October 2020 release, we updated our form embed code to load from the landing page domain when it is secured by SSL. No further changes will be made. Before:   <script src="//example.marketo.com/js/forms2/js/forms2.min.js"></script> <form id="mktoForm_1"></form> <script>MktoForms2.loadForm("//example.marketo.com", "123-ABC-456", 1);</script>     After:      <script src="//example.marketo.com/js/forms2/js/forms2.min.js"></script> <form id="mktoForm_1"></form> <script>MktoForms2.loadForm("//example.marketo.com", "123-ABC-456", 1);</script>       What customer action is required? You will need to audit the source code of your web pages to see if these URL patterns are in use by your business. If you have web pages or form usage that pre-date 2021 it is possible they are using the legacy URL pattern.  Most customers configure a CNAME and secure it via SSL early in the life of their instance, minimizing the impact on Images & Files URLs. Prior to our October 2021 release, all form embed codes used the legacy URL structure. If you have usage of Marketo forms from prior to 2021 it is very likely they will need to be updated to use the new URL pattern, which can be found by copying the form embed code from the Form asset page.   For Marketo Landing Pages and Emails, if you used the Image picker or Form picker that are included in the Landing Page editor or Email editor then no change is necessary. If you hard coded references to images or forms using the legacy URL pattern instead of using the pickers then these references will need to be updated to the new URL pattern.   Customer Support does not have the ability to perform this audit for you.   To begin preparing for this change, we suggest doing the following: Configure your Landing Page URLs with a CNAME https://docs.marketo.com/display/public/DOCS/Customize+Your+Landing+Page+URLs+with+a+CNAME Secure your Landing Pages with SSL https://docs.marketo.com/display/public/DOCS/Add+SSL+to+Your+Landing+Pages Begin updating pages where you embed Marketo Engage forms with the new embed code introduced in our October 2020 release (requires secured landing pages) Begin an audit of where you reference Design Studio assets on the web. This will help you begin a plan to update any existing references to our older URL structure before we begin deprecation in August 2023. Generally this will be on non-Marketo pages, as our Landing Page editor will automatically format embedded images and forms in a compatible manner. Only references hardcoded to the old URL structure need to be updated, e.g.  http://na-sj01.marketo.com/rs/123-ABC-456/images/cuteKitten.png. Relative references will continue to work without need changes e.g.  /rs/123-ABC-456/images/cuteKitten.png. Please work with your web developer to determine where you may need to make updates.

[FAQ attached below this article]   What's Changing? On August 31, 2020, Marketo Engage will implement a new retention policy specifically for Sent & Delivered Email activities. Under this policy, data for these two activity types will be stored for a rolling 90-day period from the activity date for use in Smart Lists. This is a change from the current default retention period of 25 months, and from the current Extended Data Retention subscription option period of 37 months.   Upon the policy taking effect, data older than 90 days for these two activities will be deleted and no longer available for export. Any Smart List with the “Was Sent Email” and “Was Delivered Email” filters (including NOT Was Sent and NOT Was Delivered) should be updated to ensure the maximum lookback date is 90 days.  If the lookback date is greater than 90 days, the Smart List will continue to function, but only activities that are 90 days old or less will qualify.   Why? In 2020, we are improving critical parts of the underlying Marketo Engage infrastructure, including Batch campaign processing, similar to the Trigger campaign improvements made in 2019. This new infrastructure, in combination with the new retention policy, is expected to result in shorter lead time with large email sends and faster segmentation processing to deliver significantly faster processing to our customers. Note, the revised retention policy is one, among several, aspects that come together to deliver this improved performance, but broadly speaking reduced retention helps with faster database look ups and search across the run-time infrastructure.     What's NOT Changing? Aggregated data – including Reports, Dashboards, and Analytics – will not be affected by this change (unless they reference a Smart List with these activities).  The new policy will not affect any activity type other than Sent and Delivered (for example, Was Opened activity data is not affected). Further, this change does NOT affect Engagement Program casts.   What Customer Actions Are Needed? First, you'll want revisit where and how you're using these two activity types. Audit your Smart Lists and ensure the date ranges for these two activity types are less than 90 days - if you must use a date greater than 90 days, we suggest running a process to export to an external system. You will need to create this before the new retention policy takes effect on August 31, 2020.  Information on how to export activities using APIs can be found on our Developers Documentation website.   We appreciate you understanding as we move toward an enhanced Marketo Engage experience for all customers. Please download and review the FAQ attached below for further suggestions, workarounds and additional information.  

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.    

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

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

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

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

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

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

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