Knowledgebase

Featured article

Included in this article Overview Data you’ll get from Email Bounces Bounce Categories Hard Bounces Soft Bounces Bounce Details Building the Directory 1. Create 6 custom fields 2. Create a Program to house everything 3. Create a Static List 4. Create two Smart Campaigns Smart Campaign One - Logging Email Bounces with Bounce Details Smart Campaign Two - Remove Leads From the List After Successful Deliveries 5. Create Custom List View Showing Bounce Details Overview Bounce activities carry details for why the email was bounced, but it’s housed within the activity log entry, not in a field on the lead record, so it’s difficult to export that data. This article will show you how to extract that information to create a directory of leads bouncing emails and how to make the list automatically update. This will also create counters for bounces and successful re-deliveries after bounces happen. Data you’ll get from Email Bounces Bounce Categories Email bounces come in different types depending on why the email was bounced; Hard Bounces or Soft Bounces. Hard Bounces Hard Bounces come in two types, Category 1 and Category 2. Category 1 bounces are emails that have been marked as spam by the recipient mail server. Many email servers monitor blacklists or spam traps, so after de-listing with them, leads that have had a Category 1 bounce previously may be able to receive emails again. Category 2 bounces occur due to an email address that is invalid or doesn’t exist. Soft Bounces Soft Bounces come in three different types, Categories 3, 4 or 9. Category 3 bounces are usually temporary, caused by full mailboxes, timeouts, or throttling. Any email with this designation has been retried for up to 24 hours (36 for AOL). Category 4 bounces are caused by technical problems, Transient Failures, Admin Failures, DNS Failures. Any email with this designation has been retried for up to 24 hours (36 for AOL). Category 9 bounces are unknown, undetermined or gibberish details. Any email with this designation has been retried for up to 24 hours (36 for AOL). Bounce Details When an email is bounced, the recipient mail server includes details of why it was bounced. These are created by the admin of the recipient mail server and vary greatly, but most will give some explanation that can give valuable information. Email Bounce Codes Building the Directory 1. Create 6 custom fields You’ll need 6 custom fields, two DateTime fields, two Score fields, and two String fields Name the DateTime fields “Bounce Date” and “Email Delivered After Bounce”. Name the Score fields “Email Bounces” and “Deliveries After Bounces” Name the String fields “Email Bounce Details” and “Email Bounce Category” Directions for creating Custom Fields can be found here: Create a Custom Field in Marketo 2. Create a Program to house everything Use a default program type and name it "Directory of Leads Bouncing Emails". Info on creating programs can be found here: Create a Program 3. Create a Static List This static list will be your actual directory that contains all of the leads that are currently bouncing emails. Name it "Active Bounce List". Info on creating a static list can be found here: Create a Static List 4. Create two Smart Campaigns These two Smart Campaigns are what will be used to add and remove leads from your active bounce list. Info on creating Smart Campaigns can be found here: Create a New Smart Campaign Smart Campaign One - Logging Email Bounces with Bounce Details Your first Smart Campaign will be used to listen for any email bounces that occur. The campaign will populate the “Bounce Date”, “Email Bounce Category” and “Email Bounce Details” fields. It will then add one point to the “Email Bounces” score field which can be used to count how many bounces have occurred per lead. Lastly, the campaign will add the lead to the static list which will be an active directory of leads who are bouncing emails. Campaign Smart List Use the two triggers of “Email Bounces” and “Email Bounces Soft” in the Smart List. Set both triggers to “is any” so that they will fire whenever any email bounces for any reason. Campaign Flow The Flow of the campaign will have 5 flow steps. The flow will use a System Token and some Trigger Tokens, which can be used to pull details out of the action that activated the trigger. In this case, the Trigger Tokens will be pulling out the details on why the emails were bounced. That info is in the bounce message and is logged in the lead's activity log. Normally you'd have to comb through the activity log one at a time to find these details for each individual lead. This method, however, will pull the details out automatically for all leads. Flow Step 1: Change Data Value Attribute: “Bounce Date” New Value: {{system.dateTime}} Flow Step 2: Change Data Value. Attribute: “Email Bounce Category” New Value: {{trigger.category}} Flow Step 3: Change Data Value Attribute: “Email Bounce Details” New Value: {{trigger.details}} Flow Step 4: Change Score Score Name: “Email Bounces” Change: +1 Flow Step 5: Add to List List Name: “Active Bounce List” Smart Campaign Two - Remove Leads From the List After Successful Deliveries Campaign Smart List The Smart List of the campaign will need a trigger for “Email is Delivered” set to “is any” and also a filter of “Member of List” looking just for leads that belong to your Static List. This way, the campaign will only apply to leads who have had an email bounce but have then had an email successfully delivered afterwards. Campaign Flow The Flow of the campaign will have 3 flow steps to do the following; log when the email was delivered, add a point to the "Deliveries After Bounce" Score Field, and remove the lead from the "Active Bounce List". Flow Step 1: Change Data Value Attribute: “Email Delivered After Bounce” New Value: {{system.dateTime}} Flow Step 2: Change Score Score Name: “Deliveries After Bounces” Change: +1 Flow Step 3: Remove from List List Name: Operational.Active Bounce List 5. Create Custom List View Showing Bounce Details The custom fields you’ve created for email bounce information won’t show automatically in the view of your list. You can create a new view of the list to show just this information so that when it is exported it will give you only the email bounce information you need. Once the list has the necessary details, it can be exported with those columns included so that you can work with it. You can identify emerging trends and issues with your deliverability by looking for common themes among the bounce details. Directions for creating Custom Views can be found here

