Knowledgebase

Issue When changing Program Status in Admin > Tags > Channel for "Event" result in this error, "Failed: no more information".  Environment Changing Program Status  Failed: no more information Solution "System mapping for Registered, Waitlisted, and Attended statuses is required." Therefore, ensure the status is mapped to Registered, Waitlisted, and Attended.   Root Cause One or more of these statuses "Registered, Waitlisted, and/or Attended" were not mapped as required. 

Issue The format of the landing page is distorted in comparison to the version displayed in the landing page preview.  Environment SSL Certificates Landing Page Domain Landing Page format is different from preview Landing Page contain unsecure content Landing page template has http instead of https   Solution Ensure all the links used in HTML code used in the landing page template is referencing "HTTPS" and not "HTTP". You can follow the steps outlined in the document below on how to edit landing page template.  Link: https://experienceleague.adobe.com/docs/marketo/using/product-docs/demand-generation/landing-pages/landing-page-templates/edit-a-marketo-landing-page-template.html **NOTE: If the landing pages is approved, a draft version of the landing page is created for any landing pages which is using the landing page template. You can mass approve those landing pages via following steps outlined in the document below. Link: https://experienceleague.adobe.com/docs/marketo/using/product-docs/demand-generation/landing-pages/landing-page-actions/approve-multiple-landing-pages-at-once.html?lang=en Root Cause Once you secure your Marketo landing pages to be served over "HTTPS", you should have not links referencing "HTTP" (unsecured) assets or pages. 

Issue When adding new IP Address to the IP Restrictions list on Admin > Login Settings > IP Restrictions, you receive this error message: "Your current IP address (XXX.XXX.XXX.XXX) cannot be blocked."   Environment Admin IP Restrictions Login Solution Ensure that you have Admin Access to the Marketo instance and that you have logged into the Marketo instance via one of the IP Addresses listed on the IP Restrictions list.  Root Cause User logging into the instance with an IP Address not on the IP Restrictions list. 

Issue What type of HTTP Redirect Rules does Marketo use when you setup a redirect rule in Admin > Landing Pages?     Solution Internal Pages such as landing pages hosted on Marketo will use a HTTP 301 Redirect External pages & non landing page URL's (when using "non-Marketo landing page") used in the redirect rule will utilize a HTTP 302 Redirect: Branding links do not use an HTTP Redirect and use a script-based redirect on the Branded links page. Example: Email branding link - http://go.mybranddomain.com/ABCDEFIlB0ETg0X063WLL1 is a Marketo hosted page that utilizes a script to redirect & point to http://www.thetargeturlinanemail.com

