Your Achievements

0% to

Next /

to gain points, level up, and earn exciting badges like the new !

View All Badges

Open Alert Bar

Knowledgebase

Featured article

(Article Updated - August 2024) Overview A blocklist is a database of IP addresses or domains that have been associated with the sending of unsolicited commercial email or spam. Internet Service Providers (ISPs) and business email networks use information from blocklists to filter out unwanted email. As a result there can be a drop to inbox delivery rates if the IPs or domains involved with sending email are listed on a blocklist. Marketo’s Email Delivery and Compliance team monitors blocklist activity on our IPs and domains daily. When an impactful listing occurs, we reach out to the blocklist, attempt to identify the sender that triggered it, and work with the blocklist organization to get the listing resolved. There are thousands of blocklists, most will not have a significant impact on your delivery rates. Below, we have compiled a list of the blocklists that commonly appear across our sender ecosystem. Each blocklist has been grouped into a top tier (Tier I) by most impactful, to the bottom least impactful tier (Tier III). These may have little to no impact across our sender network. Tier I Blocklist Spamhaus (SBL) Impact: Spamhaus is the only blocklist that we categorize as a Tier I for a reason: it has by far the greatest impact on delivery. It is the most well-respected and widely used blocklist in the world. A listing at Spamhaus will have a negative effect on your ability to deliver emails to your customer’s inbox and can cause bounce rates of over 50%. Evidence suggests that most of the top North American ISPs use Spamhaus to inform blocking decisions. How it works: Unlike many blocklists, Spamhaus lists senders manually. This means they are proactively watching sender activity, collecting data, and base listings on a number of variables. Most commonly senders are listed for mailing to spam trap addresses that Spamhaus owns. Sometimes Spamhaus will list senders based on recipient feedback as well. Next Steps: Please note that every Spamhaus email can be quite different depending on the information provided and the nature of the listing . Because Spamhaus has multiple types of listings, the remediation steps are based on which type of blocklisting has occurred. We have listed the most common types to affect Marketo customers, from most to least impactful. Impact can range from a full block of top severity, to a partial block that is less severe (CSS Data, DBL). If remediation isn’t performed and the problem not addressed, these listings can increase in severity and turn into a full blocklisting. Spamhaus Blocklistings Types SBL (full blocklisting) Considered the most impactful. Remediation steps: Our team monitors closely for Spamhaus listings. Once alerted to the listing, we send an email notifying the customer, and reach out to the Spamhaus contact to start the remediation process. Only a Marketo delivery team member should be in direct correspondence with the Spamhaus contact, to speak on behalf of the customer, and to relay their questions and instructions, ensuring quick resolution and reduced impact. Senders that trigger this listing on a shared IP range will be moved to a more isolated, penalty range (IPB), so as not to impact the other shared senders. Those affected on a Dedicated IP, only impact their own sending and will not be moved. However, depending on the severity of the issue, our team may need to revoke a customer’s ability to send any emails until full resolution. The listing will last until Spamhaus is satisfied that the offending sender has taken the appropriate steps to mitigate the problem. SBL CSS Customers are alerted of the listing with an email containing all the information needed to immediately begin the remediation process. This is part of an automated trigger listing, that allows for a customer to delist directly on the Spamhaus website, after they’ve completed remediation. Remediation steps: Customers will go to the Spamhaus IP lookup website, at https://check.spamhaus.org, where they can check on the status of their IP and continue to monitor it in real time, until it is no longer listed there. Follow the remediation and delisting instructions provided, and check for specific details in the blocklist notification email. DBL (Domain blocklisting) Customers will receive an email notification alerting of the company domain being listed. The email will contain specific information to help narrow down and identify which email source likely triggered it within Marketo. It’s important to note that any email sent from outside of Marketo, that contained the company domain, is suspect. This means, if the sender uses multiple IPs and/multiple email platforms, then any of those could be the source. Remediation steps: Follow the detailed instructions in the email, which will also provide a link to the Spamhaus Domain reputation checker webpage, to check the real time listing status of the affected domain. Once the email source is identified and cause addressed, this customer will follow the online instructions to request to be delisted. Tier II Blocklist SpamCop Impact: SpamCop is not used by any of the major North American ISPs to inform blocking decisions, but it makes it to the Tier II list because it can have a significant impact on B2B email campaigns. SpamCop is considered a Tier I one blocklist for B2B marketers but a Tier II for B2C marketers. SpamCop is a dynamic IP blocklist, that can affect a single IP or a subset of IPs Typically, the block will automatically lift within one business day, but can take longer for relisted IPs. To have triggered a SpamCop listing likely means the sender has a list management problem that should be addressed. How it works: SpamCop lists IPs for one of two reasons: Either the email hit SpamCop spam trap addresses OR A SpamCop user has reported the email unwanted. Most of SpamCop’s spam traps are previously valid addresses that have not been active for 12 months or longer. Remediation steps: If you are seeing a significant number of bouncing emails caused by a SpamCop blocked IP but aren’t sure if your email activity triggered the listing, first identify whether you are sending on a shared sender network or not. If sending from a shared IP range when this occurs, you or any other customer sending from the same network may have contributed to the IP block. This IP block will automatically get dropped within a business day. For those on a Dedicated IP that trigger a listing, refer to the above remediation steps and resources, to address the list management issue. Tier III Blocklist (Low/ No impact ) These are considered the lowest tier and therefore cause the least impact across the Marketo sender ecosystem. Some of these blocklists were more impactful at one time, while others are only impactful based on the sender region (Manitu). Others still can suddenly flare up (Lashback). There are also many blocklists that are ignored (0spam), and are not taken seriously because they do not provide any means to delist once on the list (NoSolicitado) or that they charge money to have the listing removed ( UCEPROTECT ). The pay-to-delist model is not well respected in the email industry. When using blocklist tool checkers, such as MXToolBox, many blocklists will appear, but very few are relevant. Here is our selection of Blocklists you may come across that are least impactful: Project Honey Pot SpamAssassin URIBL/SURBL DrMX PSBL 0spam HostKarma Ascams ZapBL Barracuda Trendmicro Inc. Cloudmark Proofpoint Invaluement ISP Blocklists Some ISPs use internal blocklists to make blocking decisions. Examples include AOL, Yahoo, Gmail, Outlook and Hotmail. If your IP is being blocked by one of these networks, and those networks have a large presence in your lists, a block of this kind could have a noticeable negative impact on delivery. Marketo monitors for significant ISP blocks. Those experiencing deliverability issues with emails not making it to the Inbox and bulking in the spam folder may benefit from additional services with our Email Delivery Consultants. Remediation Steps: Email Delivery Compliance Team works to resolve any ISP blocks. ISP blocks are are usually resolved or lifted within less than 24 hours of a delisting request. Customers experiencing significant blocks for Microsoft domains (outlook.com, live.com, microsoft.com), can submit a request to the delivery team to seek mitigation on their behalf. Additional Resources: Blocklist Deep Dive Abuse Report Deep Dive What is a spamtrap, or spam trap, and why does it matter? Blocklist remediation Blocklist resolution flowchart Successful lead reconfirmation What is a blocklist?