Featured article

(Article Updated - August 2024) Overview A blocklist is a database of IP addresses or domains that have been associated with the sending of unsolicited commercial email or spam. Internet Service Providers (ISPs) and business email networks use information from blocklists to filter out unwanted email. As a result there can be a drop to inbox delivery rates if the IPs or domains involved with sending email are listed on a blocklist. Marketo’s Email Delivery and Compliance team monitors blocklist activity on our IPs and domains daily. When an impactful listing occurs, we reach out to the blocklist, attempt to identify the sender that triggered it, and work with the blocklist organization to get the listing resolved. There are thousands of blocklists, most will not have a significant impact on your delivery rates. Below, we have compiled a list of the blocklists that commonly appear across our sender ecosystem. Each blocklist has been grouped into a top tier (Tier I) by most impactful, to the bottom least impactful tier (Tier III). These may have little to no impact across our sender network. Tier I Blocklist Spamhaus (SBL) Impact: Spamhaus is the only blocklist that we categorize as a Tier I for a reason: it has by far the greatest impact on delivery. It is the most well-respected and widely used blocklist in the world. A listing at Spamhaus will have a negative effect on your ability to deliver emails to your customer’s inbox and can cause bounce rates of over 50%. Evidence suggests that most of the top North American ISPs use Spamhaus to inform blocking decisions. How it works: Unlike many blocklists, Spamhaus lists senders manually. This means they are proactively watching sender activity, collecting data, and base listings on a number of variables. Most commonly senders are listed for mailing to spam trap addresses that Spamhaus owns. Sometimes Spamhaus will list senders based on recipient feedback as well. Next Steps: Please note that every Spamhaus email can be quite different depending on the information provided and the nature of the listing . Because Spamhaus has multiple types of listings, the remediation steps are based on which type of blocklisting has occurred. We have listed the most common types to affect Marketo customers, from most to least impactful. Impact can range from a full block of top severity, to a partial block that is less severe (CSS Data, DBL). If remediation isn’t performed and the problem not addressed, these listings can increase in severity and turn into a full blocklisting. Spamhaus Blocklistings Types SBL (full blocklisting) Considered the most impactful. Remediation steps: Our team monitors closely for Spamhaus listings. Once alerted to the listing, we send an email notifying the customer, and reach out to the Spamhaus contact to start the remediation process. Only a Marketo delivery team member should be in direct correspondence with the Spamhaus contact, to speak on behalf of the customer, and to relay their questions and instructions, ensuring quick resolution and reduced impact. Senders that trigger this listing on a shared IP range will be moved to a more isolated, penalty range (IPB), so as not to impact the other shared senders. Those affected on a Dedicated IP, only impact their own sending and will not be moved. However, depending on the severity of the issue, our team may need to revoke a customer’s ability to send any emails until full resolution. The listing will last until Spamhaus is satisfied that the offending sender has taken the appropriate steps to mitigate the problem. SBL CSS Customers are alerted of the listing with an email containing all the information needed to immediately begin the remediation process. This is part of an automated trigger listing, that allows for a customer to delist directly on the Spamhaus website, after they’ve completed remediation. Remediation steps: Customers will go to the Spamhaus IP lookup website, at https://check.spamhaus.org, where they can check on the status of their IP and continue to monitor it in real time, until it is no longer listed there. Follow the remediation and delisting instructions provided, and check for specific details in the blocklist notification email. DBL (Domain blocklisting) Customers will receive an email notification alerting of the company domain being listed. The email will contain specific information to help narrow down and identify which email source likely triggered it within Marketo. It’s important to note that any email sent from outside of Marketo, that contained the company domain, is suspect. This means, if the sender uses multiple IPs and/multiple email platforms, then any of those could be the source. Remediation steps: Follow the detailed instructions in the email, which will also provide a link to the Spamhaus Domain reputation checker webpage, to check the real time listing status of the affected domain. Once the email source is identified and cause addressed, this customer will follow the online instructions to request to be delisted. Tier II Blocklist SpamCop Impact: SpamCop is not used by any of the major North American ISPs to inform blocking decisions, but it makes it to the Tier II list because it can have a significant impact on B2B email campaigns. SpamCop is considered a Tier I one blocklist for B2B marketers but a Tier II for B2C marketers. SpamCop is a dynamic IP blocklist, that can affect a single IP or a subset of IPs Typically, the block will automatically lift within one business day, but can take longer for relisted IPs. To have triggered a SpamCop listing likely means the sender has a list management problem that should be addressed. How it works: SpamCop lists IPs for one of two reasons: Either the email hit SpamCop spam trap addresses OR A SpamCop user has reported the email unwanted. Most of SpamCop’s spam traps are previously valid addresses that have not been active for 12 months or longer. Remediation steps: If you are seeing a significant number of bouncing emails caused by a SpamCop blocked IP but aren’t sure if your email activity triggered the listing, first identify whether you are sending on a shared sender network or not. If sending from a shared IP range when this occurs, you or any other customer sending from the same network may have contributed to the IP block. This IP block will automatically get dropped within a business day. For those on a Dedicated IP that trigger a listing, refer to the above remediation steps and resources, to address the list management issue. Tier III Blocklist (Low/ No impact ) These are considered the lowest tier and therefore cause the least impact across the Marketo sender ecosystem. Some of these blocklists were more impactful at one time, while others are only impactful based on the sender region (Manitu). Others still can suddenly flare up (Lashback). There are also many blocklists that are ignored (0spam), and are not taken seriously because they do not provide any means to delist once on the list (NoSolicitado) or that they charge money to have the listing removed ( UCEPROTECT ). The pay-to-delist model is not well respected in the email industry. When using blocklist tool checkers, such as MXToolBox, many blocklists will appear, but very few are relevant. Here is our selection of Blocklists you may come across that are least impactful: Project Honey Pot SpamAssassin URIBL/SURBL DrMX PSBL 0spam HostKarma Ascams ZapBL Barracuda Trendmicro Inc. Cloudmark Proofpoint Invaluement ISP Blocklists Some ISPs use internal blocklists to make blocking decisions. Examples include AOL, Yahoo, Gmail, Outlook and Hotmail. If your IP is being blocked by one of these networks, and those networks have a large presence in your lists, a block of this kind could have a noticeable negative impact on delivery. Marketo monitors for significant ISP blocks. Those experiencing deliverability issues with emails not making it to the Inbox and bulking in the spam folder may benefit from additional services with our Email Delivery Consultants. Remediation Steps: Email Delivery Compliance Team works to resolve any ISP blocks. ISP blocks are are usually resolved or lifted within less than 24 hours of a delisting request. Customers experiencing significant blocks for Microsoft domains (outlook.com, live.com, microsoft.com), can submit a request to the delivery team to seek mitigation on their behalf. Additional Resources: Blocklist Deep Dive Abuse Report Deep Dive What is a spamtrap, or spam trap, and why does it matter? Blocklist remediation Blocklist resolution flowchart Successful lead reconfirmation What is a blocklist?

