Knowledgebase

Featured article

Included in this article Overview Data you’ll get from Email Bounces Bounce Categories Hard Bounces Soft Bounces Bounce Details Building the Directory 1. Create 6 custom fields 2. Create a Program to house everything 3. Create a Static List 4. Create two Smart Campaigns Smart Campaign One - Logging Email Bounces with Bounce Details Smart Campaign Two - Remove Leads From the List After Successful Deliveries 5. Create Custom List View Showing Bounce Details Overview Bounce activities carry details for why the email was bounced, but it’s housed within the activity log entry, not in a field on the lead record, so it’s difficult to export that data. This article will show you how to extract that information to create a directory of leads bouncing emails and how to make the list automatically update. This will also create counters for bounces and successful re-deliveries after bounces happen. Data you’ll get from Email Bounces Bounce Categories Email bounces come in different types depending on why the email was bounced; Hard Bounces or Soft Bounces. Hard Bounces Hard Bounces come in two types, Category 1 and Category 2. Category 1 bounces are emails that have been marked as spam by the recipient mail server. Many email servers monitor blacklists or spam traps, so after de-listing with them, leads that have had a Category 1 bounce previously may be able to receive emails again. Category 2 bounces occur due to an email address that is invalid or doesn’t exist. Soft Bounces Soft Bounces come in three different types, Categories 3, 4 or 9. Category 3 bounces are usually temporary, caused by full mailboxes, timeouts, or throttling. Any email with this designation has been retried for up to 24 hours (36 for AOL). Category 4 bounces are caused by technical problems, Transient Failures, Admin Failures, DNS Failures. Any email with this designation has been retried for up to 24 hours (36 for AOL). Category 9 bounces are unknown, undetermined or gibberish details. Any email with this designation has been retried for up to 24 hours (36 for AOL). Bounce Details When an email is bounced, the recipient mail server includes details of why it was bounced. These are created by the admin of the recipient mail server and vary greatly, but most will give some explanation that can give valuable information. Email Bounce Codes Building the Directory 1. Create 6 custom fields You’ll need 6 custom fields, two DateTime fields, two Score fields, and two String fields Name the DateTime fields “Bounce Date” and “Email Delivered After Bounce”. Name the Score fields “Email Bounces” and “Deliveries After Bounces” Name the String fields “Email Bounce Details” and “Email Bounce Category” Directions for creating Custom Fields can be found here: Create a Custom Field in Marketo 2. Create a Program to house everything Use a default program type and name it "Directory of Leads Bouncing Emails". Info on creating programs can be found here: Create a Program 3. Create a Static List This static list will be your actual directory that contains all of the leads that are currently bouncing emails. Name it "Active Bounce List". Info on creating a static list can be found here: Create a Static List 4. Create two Smart Campaigns These two Smart Campaigns are what will be used to add and remove leads from your active bounce list. Info on creating Smart Campaigns can be found here: Create a New Smart Campaign Smart Campaign One - Logging Email Bounces with Bounce Details Your first Smart Campaign will be used to listen for any email bounces that occur. The campaign will populate the “Bounce Date”, “Email Bounce Category” and “Email Bounce Details” fields. It will then add one point to the “Email Bounces” score field which can be used to count how many bounces have occurred per lead. Lastly, the campaign will add the lead to the static list which will be an active directory of leads who are bouncing emails. Campaign Smart List Use the two triggers of “Email Bounces” and “Email Bounces Soft” in the Smart List. Set both triggers to “is any” so that they will fire whenever any email bounces for any reason. Campaign Flow The Flow of the campaign will have 5 flow steps. The flow will use a System Token and some Trigger Tokens, which can be used to pull details out of the action that activated the trigger. In this case, the Trigger Tokens will be pulling out the details on why the emails were bounced. That info is in the bounce message and is logged in the lead's activity log. Normally you'd have to comb through the activity log one at a time to find these details for each individual lead. This method, however, will pull the details out automatically for all leads. Flow Step 1: Change Data Value Attribute: “Bounce Date” New Value: {{system.dateTime}} Flow Step 2: Change Data Value. Attribute: “Email Bounce Category” New Value: {{trigger.category}} Flow Step 3: Change Data Value Attribute: “Email Bounce Details” New Value: {{trigger.details}} Flow Step 4: Change Score Score Name: “Email Bounces” Change: +1 Flow Step 5: Add to List List Name: “Active Bounce List” Smart Campaign Two - Remove Leads From the List After Successful Deliveries Campaign Smart List The Smart List of the campaign will need a trigger for “Email is Delivered” set to “is any” and also a filter of “Member of List” looking just for leads that belong to your Static List. This way, the campaign will only apply to leads who have had an email bounce but have then had an email successfully delivered afterwards. Campaign Flow The Flow of the campaign will have 3 flow steps to do the following; log when the email was delivered, add a point to the "Deliveries After Bounce" Score Field, and remove the lead from the "Active Bounce List". Flow Step 1: Change Data Value Attribute: “Email Delivered After Bounce” New Value: {{system.dateTime}} Flow Step 2: Change Score Score Name: “Deliveries After Bounces” Change: +1 Flow Step 3: Remove from List List Name: Operational.Active Bounce List 5. Create Custom List View Showing Bounce Details The custom fields you’ve created for email bounce information won’t show automatically in the view of your list. You can create a new view of the list to show just this information so that when it is exported it will give you only the email bounce information you need. Once the list has the necessary details, it can be exported with those columns included so that you can work with it. You can identify emerging trends and issues with your deliverability by looking for common themes among the bounce details. Directions for creating Custom Views can be found here

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?

