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

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 When trying to sync a lead to SFDC, it fails with an error message "_createSObjects failed - AgreementTaskTrigger: execution of BeforeInsert caused by: System.NoAccessException: Script-thrown exception ()" Solution Your Salesforce instance has a custom SFDC trigger that fires when you create a lead in SFDC (in the example, the trigger is named "AgreementTaskTrigger") but the trigger was not able to execute, so the sync failed. To investigate this, you will have to set up a debug log on the Marketo sync user in SFDC and have your SFDC admin look into the details. If you disable the trigger in SFDC, the sync will work without an issue.

Issue When you use the "Add to SFDC Campaign" flow step, and the lead isn't already in SFDC, this step will sync the lead to SFDC, and you want to know which assignment rules will be applied. Solution The SFDC auto-assignment rule will be used. To explain this further, if for some reason you don't have lead assignment rules firing properly in Salesforce, it will be assigned to what is called the "Default Lead Owner" in Salesforce. It's not just "Add to Salesforce Campaign" that uses what is called "implied Salesforce actions". All of the following flow steps will sync the lead to Salesforce first before running the flow step if the person is not already synced to Salesforce: Add to Salesforce Campaign Change Status in Salesforce Campaign (this will sync them AND add them to the campaign first) Change Owner Convert Person Create Task

Issue Change Lead Owner reason shows "Synched from salesforce.com - fixup Lead Owner." Solution The "synched from salesforce.com fixup lead owner" activity means the lead owner was switched within SFDC, often times through auto-assignment rules. The phrase "fixup Lead Owner" is what Marketo records when it is taking the Owner ID being passed from Salesforce and translating it into the Lead Owner values (First Name, Last Name, Email Address, etc) to populate into Marketo.

Issue You receive the following error: "Ouch! 500 Error Something went wrong. We monitor this sort of thing, but if you are an authorized support contact, you should create a support ticket." Solution This can happen because of temporary network issues. Try out the following troubleshooting steps. 1. Clear Browser Cache 2. Try a different browser 3. Try a different device 4. Try a different internet connect (Hotspot/Tether from mobile) If you still have any issue after trying all these steps, please contact Marketo Support for further assistance.

Issue When a lead fills out the form in Marketo, SFDC sync for the new lead fails with an error "Duplicates_Detected." Solution This error, "Failed: DUPLICATES_DETECTED: Use one of these records?" is a message Salesforce is sending back to Marketo, rejecting the attempt to sync the record. This means there's a setting in SFDC preventing duplicates from being created, possibly due to a custom deduplication rule on the SFDC side. Recommended steps : Check the dedupe settings and check for these leads in SFDC based on the things other than the email address like first name, last name etc. You may need to work with your SFDC admin to determine why Salesforce rejecting the record as duplicate.

Issue You want to add multiple values to a Smart List filter as described here: https://docs.marketo.com/display/public/DOCS/Add+Multiple+Values+to+a+Smart+List+Filter . However, when you go to do so for a field that has a type of "Text" you are not able to add multiple values. Solution This is expected behavior for Marketo Text fields. As a workaround, you can add the same filter to the Smart List multiple times, one for each value you want included.

Issue When using the "Sync to Salesforce" flow step and setting up choices, selecting "Do Nothing" uses the Auto-Assignment Rules in Salesforce. Solution This is expected. For this flow step, the choices are basically asking whether the record should be assigned to a specific person or not. When it is not specified (i.e., "Do nothing") the assumption is that you still want the record to be synced to Salesforce, otherwise they would not be in that step, but that there's no particular desire to assign it to a specific person. Thus, since SFDC records need someone to be the owner, the Auto-Assign rules are used by default

Issue You are setting times using natural language inputs, but are wondering: if I set a constraint of "in past 2 days", will that looks at the last 48 hours or will it look at the last two calendar days from Midnight-Midnight based on the timezone specified in my instance? Solution Using a constraint that is looking "in past 2 days" will look at the last 48 hours, if it was set as "in past 3 days" it would look at the last 72 hours, etc.

Issue Issue Description Marketo will allow you created a new asset in the shared folder and the new asset will show in the parent folder. However, when you try to make changes the new email or landing page, Marketo will give you an error saying that you have insufficient privilege. Note: Folders that are shared will have a little padlock on them to show that they are shared. Solution Issue Resolution The reason why you are getting this error message is because shared folders are read-only. Since they are read-only, all users (including Admin users) will get the error message of insufficient privilege. If you want to make changes to the new assets, you will need to edit them in the parent folder. The parent folder will have a green arrow pointing up.

