Knowledgebase

Sort by:
Issue My token is not displayed correctly in view as webpage version of email. Environment If customers manually type a {{my.token}} and use uppercase M such as {{My.token}}, then the view as webpage version of email may not render that token as expected. The feature to HTML encode lead tokens (source of external data) for security reasons, applies to my tokens that incorrectly use uppercase M. HTML Encode Tokens Solution Use the token picker to pick the correct lowercase {{my.token}}.
View full article
If the user makes changes to the my tokens, snippets, etc during the processing of the an email that is using head start, will those changes be reflected—No If someone unsubscribes during the processing of the an email that is using head start, will they receive the email—Yes Can you cancel a head start program once the processing of the an email that is using head start has begun—Yes What happens to the processing data when someone cancels a program during the processing of the an email that is using head start—It is deleted (I.e. Program membership, etc.)  
View full article
Issue You send a sample email to test the tokens in a Calendar (.ics) file, and the tokens are not populating. Create a Calendar Event (.ics) File     Solution Tokens in an .ics file do not populate for sample emails.  Send the email to a test lead via 'Send Email' Run Action in the Database instead or via a smart campaign.
View full article
Issue You receive the "Subject is empty" error when attempting to approve an email which contains an emoji character in the subject line, and elsewhere in the email, emojis may fail to render. Solution Marketo can render any Unicode character up to 5.2 and any ASCII character, but this does not encompass emojis. The Marketo email editor will strip out any unsupported symbols. This is because we cannot guarantee the consistency of their appearance across platforms, as not all clients can render all emoji. Marketo only supports the text symbols that are generally then converted into emoji's by the recipient client or operating system. The basic symbols in a list such as https://www.copypastecharacter.com/symbols should work, as they are ASCII characters and not reliant on extra encoding. These are a set of accepted text symbols that will universally work on all clients and many will convert them to emoji. Just highlight the symbol from  https://www.copypastecharacter.com/symbols, copy and paste it into your email. Alternately, you can work around this by q-encoding the emoji in UTF-8 format, which will render a string of code to add to your subject line. This code tells the email client to render the desired emoji. All you need to do is copy your desired emoji and run it through a Unicode to UTF-8 translation tool, such as https://onlinetools.com/unicode/convert-unicode-to-utf8. As an example, say you want to send a Happy Birthday email to a lead. You could copy the  (birthday cake) emoji and run it through a translator to yield the code "=?utf-8?Q?=F0=9F=8E=82?=" Entering this code in your subject line without the quotation marks will render the emoji on the client's end, and render it in the design most compatible with their device/browser. With any email design, it's always important to test before a live send to confirm it appears the way that you expect it to.
View full article
Issue An email program with "Send in recipient time zone" was scheduled to sent out an email on Jan 8th, 2019 8:00 PM PST but you see that it was sent out to leads on Jan 8th 12:01 AM PST. Solution From the activity logs of the lead, you can observe the following: 1. Send Email activity happened on Jan 8th 12:01 AM PST. This is when Marketo issued the Send request to the server, which held the request until 8:00 PM PST, per the time zone restrictions. 2. Email Delivered happened on Jan 8th 8:00 PM PST. The MTA (message transfer agent) pushed the held emails to the receiving servers. The send email event is an indication that the lead was qualified at 12:01AM but the actual delivery of the email happened at 8:00 PM. So, the send event means the leads were processed and prepared for email delivery. The delivery event is when the email is actually sent and delivered. You will see this behavior when emails are sent with time zone restrictions. For the complete details on Recipient Time-Zone and it's working , please refer to the following Adobe experience league document :-  Schedule Email Programs with Recipient Time Zone
View full article
Issue The count for the audience of an Email blast program does not match the total members of the Email Program after it has been executed.     Environment This issue is applicable to users who have recently run an Email blast program in Marketo. Solution  The disparity in numbers occurs because the Audience Smart List is evaluated at the moment you access it. As your records evolve, this number can change after the Email Program is run. In contrast, the number of program members, who are the recipients that were emailed through the program during the scheduled run, is fixed at the point the program is executed. 
View full article
Issue Users may notice that unsubscribed or blacklisted leads still appear within the Audience section of an Email Program.  Environment This issue is relevant to all Marketo users who are managing Email Programs and observing the Audience list.  Solution Despite being blocked or blacklisted, leads will continue to be displayed in the 'People' list of a Program or Campaign's audience, as they still fit the criteria for the Smart List of that particular asset. The Audience list includes all individuals who meet this criteria.  The blocked leads do get recognized and listed under the Blocked list of that specific program. However, this Blocked list is considered a part of the broader Audience list.  If you prefer these leads to not show up in your Audience, you can modify your Smart List filters. For example, apply the "Unsubscribed is False" filter. Root Cause This situation arises because the Audience count encompasses all leads that qualify for the Smart List, including those that are blocked or blacklisted. The system recognizes and lists these blocked leads separately, but they remain as a subset of the overall Audience.
View full article
Issue: I am looking for the ID to one of my campaigns for a SOAP API project I am working on. Solution: The ID can be found in the URL of the campaign. 1.1 Log into Marketo, under Marketing Activities, find and select the campaign in question. This is a article attached image 1.2 The URL to the campaign will look something like: This is a article attached image   The Campaign ID is between "SC" and "A", in the above example it's "1150". This is a article attached image  
View full article
Technically, you cannot move records backwards in a progression status.  The only so called “backward” status that you can change the record to is a progression status of “Not In Program”; however, doing this removes them from the membership of the program.  If you do this procedure, this will allow you to re-add them with a different status.   We mentioned technically this cannot be done but logically, there is another method that allows you to juggle the record’s progression status but in a more lateral movement with what appears to be in a “backward” state.  This is all dependent on how you have your channel steps configured.  To access your channel steps, please do the following:   Choose Admin Choose Tags Click the + next to Channel Locate the channel you wish to configure and highlight it Click the drop-down menu towards the top of Tag Actions, and select Edit   You should now see a pop-up window that allows you to configure the status steps for that channel like the following example:   This is a article attached image     If you configure statuses that have the same step number, this will allow you to move the record in a lateral movement which, in a sense, is somewhat like a backward progression but it really isn't.  With the example screen capture, I can do a change in progression status of “Invited” to “Attended Show” and vice-versa because the step is with an identical number. If I wanted to change in progression status of “Invited” to “Engaged” and back, it will not work because the step value is not identical. You can reference more information about this in the Create a Program Channel article.
View full article
Issue You would like an links in an email to be tracked, but need to eliminate the tracking URL parameter on the tracked links. Solution In the Email Editor, you can uncheck "include mkt_tok" in the Edit Link box. Adding a class "mktNoTok" to any Anchor Tag will allow you to keep the Link Tracking, but disable the Tracking Token Parameter from the URL. You may also edit the Head of the email HTML to make large sections with this class.    
View full article
Issue Issue Description The user role has all the permissions to Design Studio, but whenever trying to preview an email, a limited access message is displayed: "You do not have sufficient privileges to perform this action"     Solution Issue Resolution The user role must have permission to 'Access Database'. The full access to Database is not needed, just the main access by selecting 'Access Database' and unchecking everything else underneath. The reason for this permission is that, when previewing emails, you are able to select to preview an email as a specific lead. In order for this to happen, users will need access to leads. 
View full article
Issue: My landing page is showing the wrong title, why is this and how do I fix it?   Solution: When you clone a landing page, the title of the old page carries over to the new one. In order to update the page title please see Edit Landing Page Title and Metadata for detailed instructions.
View full article
Question: How do I add a link to my lead/contact's Salesforce detail page when sending an alert from Marketo?   Answer: If the lead or contact is in both Marketo and Salesforce at the time when the alert email is sent, then the link to the Salesforce detail page will be automatically appended to the alert email sent by Marketo.   Note You will need to use the "Send Alert Info" token within your Alert email while designing your email in the Design Studio of Marketo. This is a article attached image Below is what the generated alert looks like once it is sent from Marketo (note the link to the Salesforce detail page is automatically inserted):   This is a article attached image   Note if the lead or contact is not in Salesforce then there is no link to the Salesforce detail page:   This is a article attached image
View full article
Question: I have leads that are getting created without providing information for fields which I have made required.   Answer: Marketo's field validation makes use of javascript. Most browsers have javascript enabled by default so this should be fairly rare, but a user could change their settings and turn javascript off. This would allow them to submit a form without providing all the required information.    This situation may also occur if a lead submits the first progressive profiling form and subsequently submits a second form with different questions, while also changing the email address (indicating either a different person using the same PC or the same person with two email addresses). Marketo will generate a new lead record, but it won't include the data captured in the first form. To identify if this is the case, examine the "Fills Out Form" activity and check if there is data submitted from a later progressive profile form. If so, this is likely the cause. To address this issue, follow these steps: Create a smart list with an Anonymous IP filter. Enter the anonymous IP address of the lead. The smart list may identify multiple records associated with the anonymous IP address. Merge or manually update the records as needed based on the identified information. By following these steps, you can reconcile the data and ensure that the lead records are appropriately managed.
View full article
Issue: When I try to approve an email I get the following error: Error approving Email Name - Sending IP is empty or not valid This is a article attached image Solution: You likely have multiple dedicated IPs and you did not choose which one to send this email from. 1. Edit Draft of the email in question. 2. Select which IP Address you want this email to sent from and click Save. This is a article attached image 3. Close the email editor and under Email Actions click on Approve.      
View full article
Issue Issue Description How to enable multiple selections in a picklist/select field in a Marketo form.     Solution Issue Resolution In the Field Properties, choose Field Type "Select" Edit Values to include your desired picklist options in the field Check the box for "Multiple Selections" This is a article attached image
View full article
Issue Embedded Marketo form not visible in Firefox Private Browsing mode. Solution Firefox's private mode will be enabled by default. When you embed a Marketo form in your own webpages and view it in Firefox's private mode, it will disable the Javascript as part of the tracking protection of this browser. JavaScript is needed for the forms to appear on the landing pages or webpages. The "Tracking Protection" in the Firefox browser will need to be deactivated for the form to appear. Here is an article from FireFox regarding the Tracking Protection: https://support.mozilla.org/en-US/kb/tracking-protection    
View full article
Issue Email won't be approved due to too many custom tokens Solution Sometimes when approving an email with a large number of of tokens, the following error message will appear: 'The number of custom tokens in the email exceeds the limit '   This is a article attached image   This means that you have too many custom tokens in the email and that if you wish to approve the email, you will need to remove one or more of your custom tokens in the email.    Its important to note that this only applies to custom tokens, which are tokens based on a custom field in Marketo.  This means that while you will be allowed to add more of the standard tokens to the email and approve it, you will not be allowed to go beyond the 40 custom token limit we have in place for the non-standard tokens. Here you will find all the standard tokens in Marketo
View full article
Issue Email asset does not show which template it was built on and shows the word "none" instead of the name of the template that was used to create that asset. Solution Any edit directly to the HTML code of an email will break the connection between the email and the template. Changes made to the template will no longer flow down to the email. After making those change you will see a template name of None instead of the name of a template. When editing the HTML in the email, you will see this warning message: This is a article attached image
View full article
Issue Sometimes email addresses that are CC'd can have emails bounce. This doc describes what to expect in these scenarios. Solution Sending Emails To address is valid, cc address bounces   The email will be sent to the recipient but the cc'ed recipient will not receive it (since the address is invalid).   Nothing in the Marketo UI will communicate that the email to the cc'ed address was undeliverable.   To address bounces, the cc address is valid The email to the recipient will bounce normally.  The cc'ed recipient will still receive a copy of the email.   Nothing in the email sent to the cc'ed recipient will tell them that the To: the address was undeliverable.   To address is valid, cc address is unsubscribed The email to the recipient will deliver normally.  The unsubscribed cc address will not receive the email.   Nothing in the UI will reflect that the cc'ed recipient did not receive the email because of an unsubscribe setting.  The cc'ed address will not appear in the Send Email activity under the cc'ed attribute.   Email Delivered This will not include details of the cc'ed email addresses.  There is no log item in the UI to communicate that a CC email was delivered to the recipient or bounced.   Emails in the inbox The cc'ed person will be in the cc field of the email the lead receives.  The links in the email will be tracked for the person in the To: line.  If the cc'ed person clicks the links in the email, the 'Click Link' activity will be logged on the lead in the To: address and the cc'ed recipient will be cookied by Munchkin as the person in the To: address.
View full article