Issue Description Calls made to the REST API return response code 611 "System Error". Issue Resolution Submit a Customer Support ticket with the following information The full body of the REST API call including the endpoint being called The full body of the REST API response The date and time that the call was made Customer Support will work to diagnose the root cause of the error and the reason a more identifiable error code is not being returned instead. Is this article helpful ? YesNo

Issue Description How is syndication ID set up while setting up a referral offer Issue Resolution For a referrer to be given credit they must have a Marketo Syndication ID assigned. This can be done manually (directly on the lead record) or via the social campaigns' Offer Details > Fulfillment Goal > should be set to Referred Sign-Ups. Once you set that up, the referrer will get issued a "syndication id" and be part of that social campaign's participant's list.

Issue Description You come across a few leads who failed to sync to SFDC and would like to have the list of leads who faced the same issue. Issue Resolution Unfortunately Marketo doesn't have a specific type of filter to leads who failed to sync to SFDC. However if they are new leads who haven’t synced to SFDC, then you can filter them by using the filters "Person was created" and "SFDC Type" with condition "is empty". If you want to find the list of leads (previously synced to SFDC) who failed to sync among a particular group of leads, you can filter by following the below steps. 1. Create a new Boolean type field in SFDC namely "Sync Error?" and with the default value as "true". 2. Wait for the filed to sync into Marketo. 3. Create a smart campaign to select those group of records and the flow steps to change the value of the Boolean field "Sync Error?" to ”False" and then "Sync person to SFDC". 4. Once the campaign has finished running, you will be to pull a report on SFDC on the list of leads who have the value "True" for the field "Sync Error?". It means that the value was not updated to SFDC as the record failed to sync. With this list you will be able to select the records and resolve the sync issue. You can also create a smart list of leads who were never able to sync with the following filters: Lead was synced to SFDC : Assign to : is not empty SFDC Type: is Empty I would also suggest that you refer the below list of ideas to improve the visibility of sync errors. https://nation.marketo.com/thread/33692-marketo-salesforce-integration-needs-a-serious-overhaul-dont-you-sync Who This Solution Applies To Customers integrated with Salesforce Is this article helpful ? YesNo

