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 Person record's Activity Log shows repeat Company Name changes without any Data Value Change being logged. In this example screenshot, we can see that the person had the Company Name set back to the correct value by the CRM sync, but there is no record of the Company Name being changed in the first place. This is a article attached image Environment Person records showing the change are all part of the same Account. One person on that holding Account fills out a form that updates the field "Company Name" to a value that is different from the Account Name CRM sync corrects the Company Name field back to Account Name Solution STEPS TO RESOLVE: 1. Find the lead that change the Company Name field on the account with a Smart List filter: DATA VALUE CHANGED Attribute: Company Name New Value: [Company Name from form fill-out] Previous Value: [Account Name] This is a article attached image 2. Locate the Data Value Change in the Activity Log 3. Check the date and time of the Data Value Change 4. Check that timeframe on other affected records 5. The timeframe of the Data Value Change back to the Account Name will approximately match the timeframe of the logged Data Value Change, showing that the update to the one person was the cause of the update for all others on that account. Root Cause Marketo uses Company Name as the identifier for the Account object. If you have multiple people on the account and one of them changes the Company Name via a form fill-out, the Company Name is changed for all other people on that Account. This change happens on the back end, so you will not see it until the CRM changes it back to the correct value in the next sync cycle.

Issue Lead activity log shows "Change segment" or "Add to Segment" for a segmentation (i.e. "Change Title to "Directors") The named segmentation ("Title") does not show up in the segmentation list in Database Environment Marketo instance with the Target Account Management feature Solution Even though the activity log shows a segment activity, the segment is actually a Persona, which is a feature of Target Account Management.

Issue If a record which is in a Marketo Campaign Wait Step and is merged into another record, does the winner of the merge continue through the flow? Solution Winner of the merge will continue through the Campaign flow and complete the remaining steps. To prevent this behavior, remove the record from Campaign using the 'Remove From Flow' step. Environment Records merged in Marketo Records merged in SFDC

Issue Single Flow Step to send an email to x number of leads failed Solution Create a smart campaign and override the person restriction to send an email to a number of people that is greater than the campaign restriction Root Cause The number of people selected to send an email from a single flow action exceeds the campaign person restriction/limit. The campaign restrictions apply to the single flow action because a background campaign is generally created to process the single flow action. Environment Single Flow Action Send Email Campaign Restrictions Smart List

Summary duplicate records with the same email across lead partitions can be affected by uploaded custom object activity Issue System not separating lead partitions for custom object imports Uploading custom object activity affects duplicate records across partitions Custom Object activity import writing to the most recently updated record regardless of partition Solution Use the following workaround: Run an update on the records that should be affected by the custom object activities import. This will make sure they are the most recently updated records among the duplicates Root Cause Normally when you do a list import, it would import into the one partition, whatever partition the list is located in and only impact the record in that one instance. But when you import a Custom Object, it's able the see ALL the records across ALL the partitions. If there are duplicate records, it just looks to see which one was updated most recently and grabs that one for the list import. So if you have lead record in A with Add to Custom Object already completed and you re-import again but the lead record in B has been updated more recently and has NOT had the custom object added to it, you get the duplicate "Add to Custom Object" activity. Environment Multiple lead partitions with duplicate records across them Custom Object activity import

Issue Leads recently imported cannot be found Solution Check if the example leads exist in the partition the workspace has access to. It is possible that the leads cannot be found because the workspace being checked does not have access to the partition the leads exist in. Check if any of the example leads have been deleted: by using the Campaign Inspector to review all of the smart campaigns that contain a Delete Lead flow action. Then check the run history of each smart campaign to see which recently ran and how many people qualified. If there is a significant amount of smart campaigns that contain a delete lead flow action, contact Marketo Support for additional assistance. by checking the delete lead activities via API Check if the example leads' information was changed. For example, if a lead was imported with email address "john@gmail.com" then create a smart list using "Data Value Changed" filter where "previous value" was "john@gmail.com" Root Cause Leads could exist in a partition that has not been searched, the details could have changed, or the leads could have been deleted. Environment Lead Database List Import Workspaces and Partitions Smart Campaign Campaign Inspector

Summary Estimating the external storage requirements for your Marketo Engage Database Issue I want to extract all of my data from Marketo Engage and store it. How much storage space will I need? Environment Marketo Engage and External Systems Solution Summary There is no repeatable method to accurately estimate the amount of storage you will need to extract and store your Marketo Engage database. Standing in the way of good estimation is data availability, field selection, and storage method. Any accurate estimate will take into account the potential sizes of each type of data and their quantities (known to data scientists as "facts and dimensions"). Determining ranges for these values takes a lot of preparation and may require a high level of skill. IMPORTANT NOTE: Estimating Database size is hard so any estimate used to make business decisions should be made in cooperation with a database or application architect or other qualified professional. Scope Some information won't be extracted. Information about anonymous leads, for example, cannot be extracted. Some of the data that can be extracted may not be needed at all. Selecting the right data for your needs is the best practice as it reduces the required storage and leads to a more efficient extraction process. Field Definitions How the fields are defined in the target system will affect how big the stored data is. Depending on your storage format, padding may play a role in the size of your extracted database. As an example, the "Country" field in Marketo is a string of up to 255 characters. You could chose to store 255 characters for every country value. Or you may choose a format that uses a variable amount of space. You might also know that the longest country name is "the United Kingdom of Great Britain and Northern Ireland" meaning that 199 of those characters will always be extra so you truncate the value from Marketo storing the first 56 characters only. Each choice will have an impact on the size of your extracted database. Estimating 199 unnecessary characters per lead and making similar decisions for other fields will add up to increased storage requirements and slower extraction time. Format Once the desired data is identified, the next step is to extract, transform and load (ETL) the data from Marketo Engage into your storage system. The data returned by Marketo's API is plain old text which is usually formatted as JSON or CSV. For the information to be useful, you will transform it from JSON into the format necessary for your storage system. That format could be an Excel spreadsheet, Microsoft SQL database or a schema-agnostic database like Azure Cosmos DB. How the data is formatted and encoded will make a big difference in the amount of storage needed. Take this simple example: a Microsoft Excel spreadsheet with "Marketo Engage" in cell A1. I saved that same file in four different formats which resulted in files ranging from 1 KB to 25 KB. The format you store you information in may have a bigger impact on your final storage requirement than the data itself. This is a article attached image To help illustrate the impact of the storage system, take a look at this guide for Microsoft SQL Database size estimation: https://docs.microsoft.com/en-us/sql/relational-databases/databases/estimate-the-size-of-a-database Functionalization Once you've extracted your data, what are you going to do with it? Archiving your data (simply storing it) is easiest and comes with the fewest contraints. A compressed archive (Zip file) will save dramatically on storage space at the cost of functionality and ease of use. Functionalizing your data (using it in an application) requires more: at least better speed and searchability: typically a relational database. An application will often require additional data and that will need to be accounted for too. Facts and Dimensions: Do the Math It's a lot of work to get to this stage. Once you've determined how your extracted data will be stored, you can set upper and lower bounds on the sizes for each object type extracted (lead, email, activity, etc). These are your facts. Then multiply those values by the number of each type of record. These are your dimensions. Add to that the overhead of your target storage system and its functional requirements to generate your final estimates.

Summary Unable to update Person Source as expected for records created with the LinkedIn Lead Gen Forms and Facebook Lead Ads integrations. Issue New records created through LinkedIn Lead Gen forms as well as Facebook Lead Ads results in the records not updating the Person Source field as expected. Solution Person Source may be set to block updates to the field as noted in the example for Block Updates to a Field - Marketo Docs - Product Documentation. To resolve the issue ensure the field is not set to block updates for the desired update method. Alternatively the Person Source values populated by the integrations can be kept and expected values can be updated to include these sources. Root Cause The LinkedIn Lead Gen Forms and Facebook Lead Ads integrations automatically update the Person Source to preset values when a new record is created in Marketo through the integrations. Blocking field updates to the field may prevent the value from changing to pre-configured values as a value already exist for the integration created records. Environment LinkedIn Lead Gen Forms Facebook Lead Ads

We have enhanced the behavior of the unsubscribe functionality to make it “durable”. We have added a master email status, which is separate from the unsubscribe flag visible on the lead detail record. If the unsubscribe flag is set from false to true, the master email status is updated, and the change is propagated to other leads with the same email address. Update the Unsubscribe flag from True to False (e.g. Re-subscribe a lead) When a lead is imported, the unsubscribe flag WILL NOT be overwritten by the import. Here are the ways a lead can be re-subscribed: 1. In SFDC, uncheck the Email Opt Out field. This WILL sync to Marketo. 2. Manually update the lead detail record by un-checking the unsubscribe flag 3. Run a Change Data Value Flow Action on one or many leads a. Select the attribute “unsubscribe” and set the value to False 4. Update an existing lead via SOAP API 5. Form Field – set a field on a form to set the unsubscribe flag to “false” and this will unsubscribe the lead a. Best practice would be to have text on the form that says that by filling out this form, they are agreeing to receive email communication Creating a New Lead When a new lead is created, we check it against the master email status table. If the lead was previously unsubscribed, we will update the record to be unsubscribed. Changing an email address If you change the email address of a lead to an unsubscribed email address, the lead will be unsubscribed. This change can occur in either Marketo or SFDC. If you change an unsubscribed email address to one that is subscribed, the lead will be subscribed.

Issue Description: The Activity Log shows "Fill out a form" without a page visit. How users could fill out a form without visiting the page? Issue Resolution: Google Chrome introduced Incognito. Firefox, Safari, Opera and Internet Explorer implemented Private Browsing. Pages that users visit in Private Browsing/Incognito will not leave traces, like cookies, on users' computers after they close all open windows. A normal visit to any page is not tracked during visits, regardless the navigation path. That includes other pages after the form is filled out. The new Do Not Track feature is a contributing factor for apparently incomplete Activity Logs. When users turn on the Do-not-track feature, the browser tells every website they visit (as well as their advertisers and other content providers) that they do not want their browsing behavior tracked. Honoring this setting is voluntary — individual websites are not required to respect it. Websites that do honor this setting should automatically stop tracking your behavior without any further action from users.

My export is going to take a long time, do I have to stay logged in until it completes? Thankfully no, once you get your Import or Export started, you can log out, go grab some coffee or go home and the process will continue. Export: When you start the export process, you can close out of Marketo, later in the day or the following day you can log back into Marketo, find the same SmartList or StaticList you ran the export from, select it, click on List Actions and choose "Show Export Status". The Export dropdown will show up and assuming it is finished, the download link will be available. 1. Find and Click on the SmartLists or StaticList: 2. Click on List Actions then "Show Export Status": 3. The dropdown will pop open in the top right hand corner with the export status or the download link: Import: Similarly, you can get an Import started, when you choose the CSV and begin the process the first step is for the file to get uploaded to our server where it will be further processed and imported into the database. Once the file is uploaded and the import process begins, you can close out of Marketo and come back to check on the status in the future instead of staying logged in the entire time. In a similar manner to checking export status, you can click the StaticList you are importing into as follows: 1. Find and Click the SmartList or StaticList you are Importing into: 2. Click on List Actions then "Show Import Status": 3. The dropdown will pop open in the top right hand corner.

Note: Once you have migrated to Admin Console, you can manage your support cases through the feature provided in the Admin Console Platform. To learn more, visit: https://experienceleague.adobe.com/docs/customer-one/using/home.html. Once you have submitted a case to Marketo support, we provide a simple way of staying connected to your case and the cases submitted from your company through the Marketo Support Portal. You can access the support portal through your Marketo instance by selecting Community in the top right corner: This is a article attached image You can also access the support portal directly at https://support.marketo.com and login with your Marketo credentials (login and password). This will not work for users with SSO. Once you are in the support portal you can Create a Case for Marketo Support or you can also review any cases that are open and being worked on by support or review your case history. Navigate to My Case management: This is a article attached image From the My Cases navigation you can access the following case views: This is a article attached image My Recent Cases* - Cases that you have opened in the past 30 days All Company Recent Cases* - Cases that any authorized support contact has opened in the past 30 days My Open Cases – Cases created by you that are being triaged by Support and pending Support’s response and are more than 30 days old My Closed Cases – Cases that were created by you and are now closed My Awaiting Fix Cases – Cases that were created by you where Marketo is developing a fix which will be implemented at a later date All Company Closed Cases – Cases that were created by you or your colleagues that are now closed All Company Open Cases - All open cases submitted for the account Company Awaiting Fix Cases – Cases that were created by you or your colleagues where Marketo is developing a fix which will be implemented at a later date Management Escalations - Escalations opened by you or your colleagues Survey Cases - Surveys that are available for you to fill out after a case is closed *Cases that have been opened for more than 30 days will move from Recent cases to Open cases To view specific case details, click a case number. This is a article attached image From the Case Details, you can perform the following: Close your Case - Select the "My Case is Resolved" button to close your case Add Comments - Provide additional comments to support or respond to a Support question Add Attachment - Provide any screenshots or documents that will help illustrate the issue you are reporting If your case has been closed there are two options available to you. Reopen - You can reopen your case if you are not satisfied with the case resolution by adding a comment in the case. Case Survey - Once your case has closed, please consider offering feedback on the level of Support you received.

List imports can fail for a number of different reasons, so finding what that reason was is the first step to fixing what went wrong. When a list import fails to import leads, the Import Status dialog box will give you an error to tell you that some of the leads failed to import. The “Failed: X Leads” showing in the Import Status dialog box is a hyperlink. This is a article attached image When you click on the hyperlink, it will download an Excel file that carries the details of what caused the failure. The details for the import failure will change depending on the different types of issues, so watch for the explanations in the far right column for each lead on the list. Invalid data for the field type: This is a article attached image Invalid Email Address Warning: This is a article attached image Lead belongs to a different Lead Partition: This is a article attached image

Issue When I go to the Support area of Nation, I do not have full access to all the areas and tools. Solution Our system is specific about how you need to access the Support Portal before we can authorize you to use it. The proper steps to take for us to authorize, and for you to submit cases, are as follows: Log into your instance Click the Community tile (step 1 image) Click Support in the top banner (step 2 image) Click Submit a Case option (step 3 image) Choose from top options depending on what you need to do (step 4 image) Create a case, Manage authorized contacts, edit your Info Simply going straight to the nation.marketo.com will not have the desired result. You must access the Support Portal from your instance by using these steps so that our system recognizes you properly. If this is your first time following these steps, your view of Step 3 will be different- not to worry, as that will be updated for you manually. Step 1 Step 2 Step 3 Step 4 If you experience issues, please email marketocares@marketo.com

Issue Issue Description When a lead is created through an API call, the Reason and Source attributes say "Web Service API" with no further detail. Solution Issue Resolution As described in the doc here, https://docs.marketo.com/display/DOCS/Understanding+System+Managed+Fields, "Source" and "Reason" fields are managed by Marketo: Web Service API for Original Source Type means Person was discovered by a web service API. For Registration Source Type, it states that Person was created via SOAP/REST API When a lead is created via API, no additional "Source" or "Reason" is provided to Marketo. A possible workaround is to create a custom field and populate it as needed through the API.

Issue You have a field (e.g. Most Recent Website Visit) that you want to see previous values for without needing to look through the activity log. Solution This can be done using a few custom fields, and one trigger campaign. Make duplicates of the field you want to see most recent values of (e.g. Most Recent Website Visit 1, Most Recent Website Visit 2, etc.) while still keeping the original field. Use the original field as you previously have, but set a trigger campaign to look for data value changes to that field. In the flow of that campaign, set the logic like so: (1) Change Data Value: Most Recent Website Visit 3 new value: {{lead.Most Recent Website Visit 2}} (2) Change Data Value: Most Recent Website Visit 2 new value: {{lead.Most Recent Website Visit 1}} (3) Change Data Value: Most Recent Website Visit 1 new value: {{lead.Most Recent Website Visit}} Using the above flow, the most recent values for the field can be checked without looking into an activity log. This can be useful in a number of ways, for example this information could be included in an email or alert. Another example, if the primary field (in the above example it is Most Recent Website Visit) is updated to a value that it should not have, then you can setup another campaign to update Most Recent Website Visit using the value in Most Recent Website visit 2 to restore the previous value. Warning Please Note: The above process can be somewhat resource intensive (particularly if a large number of records trigger the campaign at close to the same time), this should be done with as few fields as possible to assure good instance health overall.

Issue You would like to know which partition a record that was captured by using "Forward to a friend link" in an email will be created in. Solution The record will be created under the partition which is associated with the work space under which the email asset is present. The record will not be created under the default partition. For example, if you have a workspace named "Asia" which is connected with the partition named "APAC", then leads created via Forward-to-Friend links in emails stored in the "Asia" will be created in the "APAC" partition.

Issue You want to know the difference between a field with the type of string and text area. Solution Both a string and text field will hold information that you can freely write in. The major difference between the two fields is how many characters you can put in these fields. A string field has a limit of 255 characters, whereas a text field has a character limit of 30,000 characters. (This is a general rule. It may vary by application and platform.) A string field is a good choice if you wanting to store data like address, names, or simple custom data. A text area field is a good choice when you want to store information from something like a comment box on a form or if you are importing a large block of text.

Issue You try to approve a segmentation and get the error message of "No possible draft" even when there is a draft in place. Solution This error message can be a little misleading, as there usually is a draft in place. Check to make sure that segments in the draft have Smart List filters in place and that there are no empty values in the smart lists. An example of an empty value would be "First Name is ____" instead of "First Name is Joe."

Issue You have a lead that is marked as Email Suspended and you are not sure whether they can receive Marketo emails or not. Solution When emails bounce as spam, the lead that bounced is set to "Email Suspended." "Email Suspended" is a historical field. A more accurate name for this field would probably be "This email was suspended at some point in its history." The actual suspension only lasts 24 hours. To see if the lead is currently suspended, check the timestamp on the 'Email Suspended' field. If it is more than 24 hours ago, the lead is not currently suspended and can receive email from your Marketo instance. However, the "Email Suspended" flag will remain on the lead record for the purposes of future troubleshooting. It is not possible to set "Email Suspended" to "false" once it has been set to "true." The "Email Suspended Cause" field will provide the bounce message associated with the most recent spam bounce.

Knowledgebase

Maintaining a Directory of Leads Bouncing Emails

Person record's Activity Log shows repeat Company Name changes without any Data Value Change being logged

Segmentation - Leads Assigned to a Segmentation that does not appear to exist

What Happens to Merged Leads in Campaign Wait Steps?

Send Email Flow Step Failed

system not separating lead partitions for custom objects

Leads cannot be found

How Much Storage is Required to Extract My Entire Marketo Engage Database?

Updating Person Source for LinkedIn and Facebook created records

Durable Unsubscribe - How Leads are Unsubscribed and Re-subscribed

Activity Log Shows Form Submission without a Page Visit

My Import/Export Is Going to Take a Long Time, Do I Have to Stay Logged in Until It Completes?

Managing your Support Cases

TROUBLESHOOTING List Import Failure Reasons

Support Portal Access Issues

"Reason" and "Source" Attributes for a Lead's Activity Simply Say "Web Service API"

How to Retain Previous Values in a Field While Adding New Values

New Lead Created by 'Forward to a Friend Link' Is Not in Default Partition

The Difference between a Field Type of String and Text

Segmentation Cannot Be Approved with Error Message “No Possible Draft”

How the Email Suspended Field Works