Included in this article   Overview Sync Filters for Existing SFDC Integrations Sync Filters for New SFDC Integrations Overview It is often necessary to prevent specific leads from syncing between Marketo and SFDC. There are a few different ways this can be done, such as sharing rules on the SFDC side, but the most effective way is through a Marketo Custom Sync Filter.   A Custom Sync Filter uses a custom field to mark each lead record to indicate whether that lead is allowed to sync between Marketo and SFDC. Here’s how to get it set up!     Sync Filters for Existing SFDC Integrations   If you already have an SFDC integration in place but want to stop some already-synced leads from continuing to sync, this section will show you how to make that change.   1. Create a new custom field in Salesforce. The Marketo bi-directional sync will automatically identify the new custom field and map it between Marketo and Salesforce. The best field type to use is a Checkbox field within Salesforce and the field will need to be created on the Salesforce Object that needs to be filtered (i.e. Lead, Contact, or both). Once the field has been created in Marketo by the bi-directional sync, it will be listed under Admin > Field Management.   Note: A Custom Sync Filter field can also be created on the Account object to dictate whether an account is allowed to sync. This sync filter will be applied independently from the Lead/Contact sync filter.   2. Update the records in Salesforce with the corresponding value you need to indicate whether the record should sync or not. Sync filters can be set up in two ways—a True/Checked value can indicate that a record is allowed to sync, or a True/Checked value could indicate that a record is not allowed to sync. This choice is up to you.   3. The Custom Sync Filter can now be implemented. Contact Marketo Support and request a Custom Sync Filter be activated. Be sure you include the custom field name, which configuration you need (checked=sync vs checked=don’t sync), and all records have been populated with the correct values. Once it has been applied, you’re all done!     Sync Filters for New SFDC Integrations   If you are setting up a new SFDC integration with Marketo, you can set up the sync filter as part of the integration process. This will let you designate which leads and contacts are ever allowed to sync, but this must be done in the middle of the initial SFDC sync process.   1. Create a new custom field in SFDC. The best field type to use is a Checkbox field, and you’ll need to set it up with the same name on both the Lead and Contact objects. Note: A Custom Sync Filter field can also be created on the Account before the initial sync, and it will be applied in the same way.   2. Update the records in Salesforce with the corresponding value you need to indicate whether the record should sync or not. Sync filters can be set up in two ways—a True/Checked value can indicate that a record is allowed to sync, or a True/Checked value could indicate that a record is not allowed to sync. This choice is up to you.   3. Begin your Salesforce Sync Setup but do not finish it. There are two sets of Salesforce Sync installations, one for Enterprise/Unlimited Edition and the other for Professional Edition. For both Enterprise/Unlimited and Professional Edition versions, three documents correspond to the three different steps: “Step 1 of 3”, “Step 2 of 3,” and “Step 3 of 3”. For both versions, complete all steps of “Step 1 of 3” and “Step 2 of 3”. When you get to “Step 3 of 3”, you will only do the first half of the steps and then stop. Complete the sections “Retrieve Sync User Security Token” and “Set Sync User Credentials,” and then stop there. Do not proceed to start the sync.   4. This is when the sync filter needs to be implemented. Contact Marketo Support and request a Custom Sync Filter be activated. Be sure to include the custom field name, which configuration you need (checked=sync vs checked=don’t sync), and note that all records have been populated with the correct values. Once it has been applied and the Marketo Support case is resolved, you’re done and can start your initial SDFC sync!

Issue Your Salesforce sync cycle is taking longer than usual.  How long is too long?     Solution By default, Marketo starts each Salesforce sync cycle five minutes after the previous cycle completes.  Each sync cycle may take a couple of minutes or a couple of hours, depending on how much data needs to be written across.  If you notice your sync cycles seem to be taking longer than usual, here are some things to check. Have you done a large update recently?  This can create a backlog that can take time to work through. Have you added new fields to any of your synced Salesforce objects?  The more fields on the object, the more data needs to be written across, extending the sync cycle. If you would like to streamline your Salesforce sync, do an audit in Salesforce of fields visible to the Marketo Sync User.  If there are any fields that are not used in Marketo, remove visibility to them so Marketo does not waste time syncing them.  

Marketo calls to the Salesforce API During a single sync session, Marketo makes 25 API calls to check if your Salesforce objects need updating.  Because your Salesforce sync happens in 5 minute intervals (default setting), each day Marketo makes 7200 API calls to your account to see if any updates are needed. If there are updates, more API calls are used to sync the information.  Leads, Contacts, Accounts, Opportunities, Campaigns, and Activities are synced in batches of 200 per API call. If you use a Sync Lead to SFDC or Add to Campaign flow step in trigger campaigns, each one uses at least one API call per lead; the API call happens when the lead hits that flow step (instead of waiting for the next sync). Batch campaigns can send up to 200 leads to Salesforce with 1 API call for these flow steps. Any activities you've synced from Marketo to Salesforce (like "Filled Out Form" or "Opened Email") use an extra API call per event. You can use these to estimate the number of API calls Marketo makes per day.  For example, if you have 1,000 Lead and Contact updates a day and 100 Account, Opportunity, and Campaign updates, you'll use: 7200 (check for updates) + (1000 Lead updates / 200 per API call) + (1000 Contact updates / 200 per API call) + (100 Account updates / 200 per API call) + (100 Opportunity updates / 200 per API call) + (100 Campaign updates / 200 per API call) + 7200 + 5 + 5 + 1 + 1 + 1 = 7213 API calls When you first sync your Salesforce account to Marketo, you'll use significantly more API calls until Marketo is up to date with your Salesforce instance.  After that, you can expect the API calls to be much lower unless you make large updates to your leads (in Marketo or Salesforce) API Calls and your Salesforce edition Salesforce determines your API call limit based on the edition and licenses you have. This document from Salesforce has information on how they calculate that limit. For many Salesforce users, particularly Enterprise Edition users, the number of API calls made by Marketo is usually not a problem. If you're using a more limited edition of Salesforce or don't have many Salesforce licenses, you may hit the daily limit on your API calls.  In that case, please contact Marketo Support and ask us to decrease your sync interval.  At a 30 minute sync interval, Marketo uses around 1000 API calls per day, well under the limit for nearly every Salesforce edition. To see your API limit (per 24 hour period) and your current usage (for past 24 hours) in SFDC,  navigate to: Setup -> Administration Setup -> Company Profile -> Company Information Look for the field called "API Requests, Last 24 Hours", which will display API usage for the past 24-hour period as well as your current 24-hour limit (in parenthesis). Order of Events during SFDC Sync Marketo will sync your SFDC and Marketo objects in the following order: Lead: synch schema Account: synch schema Contact: synch schema User: synch schema Task: synch schema Opportunity: synch schema Opportunity Contact Role: synch schema Campaign: synch schema Campaign Member: synch schema Campaign Member Status: synch schema Lead: pull conversions Account: pull deletes Account: pull updates User: pull updates Lead Queue: pull updates Lead Status: pull updates Account Type: pull updates Lead: pull deletes Contact: pull deletes Lead: pull updates Contact: pull updates Lead: push updates Contact: push updates Campaign: pull deletes Campaign Member: pull deletes Campaign Member Status: pull deletes Campaign: pull updates Campaign Member: pull updates Campaign Member Status: pull updates Opportunity: pull deletes Opportunity Contact Role: pull deletes Opportunity: pull updates Opportunity Contact Role: pull updates Event: pull updates Task: pull updates Email Template: push new Email Template: push updates Task: push new Task: push updates