Issue Importing programs from one Marketo instance to another doesn't bring program membership with the program Solution There is not a direct way to import the program membership. However this can still be identified by exporting the original program membership from the first instance to a CSV file. This file can then be imported to a static list in the new instance to identify these records.Then the records can be processed either manually or by batch campaign to update the campaign membership status.

Issue Marketo is giving an "SPF Configuration Error" despite the sending domain SPF record being set properly using an "include:". Solution SPF records have a limit of 10 look-ups that can be included in the record, so if your Marketo sending domain is also used to send emails from several other systems, your IT team may need to use an "include:" mechanism in the record in order to make sure that Marketo's sending IPs are included. The tool in Marketo that verifies that your SPF record is configured properly is not able to follow such an "include:", so you will get a notification in your instance that states "SPF information for {your sending domain} is not configured correctly in the domain's DNS record". For example, if your SPF record was set up as: "v=spf1 include:spf.protection.outlook.com include:_spf.salesforce.com include:amazonses.com include:mktomail.com ~all" All the references in the SPF record are "include:" mechanisms that reference the other companies sending IPs: spf.protection.outlook.com contains "v=spf1 ip4:207.46.101.128/26 ip4:207.46.100.0/24 ip4:207.46.163.0/24 ip4:65.55.169.0/24 ip4:157.56.110.0/23 ip4:157.55.234.0/24 ip4:213.199.154.0/24 ip4:213.199.180.0/24 include:spfa.protection.outlook.com -all" _spf.salesforce.com contains "v=spf1 ip4:85.222.130.192/26 ip4:85.222.138.192/26 ip4:96.43.144.0/20 ip4:136.146.128.64/27 ip4:136.146.208.0/21 ip4:136.147.32.0/19 ip4:182.50.78.64/28 exists:%{i}._spf.mta.salesforce.com -all" amazonses.com contains "v=spf1 ip4:199.255.192.0/22 ip4:199.127.232.0/22 ip4:54.240.0.0/18 -all" mktomail.com comtains "v=spf1 ip4:199.15.212.0/22 ip4:72.3.185.0/24 ip4:72.32.154.0/24 ip4:72.32.217.0/24 ip4:72.32.243.0/24 ip4:94.236.119.0/26 ip4:37.188.97.188/32 ip4:185.28.196.0/22 ip4:192.28.128.0/18 ip4:103.237.104.0/22 ip6:2a04:35c0::/29 ~all" In this situation, all of the required sending IP addresses are included in the SPF record, and recipient mail servers are able to follow that "include:" mechanism and verify it properly, but the tool in Marketo would still give an error due. To determine whether the error is indicating that something is wrong with the record, or if it is simply due to the limitations of the tool in Marketo, you can use one of these third-party tools, once the SPF record is published, to make sure that the record resolves properly using any of the IP addresses that are included.: SPF Query Tool vamsoft.com/support/tools/spf-policy-tester These tools will then process the full SPF record and let you know with a "Pass" response if the "include:" mechanism is working properly. Other Resources: Common SPF Errors & Fixes Quick Tip: Don't over include: in your SPF

Issue Issue Description Changes made to an email template are not reflected on the email assets (that are using the template in question) after approving the draft for those emails. Solution Issue Resolution To find out why the changes are not reflected, follow the steps below: Go to the email template in question. Check if the HTML elements that have changed have the class of mktoModule, mktoEditable, mktoContainer, or any other mkto related class name. Disassociate the HTML element(s) in questions from the class above. Note: These steps will require an complete overhaul on the email template's code base, because the relationships between elements would change. This type of change will require assistance from a developer/engineer who is experienced with HTML and CSS.

Issue A form submission occurs with missing or no information provided, including required fields like email address or first/last name. Solution When you notice a record submitted a form without the required information, like email address, there can be one of two likely causes: This is a bot. A bot can circumnavigate any required fields, even hidden ones, because they are not loading the necessary Javascript on the form to enforce these rules. Therefore, they can fill out a form with no values. This is a person with Javascript disabled in their browser. This would create a similar situation as the first point, meaning they can choose to fill out whichever fields they want, or none at all, because the script that enforces which fields must be filled out is not loaded.