Issue You have two SFDC picklist fields mapped to one Marketo field but it isn't showing all picklist values for both SFDC fields. Solution When two SFDC picklist fields are mapped to one field in Marketo, the only values that will show in Marketo will be the values that exist in both picklists. Review the picklist values in Salesforce and add any missing values to the picklists so that they match exactly. This could happen in situations where the field in Marketo is mapped to a SFDC picklist field on leads as well as a SFDC field on contact/account.

Issue You need to know if Salesforce Group Edition is compatible with Marketo. Solution Having a look at the comparison between the Group Edition and Professional Edition: https://developer.salesforce.com/docs/atlas.en-us.packagingGuide.meta/packagingGuide/dev_package_features_pe_ge.htm We can see that a lot of features from the Professional Edition have been stripped in the Group Edition, mainly the removal of Workflows, Campaigns and Custom profiles. These will most likely hinder how the Marketo CRM Connector operates. The minimum would to be to have the Professional edition when syncing a native Salesforce CRM as per our Documentation on Sync Setup. https://docs.marketo.com/display/public/DOCS/Setup

Issue You have recently added a new field to a SFDC Custom Object which is synced to Marketo, but you do not see that new field available on the object in Marketo. Solution To have the new fields pulled over to Marketo, disable your SFDC global sync within Marketo and then refresh schema for custom objects. This should pull over the new fields on that custom object to Marketo. Once the schema is refreshed, please make sure that the global sync is turned back on. We would also suggest that you refer the below document which will guide you on the above steps. However, the below document is meant for first custom object sync. The same steps need to follow up for the existing object sync as well. SFDC Sync: Custom Object Sync

Issue You have been utilizing the default tracking links to send Emails to leads in Marketo and decide to change the default tracking link to your own branding tracking. When you do so, this breaks the links in emails you have already sent. Solution The branding tracking link should be one of the first steps that the customer(s) need to do when they obtain their instances. If you decided to change the default tracking link to a branded tracking link after utilizing them in emails, you should be prepared in advance that any email sent prior to the change will generate the 404 Error. We recommend not sending any emails within a week or two of the change so that an email sent on Monday is then broken on Tuesday.

Issue What happens if you log off (close) Marketo when importing a large amount of data through list import? Will it be processed or resume when you log back in? Solution It will keep running if you log off. Next time when you have a large list to import, we would recommend sending a notification to yourself. There is a little box you can put your email address in right when you start the import, it will email you when the import is done.

