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

Issue After creating an Email Program with an A/B test, you create smart lists (or smart campaigns) and would like to use filters such as "Opened Email" for the A/B test email. When starting to type the A/B test email name into the smart list filter, the A/B test email name does not show as available to select (it may show a red squiggly line). Solution The Email Program (with the A/B test) needs to be in "Approved" status before the A/B test email assets can be entered into a smart list filter.

Issue: You create Marketo campaigns but they are not showing up in Sales Insight in Salesforce. The steps below illustrates all the steps that are required to make these campaigns show in Sales Insight. Resolution: 1. Make sure the trigger campaign in Marketo that you want to access through Sales Insight is using the "Campaign is Requested" trigger with a source of "Sales Insight" This is a article attached image 2. Activate the campaign you created in Step 1 above from the "Schedule" tab of your campaign. This is very important. If the campaign not activated, it will never show up in Sales Insight.

The Marketo users at your organization have created several special campaigns for your leads and contacts. Typical examples include sending someone a whitepaper about a new product or mailing a series of nurturing emails for people not ready for sales. To add a lead or contact to one of these campaigns, go to that person's detail page and find the Actions menu in the Marketo Sales Insight section. Pick Add to Marketo Campaign and click Go: You can also select leads in your list and search views if you've added the Add to Marketo Campaign button to those views. You can add 200 leads at once this way: After picking the leads, you'll see a list of potential campaigns; below the selected campaign is a brief description provided by your marketing team. Pick the campaign for this person in the Campaign Name pulldown, then click Finish:

Issue Issue Description When using a Velocity scripted my.token, the default value is not being used if the field the Velocity script is pointing to is not populated. Solution Issue Resolution The reason for this is because Velocity script isn't designed to consider a default value the way that a lead token would. It's designed to execute the code to provide the rendered value. Although the UI specifies to look for a default, that's ignored by design since the code itself is only looking for the value for those leads. If the goal is for it to evaluate and provide a known value, otherwise then render a specified default, that needs to be built into the Velocity script code itself.

I'm trying to find out who had a lead score change from a specific smart campaign - would I use data value changed with a reason or some other filter? The Data Value Change trigger/filter with the Reason constraint is appropriate for finding leads that had their Lead Score changed by something such as a manual edit or Smart Campaign. This is a article attached image This is a article attached image This screen shot shows examples of how you might set this up. The list below shows a few of the values you may see in the Reason field. If you know the exact phrase you are looking for, use the "is" operator. For example, "Changed by Smart Campaign Contact Us." If you don't know the exact value, try using the operator "starts with" or "contains." Synched from salesforce.com Changed by Smart Campaign System flow action System action reset Form fill-out SOAP API Manual lead edit Munchkin API Import/merge into list The Reason filter constraint is available in these filters: Data Value Changed Lead Partition Changed Progression Status was Changed Revenue Stage was Changed Not Data Value Changed Not Lead Partition Changed Not Progression Status was Changed Not Revenue Stage was Changed

Included in this article Overview Troubleshooting To Try http:// and https:// No Munchkin Tracking Code on Web Page No Visitors to the Web Page Yet Tips for Triggers and Filters Selectors Overview Have you ever tried to enter a web page into a Visits Web Page trigger or filter and gotten an unexplained red squiggly line? It looks like the one you get in Microsoft Word when you have a spelling error. You hover your mouse over it and it says "Invalid URL" even though you know that the web page is a good one. This can be a frustrating one, but here are a few things to look for to troubleshoot this problem. Troubleshooting To Try There are a few different reasons why this could happen. You could have an error in the formatting of the URL entered, you could have a page that isn't being tracked or hasn't had any visitors. Here's what to check for. http:// and https:// Using http:// or https:// in the beginning of the URL can cause the red line to appear. Check if you have it in the URL. If yes, remove it and the red line should disappear. No Munchkin Tracking Code on Web Page If the web page you're entering doesn't have the Munchkin tracking code on it yet, there's no way for Marketo to "see" the page at all. Make sure the Munchkin code is on the page and is actively tracking as it should be. For more details, check out Add Munchkin Tracking Code to Your Website - Marketo Docs - Product Docs No Visitors to the Web Page Yet Another cause for the red squiggly line to appear is if there have been no visitors tracked by munchkin on the targeted page. Filters look through lead record activity logs for the activity they're looking for. If the filter is searching for leads that have visited a particular web page but no leads have logged that activity yet, the filter can read this as an invalid URL, similar to if there were no Munchkin code on the page. Check the page for visits. Make sure you have a munchkin installed on the page you are requesting. Create a test lead and visit the targeted page. Tips for Triggers and Filters Here are a couple of things that may help when using these filters and triggers. Selectors "Is" Selector In Triggers and Filters, if you use the selector "Is", (as in "the web page IS xyz.123.com") then the results returned will only be those from an exact URL match. If you want to also find results for the page xyz.123.com/sales, they won't be returned when using the "is" selector. NOTE: The "is" selector will return results in filters much faster since it is only looking for exact matches. "Contains" Selector If you use the selector of "contains", (as in "the web page contains xyz.123.com"), then this would return results for all pages that have xyz.123.com. Therefore, xyz.123.com/sales would match. The page xyz.123.com/products would match. All variations of that site xyz.123.com would match up. NOTE: The "contains" selector in filters will take a little longer to process because it has to evaluate the entire URL string in every web page visited to identify whether there's a match for the value anywhere within the URL. It's not extremely long of a delay, but you may notice a little slowness.