Issue The activity log is not recording the Open Email activity for an email send. Solution Issue Resolution Email opens are linked to an individual asset. If a record is sent the same email more than once, only the first open activity will be recorded. If you are not seeing opens record for a record, search the activity history to confirm whether or not the asset has been opened previously. Also, Text-Only emails lack the tracking pixel used to determine whether an email is opened, so Text-Only emails will never show opens in the activity log. In Email Performance Reports, Opens will be backfilled by the report's internal logic if the customer clicks a link in the Text-Only email. Otherwise, opens will not be recorded.

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

Issue After an email send, the number of emails sent is much lower than the number of people that qualified for the email. Solution Issue Resolution One possible reason you are seeing a different number of emails sent versus the number of people that qualified for that is email is because of communication limits. If a person qualifies for an email, Marketo will try to send it. However, if a lead has already reached their daily or weekly communication limit, Marketo will not send the email (with the exemption of operational emails). To check to see if a lead did not get an email due to communication limits, follow the steps at Email Program Fails to Send Emails.

Issue You are unable to archive or delete an asset in Marketo. When you try to do so, you get an error: "The following assets are in use or used by other assets." Solution To archive or delete the asset, you will need to determine where it is being used. Click the Used By tab for the asset you are trying to delete and see what other assets reference it in some way. For instance, aSmart Campaign may be using it in the Smart List or the Flow Steps, or a report might have it in the Smart List. Once you find where your asset is being used, you can go and remove references to it from the other assets. This should allow you to delete or archive it.

Issue A lead/person completes an action that should trigger a Smart Campaign located in a Workspace, but the campaign does not trigger. Solution If you have Workspaces and Partitions set up on your instance, some leads may not be available to some campaigns, due to workspace and partition restrictions. When a workspace only has access to certain lead partitions, leads in other partitions are unable to trigger campaigns in that workspace. So if Workspace 1 has access to Partitions A and B, leads in Partition C cannot be included in any campaigns for Workspace 1. To resolve this issue, you would need to change the restrictions that are preventing the leads from being able to trigger campaigns in a particular workspace. These can be changed by going to Admin > Workspaces & Partitions > Edit Workspace (with the appropriate workspace selected). Whether it makes sense to make this change should be reviewed first. Often workspaces are setup to be specific to regions, so check whether it makes sense from a business point of view for leads in a partition to qualify for campaigns in a certain workspace. It may not be desired, and instead it should be checked whether the lead should be in fact in a different partition. Who This Solution Applies To Customers who have Workspaces & Partitions set up in their instance.

Issue You want to change the description of an email template after the template has been created. Solution To update the email template description, follow these steps: Go to Design Studio > Emails > Templates. Click the name of the template. Hover your mouse cursor over the name of the template. When a pencil appears beside it, click the name of the template to change it to an editable field. Write in the desired name of the template. Click the Save button.

Issue You have the Munchkin tracking code on your non-Marketo web page but visits to the page are not being tracked. Solution If you have customized the Munchkin tracking code, it may not work. Marketo only supports the Munchkin code as it is provided in your instance. If you need to alter the code, you would need to work with your web developer to determine why the customized code is not working. To find the supported Munchkin tracking code: Go to Admin > Munchkin. Select the version of Munchkin you intend to use. Place the Munchkin code on your page as outlined in our document on adding Munchkin tracking to your site.

Knowledgebase

Maintaining a Directory of Leads Bouncing Emails

Top Blocklists - What You Need to Know

Marketo - SFDC sync error _createSObjects failed

Assignment Rules used for Add to SFDC Campaign Flow Steps

Change Lead Owner Activity Shows Reason Synched from salesforce.com - fixup Lead Owner

Troubleshooting Ouch! 500 Error

SFDC Sync Error : Failed: DUPLICATES_DETECTED: Use one of these records?

Adding Multiple Values to a Smart List Filter Using a "Text" Type Field

Sync to Salesforce Flow Step Choice of Do Nothing Uses Auto-Assign

In Past X Days in Campaign Filters and Steps

Can’t Edit a New Asset Created in a Shared Folder

Importing Program Status from One Marketo Instance to Another

“SPF Configuration Error” Notification on Redirected SPF Record

How to Roll Out Changes from Email Template Edits

Form Submission Has No Fields Filled In

Email Opens Not Showing in Activity Log

Email Asset Shows Template “None” Instead of an Actual Name

Seeing a Lower Number of Emails Sent Than People That Qualified for a Campaign or Email Program

Unable to Archive or Delete: “The Following Assets Are in Use or Used by Other Assets”

Lead/Person Fails to Trigger Smart Campaign Located in a Specific Workspace

Change the Description of Email Template

Munchkin Not Tracking Page Visits to Non-Marketo Page