Issue What is the typical sync interval timing? Is there a timing difference between updates and inserts? If the change originates in SFDC vs MKTO? Solution By default the sync interval in Marketo is set to 5 minutes. This can be set to be greater than 5 minutes on request. Now this doesn't mean that Marketo will sync updates every 5 minutes, it means that there will be approximately a 5 minute wait after one sync cycle finishes and and the next sync cycle begins. The duration that an individual sync cycle will take depends on how many records for each object need to be updated/created. Remember flow actions in smart campaigns are immediate, so if you ever don't want to wait for the background sync for a specific lead or set of leads then you could always run an intimidate flow action, just bear in mind that flow actions use 1 API call per lead record whereas the background sync is much more efficient and can handle 200 records with just one API call.

Issue Sometimes, you may receive an auto response from an email that has been sent through a batch campaign. The auto response email will not show the lead's email address instead it does contain the HTML of the email along with the Marketo decorated link. Is there a way to decipher this to determine which lead record this corresponds to? Solution You could try opening a new browser window and either clear your cookies first or use the browser's private browsing feature (makes a cookie sandbox) so you don't confuse Marketo and tie that person's lead to you by accident. Anyways, in your cookie-free browser, click the link and then go to a form that Marketo prefills for you and you may see the email address that was originally targeted.

Issue Leads with the same first and last name are not showing up in the Possible Duplicates list. Solution For leads to be in Possible Duplicates, they need to have the same email address which is the unique identifier in Marketo. This is the only matching that Marketo does. If the first and last name are the same and one is missing the email address or has a different email address, Marketo will not recognize this as a duplicate.

Issue Visit Web Page activity is tracked and showing up for one subdomain on your site, example.marketo.co, on a record but it is not recording activities for a different subdomain, pages.marketo.co. Solution The reason that this behavior is taking place is because the domain that is being utilized has a two letter top level domain "example.co". For domains that end with a two letter suffix, “example.co”, the Munchkin script is setting the tracking cookie to the third domain level by default. This is to take into account two letter country codes such as “.jp”, “.us”, “.cn”, and “.uk”. This means that when someone visits “info.example.co”, the Munchkin script will assign a new cookie to “info.example.co” instead of “example.co”. When someone visits or is referred to a different subdomain, such as "pages.example.co” it will create a new cookie for this domain “pages.example.co”. To prevent this from taking place you will need to add the Munchkin Initialization Parameter setting the “domainLevel” to “2”. This will cause the cookie to be set to the second domain level “example.co” when visiting either the Marketo or non-Marketo hosted landing pages. Details about the Munchkin Initialization Parameters can be found in this Developers Doc: http://developers.marketo.com/javascript-api/lead-tracking/configuration/#domainlevel_property Since the Marketo hosted landing pages will, by default, use the same 3 third level domain behavior, you will need to disable tracking at your template level using the steps at the end of this article: http://docs.marketo.com/display/public/DOCS/Create+a+Free-form+Landing+Page+Template This will disable the default tracking that all landing pages get in Marketo. Then, similar to external landing pages, your team will need to add the Munchkin tracking code to your Marketo templates, where you would have control to set the domain level to 2 (instead of 3). Once this has been updated on both the external landing pages and Marketo hosted landing pages, the tracking cookies will be set at the second domain level and work across the various sub-domains. Who This Solution Applies To Customers with two letter domains

Issue When editing a form, a field called 'x' is visible. However, when previewing the form, the field is not visible. Solution The reason why the field 'x' in the form edit mode was not visible when previewing the form because the form that was being previewed was the approved version which did not contain the field 'x'. The field 'x' was in the draft version of the form, which needed to be approved in order to see it in the preview of the approved version of the form.

