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?

With Marketo's Customer Engagement engine, you can now easily nurture and engage your leads. Not only does the Customer Engagement engine automatically and intelligently deliver the right content to the right person, at the right time, but you now no longer have to manually create or maintain complex workflows. View this training webinar if you are on the Spark or Standard Edition of Marketo and want to learn how to best set up nurturing with the Customer Engagement engine. pages2.marketo.com/cee-training-nurture-aug-2013.html Is this article helpful ? YesNo

Issue How page views and form fills are counted in the statistics section of a Marketo Landing Page asset. Solution How they're calculated When viewing the Landing Page asset in either Design Studio or Marketing Activities, the statistics section provides information regarding page views and form fill outs, if the page has a form located on it. The page views are a cumulative total indicating how many times the page was loaded, regardless if the visitor was a known record in the database. This means anonymous people can record a view here, due to Munchkin tracking on the page. This section provides a total number of views, not unique visits. This means that a person can load this page multiple times and each visit will be tallied in this section. The form fills section (x Filled out Form (x%)), indicates how many times a visitor filled the form out on the page, if it has one. This total is also counted in the same way the views section is, meaning it's a total number of submissions. Therefore, if a record in your database fills out the form more than once on a page, it will be counted toward the total. Difference between calculations The difference between these two metrics is that the page views will keep a historical record of visits to the page. This means the total will not change if you happen to delete a bunch of records that visited the page in question - the total persists regardless if the record is no longer in the database. With that said, the forms section does not. This area is tied specifically to the existence of that known record in your database. This means that, once a record who filled the form out is removed from your database, the submissions they performed will be subtracted from the total.

Applies to: Email Performance Report, Email Link Performance Report, Engagement Stream Performance Report, Landing Page Performance Report, Program Performance Report, Sales Insight Performance Report When you create a report in the Analytics area, by default the report will only show reporting for the current workspace. This is a article attached image Once the report is created, under the Setup tab, you can add filters to filter by asset. For example, Filter Assets in an Email Report. If you filter for the workspace, it will show reporting for all assets in the workspace, similar to the default view without a filter: This is a article attached image To add reporting across all workspaces, use Enable Global Reporting in the report settings within the Setup tab. Note: Global Reporting is only available in your instance's default workspace.

Issue Description Does the email address assigned to the API user need to be an email address maintained by an actual person? docs.marketo.com/display/public/DOCS/Create+an+API+Only+User Issue Resolution The email address assigned to an API user does not need to be an existing email address or an actual person. It is used as an identifier for the API user. Generally, customers name the API user according to the integration the API user is being used for (e.g. integrationuser@company.com). This is useful for tracking where API calls are coming from when there are multiple integrations configured with Marketo via the API

Issue: When creating an event the WebEx connector may throw the message: Error registering with webinar provider. exception="WebEx API call error; Self registration is not supported by this service type or current meeting. [WebEx exception ID = '110051'] " Solution: Please make sure the event in WebEx is set up to receive registrations. To do this you need to go to the event in WebEx and check the registration required checkbox. References Create an Event with WebEx - Marketo Docs - Product Docs WebEx Event Center guide

Included in this article Overview Troubleshooting Checklist: Verify that you are using the most updated RTP tag version on your website. Verify that the RTP tag is the first script in the header of your pages – between the <head> </head> tags. Are you using a tag Manager? Check the campaign itself. Overview Sometimes you may experience latency when your RTP campaign displays on your webpage and pages appear to load slowly. The following checklist will help you find issues that may be contributing to campaign latency. Troubleshooting Checklist: Verify that you are using the most updated RTP tag version on your website. Go to your website > Right click on the page and select "View Page Source" > Search for 'RTP' to find your tag. Verify that this tag matches the code provided for your instance. You can find more information on finding your RTP tag here. Verify that the RTP tag is the first script in the header of your pages – between the <head> </head> tags. If the tag is not in the recommended placement, follow the documentation on deploying the RTP tag. Moving the tag to the recommended placement will resolve most latency issues. Are you using a tag Manager? Using a tag manager for your RTP tag is known to affect campaign performance. If you are experiencing campaign latency while loading the RTP tag via a tag manager, we recommend moving the tag into the code itself. You can find more information on deploying the RTP tag here. Check the campaign itself. Campaign customizations that load additional content can contribute to increased RTP campaign loading times. For example, a campaign with an embedded Marketo form may experience a small delay as the campaign loads the form from your Marketo instance, so it's one code loading another script, which then loads another. That can cause latency while the browser catches up, so the simpler you can make the code, the better.