Issue Lead conversion/qualification through workflows in Microsoft Dynamics CRM resulting to duplicates (i.e. Lead and Contact) in Marketo Environment Microsoft Dynamics CRM Lead conversion Sync Solution While lead qualification through workflows is currently not supported, one approach that we saw implemented by a customer that did not result in duplicates is by redeveloping the lead qualification workflow using the msdyncrmWorkflowTools (1.0.54.0): QualifyLead step. Dynamics-365-Workflow-Tools/Qualify Lead.md at master · demianrasko/Dynamics-365-Workflow-Tools This was verified to result in no duplicates as the workflow writes the "Create [Qualify Lead]' operation type to the Marketo Log which is like the standard qualify button. Should there be any further assistance needed in developing the lead conversion workflow, it's recommended to engage with our Professional Services / Consulting team Root Cause Marketo's integration with Microsoft Dynamics CRM currently does not support custom qualify workflows.

Image: Step Flow for Predictive Content for Web and Email What is Auto Content Discovery? This post explains the first part of the flow image above: discovering, mapping, and tracking your content assets. Content Discovery is used in the Predictive Content app to auto-discover all the content assets (videos, pdfs, blog posts, press releases, white papers, etc.) on a website/domain. Once discovered, you can see how your content is performing and decide which pieces of content should be prepared, approved, and enabled for the Predictive Content outcomes on web (either in the recommendation bar or rich media) and email.   Setting up Predictive Content and Content Discovery See Set Up Docs: http://docs.marketo.com/display/public/DOCS/Getting+Started+with+Predictive+Content Steps RTP Javascript tag is installed on all your web pages (Note: RTP is now called Web Personalization) Set Asset Discovery to On Asset Discovery auto-discovers extensions (PDFs, PPT, MP4, OFF, WEBM) and a click/view on embedded videos (Youtube, Vimeo, Wistia) Create URL Patterns Setting URL patterns auto-discovers content when a web visitor clicks on the HTML web page relevant to the content pattern. The URL syntax pattern determines your ability to use this feature optimally (e.g., to create a pattern for press releases, your press releases should all be stored on a page identified as www.yoursite.com/press-releases/*). How is content auto-discovered? The content discovery technology uses an event listener that runs on every web page (where the RTP Javascript tag is installed) and waits for a web visitor to click on a URL link or arrive directly on that web page in a browser. If that link includes an extension (PDF, ppt, embedded video) or matches the URL pattern defined, then it will be discovered and added to the All Content page in the Predictive Content app.   Only content pieces that a web visitor interacted with (clicked on or viewed) once the RTP Javascript tag has been installed are discovered via Content Discovery. If the content is already discovered, it will add to the tracking and views of those discovered pieces. You can also manually add new content to be listed and tracked in the All Content page.   Image: All Content Page in the Predictive Content app displaying and tracking all discovered content What data is discovered? Visitor Data (Used for Analytics + Predictive Algorithm) Pages Viewed  - number of page views by the user in the session Visit Count for Web Visitor Last Content URL Seen Last 5 Content Assets clicked via Predictive Content that this visitor has seen in the last 90 days Last Web Campaigns Seen - 10 last campaigns per session (within the last 5 sessions) Inferred Organization Inferred, Industry, Size, Revenue Inferred Country, State, City Search Term   Content Data  Extensions Video (Youtube, Vimeo, Wistia) Video Name Video URL Video Image URL PDF PDF Name PDF URL   URL Patterns (HTML pages) Found via metadata of the HTML page Content Name Content URL Content Image URL Content Description What data is auto-populated during the auto-discovery phase? Based on the content data we discover, the aim is to populate as much of the Predictive Content as possible, making it quicker, easier and involves less prep work for you. However, you still need to review the discovered content and then approve and enable it for the Predictive Source (Email, Rich Media, Recommendation Bar). Assuming we discover an HTML page defined in URL patterns, this HTML content piece will be populated in the following fields in Predictive Content:   Predictive Content Fields Auto-Populated Value Notes Content Name (Content Name) Unique Value Content URL (Content URL) The URL is consistent for all sources (email, bar, rich media) Categories Video OR Category Name from URL Pattern If Video is discovered, the category is populated as Video. Category populated from defined URL Pattern. e.g., Marketo.com/blog = Blog all discovered content based on this URL would receive Blog as a category Category is consistent for all sources (email, bar, rich media) Content Title (Content Name)   Email Title (Content Name)   Email URL (Content URL)   Email Image URL (Content Image URL)   Email Button Label Read More Not Auto-populated. Default is "Read More." Rich Media Title (Content Name)   Rich Media URL (Content URL)   Rich Media Image URL (Content Image URL)   Rich Media Description (Content Description)   Bar Title (Content Name)   Bar URL (Content URL)       Image: Example of Populating Metadata for HTML content into Predictive Content