Issue You have developed a Marketo landing page and enabled Personalized URLs (PURLs) for your records but when people visit the PURL, form pre-fill does not take place. Solution When a person visits a PURL landing page, the form pre-fill checks their Munchkin tracking cookie to identify what values to populate for the form fields. If that person has a Munchkin tracking cookie associated to a known record in the database, it will pull and populate the information from that record. However, if this is the first time this person has visited a Munchkin tracked page or their browser is tied to an anonymous record, the pre-fill will not populate any information into the form. The customer/prospect will need to fill out a form or click on a tracked link in an email sent from Marketo. This will allow future PURLs that people visit going forward will have pre-fill populate as their cookie will be tied to a known record in the database. The web page visit will be associated back to the know record for the PURL. Additionally, you can also use Person related tokens on the landing page and those will resolve. For examples having the token in the text that states {{lead.First Name:default=Default}} within the body of the landing page will populate with the expected persons first name for the PURL they visited. This is because the token generation goes through a different path on the back end for PURLs.

1. Navigate to https://status.adobe.com 2. Click Manage Subscriptions 3. Sign in using your Adobe credentials or click Create an Account to log in 4. Click Create Subscriptions 5. Under Experience Cloud, click on Adobe Marketo Engage to expand: 6. Select Product Offerings or Services and click Continue Prior to selecting a regional location(s), you will want to identify what data center and pod/server your instance is located in. You can access this information from the Adobe Marketo Engage Admin tab. After clicking on this tab from the menu at the top of the page, select My Account on the left rail: Scroll down to the Support Information section to see the data center and pod in which your instance is located: The example above indicates that this instance is in our Ashburn data center on pod 38. This user would select the regional location Marketo Ashburn, and then pod AB38, as shown below. The abbreviations for all of our data centers are as follows: ab = Ashburn sj = San Jose sn = Sydney lon = London nld = Amsterdam NOTE: This method can also be used to identify what Real Time Personalization (RTP) pod/server your instance is in. 7. Select regional location(s) and event type(s): Major Service Issues indicate service unavailability or severe performance degradation for multiple users on production systems. Minor Service Issues indicate partial service unavailability or moderate performance degradation for multiple users on production systems. 8. Select the environment(s) you would like to subscribe to and click Continue 9. Review your subscription preferences and click Confirm preferences

Issue General recommendations for managing and improving deliverability to China. Solution If you are looking for general recommendations around delivering to China, here are some resources both from our Community and external sources. Navigating email delivery into China Golden Shield Project overview Sampi China Email Marketing and Chinese Anti-Spam Laws Summary English language version of the Measures for Administration of Email Service on Internet Lehman, Lee & Xu English language version of the Measures for the Administration of Internet E-mail Services 2006

Issue You are using choices within flow steps with parameters such as "Member of Program" and the lead is qualifying for the choice when they are not part of the program. Solution When using a flow step for a campaign, you have the option of adding "choices" to the flow step so different leads can have different interactions. When using a choice parameter such as "Member of Engagement Program" or "Program Status". If the lead has been part of ANY engagement program, or has EVER had a program status equal to the parameter (i.e program status is email > sent), then the lead will qualify for that step. To prevent outside leads from being pulled in, use the "Member of Program" filter in your campaign Smart List to make sure content is delivered to your intended audience.

Issue Attempting to push a custom audience to Facebook results in a Facebook Authorization Error visible in Notifications. Some custom audiences can be pushed and it appears to be only affecting a certain Ad account. Solution Issue Resolution 1.) Check if the Custom Audience Terms (facebook.com/legal/terms/customaudienc) have been accepted 2.) Log in as the user used in the Facebook Custom Audience service in Marketo and check in Audience Manager to see if there are any custom audiences that have the "Accept Terms" button pop-up similar to this screenshot. 3.) As per our recent release notes at docs.marketo.com/display/public/DOCS/Release+Notes%3A+Winter+%2719: "Facebook now requires a Business Manager account in order to leverage your Custom Audience integration. Your Facebook LaunchPoint service must be associated with a Business Manager account or your integration will no longer work after January 14, 2019. To set up a Business Manager account, please refer to Facebook Help." 4.) Check if the user used in the Facebook Custom Audience service in Marketo is a Business Manager account 5.) After completing the checks above, try to push a custom audience again to the affected ad account. If unsuccessful, recreate the Facebook service and test to push a custom audience from there.

