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

Summary Aggregating/summing two score fields Issue You have two new score fields (for example: 'Implicit score' and 'explicit score') and you're wondering if there's a way to sum/aggregate these scores together for all records within Marketo. Solution To aggregate different score values together within Marketo, you should first create a third 'sum' field meant to capture the aggregate of the two scores. (Example: 'sum score') Now, we have 3 scores: Explicit Score, Implicit Score, and a Sum Score SOLUTION First, setup the scoring smart campaigns for implicit and explicit score as you normally would. Once those scoring programs are setup, add the sum score field to the flow of each respective campaign, increasing that score by the same interval that you increase the implicit or explicit score by. This should allow the scores to aggregate over time. Example 1 "Implicit Scoring campaign: Trigger: Visits web page 'x' Flow: 1. Change Score [Implicit score] Change: +5 2. Change Score [Sum score] Change: +5 Explicit Scoring campaign: Trigger: Fills out form 'y' Flow: 1. Change Score [Explicit score] Change +10 2. Change Score [Sum score] Change +10 Final result if a record runs through both campaigns > Implicit score: 5, Explicit score: 10, Sum score: 15" In the above example, the sum score flow step is simply added to each respective explicit/implicit scoring campaign, with the same change interval applied. Once applied to all relevant scoring programs in the instance, the sum score should continue aggregating the two scores into the sum score field. If you're increasing both explicit and implicit scores within one campaign instead of separating out by score type, you could also accomplish this with the same logic and instead adding the summed score interval within that same flow, for example: Example 2 "Scoring campaign: Trigger: Person is created Flow: 1. Change Score [Implicit score] Change: +3 2. Change Score [Explicit score] Change: +4 3. Change Score [Sum score] Change: +7 Result > Implicit: 3, Explicit: 4, Sum: 7" -------------------------------------------------------------------- Potential Alternative solutions: 1. Have your SFDC/CRM Admin create a workflow within the CRM which sums the two fields as they sync. This requires the score fields in question to be synced to the CRM. 2. Call a webhook, which will keep the aggregate in line with the individuals each time it's called. This would be a custom webhook implementation that Support cannot assist with. Sources for alternative solutions: How to sum Lead Scores in one aggregate score field Add two Scores in Marketo

Summary This article explains why certain Company fields show up on the Person/Lead Object when you do a describe API call to Marketo. Issue When making the Describe call on the Lead object in Marketo (/rest/v1/leads/describe.json), several Company object fields are returned along with the Lead object fields. Environment Marketo REST API Solution This is expected behavior. Users can utilize the Describe Leads call to retrieve a full list of the fields available for interaction via the REST API. Several areas within Marketo treat custom Company fields as though they were on the Person/Lead object. For example if you were doing a Bulk Import, you can target the Company and Person/Lead fields and you have the ability to update Company field values as if you were changing it manually on a Person record in the UI. Root Cause This is expected behavior, due to how the Describe call retrieves all

Issue A lead shows as being a member of a campaign that had a single flow step of 'Change Data Value'. However, the lead doesn't show in the Results tab of the campaign, nor is the CDV activity logged in the activity log for the lead. Solution This can happen if the field to be updated was blank/null, and the new value in the CDV flow step is derived from another field, using a token, and this other field is also blank. Because the value 'changes' from blank to blank, we don't log anything in the activity log, but the lead is a member of the campaign.

Knowledgebase

Maintaining a Directory of Leads Bouncing Emails

Aggregating Two Score Fields

Company Fields Appear in Lead Object "Describe" API Call

Lead went through CDV flow step but it's not logged in the activity log