Issue Description What happens when you enable "Send all Tout emails in my team through this server connection" within the SMTP Server settings on ToutApp.com Issue Resolution When you select "Send all Tout emails in my team through this server connection" within the Tout admin panel, this will provide the option to all standard users to either choose to use the ToutApp Email Servers or your company's own Email servers. If you decide to share the SMTP Settings with the team, t is recommended that you have your IT team setup a dedicated STMP/Email account to use as the Custom SMTP Credentials. Note: Each user can choose to either use the Tout servers or the configured & shared SMTP server. It is not applied automatically to all users.

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

Issue Description There is a discrepancy for certain emails between Email Insights and Email Performance Report. The data (e.g. sent, delivered, opened and clicked) are significantly lower in Email Insights for the emails as compared to the Email Performance Report for the same emails. Issue Resolution There is most likely a discrepancy because at the time Email Insights was first enabled "you’ll have four weeks of historical Email data in addition to all new email activity". There was no request to Marketo support to upload historic data beyond four weeks which would have included data for the emails above. This request relates to the notes below from the article: "We’ll give you a four-week period before you can request Marketo Support to upload your data" Supplement: Email Insights Launch Process - Marketo Docs - Product Documentation The solution is to request that Marketo Support backfill the report data so you have data for Email Insights beyond the four weeks. Who This Solution Applies To Customers using Email Insight

Issue Description Leads would be qualifying for a Smart List filter that was set up to only qualify those leads that had a date "on or before mm/dd/yy", leads that have null would also qualify for this filter when they should not. Issue Resolution When the field is left as null, by default Null value is treated as epoch timestamp (i.e, jan 1 1970). In this case it is recommended to change the filter date from "on or before" to "between" in order to exclude those leads that have null in the date field. Is this article helpful ? YesNo

Issue Description Email Link Performance report on the same email shows more clicks compared to clicks in the Email Performance Report. Issue Resolution Email Performance Report clicks shows the total number of leads who has clicked any link in that email. This count is independent of any links and how many times a lead has clicked any link on that email. Email Link Performance shows the number of unique people who clicked each link. It shows the number of leads who clicked that particular link. The same lead could’ve clicked another link. So in the total it would be counted as 2 leads in the report but in reality both are same leads. This is the reason why you see Email Link Performance report shows more clicks compared to clicks in the Email Performance Report