Question: Is it possible to assign a lead owner during a list import? Answer: No. The reason for this is because lead ownership is a Salesforce functionality and should be first done from within Salesforce. If you are not able to do the assignment in Salesforce, here is one option that is available to you within Marketo: 1) Upload your leads into Marketo's Lead Database without lead owner information. i.e. your import CSV will not have any lead owner column in it. More information on importing leads can be found here: Import a List of Leads from a Spreadsheet into Marketo (Import List). 2) Once the list import is successfully completed and your leads are in Marketo, you can use the "Sync Person to SFDC" flow action to assign lead ownership. More information on the "Sync Person to SFDC" flow action at Sync Person to SFDC.

Issue You create a new field on the Lead and Contact objects in SFDC and two fields are created in Marketo, one mapped to Lead and the other mapped to Contact. Solution You will see this behavior if the an SFDC field is created on two objects across more than one sync cycle, one before a sync cycle starts and the other one during or after the sync cycle completes. To ensure both the lead and contact show up mapped to the same custom field Marketo, do the following Disable the global sync in Marketo. (Admin > Salesforce) Create the field on your desired objects in SFDC. Make sure they both have the same API name. Re-enable the global sync in Marketo, allowing the field in both objects to sync down to Marketo at the same time. If you find yourself with multiple fields in Marketo after the sync, contact Marketo Support to have the fields merged or remapped as necessary.

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 imageThis 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.

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 Multiple alerts are sent from the same campaign. Solution Recognize that Send Alert functions at the person level, triggering an alert for each individual in a campaign. Utilize Marketo's reporting to send a consolidated notification: Create an Email or Campaign Performance report. Tailor the report settings for the specific campaign. Schedule the report to be sent after campaign completion. This method provides a summarized notification, avoiding the repetition of alerts per campaign member. Alternatively, use Send Alert for individual notifications where needed, such as: Alerting a lead owner of a form submission. Triggering personalized alerts for specific lead activities.

Issue Does Marketo have an SLA for REST API? Solution No, Marketo does not have an SLA for REST API. Our REST API Responses time out after 30 seconds. Unless written within the subscription contract, there is not a commitment for Marketo to provide an SLA for REST API Responses. As mentioned in our API License document: http://developers.marketo.com/api-license/ in section 6 B: "B. No Support. Unless otherwise agreed to in writing, Marketo shall not be responsible for providing any support, maintenance, or other services (or level of service) to You or a user of the Software Application for the Marketo APIs."

Issue Often times customers ask which messages they should send to the Email Deliverability Power Pack seedlist. Consider these guidelines to prioritize. Solution Routinely seed from each IP/domain combination Prioritize seeding to any of the following: High priority segments (customers, employees, investors, etc. that have high strategic value) High risk segments (lapsed subscribers, new audiences, audiences that have not been mailed for more than 3 months) even if they are low volume Segments showing poor/declining performance (lower opens/clicks/conversions) Segments that reflect large audiences (weekly/monthly newsletters or operational notifications that go to the entire database) Setup a recurring campaign that sends to one (or more) of the templates on a periodic basis, especially if you see declining performance. Who This Solution Applies To Customers with the Email Deliverability Power Pack

