Knowledgebase

Sort by:
Issue Issue Description You encounter the error "You do not have permissions to do this" in one of the following situations: When you are creating an email template, you click on the Validate HTML button When you are trying to edit an existing email     Solution Issue Resolution This error is caused by Javascript in the HTML of the template. Email clients do not often allow <script> and Javascript in their Emails, so even though the email asset may be able to be approved, the email will present this error if attempted to be edited again or if you attempt to validate the HTML.   The solution in this situation would be to remove the <script> tag, including all Javascript, from the email HTML. After this, you should be able to edit the email or validate the HTML.   If you are unable to actually edit the asset, the workaround is to clone the asset.  If you clone the email, it can open in the editor and then you have the ability to remove the script. After this, the email will be good to go.    
View full article
Issue Issue Description Importing a program from one subscription to another is failing and is returning the following error sent via email:   Marketo encountered an error while importing [Program Name] The token "lead.First Name" is not available in the destination subscription. It is either a custom field that you have to create or need to be synced from your CRM system, if you use one. This is a article attached image   Solution Issue Resolution Check if there is any malformed lead.First Name token in email Check if there is any malformed lead.First Name token in email template used by the email(s) in the program Check if there is any malformed lead.First Name token within a program token Check if there is any malformed lead.First Name token within smart campaign flow step(s) This error has been known to occur when the email template had a lead token coded as follows, with a line break between 'First' and 'Name': {{lead. First Name}} Note: In this scenario, the error message received via email is actually referring to the token in the email template that contains a line break between 'First' and 'Name' but is stripped out on the message when HTML is rendered.  
View full article
Issue Duplicate records were sent an email from an Email Program. Solution While Marketo prevents sending emails to duplicate records (i.e. same email address) via the same Smart Campaign, it is possible to send an email to duplicate record when there is A/B test configured for the Email Program. Specifically, one record can be sent an email from the test send while the duplicate record can be sent the email from the winner send. For example, if there are two records for "mary@mail.com" in the audience, Mary can be sent two emails as follows: One record can be sent the email by qualifying for receiving the test from the sample size of the A/B test The other record can be sent the email by qualifying for receiving the winner from the sample size of the A/B test   Note: sending the test and sending the winner utilizes individual campaigns which is why the systematic deduplication of emails within a smart campaign does not take effect for this scenario. To prevent this from occurring, exclude the duplicate records from the smart list of the email program.
View full article
Issue You created a batch A/B test with a sample size of 100%.  Even though all the leads should have been sent the test email, some leads still receive the winner.     Solution Email Batch Programs are built in such a way that the test is sent with an background 'exploration' Smart Campaign, and the winner is sent with a background 'exploitation' campaign.  The exploitation campaign will send the "winner" email to the following Smart List: Member of Program Not Sent Test Email There are two situation where the exploration campaign may not send to all the leads in the program, even when the sample size for the test is 100%. If there are duplicate leads in the program, the program will not send the email to the same address twice.  It will send the test email to the first lead and skip all following leads with the same email address.  Those skipped leads will then qualify for the "winner"/exploitation campaign and will receive the winner. If there are leads in the program who hit their Communication Limits while the "test"/exploration is running, they will be skipped.  When the "winner"/exploitation campaign runs, if those leads are not at their Communication Limits at that time, they will be sent the winner email because they were not sent the test email.  
View full article
Issue You have a Smart List that should exclude a group of leads from a campaign, but they still show up in the Qualified Leads list     Solution Check the filter logic for your Smart Lampaign. "Or" logic allows leads that only qualify for some but not all of the filters to be included in the membership.  For example, you could have a Smart List with the following filters. SFDC Type = Contacts Unsubscribed = False (You are trying to exclude unsubscribed leads) Visited Webpage - http://www.company.com/products   If you use the following Advanced logic - "(1 or 2) and 3" - you will still have unsubscribed leads showing up in the list because they are Contacts, and the logic says they can be either Contacts or Unsubscribed = False.  They only need to satisfy one of the two filters to qualify, and an unsubscribed Contact would go through. There is a blog post that goes into more detail on this.  Smart List Logic - How many people do you want in your club?    
View full article
Issue An Engagement Program failed to send an email in the nurture stream. Solution Check the approval date of the email against the date of the last engagement cast. If the email was unapproved at the time, or was not activated as content, the email would not have been sent.      
View full article
Issue When a piece of predictive content is approved the following error appears: "Action failed. Please contact support. Error code:24 Error message: Invalid email title Error message: internal error, reported to support." Solution Change the title of the content to less than 48 characters. This error indicates that the title for the content is too long. The maximum number of characters for a title in content AI is 48 characters.      
View full article
Issue After running an A/B test, some records appear to have received both Test and Winner.     Solution In an A/B test, the sample size of the audience is sent the variants, and then for the winner: the entire audience minus the test audience is sent the Winning email. So let's say that you received both Test and Winner. This means you have duplicate records in the database. Marketo is designed to not send duplicate leads the same email at the same time. So one of the duplicates is qualified for the Test, and then when the Winner is sent, it's the total audience minus the test audience, the Winner is sent to the duplicate record. This above situation can apply to Lead Records as well, because of duplicates with the same email address, but also duplicate records that may have a FWD set up between them (record B emails FWD to Record A email address). To reduce the chances of this happening, you may wish to run a de-duplication pass on your database.    
View full article
Issue A Change Data Value activity gets recorded on a person record but the Updated At field for the record doesn't get changed to reflect it.   Solution The "Updated At" field in Marketo is a system managed field that gets refreshed any time that there is a data value change to a person field, but not when the field is on the company object instead.  To confirm what object the field in question is on, search for it in Field Management and check what folder it is located in.  The folder Info (or Lead Info) contains person fields while company fields are contained within the Company Info folder.
View full article
Issue You have a Marketo form embedded on a non-Marketo page.  When you open developer tools in your browser you see: "Error loading form: Object error: true errorCode: 400 message: "Subscriber <Your Munchkin ID> is not valid" "   Solution The form embed code you are using is looking for your instance in the wrong place. Check the URL when you first log in to Marketo, make sure the sub domain in that URL matches what is in your embed code. For example: If you see https://app-sjst.marketo.com/ then make sure you have that same "app-sjst" in your embed code. Please note: This may vary between your sandbox and production instances.        
View full article
Issue How do Revenue Cycle Explorer filters operate? Solution RCE Filters operate in the following ways: Select from a List (Includes, Excludes) -- This filter type within RCE will let you include or exclude preset values Match a specific string (Contains, Does not Contain) -- This filter type will let you enter a free form value such as Contains "We" to find statuses which may have Web in them. The not-contains would filter anyone who did not have "We" in the status. On either filter you can select Multiple Values. Within the Match a Specific String function click on [+] and add another value option and this will then add additional string areas to use. A example would be Status contains: Reg Regis Registered Registered - Web etc.. As you can see you can match to one of many values!  
View full article
Issue You are trying to access the Marketo site, but keep reaching a screen telling you your browser encountered an error. These error messages include: "ERR_EMPTY_RESPONSE" or "DNS_PROBE_FINISHED_NXDOMAIN"   Solution Flush the DNS Cache on your local machine. To do so: Open Windows command prompt as admin (you can do this by searching for command prompt in Windows, then right clicking it and selecting "run as administrator") Run the command: ipconfig /flushdns The command will return a simple completed message or will prompt you for another command when it is done Re-open your browser and go to the site you wanted to reach Please note: The DNS Cache is cleared on a normal reboot too. However, the hosts file on your computer will be used during startup to put in new DNS entries, so it will never appear completely empty if you open cache.
View full article
Issue Admin > Sales Insight > Licensed Seats displays the number of seats used in the last 30 days.  How is this calculated?     Solution The number of seats used is calculated by the number of unique SFDC users that have loaded either the Sales Insight panel on a Lead/Contact/Account/Opportunity page layout or accessed the Marketo tab in the past 30 days.   Who This Solution Applies To Customers with Sales Insight for Salesforce    
View full article
Issue You want to create a field that will grab the web page the form was filled out on and add this as a token in an alert that goes to sales when a form is filled out. Solution This can be achieved either through a Smart Campaign or the JS API code. The code is more efficient because it doesn't mean another trigger is active in your instance. Smart campaign: You'll want to create a smart campaign with Smart List - Fills Out Form and Flow - Change Data Value, [your field name], New Attribute is {{trigger.Web Page}} You would need to reference the trigger token in the alert email so the team knows what product page the end user filled out the form on.   Code: (Embedded Form) This can be done with a hidden field.   MktoForms2.loadForm("//app-**01.marketo.com", "***-***-***", 148,     function(form)     {         form.addHiddenFields({ LastFormURL : document.location.href })        }); The asterisks represent your company's Marketo data (your Munchkin ID and Marketo instance). Your developer will know what to do if s/he is already using the embed code.   Code: (Marketo LP) In a Marketo LP, you will have to edit the template and put this at the end, before the </body> tag :   <script> MktoForms2.whenReady(function (form) {     form.addHiddenFields({ LastFormURL : document.location.href }); }); </script>
View full article
Issue Is the System.DateTime token populated based on the timezone of the instance? Solution System.DateTime token is based on your account timezone settings.
View full article
Issue There is a discrepancy for certain emails between Email Insights and Email Performance Report. The data (e.g. sent, delivered, opened and clicked) are significantly lower in Email Insights for the emails as compared to the Email Performance Report for the same emails. Solution There is most likely a discrepancy because at the time Email Insights was first enabled "you’ll have four weeks of historical Email data in addition to all new email activity". There was no request to Marketo support to upload historic data beyond four weeks which would have included data for the emails above. This request relates to the notes below from the article: "We’ll give you a four-week period before you can request Marketo Support to upload your data" The solution is to request that Marketo Support backfill the report data so you have data for Email Insights beyond the four weeks.    
View full article
Issue URLs generated by a Velocity script token are not tracking when a person clicks on the link in an email   Solution Velocity scripting enforces strict formatting of links in order for them to be tracked:   http:// or https:// must be included in the URL.  If using a variable, the http:// or https:// must be output outside of the variable. The URL must be part of a fully formed <a> tag.  No other type of link tag will work Links must not be outputted from within a for or foreach loop To ensure links are tracked properly, set the entire path inside a variable and then print the variable. Correct: #set($url = "www.example.com/${object.id}") <a href="http://${url}">Link Text</a>   Correct: <a href="http://www.example.com/${object.id}">Link Text</a> Incorrect: <a href="${url}">Link Text</a> (missing http/https) <a href="{{my.link}}">Link Text</a> (missing http/htpps, cannot reference an outside my.token) <page xlink:type="simple" xlink:href="https://www.example.com">Click me</page> (must use an <a> tag)    
View full article
Issue You come across a few leads who failed to sync to SFDC and would like to have the list of leads who faced the same issue.   Solution Unfortunately Marketo doesn't have a specific type of filter to leads who failed to sync to SFDC. However if they are new leads who haven’t synced to SFDC, then you can filter them by using the filters "Person was created" and "SFDC Type" with condition "is empty". If you want to find the list of leads (previously synced to SFDC) who failed to sync among a particular group of leads, you can filter by following the below steps. 1. Create a new Boolean type field in SFDC namely "Sync Error?" and with the default value as "true". 2. Wait for the field to sync into Marketo. 3. Create a Smart Campaign to select those group of records and the flow steps to change the value of the Boolean field "Sync Error?" to ”False" and then "Sync person to SFDC". 4. Once the campaign has finished running, you will be to pull a report on SFDC on the list of leads who have the value "True" for the field "Sync Error?". It means that the value was not updated to SFDC as the record failed to sync. With this list you will be able to select the records and resolve the sync issue. You can also create a smart list of leads who were never able to sync with the following filters: Lead was synced to SFDC : Assign to : is not empty SFDC Type: is Empty      
View full article
Issue How to copy the data from one field to another field using tokens. Solution It’s very easy and it can be achieved through a Smart Campaign. Create a Smart Campaign and set up the Smart List to target the specific leads you want. In the Flow, use the Change Data Value step. You would need to choose the field you are copying to as the Attribute, and the new value as token {{lead.fieldYouAreCopyingFrom}}. When you run the campaign, the values will be copied across.  Be careful when doing this as the process cannot be reversed and any existing data in the field you are copying to will be destroyed. Note: Use appropriate tokens for the field, if the field is available under lead use lead tokens otherwise company tokens.
View full article
Issue Description Campaign has a "Visits Web Page" trigger and a wait step in the flow.  Leads were showing as being in the wait step, but are not shown in the Campaign Members tab Issue Resolution The leads do not show up in the Campaign Members list because they are anonymous. Anonymous leads can trigger "Visits Web Page" but do not show in the campaign membership.  They can go through the flow, including going into wait steps. To prevent this, add the filter "Email Address is not empty" to the Smart List for your campaign.  This will prevent anonymous leads from being pulled into the flow.
View full article