Issue Description The call Webhook flow is successful but the Marketo field mapped is not updated. Issue Resolution Marketo can translate data received by a Webhook to a lead field. If the fields are not getting updated: Check if the Response types are JSON or XML. The correct response type must be selected in order to map properties of the response back to lead fields in Marketo Check if the fields are blocked from Updates in field management. If the response type is XML, all elements in the XML hierarchy must be referenced in the mapping. For example: If the XML is: <?xml version="1.0" encoding="utf-8"?> <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <soap:Body> <GetDealerByPostcodeResponse xmlns="http://webservices.hmca.com.au/DealerLocatorMapService/"> <GetDealerByPostcodeResult> <xs:schema id="NewDataSet" xmlns="" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata"> <xs:element name="NewDataSet" msdata:IsDataSet="true" msdata:Locale=""> <xs:complexType> <xs:choice minOccurs="0" maxOccurs="unbounded"> <xs:element name="Table"> <xs:complexType> <xs:sequence> <xs:element name="dl_tradingName" type="xs:string" minOccurs="0" /> <xs:element name="dl_physicalstreetname" type="xs:string" minOccurs="0" /> <xs:element name="dl_physicalsuburb" type="xs:string" minOccurs="0" /> <xs:element name="dl_physicalstate" type="xs:string" minOccurs="0" /> <xs:element name="dl_physicalpostcode" type="xs:string" minOccurs="0" /> <xs:element name="pcmaplat" type="xs:float" minOccurs="0" /> <xs:element name="pcmaplng" type="xs:float" minOccurs="0" /> <xs:element name="maplat" type="xs:float" minOccurs="0" /> <xs:element name="maplng" type="xs:float" minOccurs="0" /> <xs:element name="distance" type="xs:float" minOccurs="0" /> <xs:element name="dl_phonenumber" type="xs:string" minOccurs="0" /> <xs:element name="dl_faxnumber" type="xs:string" minOccurs="0" /> <xs:element name="dl_emailaddress" type="xs:string" minOccurs="0" /> <xs:element name="dl_code" type="xs:string" minOccurs="0" /> <xs:element name="pd_postcode" type="xs:string" minOccurs="0" /> <xs:element name="dl_webaddress" type="xs:string" minOccurs="0" /> <xs:element name="dl_dealershipregion" type="xs:string" minOccurs="0" /> <xs:element name="dl_deliverycharge" type="xs:float" minOccurs="0" /> <xs:element name="dl_regionstate" type="xs:string" minOccurs="0" /> <xs:element name="BkAServiceDesktop" type="xs:string" minOccurs="0" /> <xs:element name="NewWinBkAServiceDesktop" type="xs:string" minOccurs="0" /> <xs:element name="BkAServiceMobile" type="xs:string" minOccurs="0" /> <xs:element name="NewWinBkAServiceMobile" type="xs:string" minOccurs="0" /> </xs:sequence> </xs:complexType> </xs:element> </xs:choice> </xs:complexType> </xs:element> </xs:schema> <diffgr:diffgram xmlns:msdata="urn:schemas-microsoft-com:xml-msdata" xmlns:diffgr="urn:schemas-microsoft-com:xml-diffgram-v1"> <NewDataSet xmlns=""> <Table diffgr:id="Table1" msdata:rowOrder="0"> <dl_tradingName>Wild West Hyundai</dl_tradingName> The Response attribute must be: soap:Envelope.soap:Body.GetDealerByPostcodeResponse.GetDealerByPostcodeResult.diffgr:diffgram.NewDataSet.Table.dl_tradingName All the elements need to be referenced in the top down approach.

Issue Description Getting the following error when trying to push leads to Salesforce as members of an SFDC Campaign. Failed: CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY: RHX_PRO_NQ.RHX_PRO_CampaignMember: execution of AfterInsert caused by: System.QueryException Issue Resolution This error is generated from Salesforce when the Marketo Sync User does not have permission to view the members of a particular Campaign in SFDC. In this case, you can try manually adding one of these Leads as a Campaign Member in SFDC while logged in as the Sync User. Also, check with the Salesforce Admin for the required permission for accessing the associated SFDC campaign. Who This Solution Applies To Customers integrated with Salesforce Is this article helpful ? YesNo