Issue When searching or grouping a list of leads based on email address filter ‘Contains’ @ sign, you may encountered the different numbers in the ‘People’ tab (result). Environment This behaviour is specific to the email filter as it uses two main indexes; we’ll call them Index 1 and Index 2 when using the contains/not contains operator. Index 1 searches for the entire email address value from beginning to end. This Index is used when the @ character is not included in the list of values. Index 2 searches only for the domain half of the address, which comes after the @ symbol. This Index is used when the @ character is included in the list of values. Solution A suggestion is to create a smart list with two Email Address filters wherein you will have all the ones that do not have the '@' symbol, and for the other, you will include the '@' symbol for the email address and use the logic as 'Any'. That would give you the preferred number of leads in your smart list. Root Cause Marketo database searches for email domains in a way that when using the 'contains' keyword in the 'Email Address' filter, you must make sure that if you are using the '@' symbol in your list of domains that all email domains contain this. If you want to filter for email domains that do not include the '@' symbol, you must make sure that no email domains in your list use the '@' symbol. This behaviour happens when the indexing of the database and the rules that apply to the contains operator.

Summary You have set up a campaign or campaigns in the Email Deliverability Tool (250ok), but there is no engagement metric showing Total opens and Unique opens, which should be available in the ‘Engagement Overview’ in the Email Deliverability tool. You would need to ensure that you have configured the necessary setup for the tracking to work in the Email Deliverability tool. Issue Campaigns created in the Email Deliverability tool (250ok) doesn’t show any engagement overview metric such as total opens and unique opens. Environment Email Deliverability tool (Production/Sandbox) Solution You would need to implement the necessary setup for the metric to show in the Engagement Overview in the Email Deliverability tool (250ok)    Follow the steps below to ensure you have configured the setup for campaign tracking.   1. Ensure your DNS CNAME is configured. (All that is required is creating a CNAME DNS entry on this domain that points to 250analytics.com)  For more information, you can refer to this external documentation: https://www.validity.com/knowledge-base/what-are-custom-domains-in-250ok-analytics/   2. Insert the correct tracking pixel code retrieved from the Email Deliverability tool.    3. Always utilizing the ‘c=‘ tag in your tracking code for your campaigns to ensure the tracking is measured correctly in the Email Deliverability tool. (Obviously, the CNAME above is essential to have it set up correctly). You can follow a guide on how to implement the ‘c=‘ tag and retrieve the tracking pixel is here: https://help.returnpath.com/hc/en-us/articles/360046308092-How-Do-I-Add-My-250ok-Tracking-Pixel-   Once you have all these configuration settings, you can start tracking your campaigns which are sent via Marketo in the Email Deliverability > Engagement Overview. Root Cause Mis-configuration or no configuration made causing the campaign tracking does not work.

