Knowledgebase

Sort by:
Issue Clicking a tracked link in an email either leads to a 404 page or the fallback page. Environment Tracked links Tokens Specific Characters: "#", "$", unbalanced brackets "{" or "}" Solution Do not use the following characters "#", "$", unbalanced brackets "{" or "}" in a link that is tracked when using a token as well. For example: www.google.com/ebook-download.html?ebook={{lead.ebook}}# This will not work and will either direct to a 404 page or redirect to fallback page. When hovering over the link you will see that it is not a normal tokenized link, it will contain something along the lines of: $mktEncrypt.encrypt($mkturl2)/<random characters> Root Cause When using tokens in the url of a tracked link, the email is processed and the tokens are substituted and populated with the correct information. The engine that assembles this information have some characters reserved for use such as #.
View full article
Issue CORS Policy Error for form submission occurring intermittently   Solution   1) Confirm there is only one form embedded on the page.  2) Create a blank landing page on the same domain as the page with the issue 3) Embed your form using the exact code provided by Marketo 4) Confirm whether the error occurs on the blank page with the Market embedded code 5) If you are still experiencing CORS Errors after conducting this testing, then create a support ticket with the following details: -The form -The test landing page you used -The domain that you are experiencing issues with -Screenshots of the error received   Root Cause If you have customized the embedded code, Marketo Support is not able to troubleshoot custom code. Multiple embedded forms on a single page can cause the forms to not work incorrectly. Multiple forms embedded with different domains may require your IT team to make sure resources are requested correctly from one domain to another. Environment Marketo form embedded on a non-Marketo webpage  
View full article
Issue Why is there a difference between the Exhausted Count displayed in an Engagement Program Stream vs. a smart list using the "member of engagement program stream is exhausted" filter? Solution To account for the difference in a smart list that is displaying a different number of people that have exhausted the content in a stream, in the smart list account for the other conditions the Exhausted Count uses: Engagement Program Cadence of "normal" - this can be included as a constraint on the "Member of Engagement Program" smart list filter The members were not blocked - this can be included in the smart list by using the smart list filters: member of smart list is not blocklisted, unsubscribed = false, marketing suspended = false, email address is not empty and/or email invalid is false. Have not exceeded the communication limit at the last nurture cast - there is no specific smart list filter for this, so it will need to be manually checked in a lead's activity log. Root Cause The Exhausted Count represents the latest exhausted number after the last run/cast. It has other conditions like the nurture cadence of a member should be "Normal", and the member was not blocked or have not exceeded the communication limit at the last nurture cast. If the smart list is configured as follows, then it will display a different number as it does not account for the engagement program cadence of 'Normal' and if a member is not blocked and has not exceeded the communication limit at the last nurture cast. #1: Member of Engagement Program is any Exhausted Content is true Program is [Program Name] Stream is [Stream Name] Environment Engagement Program Exhausted Content Smart List
View full article
Summary Marketo-only records must be manually synced, become a member of a default-program, encounter a Salesforce flow step in order to sync with Salesforce. Issue Records are in the Marketo database but are not syncing over to Salesforce automatically like I thought they would. Solution The sync between Marketo and Salesforce is bi-directional. However, in order for a record to be synced, one of the following conditions must be met: The record becomes a member of a program which is synced to a Salesforce campaign. This occurs when the background sync is used to keep members of a Salesforce campaign in sync with a Marketo Program status. This can easily be verified by navigating to the program and looking at the summary view. More information on this feature can be found here: https://docs.marketo.com/display/public/DOCS/Sync+an+SFDC+Campaign+with+a+Program https://docs.marketo.com/display/public/DOCS/SFDC+Sync%3A+Campaign+Sync The record encounters an SFDC flow step. Any time a record encounters a Salesforce related flow step in a smart campaign, this will cause the record to sync with Salesforce. Some of these flow steps have other implied actions, which you can read about here: https://docs.marketo.com/display/public/DOCS/Implied+Salesforce+Actions The record is manually synced to Salesforce through a single-flow action. This is an intentional user action. It can only occur when you find the record in your database or in the people tab of a smart list and select the option from the 'Person Actions' menu. More on how to do this can be found in this document: https://docs.marketo.com/display/public/DOCS/Run+a+Single+Flow+Step+from+a+Smart+List Root Cause Records had not encountered SFDC flow steps, become members of a program synced with a Salesforce campaign and hat not been manually synced to Salesforce. Environment Marketo with the built-in integration with Salesforce
View full article
Marketo has the ability to see and pull data from Salesforce Formula fields, there is however a catch which will be explained in this article.   Everytime the Marketo Sync connects to Salesforce, it will scan records and look at the " SytemModStamp " (salesforce system field) for each one of them. It will compare this value with the stored value, which was pulled at the last scheduled sync. If the values match, Marketo will move on to the next record. If the values are different (new value later date than previous value) , then Marketo will do a compare and contrast of all fields on that record in both systems and update the information as needed.   When a normal non-formula field is updated and changed on a Lead/Contact record in SFDC, the SytemModStamp value is updated. This is how on next sync Marketo knows to do a compare/contrast check and pull updates. Formula fields do not behave the same way. A formula field is calculated based on data in fields called upon in the formula; this means that the formula field calculation itself will not update the SytemModStamp in Salesforce.   Chances are you already have existing records in SFDC and Marketo. If you were to create a formula field today in your instance of SFDC and have it sync down into Marketo, the data calculated for the formula field in SFDC will not come into Marketo right away. The reason for this is, the formula field has created data based on already existing data, this does not result in a SytemModStamp change.   Typically formula fields will be a calculation of data from fields which are somehow related to the lead/contact record. This means that moving forward, any change in the normal field, will result in a SytemModStamp change as well as a recalculation of the formula field. In this case, Marketo will see the updated SytemModStamp due to the normal field change. Marketo will do the compare/contrast excercise and find that the formula field also needs updating.   If you create a formula field in SFDC and would like to have all the historical data for the formula field to come into Marketo, you can force an update on the records in SFDC to update the SytemModStamp. This way, on next sync, Marketo will see the formula data and pull it in. Alternatively, you can simply allow for natural SytemModStamp updates in SFDC to occur which should result in a slow trickle of historical data from SFDC into Marketo for the newly created formula field.   You can only use data from a formula field in Marketo to segment data and filter. If you try to do a change data value, Marketo will accept the change, tries to sync it to Salesforce and fails to update there. Eventually the Salesforce calculated value will come back into Marketo.  
View full article
Issue Description: Salesforce refreshed your sandbox and it no longer syncs with Marketo Issue Resolution: As a safety precaution, once an instance of Salesforce is synced up with Marketo, we no longer allow the user to sync this particular instance of Marketo with any other instance of Salesforce. When Salesforce does a “refresh” of your sandbox, they are actually canceling your old sandbox account and creating a new account and pulling fresh data from your production. This means the refreshed sandbox is actually a different account and has a new OrgID. Marketo Support can assist by unlocking your Marketo sandbox to be synced up with a refreshed Salesforce sandbox. If you run into this scenario, please create a support ticket requesting that we enable the reset of the OrgID for your SFDC sandbox.
View full article
Article Text Included in this Article: Overview Check if Data is Being Transferred to GA Troubleshooting Steps Check if GA is Enabled Verify both RTP and GA tags are loading on your website Check GoogleAnalyticsObject customizations   Overview Data from RTP can be linked to Google Analytics (GA) for further analysis. Below we show you how to check if data is being transferred and a few troubleshooting steps if you find that it isn't.   Check if Data is Being Transferred to GA        Log in to GA and navigate to Reporting > Behavior > Events > Top Events You should find events with either the category "Insighterra" or "RTP". If not, another place to check for incoming RTP data is in the Custom Variables tab.      Navigate to Reporting > Audience > Custom > Custom Variables If you use custom variables, you should see RTP data populated here.   If you expected to see populated data in either of these two areas but you aren't seeing any, then you are having issues with your RTP-GA integration. Check out the steps below for some troubleshooting tips.     Troubleshooting Steps If you have confirmed that there is no data flowing to GA, there are a few troubleshooting steps which you can take.   Check if GA is Enabled        Go to Account Settings       At the bottom of the page, verify that Google Analytics or Google Universal Analytics is enabled. Only one of these integrations should be enabled at a time - if both are, disable one of them.   If neither is enabled, go ahead and enable one of them. Follow this article to learn more about enabling and integrating GA with RTP.     Verify both RTP and GA tags are loading on y our website   To verify this, you will need to navigate to your web page and open the browser's developer tools window. Follow this link to learn what the developer tools window is and how to get there on different browsers and operating systems.        Navigate to your browser's developer tools          Click the Network tab and search for "analytics.js" and "rtp.js"   If both "analytics.js" and "rtp.js" show up in your search, then both RTP and GA are loading on your website. If one or both are missing, go through these steps to add an RTP tag to your website, and these steps to add a GA tag.       Check GoogleAnalyticsObject customizations   If you're using Google Universal Analytics, check if customizations have been made to the GoogleAnalyticsObject . Read this article to learn more about this object and its possible customizations. To check for customizations, follow the steps below:        Click on the Console tab in the developer tools and run GoogleAnalyticsObject          Type "GoogleAnalyticsObject" and hit Enter to check the object's type     If the object's name is "ga", then you are in the clear. If not, unfortunately we do not currently support the customization.    
View full article
Issue Issue Description Using a token in the Smart List of a Smart Campaign yields unexpected results, an error, or the campaign to not trigger.    Solution Issue Resolution Tokens cannot be used in the Smart List section of Smart Campaigns. Tokens can be used in the Smart Campaign Flow, in the following steps: Interesting Moments Change Data Value Salesforce Campaign Steps (add, remove, change status) Create Task
View full article
Issue You have been sending live emails (non-samples) to yourself or colleagues to test functionality of an upcoming email blast, and even though you may be opening the email, you are not seeing the open email activity on the Lead Activity Log.     Solution Note that there may be a slight delay between opening the email, and the activity displaying on the Log. Marketo considers an "open" to be when the images in the email are downloaded, specifically a single-pixel tracking image. The recipient may be receiving the emails and viewing them, but not downloading the images. This would not count as an "open."  Please note that since text-only emails have no images, so they will never log an Open activity. If the images are being downloaded, and you are still not seeing the activity after about 5 minutes, check to make sure there are no duplicate leads that are logging the activity instead.  If you need further assistance, please contact Marketo Support.    
View full article
Issue Updating an Email Template is creating a draft for existing emails without the desired changes     Solution When changes are made to an Email Template in the Design Studio that is already in use and those changes are approved, it will create a Draft for any existing Email that was created from that Template. If the draft is not reflecting changes you would like to see made, you may have included the changes within a mktEditable or Editable class <div> tag. The content within a mktEditable class element within an email template are ignored from any changes as they are considered to be "default content". Any content within these elements will not see any changes made to them based on changes to the template, and will only be seen when creating a new Email asset. You can update an editable section to remove it's editable status, however this will remove any changes to the content done in any email. You can see which elements can be classified as Editable here: https://docs.marketo.com/display/public/DOCS/Email+Template+Syntax    
View full article
Issue A landing page is taking a significant time to load. Solution The load time of a landing page is generally due to resources that have a large file size or due to third-party scripts. This can be identified by using tools like https://tools.pingdom.com/ that breaks down the loading time of individual resources and scripts within a landing page. Another way to inspect the loading time of resources and scripts within a landing page is using the network feature of the developer tools in Google Chrome, Firefox, Safari or any other web browser: https://developers.google.com/web/tools/chrome-devtools/network-performance/reference https://developer.mozilla.org/en-US/docs/Tools/Network_Monitor https://developer.apple.com/safari/tools/    
View full article
Issue Sometimes you may get this error when trying to sync a Marketo Program to an SFDC Campaign -  "Not allowed: Salesforce campaign contains incompatible statuses", even though the statuses match in the Marketo program and SFDC campaign.   Solution Check for the statuses in the Marketo program channel and SFDC campaign - you will see the same statuses. This error occurs if there is any case-sensitive error in the statuses. For example, if your Marketo program has the following statuses: Attended, Registered, Unable to Attend and the SFDC campaign has Attended, Registered, Unable to attend. Then you will encounter the above error. You have to change the status in Marketo as "Unable to attend" or change the status in SFDC Campaign as "Unable to Attend"  in order to fix this.    
View full article
Issue Email Link Performance report on the same email shows more clicks compared to clicks in the Email Performance Report. Solution Email Performance Report clicks shows the total number of leads who has clicked any link in that email. This count is independent of any links and how many times a lead has clicked any link on that email. Email Link Performance shows the number of unique people who clicked each link. It shows the number of leads who clicked that particular link. The same lead could’ve clicked another link. So in the total it would be counted as 2 leads in the report but in reality both are same leads. This is the reason why you see Email Link Performance report shows more clicks compared to clicks in the Email Performance Report    
View full article
Issue Links placed into emails by a token are not being tracked and do  not show successful click activity in the lead/person record.     Solution When Marketo sends emails, you can think of building the email in 2 steps: Marketo searches the email code for "http" or "https" and wraps the tracking code around the URL Marketo inserts the values of {{tokens}} into the email.   If the {{token}} value is http://www.domain.com , that would be expected to not track because of the above 2 steps. After the {{token}} value is inserted, Marketo does not go back to wrap tracking code around http/https. The {{token}} doesn't look like a URL when the system applies the tracking code because the tokens don't pull the values in until the next step after. The solution to tracking tokens is to place http:// or https:// on the outside of the token, like such: http:// {{token}} That way, when Marketo builds the email, in step #1, the system recognizes the http and knows it's a URL. Then the tracking is wrapped around the http and the {{token}} as well. Then in step #2, the {{token}} value is inserted into an already-wrapped link. Keep in mind is that if the {{token}} value contains http, but http is on the outside of the {{token}}, the link will break. Let's say the URL you want to insert is http://www.domain.com . You have to move the http:// out in front of the {{token}}, but you don't want to also have it inside the {{token}} as well or your link ends up being http://http://www.domain.com. To get around this, you'll need to remember to take the http:// out of the {{token}} value. {{http://www.domain.com}} would instead be http://{{www.domain.com}}
View full article
Issue You want to re-map a synced SFDC field to a different field in Marketo. Solution Yes, it is possible to re-map Salesforce - Marketo fields after initial sync. For this you need to Contact Marketo support with a request for your current field mapping and your desired field mapping. You will need to provide the Marketo Field(s) and the Salesforce API Name(s), then format your request similar to the example below.   Important Note Before initiating the re-mapping, please export the records and their field values from Marketo and import the values into their Salesforce or create a smart campaign to write the data from one field into the other. This is important so that there is no data loss after the remapping work has been performed. Marketo will not automatically push these values to SFDC, after the mapping is complete.   Example Request Current Mapping: Field Label: [Marketo Field Name 1] CRM Field Map: fieldName__c (SFDC Lead)   Field Label: [Marketo Field Name 2] CRM Field Map: fieldName__c (SFDC Contact) Desired Mapping: Field Label: [Marketo Field Name 1] CRM Field Map: fieldName__c (SFDC Lead) fieldName__c (SFDC Contact)   Field Label: [Marketo Field Name 2] CRM Field Map:   Limitations - Fields need to be of the same type (String/String, Date/Date, etc) - The losing field must be completely removed from use from any Campaign, Form, etc. - The fields must exist on the same object in Marketo (for example a field on Company cannot be merged into a field on Person or vice versa) - Fields can only have one of each object type (eg: A Marketo Field could be mapped to a SFDC_1 (Lead) field and a SFDC_1(Contact) field, but can not be mapped to both SFDC_1 (Lead) and SFDC_2 (Lead). - Fields can be mapped to a maximum of 2 SFDC fields - SFDC fields can only be mapped to one field in Marketo   Please note that there may be additional limitations in certain circumstances. The Marketo Support agent that handles your request will provide any further details should such a situation arise.  
View full article
Issue Calls made to the REST API return response code 611 "System Error".   Solution Submit a Customer Support ticket with the following information   The full body of the REST API call including the endpoint being called The full body of the REST API response The date and time that the call was made Customer Support will work to diagnose the root cause of the error and the reason a more identifiable error code is not being returned instead.        
View full article
1. Navigate to  https://status.adobe.com     2. Click Manage Subscriptions       3. Sign in using your Adobe credentials or click Create an Account to log in                                     4. Click Create Subscriptions       5. Under Experience Cloud, click on Adobe Marketo Engage to expand:   6. Select Product Offerings or Services and click Continue                                         Prior to selecting a regional location(s), you will want to identify what data center and pod/server your instance is located in. Yo u can access this information from the Adobe Marketo Engage Admin tab. After clicking on this tab from the menu at the top of the page, select My Account on the left rail:            Scroll down to the Support Information section to see the data center and pod in which your instance is located:  The example above indicates that this instance is in our Ashburn data center on pod 38. This user would select the regional location Marketo Ashburn, and then pod AB38, as shown below.    The abbreviations for all of our data centers are as follows:  ab = Ashburn  sj = San Jose  sn = Sydney  lon = London  nld = Amsterdam   NOTE: This method can also be used to identify what Real Time Personalization (RTP) pod/server your instance is in.      7. Select regional location(s) and event type(s)     8. Select the environment(s) you would like to subscribe to and click Continue       9. Review your subscription preferences and click Done  
View full article
Issue Issue Description Even though the Success Path Analyzer and the RCE report may be looking at the same thing (e.g the conversions from one stage to another), the numbers in Success Path Analyzer and RCE Conversion Ratio will not match. Solution Issue Resolution Success Path Analyzer is telling you that records are flowing from one stage to another, for example a record moving from Cold List to MQL, the conversion rate will display the rate from this stage to the next stage. If you look at the RCE Conversion Ratio, this is not tracking just the conversion from the first stage on the Success Path Analyzer to the second but instead this tracks all the conversions from this stage to another (eg. Cold List to MQL, Cold List to Attempting). Thus resulting in a much higher conversion percentage as the RCE is not bound to the green path from the Success Path Analyzer. Who This Solution Applies To Customers using RCE, Customers using Success Path Analyzer
View full article
Issue When trying to create a new Engagement Program, you get an error stating that your instance has reached maximum number of active engagement programs.     Solution Due to engineering constraints and as well as to have better user experience, we have limited the total number of active Engagement Programs to 100. So you can create as many Engagement Programs as you want, but when you try to activate more than 100, you will get an error message that says “You have reached 100 Active Engagement Programs. Please deactivate some of your existing Engagement Programs to activate this program." The easiest way to see all your Engagement Programs is to use the filter on the navigation tree.  Click the filter icon and select Engagement Programs from the list. This will allow you to see which Engagement Programs are no longer needed so that you can deactivate them to make room for more.
View full article
Issue Description Can you remove a CRM from Marketo? Issue Resolution You cannot remove a CRM integration from an instance. Once the CRM of your choice is clicked (Dynamics or Salesforce) the instance is set to use that CRM for the remainder of its life. Once the login and mappings have been setup for a instance, the CRM instance or org cannot be changed as well. If for a reason you do need to change the CRM or the linked instance, you would want to reach out to your Customer Success Manager to get information on provisioning a new Marketo instance.
View full article