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 When you send an email that was cloned from a previous campaign and updated, the sent email shows the old content rather than the new content. Solution This can be caused by Dynamic Content in the email. If you clone an email with Dynamic Content but only update the default content, then the old content will be sent to leads who are not part of the default segmentation. Open the email in the editor and see what email elements are displayed in the Dynamic tab. Check the different segments in the editor and see which ones have the old content. You can update the dynamic content for each segment or simply make the content static, which will make the email use the default content for all leads.

Issue You are unable to log into Marketo because you need to be authorized on your device. Solution Marketo tracks authorized devices by IP. If you are logging in from a different network, such as a home or hotel network, your IP will be different and you may need to authorize or re-authorize your device. Also, some networks assign IPs dynamically, so even if you are logging in from a location and device you have used before, the IP address may have changed and you would need to re-authorize the device. You should receive an email with a code that allows you to authorize and log in. If for some reason you are not able to do so, please contact support and we can authorize your device for you. Another option would be to disable the IP restrictions in the Admin panel: Admin > Login Settings > Edit IP Restrictions.

Issue Description No data appears in the email performance report (configured for a specific time frame) even though emails have been sent to the leads. Issue Resolution The reason why the leads who were sent the email do not appear in the email performance report configured for a specific time frame is because "The Sent Date filter is based on the first date that the email was sent.". Email performance reports only show data for the first time an email was sent. docs.marketo.com/display/public/DOCS/Email+Performance+Report If the first time the leads that were sent an email falls outside of the specified time frame in the email performance report, the report will not show any results for those leads. Apart from that, it is also worth to check if the email performance report has any additional smart list filters that the leads may not qualify for. Is this article helpful ? YesNo

Issue You are using the Add to Program or Add to SFDC Campaign flow step and want to know if it's possible to assign a specific status when that flow step is used. Solution When you use the Add to Program or Add to SFDC Campaign flow step, Marketo will assign the first status listed in the Channel associated to that program. If you want to choose a different status, you can use the flow step of Change Program Status or Change SFDC Status. If the lead is not a member of the program or campaign, using the flow step of Change Program status will add them.

What is a Blocklist? Can I Still Send My Emails, or Are You Blocking Me from Sending? What Is a Spamtrap and Why Do They Matter? Can You Give Me the Spam Trap Address That Triggered the Blocklist So I Can Remove It from My Database? Can You Give Me More Information regarding the Blocklist Issue? What Is the Quarantined IP Range? I Sent This Email Campaign a While Ago. Why Am I Only Getting Notification of the Blocklist Issue Now, and Am I Still Blocklisted? The Blocklist Notification Went to the Wrong Email Address. Why Was It Sent to That Address? Which blocklists should I be concerned about? - Top Blocklists – What You Need to Know How do blocklist issues get resolved? What steps do I need to take to resolve the blacklist issue? - Blocklist Remediation

Issue Clicking "Automatically copy over from HTML" or "Copy from HTML" in the Email Editor fails to copy the contents over to the Text Only version of the email. Solution This can occur if there are no editable sections in the email asset. By default, Marketo automatically copies the text content of any Rich Text element that’s in your email over to the Text version. Marketo defines a Rich Text element inside of an email template as a section using either mktEditable or mktoText classes. If the email's HTML does not contain either class, then no content would automatically be copied over. Here is additional documentation related to Email Text Versions: https://experienceleague.adobe.com/docs/marketo/using/product-docs/email-marketing/general/creating-an-email/edit-the-text-version-of-an-email.html?lang=en A quick workaround would be to manually copy and paste the content you wish in the Text Version, and in the future build/use templates to make emails with editable sections.

NOTE - Only authorized support contacts from your organization can submit support cases. To tell if you are an authorized support contact or not, access the Support Tab and select Create Case. If you are not an authorized contact, you will receive the below screen. Please contact your Support Admin to be added to the Support Entitlement. 1. Go to Support. 2. Click My Case Management 3. Click on +Create A Case 4. Enter a Subject to see suggested articles on the problem. Select an article to open a new tab. Select the + if you would like to see the full subject of the article first. 6. Didn't find the help you needed? Enter your information into the required fields. Click Submit. Great! You've submitted a case. A support rep will reach out to you shortly.