The SFDC is Deleted field can be used to identify a SFDC Lead or Contact which used to be in SFDC but was deleted and now only lives in Marketo. Typically the record is deleted from SFDC for a specific reason and most customers will honor the deletion in SFDC by also setting up a smart campaign to also delete the record from Marketo. If you decide to keep the deleted record (SFDC Lead or Contact) in Marketo to nurture it, the next time the record flows through the SYNC Person to SFDC flow step Marketo will insert it into SFDC as a new lead record. A strategy should be in place to make sure you're not syncing/inserting records you really don't want. If you decide to delete a SFDC Lead or Contact in Marketo only you should only do it if you have a custom sync rule set-up. Otherwise the next time the record is updated in SFDC it will sync again to Marketo with a new Marketo ID. Here are the steps to delete a SFDC record which is syncing to Marketo: Create Smart Campaign Set Smart List Set Flow Change Data Value of the "Sync to Marketo" field to False Wait 1 hour Delete record from Marketo only Schedule Run once Additional resources for learning about the Marketo integration with SFDC.

Issue Description The exact distinction between the "Email Bounces" and "Email Bounces Soft" filter and trigger is unclear. Issue Resolution The “Email Bounces” trigger or filter will look only at hard bounces, where Marketo received a definitive "No" from the target server. The “Email Bounces Soft” trigger or filter only looks at soft bounces, which occur when we are unable to deliver the email, but did not receive a rejection from the target server. You can use both filters with "OR" logic in order to look at all bounces.