Issue Description After syncing a Dynamics Custom Entity to create it in Marketo, not all constraints appear as options when setting up filters for the custom entity in a Smart list. Issue Resolution When a custom entity is added after the initial sync, it may not end up with a direct relationship in the database. To resolve this, fully refresh everything to see if that helps re-establish the relationship using the following steps: Remove all the references from this entity (which you can see under Object Properties: Object Used By") Disable the custom entity Refresh schema and re-sync the custom entity Who This Solution Applies To Customers using MS Dynamics Custom Entities Is this article helpful ? YesNo

Issue Description Additional domains or subdomains need to be configured for Web Personalization (RTP) Issue Resolution If you want to add a new domain, check your subscription or contract to see how many additional domains are included. Your Customer Success Manager should be able to provide this information If not all entitled domains are configured in Marketo, reach out to support to add the domain(s) If all entitled domains are configured in Marketo, reach out to your Customer Success Manager to purchase more. If you wish to add a subdomain, reach out to support as additional subdomains do not incur a cost. Who This Solution Applies To Customers using Web Personalization

Issue Description You want to measure who clicks a specific link that uses a query string from a landing page, but when you try to use this logic in a smart campaign or smart list, it tells you the URL can’t be found, even though you can see the URL embedded on the landing page. Issue Resolution If you are using the link "marketo.com/company/contact/?firstname=test", then you need to seperate the url into the link and the query string. The root domain (Link in the filter/trigger) will be marketo.com/company/contact/ and the query string (from Add Constraint dropdown) will be firstname=test. This will allow you to correctly track the links you are wanting. Make sure that you have the correct Web Page associated as a constraint as well. For a better understanding of what query strings are, they are the parameters that are preceded by the "?" in the url. Is this article helpful ? YesNo

Issue Description Are smart list filters that accept text values case-sensitive (e.g. First Name, Last Name)? Issue Resolution Smart list filters are NOT case-sensitive. For example: If you use the smart list filter 'First Name is John', it will return leads with First Name 'John' or 'john' with a lower case 'j' Vice versa: If you use the smart list filter 'First Name is john', it will return leads with First Name 'john' or 'John' with an upper case 'j' Is this article helpful ? YesNo

Issue Description A lead record is deleted on Marketo but available on SFDC. Is it possible to recreate the record on Marketo? Issue Resolution Yes, it is possible to re sync the record from SFDC to Marketo by updating the value of any field for that record on SFDC. By doing so, it will update the time stamp which in turn creates/updates the record into Marketo. However the newly created record will not have the past activities of the record that was present prior to deleting the record on Marketo. If the record does not sync back to Marketo, make sure it is visible to the Marketo sync user and that you do not have a sync filter in place preventing it from coming back across. Is this article helpful ? YesNo

Knowledgebase

Maintaining a Directory of Leads Bouncing Emails

Top Blocklists - What You Need to Know

REST API returning 611 errors

Setting up a Syndication ID for a social campaigns

Filter out the list of leads who failed to sync to SFDC

ToutApp Custom SMTP Team settings and how they work

Email server used when sending Tout Emails from Salesforce

Change Lead Owner shows "Synched from salesforce.com - fixup Lead Owner"

Discrepancy between Email Insights and Email Performance Report

Lead qualifies for Smartlist filter utilizing "on or before" date filter when lead has no date in the corresponding date field

Email Performance Report and Email Link Performance report showing different click counts

Webhook fails to update Marketo field

CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY

Link performance report for specific campaign/program emails

Adding SFDC link to the lead in reports

Dynamics Custom Entities - Constraints do not appear for Smart Lists

Configuring additional domains or subdomains in Web Personalization (RTP)

URL not appearing on filter for Smart Campaign or Smart List

Email Performance Report send count is lower than the campaign results for Send Email

Smart List filters case-sensitivity

ToutApp: Unable to delete Template categories

If a record is deleted from Marketo but not SFDC, is there a way to re-create the record back in Marketo?