Issue Per our developer page: https://developers.marketo.com/rest-api/assets/programs/#update, it is possible to update tags on your existing program When updating a program tag within an existing program, you may encounter an error below given the tag and its values are correct.  {"code": "709","message": "Required tags are mandatory"}]} Environment Any API clients when performing the Web Service API Solution The workaround is to have the tag updated via the UI. Root Cause "Updating tags is a destructive operation." Any attempt to update the tags of a program must include valid values for all of the required tags for a program. Unless the 'specific' tag type you are working on is the only required tag type in the instance, then that is possible to update it using the API. Otherwise, you'll encounter the error above as it is a system behaviour.

Issue Initial MS Dynamics sync gives the error 'is missing prvReadSdkMessageProcessingStep privilege'   Environment MS Dynamics CRM integration Solution Issue Resolution These permissions, found within Security Role, require a Microsoft Dynamics Admin to set and change., Navigate to Settings > System > Security and select Security Roles icon. Click on the Marketo Sync User to bring up the individual access level for each individual entity. For the sync to work the individual privileges are as follows: Under 'Core Records':   Under 'Customisation':   Under 'Custom Entities': Any role with Marketo needs to have all permissions.     More information on Managing Users and Security Roles can be found on the Microsoft Dynamics Site: https://docs.microsoft.com/en-us/dynamics365/customer-engagement/marketing/manage-users       Root Cause The error indicates the Marketo Sync User in Dynamics lacks some of the required permissions for the sync.

Issue The Source Campaign field in Microsoft Dynamics is not getting updated when the field is updated in Marketo. The sync from Microsoft Dynamics to Marketo will be working fine. Environment Native integration with Microsoft Dynamics Campaign Sync not Enabled Solution To sync Campaign Source from Marketo to Dynamics, the option 'Campaign Sync' needs to be enabled as per this documentation: Enable Campaign Sync | Adobe Marketo Root Cause If the Campaign Sync is not enabled we will not be syncing over the value of the field to Microsoft Dynamics as it is part of the Campaign Sync.

   

What is a Blocklist? Can I Still Send My Emails, or Are You Blocking Me from Sending? What Is a Spamtrap and Why Do They Matter? Can You Give Me the Spam Trap Address That Triggered the Blocklist So I Can Remove It from My Database? Can You Give Me More Information regarding the Blocklist Issue? What Is the Quarantined IP Range? I Sent This Email Campaign a While Ago. Why Am I Only Getting Notification of the Blocklist Issue Now, and Am I Still Blocklisted? The Blocklist Notification Went to the Wrong Email Address. Why Was It Sent to That Address? Which blocklists should I be concerned about? - Top Blocklists – What You Need to Know How do blocklist issues get resolved? What steps do I need to take to resolve the blocklist issue? - Blocklist Remediation  

Issue When looking at Email Insight it is only showing the first email activity (Send, Delivered, Click or Open), even though the email has been sent several times in the past few days/weeks/months. Environment Email Insight Solution Use different Smart Campaign to send the email if you want to track statistics of the email. Root Cause Email insights will only track the first email activity associated with the email if using the same campaign. this is the same as Email Performance report in terms of this note. Multiple sends from the same campaign to the same person are counted only once.

Issue Error 603 'Access Denied' is returned for when an API user with the default Admin role attempts to make an API call http://developers.marketo.com/rest-api/error-codes/   Environment REST API Users and Roles Permissions Solution To avoid this error, create a new role: Create, Delete, Edit and Change a User Role | Adobe Marketo Root Cause It is expected that when the default 'Admin' role is used for an API user, attempting to make API calls will return error 603.