Issue The GoToWebinar service in Admin > Launchpoint shows a Failed API Error - API Error: ERROR -> HTTP Code = '403' Solution This error occurs due to an issue with the credentials Marketo uses to access the GoToWebinar service. To fix this, you would need to re-login to the GoToWebinar service under Admin > Launchpoint. Once this is done, the error should be resolved. You should also check the program membership for the webinar programs in Marketo, since any leads who attempted to register for a webinar while the error was in effect will have a status of "Registration Error" and will need to have their status corrected to "Registered." Who This Solution Applies To Customers integrated with GoToWebinar

This is a article attached image 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: 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. This is a article attached image 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) This is a article attached image Image: Example of Populating Metadata for HTML content into Predictive Content

Issue Description Can I use Marketo Sales Insight Outlook plugin with Office 365? Issue Resolution The Marketo Sales Insight Outlook plugin is currently not supported for Office 365 Web Application. The Outlook versions it supports include: Outlook 2000 Outlook 2003 Outlook 2007 Outlook 2010 Outlook 2013 Outlook 2016 Outlook 365 Local Installation docs.marketo.com/display/public/DOCS/Install+the+Marketo+Email+Add-in+for+Outlook+with+a+Registration+Code If you would like for Marketo MSI to be supported for Office 365 Web Application, you can raise it as an idea in our community: https://nation.marketo.com/community/product_and_support/ideas Our product managers refer to these ideas for improving on existing features and implementing new features in future releases.

Issue Description Additional domains or subdomains need to be configured for Web Personalization (RTP) Issue Resolution If you want to add a new domain, check your subscription or contract to see how many additional domains are included. Your Customer Success Manager should be able to provide this information If not all entitled domains are configured in Marketo, reach out to support to add the domain(s) If all entitled domains are configured in Marketo, reach out to your Customer Success Manager to purchase more. If you wish to add a subdomain, reach out to support as additional subdomains do not incur a cost. Who This Solution Applies To Customers using Web Personalization

Issue How and where to locate Salesforce ORG ID. Solution Choose one of the following options to find your Org ID: Improved Setup User Interface (Enabled) 1. Select Setup | Company Profile | Company Information. 2. In the "Organization Detail" section, your Organization ID is listed in the "Salesforce.com Organization ID" field, starting with 00Dxxx. Improved Setup User Interface (Disabled) 1. Select <YourName> | Setup | Company Profile | Company Information. 2. In the "Organization Detail" section, your Organization ID is listed in the "Salesforce.com Organization ID" field, starting with 00Dxxx. Lightning Experience 1. Click the Gear icon, then select Setup. 2. Select Settings | Company Settings | Company Information. 3. Your Organization ID is listed in the "Salesforce.com Organization ID" field, starting with 00Dxxx