Included in this Article: Tracking Clicks Potential Issues Segment Matches Few or No Visitors Segment Numbers Don't Match Google Analytics Tracking Clicks In order to better track how many people are clicking the content in the Recommendation Engine, you may wish to create a segment called "Recommended Assets" and include "*rcmd*" in the Specific Pages parameter. Go to the Segments page Create a new segment Drag the Include Pages field into the editor and include *rcmd* Recommended content will have "rcmd" in the URL. With this filter, the segment will only include website visits with "rcmd" somewhere in the URL, meaning it will include all visits to recommended pages. Potential Issues Segment Matches Few or No Visitors After making this change, you may see that the segment doesn't match anything or only shows a few visitors. In that case, verify that your Asset Discovery is working Segment Numbers Don't Match Google Analytics The numbers you see in the segment may not match the numbers you see in Google Analytics. Unlike Google Analytics, RTP segments count the number of visitors that matched the defined parameters, whereas the 'Site Content' report in GA counts the number of times the pages were viewed by visitors. This means that if the same visitor clicks on more than one piece of recommended content, in RTP only one segment match will be recorded whereas GA will record 2 page views.

If you are encountering issues with importing to certain fields, it is recommended that you create an import template. To make sure your field names are correct for an import, start by exporting a small list from your lead database. You can selected your required fields via the column chooser by right clicking a field in your list. Then select Export list under List Actions, then select Visible columns or All columns in your export. In the exported .csv file check the first row; your correctly named fields should be listed in there. You can now copy the field names to your import list, or copy the cells from your list to this exported .csv. You should now be able to import without issue. Please note: if you select All columns then the exported .csv file contains system fields that cannot be re-imported to. Please see the related article: Ignored Fields and Blocked Field Updates During List Import

Issue Description After running an A/B test, some Lead records appear to have received both Test and Winner. Issue Resolution In an A/B test, the sample size of the audience is sent the variants, and then for the winner: the entire audience minus the test audience is sent the Winning email. So let's say that you received both Test and Winner. This means you have duplicate records in the database. Marketo is designed to not send duplicate leads the same email at the same time. So one of the duplicates is qualified for the Test, and then when the Winner is sent, it's the total audience minus the test audience, the Winner is sent to the duplicate record. This above situation can apply to Lead Records as well, because of duplicates with the same email address, but also duplicate records that may have a FWD set up between them (record B emails FWD to Record A email address). Because this is expected from the design decision, the resolution is to deduplicate your database. Is this article helpful ? YesNo

Issue The Engagement Program has no engagement score more than 72 hours after the Engagement Program cast. Solution First, make sure that is has been more than 72 hours since the Engagement Program cast, since it takes some time for the engagement score to update. If you are using child programs in the Engagement Program stream, check the individual programs to see if leads have achieved a Success status in those programs. When programs are used as content in streams, the engagement score is based on program membership and success status, not email interaction (clicks, opens, unsubscribes). Also, if there are any campaigns in the child program that contain wait steps, the Engagement Score will not populate until the campaign is complete. docs.marketo.com/display/public/DOCS/Understanding+the+Engagement+Score

Issue Only three Engagement Program casts are shown in the Calendar but the program has more casts than that. Solution The Global Calendar is not designed to show every cast of an Engagement program. This is to prevent a customer's calendar from becoming overwhelmed with ongoing Engagement programs. The following do not show: Trigger campaigns Smart Campaigns that are not a child of a program Engagement casts more than 3 casts away

Knowledgebase

Maintaining a Directory of Leads Bouncing Emails

Top Blocklists - What You Need to Know

Customer Engagement Engine Training: Nurturing with Standard or Spark

Statistics section on a Marketo Landing Page asset

How Workspaces & Partitions work with reports in Analytics area

API User email address

WebEx Registration Fails With "Self registration is not supported by this service type"

Troubleshooting Web Personalization (RTP) Campaign Latency

Is It Possible to Assign a Lead Owner during a List Import?

Creating a New Field in SFDC Creates Two Fields in Marketo

My Marketo Campaigns Are Not Showing Up in Sales Insight

Assignment Rules used for Add to SFDC Campaign Flow Steps

Multiple alerts sent from the same campaign

How accurate is the geolocation targeting

SLAs for Marketo REST API

Email deliverability

Testing Deliverability Using the Deliverability Tools Seed Lists

Web Personalization (RTP) - Tracking Clicks on Recommendation Engine Content

How to create an import template

Received 2 Emails in the A/B Test: Test and Winner

Engagement Program Has No Engagement Score

Calendar Not Displaying All Engagement Program Casts