Issue Trigger Tokens in a Batch Campaign Flow are not functioning as expected, or result in an error. Solution Issue Resolution Trigger Tokens can only be used in a Trigger Campaign Flow and will not work in batch campaigns. While originally intended for Interesting Moments, Trigger Tokens will also work in Change Data Value flow steps. The associated Trigger Tokens will only function with the corresponding Triggers denoted by the green check-marks in the chart here.

Issue Best practices for trigger campaigns. Environment This applies to all Marketo users who are utilizing trigger campaigns in their marketing activities. Solution Marketo's trigger campaigns are designed to monitor every relevant activity, even if it doesn't immediately meet certain constraints or filters. For example, if there are 10 active Clicked Email Campaigns and 100 leads engage with an email, each lead will be evaluated 10 times to check if they qualify for a trigger. In this example that would lead to 1000 evaluations total. This happens even if they don't meet the criteria due to certain filters or constraints. To make your trigger evaluation process quicker and more efficient, follow these best practices: 1. Deactivate any trigger campaigns that are no longer needed. This reduces the number of active monitors that could potentially activate trigger event evaluations. Note: Marketo automatically deactivates smart campaigns that have been dormant (no lead triggers them) for 6 months or more on a quarterly basis. However, you can manually deactivate campaigns whenever necessary. 2. Convert Trigger campaigns to Batch campaigns if immediate responses are not required. This is particularly useful for activities or campaigns that can run overnight. Batch campaigns operate on a separate component of Marketo's processors, meaning they won't impact the speed of Trigger qualifier processes.

Issue When you go to schedule a Smart Campaign, the Status tab says it is "set to affect about N/A people" instead of showing the actual number of leads that should go through the campaign. Solution There are two probable causes for this There is an error in the Smart List. If the Smart List references another nested Smart List, the error may be in the secondary Smart List, so you may need to drill down when you check this. The Smart Campaign has a Smart List in it with the same name. For example, if the Smart Campaign were named "EMEA Networking" but it also contained a Smart List named "EMEA Networking", it would cause the list processor to give this error. Making one of the names slightly different - "EMEA Networking Smart List" - should resolve this issue. If you have tried both options and are still unable to get the affected leads count to resolve, please contact Marketo Support with the results of the above troubleshooting and we will investigate further.

Issue You are trying to add a new stream to an Engagement Program but get an error stating that your program has reached maximum number of streams per program. Solution Due to engineering constraints and as well as to have better user experience, we have limited the number of Engagement Program Streams per program to 25. When you try to add 26 th stream, you will now get the error message “You have reached the maximum number of streams. Create another program”. So the solution is to create a separate Engagement Program and a Smart Campaign that moves leads from the original Engagement Program to the new one.

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 A recent Smart Campaign or Email Program sent Person records in Marketo more emails than should be allowed based on settings in Communication Limit Settings in the Admin area of Marketo. Solution This is commonly caused by one of three things: The emails that sent after the communication limit was hit were Operational. To verify if this is the case, select the email asset from the menu tree on the left and review the summary of the asset in the canvas where you will see if the email is Operational or not. The Block non-operational emails checkbox is not checked in Edit Communication Limit Settings. Setting values the "Per Day" and "Per 7 Days" dropdown menus does not enforce the communication limit. In order for this limit to be enforced, the "Block non-operational emails" checkbox must be checked. Enable Communication Limits The Email Program or Smart Campaign are not set up to follow Communication Limits. Apply Communication Limits to Smart Campaign Enable/Disable Communication Limits in an Email Program