Issue Is there a way to make a landing page only accessible through a form? In other words, if someone gets to the thank you page and then forwards that URL along, you don't want the next person to be able to access it without filling out the form first. Solution Marketo does not currently have functionality that can support this Use Case. If a Landing Page is approved, it's published on the web and if anyone has the URL then they can visit the page. That being said, perhaps there is some custom implementation that you can have a developer create. Here are two possible approaches: Custom coding that would look at the previous page of the visit; when accessing the Thank You page, if the Referrer is not the page with the form, then reject access or redirect it to display the page with the form Have the page submission pass along some kind indicator (URL Parameter) so that a reroute logic (on the thank you page) would run on that page all the time except when that indicator is present Marketo Support would not be able to assist in custom implementations. However if you were interested in a Professional Service Engagement we can explore the option of Marketo building this out for you.

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 How to disable the Marketo tracking token without disabling link tracking. Issue Resolution Within the <a> tag, you can add a specific class: class="mktNoTok" and this will disable the tracking token, and yet still allow the clicks to be tracked within the email. If you are proficient with HTML, you may be able to enter this unique class within the header, or other areas of the HTML doc. You can also disable this through the UI on a per-link basis. Instructions: here Is this article helpful ? YesNo

Issue The Facebook Lead Ads forms are not showing up in Marketo within filters/triggers. Solution If the Facebook Lead Ads form is not showing up in Smart List filters/triggers, check the following: 1. The user needs to be an admin on the Facebook account. 2. The user needs to have page admin access on the pages that they are subscribed to in Launchpoint. 3. At least one lead must have filled in the form with the form name recorded in the form filled out activity in Lead's activity log. If all these conditions are met and you are still not seeing the Smart List options, please contact Marketo support for further troubleshootig Who This Solution Applies To Customers integrated with Facebook

Issue Description A recent email send resulted in a number of leads specifically blocked by Communication Limits, as seen within the Results or Lead Activity Log. What are the re-sending options? Issue Resolution The Marketo Application does not offer any automatic re-sending/rescheduling functions within the campaign. If communication limits are low, and records are blocked from being sent emails, you may need to adjust the limits or set the necessary programs or campaigns to ignore communication limits. Enable/Disable Communication Limits in an Email Program - Marketo Docs - Product Documentation Apply Communication Limits to Smart Campaign - Marketo Docs - Product Documentation - you would need to undo this process in this case. Even if the records were not sent the email because of Communication Limits, they would still be made members of the campaign or program. If you were going to try to re-send these records that were blocked due to communication limits you could try this Filter combination: Member of Smart Campaign/Member of Program and Not Was Sent Email Those 2 filters will show you the members that were not sent the email, and then you could re-send them at a later time.

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 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 You may notice that there may be a block in SFDC that stop syncing unsubscribes from Marketo to SFDC. After fixing the block in SFDC the new unsubscribes will sync as expected. How to get all the unsubscribes that happened before this fix to sync into SFDC? Issue Resolution You would need to set up a campaign to reset the field value. Smart list: Unsubscribed = true Flow: Change data value "unsubscribed" -> False Change data value "unsubscribed" -> True That would take everyone who is currently unsubscribed, switch to false and then back to true. That should cause the true value to sync up to SFDC for all of those records. However, make sure you do this at a time when you are absolutely positive there are no email campaigns going out. Who This Solution Applies To Customers integrated with Salesforce Is this article helpful ? YesNo

Knowledgebase

Maintaining a Directory of Leads Bouncing Emails

Top Blocklists - What You Need to Know

Cloned Email Showing New Content But Sending Old Content

Does Marketo Event Check in app support different languages?

DMARC Policy Bounce in ToutApp

Unable to Log Into Marketo - Device Authorization

Email Performance Report returns no data

Status Assigned to Lead in Flow Step Add to Program

Blocklists: Frequently Asked Questions

HTML Email Not Copying Over to Text Only Version in Editor

Submitting a Support Case to Marketo Support

Smart List Cannot Be Added to Report Custom Columns

Smart list subscription "Download report"

Block Landing Page Access for Leads That Have Not Filled Out A Form

Webhook fails to update Marketo field

Keep Link Tracking, Disable Mkt_Tok

Facebook Lead Ad Triggers and Filters Not Available

Re-sending Emails 'Blocked By Communication Limits'

Setting up a Syndication ID for a social campaigns

REST API returning 611 errors

Sync past unsubscribes into SFDC

Adding SFDC link to the lead in reports