Knowledgebase

Sort by:
Issue Delay in SFDC Sync causes email to be sent with unpopulated tokens Wait steps in campaign designed to prevent race conditions are sometimes not long enough for the SFDC Sync to complete Wait steps cause delay in customer receiving their email after filling out for - bad user experience Environment Smart Campaign triggers off form fill and flow step syncs Person record to Salesforce  Info from SFDC sync is used to populate tokens in email Campaign uses Wait steps to hold email send until sync is finished Solution Split the Smart Campaign into two campaigns The first campaign runs the sync activities, but does not send email The second campaign triggers off of the Data Value Changes resulting from the sync and sends the email with the email tokens populated
View full article
Issue You are seeing a discrepancy in email activities (Sent, Delivered, Open, etc.) when comparing the RCE Email Analysis report and Email Performance Report, when looking at the same email and date range.   Root Cause Here are some of the most common reasons for a discrepancy between the RCE and Email Performance Report (EPR): Deleted/Merged Leads: If you have leads that received emails and then were deleted or merged in Marketo, their individual email activities will be included in EPR. RCE will not count deleted or loser leads from a merge Re-sent Emails: If you re-send the same email to the same lead using the same smart campaign, EPR will only show the 1st send occurrence. RCE will show all email activities for a lead. Delivered & Soft Bounce: There are situations where a lead will log a Delivered activity and then shortly after, a Soft Bounce activity. In these situations, EPR will show this lead as a Soft Bounce count, whereas RCE will show this lead as a Delivered count. If you are still seeing a discrepancy between the reports that cannot be explained with the above, reach out to Marketo Support to help advise.
View full article
Issue How to subscribe to Marketo service interruption and outage notices.       Solution Issue Resolution   Follow the instructions RE: Subscribe to Status page notifications for the latest information on service issues, degradations, or disruptions that may be impacting your Adobe Marketo Engage subscription.   
View full article
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. 
View full article
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.
View full article
Issue A smart campaign is configured to clear the field value for a field, however, when the smart campaign ran, it didn't appear to have cleared the field values and the campaign results display no activities. Solution Check to see if people qualified for the smart campaign and became campaign members by clicking on the 'View Campaign Members' button. If there were people that are in the campaign members list, then it means people qualified and the flow step did not process. If people did qualify, then check [Admin > Field Management] to see if there is a block field updates enabled on "Flow change data value" - In this case, temporarily disable the block field updates on "Flow change data value" for the field, run the campaign so that it can clear the values on the field and then re-enable the block field updates. Root Cause The smart campaign did not return any activities in the results if the flow step was only configured to change the data value of a field that has block field updates enabled for "Flow change data value" Environment Smart Campaign Change Data Value Clear Field Values Field Management Block Field Updates
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 This method can be used when moving a CNAME from an old instance to a new instance. Often at times, when changing to a new instance, this question can come around, and ones would wonder how to do it or a solution on how to do it. This steps will show you the two phases which I will explain below. (Note: This would need to be done before the old instance deactivated) Issue A CNAME needs to be moved from an old instance to a new instance Solution NOTE: You cannot have the same CNAME in two different instances (Pointing to two instances, e.g. cname1.company.com pointing to instance1.mktoweb.com and instance2.mktoweb.com)   Key terms: CNAME 1 = Initial cname in the old instance CNAME 2 = Additional cname created in the old instance INSTANCE1 = Old instance (Instance Name) INSTANCE2 = New instance (Instance Name)   Phase 1: --------------- 1. Create an additional CNAME (a replacement CNAME) which you would want to swap as the default in the second step. CNAME 1 > INSTANCE1 (Default) <Existing CNAME in the Marketo Admin > Landing Pages section> CNAME 2 > INSTANCE1 This would be the additional CNAME created for the replacement.   2. Swap the default with the replacement CNAME you just created in step 1 and set this CNAME1 as a domain alias in the old instance. CNAME 1 > INSTANCE1 A domain alias in the old instance. CNAME 2 > INSTANCE1 (Default)   —————————————————————————————————————————————————————————————————   Phase 2: --------------- ** Transition might not be smooth during the cutover. 🙂 (The Landing page links might get some interruption during the cutover)   During the Cutover (Before the old instance deactivated) :  1. [Your Action] - To remove the CNAME1 which is a domain alias in the old instance (INSTANCE1)  2. [Your Action (IT Team)] - To create CNAME1 as a domain alias in the new instance (INSTANCE2).  (During this time the link to old landing pages will be broken) 3. [You need to raise a support ticket to enable SSL for CNAME1 for the new instance (INSTANCE2).  If you have any questions, please contact Marketo Engage Support at https://support.marketo.com.   Environment Production/Sandbox
View full article
When trying to sync updates to your salesforce.com instance from Marketo you see one of the following errors in the activity log : Failed: INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITY INSUFFICIENT_ACCESS_OR_READONLY INVALID_CROSS_REFERENCE_KEY This is an error sent to Marketo from Salesforce. There are a number of reasons why this error could occur. INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITY means that the user who is trying to make the update does not have access to a related element that is required for the record to be updated and saved in SFDC. There are a number of specific examples of what might be the cause but these will vary from organisation to organization depending on the configuration of your salesforce.com. If you were to connect to sfdc as the Marketo user and try manually updating the same record that Marketo is trying to update then you will get the same error in the salesforce.com UI. Here are a list of some elements that you should check in SFDC if you see this error: Do you use record types? If so make sure that the the Marketo user has access to all required record types and that the Record Type Id in Marketo is correct for the Lead or Contact. Sometimes, when a Lead is converted to a Contact in SFDC, the Record Type ID fails to update in Marketo, causing the sync to fail. This is one of the most common causes for these errors. Are there any look-up or master detail fields on the object in question? If these types of fields are being updated then make sure that the Marketo user has access this object/ these records. Do you use Apex? If so you may have trigger that fire on the the update of a record, you will need to make sure that the Marketo user has profile access to the relevant Apex classes. If you have any workflow rules or assignment rules that send an email when the record is saved then you will need to make sure that the Marketo user has the send email permission and has access to the email folder that contains the mails that are sent rules are triggered. Make sure "Convert Leads" is turned-on within SFDC.  If it is not, you will get this error message when trying to merge leads that exist within Marketo and SFDC.  
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
Question: Is it possible to assign a lead owner during a list import?   Answer: No. The reason for this is because lead ownership is a Salesforce functionality and should be first done from within Salesforce. If you are not able to do the assignment in Salesforce, here is one option that is available to you within Marketo:   1) Upload your leads into Marketo's Lead Database without lead owner information. i.e. your import CSV will not have any lead owner column in it. More information on importing leads can be found here: Import a List of Leads from a Spreadsheet into Marketo (Import List).   2) Once the list import is successfully completed and your leads are in Marketo, you can use the "Sync Person to SFDC" flow action to assign lead ownership. More information on the "Sync Person to SFDC" flow action at Sync Person to SFDC.
View full article
Issue description:  The token {{member.webinar url}} does not populate when you send a confirmation using an Email Program within the Event program.   Issue Resolution:  When you use an Email Program to send your webinar confirmation, the token {{member.webinar url}} is only able to look at the membership properties of the Email Program, not the top-level Event program. Because of this, it is not able to populate the token.  Instead, you should send your webinar confirmations using a Smart Campaign inside the Event program.  
View full article
Issue How page views and form fills are counted in the statistics section of a Marketo Landing Page asset. Solution How they're calculated When viewing the Landing Page asset in either Design Studio or Marketing Activities, the statistics section provides information regarding page views and form fill outs, if the page has a form located on it.  The page views are a cumulative total indicating how many times the page was loaded, regardless if the visitor was a known record in the database. This means anonymous people can record a view here, due to Munchkin tracking on the page. This section provides a total number of views, not unique visits. This means that a person can load this page multiple times and each visit will be tallied in this section. The form fills section (x Filled out Form (x%)), indicates how many times a visitor filled the form out on the page, if it has one. This total is also counted in the same way the views section is, meaning it's a total number of submissions. Therefore, if a record in your database fills out the form more than once on a page, it will be counted toward the total.   Difference between calculations The difference between these two metrics is that the page views will keep a historical record of visits to the page. This means the total will not change if you happen to delete a bunch of records that visited the page in question - the total persists regardless if the record is no longer in the database. With that said, the forms section does not. This area is tied specifically to the existence of that known record in your database. This means that, once a record who filled the form out is removed from your database, the submissions they performed will be subtracted from the total.
View full article
Issue Issue Description The 'Marketing Suspend Cause' field is not available as an option in the Change Data Value flow step, or in the Smart List of a Smart Campaign, nor is it possible to manually update the field in the lead record.     Solution Issue Resolution Unlike the 'Marketing Suspended' field which is not system managed and can be manipulated by the user, the 'Marketing Suspended Cause' field is a System Managed field and is not able to be updated by the user. The intention of the field is to provide additional details about why a record may have been marked as "marketing suspended" based on a background process. Note: The "Marketing Suspended Cause" field is no longer used by any background processes. It has been retained as a legacy field to preserve any information that might have been written to the lead record in the past.
View full article
Issue The GoToWebinar integration is not able to see a webinar that has been set up as a "Simulated Live" record type. Solution GoToWebinar requires v2 for the GoToWebinar API for the "Simulated Live" webinars.  Marketo is still on v1 of the API so "Simulated Live" webinars are not supported at this time.    Who This Solution Applies To Customers integrated with GoToWebinar
View full article
Issue You created a picklist field in SFDC and want to know if that field will sync down to Marketo with the field type of picklist.     Solution Marketo has a picklist option in form fields, but not in Lead Database fields. When you sync a field from SFDC that has the type of picklist, this field will show in Marketo with a type of String. However, when you create a form, the field type for your field will show as "select," which is a picklist.  
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 Is there a way to prevent opening a new browser window when a mailto/email address link in an email is clicked? Solution The reason why the link clicked in an email redirects to a new browser window occurs is because the link is a tracked link. As per design of Marketo tracked links, they are required to be loaded in a browser first which is why the mailtolink/email address clicked is loading in the browser first. If you wish to load the link clicked in the same window and not redirect to a new browser window, you will need to disable tracking on the link. https://docs.marketo.com/display/public/DOCS/Disable+Tracking+for+an+Email+Link    
View full article
Issue No data appears in the Email Performance Report (configured for a specific time frame) even though emails have been sent to the leads. Solution The reason why the leads who were sent the email do not appear in the email performance report configured for a specific time frame is because the Sent Date filter is based on the first date that the email was sent to a given lead. Email Performance Peports only show data for the first time an email was sent. If you send the same email multiple times to the same leads, reports intended for later sends will not include leads who first received the email outside of the report's time frame. Apart from that, it is also worth to check if the email performance report has any additional smart list filters that the leads may not qualify for.    
View full article