Issue An email was expected to sent out on a specific cast of Nurture Program but a specific lead or couple of records did not receive it. Environment Marketo>Engagement Program Solution There are a number of steps to begin troubleshooting this query and here is a flowchart how to proceed. 1). Check if engagement program is turned on from its setup up. Also check if at the time of email cast, the program status was on (this can be checked from Admin>Audit Trial) 2). Check if the email asset which was expected to send was present in the Nurture Stream at the time of cast. Also check if that email asset was activated (having green arrow). Both of these can be checked from Audit trail where you will find the log of "Add Email" and "Activate Email" along with its date/time. 3). Check if the lead is present in that specific stream using the smart list filter "Member of Engagement Program > Stream = <required stream>" 4). In the same smart list, use filter of "Engagement Program Cadence Changed" and set "New Value = Paused" and see if that lead qualifies it or not. A paused cadence would mean the lead has been temporarily restricted to move in the flow of nurture stream and hence will not received any email content. 5). Most important step- Go to the activity log of lead and search for the engagement program's name in the quick find bar. Look for all logs along with their dates when the lead performed any activity related to that engagement program like added to program, changed cadence, removed from program, etc. 6). In continuation of step 5, check in the activity log if the lead was added to engagement program in less than 25 hours before the next cast by looking at the time of log "Added to Engagement Program". This is because as per the doc, the lead must be added atleast 25 hours before the cast to abide by the recipient time zones otherwise it will skip that current cast and will qualify for the next cast. Schedule Engagement Programs with Recipient Time Zone | Adobe Marketo Engage 7). In continuation to step 5, check if the lead was moved to a different stream via getting qualified into transition rules. Transition rules are present in stream of those engagement programs that have more than one stream and are used to move leads from one stream to another. Transition People Between Engagement Streams | Adobe Marketo Engage 8). Check if the lead is unsubscribed, email invalid, email suspended (this one is only valid for 24 hours), marketing suspended or block listed because any of these 5 conditions would block the lead from receiving any communication from any of the Marketo's program or campaign. 9). Check if the record has hit the communication limit. Go to Admin>Communication limit and see what we currently have setup. If limit is 2 emails per day, then create smart list "Was sent email>Email Is ANY> Minimum Number of times 2" and see if lead qualifies in it. Alternatively you can go into lead's activity log and manually count number of "Send Email" logs in last 24 hours and in last 7 days and match it with the communication limit of Admin tab. Using programs as stream content: We can also use programs (default and event) in nurture stream instead of direct email assets. 10). In case of using a program, the email can be sent out to the required audience only if that program have a smart campaign with filter "Member of Engagement Program>Name of Program" and flowstep of "Send Email". So make sure the smart campaign has these configurations. (Make sure the campaign has to be a batch campaign and not trigger) 11). If above pointer is true still record is not present in the result tab of the campaign, then check all steps from step 1- step 9. If nothing is found then check if smart list has more than just "Member of Engagement Program" filter and if the lead is failing to qualify any of the other filter. 12). Check in the schedule tab if qualification rules says "Each Lead can qualify only once". If yes then go to campaign member tab and search if lead is already a member, if yes then lead will not qualify again and this is why email was not sent. 13). Check if flowstep has a wait step and the lead is stuck there because wait step does not create any log in the results tab. People in waitstep can be checked from dashboard of the smart campaign. 14). For any other possible reason why the lead did not qualify the smart campaign, you can look for the knowledge base "Lead not qualifying smart campaign- Universal Checklist" under heading of Batch Campaign: marketo.my.salesforce.com/articles/en_US/Article/Lead-not-qualiying-smart-campaign-Universal-Checklist?popup=true 15). If all above pointers have been checked still unable to figure out why the email was not sent on a specific cast, escalate the case to Tier 2.

Summary Flow step choice condition for "Person was Deleted from SFDC" with 'in past' "7 days" causes campaign failure Issue This flow step choice type causes a campaign failure because it is not supported. This is expected behavior. Solution Customers have to use Member of Smart List as indirection for the desired filter condition. i.e. Create a new Smart List with the "Deleted from SFDC" filter. Then change this failing flow step choice to use 'Member of Smart List' with the Smart List just created. Example flow step:

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 Issue Description Getting 'Communication Failure' error popup repeatedly when doing normal operations within the application. Solution Issue Resolution: - Disable all browser extensions especially any dealing with ad blockers as they seem to be the primary cause of this issue ("Ghostery" is an example of extension known for blocking multiple Marketo operations/ tasks). - Try to repeat same operations after you have cleaned cache and cookies - (If above option does not work) Try to repeat same operations while using a incognito browser window.

Issue Issue Description An email has been added to multiple streams within the same nurture program, for example stream 1 and stream 2. Would a lead that received the email in stream 1 receive the same email from stream 2? Solution Issue Resolution No, Engagement Program will still apply the rule of not sending the same email to leads more than once as long as the email ID in stream 2 is the same from stream 1.

Knowledgebase

Maintaining a Directory of Leads Bouncing Emails

Unable to reference AB test email in smart list or campaign

My Marketo Campaigns Are Not Showing Up in Sales Insight

Adding People to Marketo Campaigns from Salesforce

Velocity Scripted Tokens Not Using Default Values

Using the Reason Constraint on the Data Value Changed Filter

Troubleshooting Visited Web Page Filters/Triggers Giving Invalid URL Message and Red Squiggly Line

Trigger Tokens in Flow Steps Render Incorrectly

Trigger Not Capturing Change: SFDC Is Deleted

Trigger Campaign Best Practices

Smart Campaign Status: Set to Affect Around N/A Existing People

Reached Engagement Program Stream Limit

Error Approving Email - Token Key Not Found

Email Sent to Leads Who Have Exceeded Their Communication Limit

Engagement Program not shooting email

Flashing Clock Icon on Batch Campaign

Flow step choice condition for "Person was Deleted from SFDC" with 'in past' "7 days" causes campaign failure

Flow Step Choices Qualifying Leads who are Members of Other Programs

Getting Repeated 'Communication Failure' Errors

Having the Same Email within Multiple Streams in a Nurture Program

How to Create a Custom Interesting Moment Type