Issue You are trying to configure Marketo and Okta for SSO, but encounter errors. Solution 1. Log in to Okta and go to the admin section. 2. Click "add applications" then "create new app" (Do not use the community sourced Marketo app) 3. For platform select "web" and for signon method select "SAML 2.0" 4. Name the app "Marketo" (or any name you prefer) and upload the Marketo logo you would like to see displayed on the login tile, then click next 5. In "SAML Setttings" for the Single sign on URL you will want: login.marketo.com/saml/assertion/<YOURMUNCHKINHERE> . For the Audience URI you will want: saml.marketo.com/sp Default Relay State can be left blank. For Name ID format select "email" or "emailAddress" and for application username you will want to select email (Be sure that your Okta user email matches what is in the login field for your Marketo user within Admin > Users & Roles). Leave attribute statements unused. 6. Select finish and you should be brought to a page where you can select either "view setup instructions or identity provider metadata". 7. One of those links mentioned in the last step will take you to a page where you can retrieve the issuer ID which will be put in the Marketo settings (under both Issuer ID and Entity ID) as well as the certificate you will need to download and then upload into your Marketo SSO configuration. 8. Once you have set the issuer id, entity id, and certificate as described above, confirm that your Marketo User ID Location is set to Subject and then enable SSO. When you hit "save" in the SAML settings window in Marketo, the popup may not close, but your settings are retained and the window can be closed (if you would like to confirm it was saved, you can reload the page and will see the new saved settings) 9. When you first setup SSO it is preferable to have all the SSO users available to confirm there are no issues with a particular user in an otherwise operational SSO configuration. However, if SSO works for one user, then the overall configuration is set correctly. Disclaimer: Marketo Support does not support 3rd party products, and cannot configure an SSO Identity Provider on your behalf. This document exists to aid users in configuring SSO, however, no guarantees are made that these setup steps will work. Who This Solution Applies To Okta Users, SSO users

Issue Issue Description Occasionally, one leads information may be shown when the form has pre-fill enabled. There are specific circumstances where this is possible, and it is most common during testing. These articles outline the scenarios: Why am I seeing someone else's information pre-filled in my form? Troubleshooting Pre-Fill Forms However, what if the information in the form is submitting to the original lead whose information was shown on the form? Solution Issue Resolution Since the information originally shown in the form was from a cookie, Marketo assumes this is a known record. If no email address is included on the form (this is a bad idea), the data entered into the form will be submitted to the original record shown because there is not an email address to deduplicate against. The solution is to ensure there is an email address on the form. This also prevents leads who are unknown from filling out the form and creating a record in your database with no email address.

Knowledgebase

Maintaining a Directory of Leads Bouncing Emails

Top Blocklists - What You Need to Know

Two SFDC Picklist Fields Mapped to One Marketo Field Aren’t Showing All Picklist Values in Marketo

Email URL Is Defaulting to the Fallback Page

Salesforce Group Edition Compatibility

New Fields Created on SFDC Custom Object Not Found in Marketo

Smart List Subscription “Download Report”

Changing the Default Tracking Links to a Branded Tracking Link

Log off (Close) Marketo While Importing a List

SFDC Sync Intervals

Determine Lead Record Using a Decorated Email Link

Duplicate Name Leads Not Showing Up in the “Possible Duplicates” Smart List

Tracking Two-Letter Top Level Domain

Field in Form Edit Mode Not Visible in Form Preview

Personalized URLs Are Not Working for Form Pre-fill

How to Subscribe to Status Page Notifications

Deliverability to China - Resources

Flow Step Choices Qualifying Leads who are Members of Other Programs

Facebook Authorization Error - Custom Audience

Setting Up Marketo SSO with Okta

Email server used when sending Tout Emails from Salesforce

Form Pre-Fill Writes One Lead's Info to Another Lead's Record