Included in this Article: Testing Campaigns by Sandboxing General Tag Checklist Check the Product Documentation: Verify the tag exists in the HTML code on your website Make sure that the right tag has been inserted properly Verify the tag is enabled Website Checklist Verify there are no jQuery or JavaScript errors Verify In Zone campaign Div IDs Segment Checklist Verify that the segment has had matches. Verify the Segment is set for the relevant domains. Verify ISP setting Verify location settings Campaign Checklist Important notes about Widget campaigns Is this article helpful ? YesNo Testing Campaigns by Sandboxing Sometimes you'll need to see what your campaign looks like live on your website without customers being able to see it. Sandboxing allows you to match a segment and see the campaign live by targeting a specific term added into the URL. Since leads won't randomly guess the value and alter the URL, it's safe to test on a live site. Here's how you do it. 1. Create a new 'Sandbox' segment and call it "Sandbox=1" Add the Included Pages filter and enter *sandbox=1* as the value for the URL matches. Add all other filters you need. When used in combination with the *sandbox=1* URL match, it will match just like your other segment you want to test, but only if you have "sandbox=1" in the URL. 2. Create a campaign called: "Sandbox=1" (or alter the campaign you're working on) to use the "Sandbox=1" segment. Verify that your campaign is set up properly, then launch the campaign. 3. Go to the webpage you're testing with. Let the page load fully. 4. Add ?sandbox=1 at the end of the URL and hit enter. 5. Verify whether the sandbox campaign is being displayed. General Tag Checklist Check the Product Documentation: Troubleshooting Web Personalization (RTP) - RTP Tag Verify the tag exists in the HTML code on your website All pages, all domains, all sub-domains and landing pages need to have the RTP tag in the code in order for it to work properly. The RTP tag can be loaded through a tag manager like Google Tag Manager, Adobe Tag Manager or Tealium Tag Manager. If the RTP tag is not directly in the HTML of the page, remove it from the tag manager and load it directly into the HTML of the page. RTP tags can be used with tag managers, but removing it and placing the tag into the HTML of the page directly will let you test whether there is a problem being introduced by the tag manager itself. Make sure that the right tag has been inserted properly Check the Deploy the RTP JavaScript - Marketo Docs - Product Docs documentation for how to locate the RTP script tag. This will show you how to actually locate and deploy the RTP script tag. If your instance has more than one domain configured, you will have access to more than one RTP tag that can be deployed. Each domain that is configured in your instance will have its own unique script tag. If you use the wrong one in the wrong place, your campaigns will not execute as planned. Verify the tag is enabled 1. Go to 'Account Settings' 2. Make sure the tag is enabled Website Checklist Verify there are no jQuery or JavaScript errors Navigate to your site and open the developer's tool Console panel. Check for any errors such as this: Verify In Zone campaign Div IDs In Zone campaigns utilize a Zone ID to identify where the RTP campaign should be inserted into the body of the page. This is the Div ID in the HTML code of you website. Verify the Div ID exists in the HTML code on the page where the campaign should be displayed. Even small differences in the Div ID will cause it to not match, resulting in the campaign not displaying. Segment Checklist Verify that the segment has had matches. When viewing you list of segments, make sure that there have actually been matches. If your segment hasn't matched any leads, there's no way the campaign can be called to action Verify the Segment is set for the relevant domains. Segments can be set to only apply to certain domains configured in your instance. If your segment is only applying to one of multiple domains you need, that would stop the segments from matching very often, and stop the the associated campaign from being called to action. Verify ISP setting When using the "Exclude ISP" filter, it's important to make sure when testing that you aren't showing up as an ISP. The network you're on plays a very big part in how you appear to the RTP system. Verify location settings If you have a location filter in use, you could be not matching the segment because the filter thinks you're coming from a different location based on your network's settings. Are you physically in the location your filter is searching for? Is your network representing the correct location? Campaign Checklist Check for target URL If the campaign is set for a specific target URL and you aren't viewing that exact page, the campaign will not display. Are there any JavaScripts in the campaign? JavaScript running inside of an RTP campaign can cause conflicts. Try removing the JavaScript and testing it. If the campaign displays as it should, then you know the JavaScript caused the issues. Important notes about Widget campaigns Widget campaigns will only show up once per session. A session lasts for 30 minutes since the last click on a tracked web page, so the session times out after 30 minutes of inactivity. To view your campaign again, clear your cookies, use an incognito mode, or use a different browser

On your Marketo landing pages, if you want to retrieve a URL parameter via Javascript, here's how to do it. First, identify the URL parameters you want to capture. We'll use Google search parameters -- "utm_keyword" "utm_campaign" "utm_term" and "__kk". Please ensure that you have access to an experienced JavaScript developer. Marketo Technical Support is not set up to assist with troubleshooting JavaScript. Below is the Javascript you'll need. Add this to your landing page with a Custom HTML element or by editing a landing page template: <script language="Javascript" src="/js/public/jquery-latest.min.js" type="text/javascript"></script> <script src="/js/public/jQueryString-2.0.2-Min.js" type="text/javascript" ></script> <script> // to set cookies. Uses noConflict just in case var $jQ = jQuery.noConflict(); var utm_keyword = $jQ.getQueryString({ ID: "utm_keyword" }); var utm_source = $jQ.getQueryString({ ID: "utm_source" }); var utm_term = $jQ.getQueryString({ ID: "utm_term" }); var __kk = $jQ.getQueryString({ ID: "__kk" }); </script>

Issue If your Smart Lists are processing slowly, you may be able to speed them up using Segmentations for exclusion lists. Solution Many companies maintain email exclusion lists based on a number of criteria. In Marketo, these are often set up using Smart Lists that are then referenced in "Member of Smart List" filters. However, Smart Lists that reference other Smart Lists can be slow to resolve. Using a Segmentation for your exclusion lists instead of Smart Lists can help your campaigns and programs run more efficiently. Instructions for setting up Segmentations can be found here: Create a Segmentatio. You can then use the Segmentation filters in your Smart List rather than the "Member of Smart List" filters: Use Segment Filters in a Smart List.

Issue You made an A/B Test within an Email Program, and now when you are in a Smart List or Smart Campaign and are attempting to set up a filter (such as Opened Email), you are unable to locate the A/B test email asset in order to select it. Solution When an A/B test is made in an Email Program, the Program must be approved in order for the email to be located by other assets (Smart Lists/Smart Campaigns.) When the Program is approved, the email asset name will be changed to whatever kind of A/B test is used, and will be available for reference in other assets. For example: [program name].Subject Line Test; or [program name].Whole Email Test

Issue A webhook that looks to be structured the same as other functioning webhooks is failing with HTTP Error 400: Bad URL request. Solution A 400 error message usually means that the request was malformed. In other words, the data stream sent by the client to the server wasn't formatted in the exact way required by the receiving service. You will need to work with the service you are trying to reach to figure out the exact cause of the error with the webhook.

Issue Issue Description How to add a seed list in a batch Smart Campaign or Email Program. Solution Issue Resolution Import the seed list addresses into an appropriately-named static list Add a filter in the Program/Campaign Smart List to include the static list. The trick will be to make sure the filter logic is correct. Advanced Logic may need to be used in the Smart List of the Program/Campaign. For example, if there's a sending campaign with 5 filters to send to an audience 1 AND 2 AND 3 AND (4 OR 5) then you will want to use Advanced Logic and put parentheses around the original filter set (1 AND 2 AND 3 AND (4 OR 5)) and add the seed list outside the parentheses with OR logic (1 AND 2 AND 3 AND (4 OR 5)) OR 6 In that advanced logic, the original intended membership (1 through 5) exist within its own set of parentheses and the Seed List is included in addition (OR 6).

This article covers advanced concepts when designing your campaign flows. You need to be familiar with Smart Campaigns before reading this article: Building smart campaigns Auto-responder Priority If you have a campaign that sends an email following a form fillout, you should make sure that theSend Email flow step comes first. You can put other flow steps after that. People who complete a form expect a quick email response. If you put the Send Email first, Marketo will assume this is an auto-responder campaign and thus needs to be prioritized higher. If you put the Send Email step later in the flow, your campaign may be prioritized lower causing the email response to be delayed. Add Choice The Add Choice option in a flow step lets you execute flow steps based on a specific condition. Say you're building a scoring campaign based on the lead's job title -- 10 points for a CEO, 8 for a VP, 6 for Director, and so on. Instead of building a separate campaign for each title, you can use Add Choice to put this in one flow step. Create a new campaign called "Job Title Scoring." In the Smart List, trigger the campaing to launch when the Job Title changes: Open the Flow tab and drag in the Change Score step. Then click the Add Choice button. This adds a "Choice 1" and "Default Choice" to the flow step. In the "If:" part of the choice, you can pick which field should be checked for what value(s). In the example below, the lead's Job Title field will be checked to see if it matches CEO. If so, the lead will get +10 points. Otherwise, the default choice will run -- no score change. Click Add Choice again to add a second choice and set it up to add 8 points if the lead has "VP" in the title. When there are multiple choices in a flow step, only the first matching choice is executed. If no choices match, the default choice will be executed. Add the remaining flow steps. Below, you can see how it might look like. If you ever want to get rid of a choice, click the red X to the right of that choice.

Issue Unable to change the email address used for a Marketo user's login. Solution All of a user's activity is based on that specific login email address. If somehow there was a way to change the login, all that history would be gone or mixed up with multiple login names and hence Marketo doesn’t allow to change the login email address. You can however, create a new user by inviting new user in the Admin area under Users & Roles with that new email address and a new login will be created that can now be used with that email address. So you can now use that new login and delete the old if you want. This login email address is different from the communication address. It is just like a user name for login purposes. All the communication/notification emails will be sent to the email address mentioned in the email column of your account and this should be a valid email address. You can check this under Admin > My Account > Email. If your instance does not have the feature allowing the login email address to be different than the email address used for communication, please contact Marketo Support to have it enabled.

Issue You're receiving an error that states 'Not Allowed - Error approving <asset-name> - {{token-name}} : Token key not found' when trying to approve an email asset. Solution Check that token syntax is correctly inserted with no missing left or right 'curly' brackets '{{' '}}' Check that the field name of the token does not have any incorrect spelling (e.g. Email Address) If the token syntax is correct and the field name of the token is spelled correctly, it is possible that the field name of the token contains a Unicode non-breaking space (e.g. between 'Email' and 'Address'). This would have been inserted if it was copied across from a platform that was encoded with Unicode (e.g. Microsoft Word) - To rectify this, delete the space in the token and re-insert it with a normal space using the spacebar on the keyboard. Once this is corrected, the email approval should work.

Issue After clicking on a link within a sent email, link gets a 404 redirect error instead of going to the expected landing page. However when clicking to that link within the Marketo Email Editor it goes to the expected landing page without error. Solution This happens when the tracking link domain name is pointing to the wrong Canonical Name (CNAME). The reason it works in the previewer is that the previewer does not use tracking links. Run a CNAME lookup on a tool like mxtoolbox.com. Take note of the Canonical Name Double check that it is the same as the "Tracking Link" found under Admin/Email/Tracking Link. If the CNAMES are not the same you will need to work with your IT team to modify them. Once this has been modified and propagates through the web (24 hours or so) tracking links should work.

Issue Leads in a GoToWebinar event program have a "registration error" status. Solution If this is affecting all new leads registering for the webinar: This is caused by Marketo losing connection with the GoToWebinar service. To resolve this Go to Admin > Launchpoint. Open the GoToWebinar service. Re-enter your GoToWebinar credentials. Once this is done, you can go back to the webinar program and change the status of the affected leads from "Registration Error" to "Registered." If this is affecting only specific leads registering for the webinar: Check the name, email, company, and job title fields for any special characters. GoToWebinar often doesn't allow special characters and will throw an error.

Issue Issue Description How to Pull Data for Program ID, similarly to Campaign ID. (Example): Pull Individual Program Activity Data, then join Data with Programs via Program ID. Solution Issue Resolution [Note]: You can not get the Program directly from the Activity Endpoint. - After one has obtained the Smart Campaign ID, they can use a seperate API Call to get the Program ID. - Within the Get Activity API Call, there will be a Campaign ID. - Once this has been obtained, one can make a Get Campaign API Call with that Campaign ID and it will return the Program ID. [Get Activity]: > Use this [Get Activity - URL] to Obtain Campaign ID. developers.marketo.com/rest-api/endpoint-reference/lead-database-endpoint-reference/#/Activities/getLeadActivitiesUsingGET [Get Campaign, with the ID]: > Use this [Get Campaign, with the ID - URL] to Obtain Program ID. developers.marketo.com/rest-api/endpoint-reference/lead-database-endpoint-reference/#!/Campaigns/getCampaignsUsingGET The Program ID is not something that is returned in an Activity Call. The above method is the quickest possible way to obtain that information. Who This Solution Applies To API Users Updated Links Activity API https://developers.marketo.com/rest-api/lead-database/activities/ Swagger: https://developers.marketo.com/rest-api/endpoint-reference/lead-database-endpoint-reference/#!/Activities/getLeadActivitiesUsingGET Get Campaign By ID https://developers.marketo.com/rest-api/assets/smart-campaigns/#by_id Swagger: https://developers.marketo.com/rest-api/endpoint-reference/asset-endpoint-reference/#!/Smart_Campaigns/getSmartCampaignByIdUsingGET

Issue Changing your primary domain can be a bit of a daunting task if you don't know where to start, this guide will walk you through the steps you will need to take to use a new domain with your Marketo instance. Solution Create your new CNAME and point that to your Marketo instance. If this new CNAME is going to be used as your primary domain, then the Domain Name in Admin > Landing Pages will need to be changed to reflect your new domain and your old domain should be added as a domain alias so any old links will be redirected to your new domain Add Additional Landing Page CNAMEs Adding a new branding domain is recommended when changing your domain. This will allow tracked links in emails add a tracking cookie when being directed to your new domain. A new CNAME will also need to be created for this and will need to point to the original tracking link for your instance. Add an Additional Branding Domain with Workspaces If you plan on signing your emails with your new domain, setting up a new SPF/DKIM record is recommended to help keep your deliverability rates as high as possible. Set up SPF and DKIM for your Email Deliverability Set up a Custom DKIM Signature

Knowledgebase

Maintaining a Directory of Leads Bouncing Emails

Top Blocklists - What You Need to Know

SFDC Sync Tip - Deleting a Synced Record in Marketo or SFDC

The Difference between “Email Bounces” and “Email Bounces Soft”

GoTo Webinar connection error 403

How Auto Content Discovery Works in Predictive Content

Marketo Sales Insight Outlook plugin compatibility with Office 365

Configuring additional domains or subdomains in Web Personalization (RTP)

How to Locate Your Salesforce ORG ID

Troubleshooting - Web Personalization (RTP) Campaigns Not Showing

Get URL Parameters via JavaScript on a Marketo Landing Page

Using Segmentations for Exclusion Lists

Unable to Select A/B Test in Smart List/Smart Campaign

Webhook Error: HTTP Error 400: Bad URL request

Adding Seed List to Smart List in Batch Campaign or Email Program

Advanced Flow

Change Login Email Address

Error Approving Email - Token Key Not Found

Link In Sent Email goes to 404 Error/Page Cannot Be Displayed

Registration error status for GoToWebinar

How to Use Campaign ID to obtain Program ID with API Calls

Changing Landing Page and Tracking Link Domain