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?

How do I verify that my tracking link domain is secure? There are two primary methods for verifying that your domain is secure; by testing within a web browser and using a third-party SSL checker. Verifying Domain Security Through Web Browser 1. In your Marketo instance, navigate to Admin --> Email 2. In this link https://<your_tracking_domain>/trk?=ping, replace <your_tracking_domain> with your actual tracking domain. 3. Enter this link into your browser and click Enter. 4. Click the padlock at the left of the URL in the address bar. 5. In the pop-up box, verify that the certificate is valid and shows no security warnings. Verifying Domain Security Through Online Service You can also verify your SSL certificate to make sure it is correctly installed, valid, and trusted using the SSL Shopper SSL Checker tool. This is a third-party tool not owned or operated by Marketo, but it is a useful resource many utilize. 1. Navigate to https://www.sslshopper.com/ssl-checker.html 2. Type in your branded tracking domain you wish to verify. 3. Click "Check SSL". 4. Ensure that all check marks are green. If all check marks are green the certificate is valid and your domain is secure.

Issue Description In sent emails, if the system token {{system.viewAsWebpageLink}} is used, the link will load successfully on web browsers. However on the same browser session, after refreshing the page once, the link will return an error "Cannot get email content- Customer does not belong to any POD". Issue Resolution After Marketo's 2019 Q1 release, a security enhancement has been set for Marketo emails. When loaded on a browser, a View as Webpage Link will include the recipients' unique mkt_tok parameter. If recipients of the Marketo emails were sharing these links, this would mean that they are also sharing their unique/private mkt_tok with third parties. With this enhancement, the view as webpage link is only expected to load once and the mkt_tok value which is contained in the link will disappear after the page has loaded. With the removal of the mkt_token value on the link, hitting refresh will send a request to Marketo that does not contain the recipient's lead and email information, so there is no data for the link to return.

Issue Description Importing a program from one subscription to another is failing and is returning the following error sent via email: Marketo encountered an error while importing [Program Name] The token "lead.First Name" is not available in the destination subscription. It is either a custom field that you have to create or need to be synced from your CRM system, if you use one. Issue Resolution Check if there is any malformed lead.First Name token in email Check if there is any malformed lead.First Name token in email template used by the email(s) in the program Check if there is any malformed lead.First Name token within a program token Check if there is any malformed lead.First Name token within smart campaign flow step(s) This error has been known to occur when the email template had a lead token coded as follows, with a line break between 'First' and 'Name': {{lead. First Name}} Note: In this scenario, the error message received via email is actually referring to the token in the email template that contains a line break between 'First' and 'Name' but is stripped out on the message when HTML is rendered. Who This Solution Applies To Customers importing programs between two instances

Issue Description Naming conventions of email in email performance report Issue Resolution Email reports will use an email's full label including the program it exists in. Although asset names cannot duplicate within Programs, they can be duplicated within the whole Instance and Email Performance Reports have access to emails from an entire instance. For example if you had two newsletter programs, both with an email named "October Newsletter" the full program name can help differentiate between the two. NL-2018-10-Technology Program.October Newsletter NL-2018-10-Industry Program.October Newsletter The email report will always display with the full email name including the program it was created in to avoid this confusion. Even within a specific Program Report, you can access all emails within the Instance.

Issue Description Example: Person A was sent an email from Marketo, clicked on a tracked link in an Email to a tracked web page, but the web page activity was recorded on Person B Issue Resolution This can happen if Person A and Person B are sharing a computer. Prior to Person A clicking on the track link in the email to redirect to the tracked web page, Person B was already 'cookied' as a known lead on the same computer and web browser. In Marketo, once a lead becomes known, cookied and tracked on a web browser, any tracked web activities on that browser will be associated to the first cookied lead until the cookie is expired or deleted. Note: to confirm that Person A and Person B are using the same computer and web browser, you can check the details of the most recent web activities and compare if their User Agent and Client IP address is the same.

Issue Description In an attempt to approve an email, a 'Not Allowed' error message is being displayed with the following details: {{lead.Email Address}} : Token key not found Issue Resolution Check that token syntax is correctly inserted with no missing left or right 'curly' brackets '{{' '}}' Check that the field name of the token does not have any incorrect spelling (e.g. Email Address) If the token syntax is correct and the field name of the token is spelled correctly, it is possible that the field name of the token contains a Unicode non-breaking space (e.g. between 'Email' and 'Address'). This would have been inserted if it was copied across from a platform that was encoded with Unicode (e.g. Microsoft Word) - To rectify this, delete the space in the token and re-insert it with a normal space using the spacebar on the keyboard. Once this is corrected, the email approval should work.

Issue Description Integration is not able to see a webinar that has been set up as a "Simulated Live" record type in GoToWebinar Issue Resolution This is not currently possible as the Launchpoint integration between GoToWebinar and Marketo does not utilize version 2 of the GoToWebinar API and v2 is required for "simulated live" (recorded) webinars. Who This Solution Applies To Customers integrated with GoToWebinar

Included in this article Overview Your Premier Support entitlement has been enhanced with a Premier Success Team. Now, your Named Support Engineer is part of a 5-member Premier Success Team whose members work in concert to provide a full range of complementary skills. All your Premier support features remain intact (Mentoring Sessions, Accelerated SLAs, etc), but now your Named Support Engineer will be backed by a focused team of Premier Support Engineers to deliver world-class support tailored to meet the needs of your account. Benefits Each team is led by two Lead Support Engineers, and aided by three Premier Support Engineers. With a larger team, your engineers can specialize in specific knowledge areas, and we can connect you with our most senior engineers for your half-yearly instance reviews and mentor sessions. This will help to increase case resolution speed, decrease escalations, and elevate your overall support experience. Your Team Bethany Sweet, Senior Technical Support Engineer Bethany has been with Marketo Support since 2015. She Specializes in Deliverability & Microsoft Dynamics CRM, and letting Brian get out of line In her free time Bethany participates in tabletop gaming and going outside Dietrich Struble, Senior Technical Support Engineer Dietrich has been with Marketo Support since 2014, and Premiere Support since 2016. Marketo Certified, he specializes in Deliverability and keeping Brian in line In his free time, Dietrich enjoys PC gaming and gardening Brian Burks, Technical Support Engineer Brian has been with Marketo since 2017, and specializes API, Coding, and fierceness In his free time Brian participates in tabletop gaming and staying indoors Tamar Borneman, Technical Support Engineer Tamar has been with Marketo since 2016. She specializes in RTP and is MCE Certifiable In her free time Tamar participates in tabletop gaming and staying indoors Gio Alvarez, Associate Technical Support Engineer Gio has been with Marketo since 2017 and is a native of Texas. In his free time Gio participates in tabletop gaming and staying indoors.

Issue Description When using a Change Data Value flow step for a datetime field type and manually entering in a date and time, the time is displayed, but removed from flow step upon refresh. Issue Resolution The reason that the time is removed is because the display field in the flow step is a calendar picker (the drop-down). Calendar pickers do not support displaying the time. It is meant to select a date on the calendar and display that date. It appears to store the value to the record when manually entered in the field, but it will not remain upon campaign refresh.

Issue Description Why is the number of records shown in the Opportunity Analysis report in Revenue Explorer different from the number of records shown in a smart list with the same filters? (e.g. 100 records in Opportunity Analysis vs. 200 records in smart list) Why are some records in the smart list do not appear in the Opportunity Analysis report? Issue Resolution The attribution settings is set up to report on "Explicit: Only contacts with roles (default)" This means, the records in a smart list that do not appear in the Opportunity Analysis Report in RCA, are contacts without roles. Who This Solution Applies To Customers using Revenue Cycle Analytics

Issue Description Whenever a lead enters Marketo, it is being deleted automatically. Issue Resolution Marketo will never delete any lead records on its own unless you have setup a trigger or batch campaign to do so. We suggest you to review your campaigns in Campaign Inspector and check for the campaign that is using "Delete Person," or "Delete Person from SFDC" with the value true for "Delete in Marketo." If you have figured out the campaign and you would like to restore the deleted leads, contact support (https://nation.marketo.com/docs/DOC-1670-about-support) and they may be able to restore the deleted leads with a buffer period 30 days from the date of lead deletion. Is this article helpful ? YesNo

Issue Description G tags such as <g class="gr_ gr_19 gr-alert gr_gramm gr_inline_cards gr_disable_anim_appear Style multiReplace" id="19" data-gr-id="19"> </g> are added to the HTML edited in the TinyMCE Editor Issue Resolution This code is caused by the 3rd party browser extension Grammarly when an edit to an text component is made. This is not something in Marketo's control due to how Grammarly is modifying the text. Is this article helpful ? YesNo

Issue Description Currency type fields are changing unexpectedly. It may appear that they are being rounded off at first glance, but a better description is that they are being approximated imprecisely. This is a feature of all floating point values. For example: if you enter the value as 8092384905, Marketo will truncate it to 8092390000. Issue Resolution This is an expected behavior. Currency type fields are stored as single precision float values which have 6-7 digits of significance. Since standard fields type cannot be changed, we suggest that you create a new custom field to hold the currency value. Human-readable Values: Strings Often the easiest work-around for larger currency values is to use a field of type "String". String fields are adequate for storing a value, but do not offer the capability to compare (between, greater than, less than, at least, at most) values. Comparable Values: Integers To preserve comparison capability, store the value as an integer which can take on values from -2147483647 to 2147483647. For US Dollars, this integer can represent the number of cents (pennies) and therefore currency values from ($21,474,836.47) to $21,474,836.47. Using this technique, the operators between, greater than, less than, at least, and at most will work, just remember you're what you're comparing: cents in this example. Even Larger Comparable Values: Compound Integers If even larger values are required, two integer fields (large and small) can be used to represent currencies (again, assuming cents) from ($46,116,860,141,324,206.00) to $46,116,860,141,324,206.00. To break up a currency value into two fields, divide the number of cents by 2147483647 and store in the large value field, then store the remainder (modulus) in the small value field. To compare a compound (two fields) value, compare the large values first and if they are equal, then compare the small values. Since compound fields will be hard for a human to read, it may be prudent to also store the value as a string depending on your requirements. Is this article helpful ? YesNo

Issue Description You have developed a Marketo landing page and enabled Personalized URLs (PURLs) for your records, but when people visit the PURL form pre-fill does not take place. Issue Resolution When a person visits a PURL landing page, the form pre-fill checks their Munchkin tracking cookie to identify what values to populate for the form fields. If that person has a Munchkin tracking cookie associated to a known record in the database, it will pull and populate the information from that record. However, if this is the first time this person has visited a Munchkin tracked page or their browser is tied to an anonymous record, the pre-fill will not populate any information into the form. The customer/prospect will need to fill out a form or click on a tracked link in an email sent from Marketo. This will allow future PURLs that people visit going forward will have pre-fill populate as their cookie will be tied to a known record in the database. The web page visit will be associated back to the know record for the PURL. Additionally, you can also use Person related tokens on the landing page and those will resolve. For examples having the token in the text that states {{lead.First Name:default=Default}} within the body of the landing page will populate with the expected persons first name for the PURL they visited. This is because the token generation goes through a different path on the back end for PURLs. Is this article helpful ? YesNo

Issue Description Your phone calls are not logging to Salesforce Issue Resolution Tout Phone is a great way to get your call information logged to Salesforce, but there are a couple things you will want to be aware of when using the log a call feature. 1. The Contact must have a Salesforce ID attached to them. 2. We currently do not log calls to Opportunities. Who This Solution Applies To ToutApp customers Is this article helpful ? YesNo

Issue Description You sign up for ToutApp and receive a notice that your account is under review or your account is not verified. Issue Resolution If you sign up for ToutApp using a generic email address such as Gmail, Yahoo, Hotmail, Outlook or other email providers your account may require verification by Marketo Support. Please contact Marketo Support with the following information. Company Name: Business Address: URL(s) of your primary Web site(s): What is your average weekly and/or monthly email volume? Do you purchase, or have you ever purchased lists of leads? If yes, which providers have you used and when was your last purchase?

Issue Description A lead ran through a smart campaign and should have been sent a push notification but there is no activity of this happening even though the lead is a member of the campaign. Issue Resolution Assuming other leads are receiving the push notification (which suggests the app itself is not to blame) the first thing to check is the lead record itself. If the lead is marked as Marketing Suspended or Black Listed, this will prevent the record from receiving a push notification. Mark these fields as "False" and send the record through the campaign again, the lead should now be sent the push notification. Who This Solution Applies To Customers using Marketo's mobile app integration

Knowledgebase

Maintaining a Directory of Leads Bouncing Emails

Top Blocklists - What You Need to Know

Secured Domain for Tracking Links: Domain Verification

Email Viewed as Webpage Returning an Error after Refreshing Browser - "Customer does not belong to any POD"

Error Importing Program – Token Is Not Available in the Destination Subscription

How are emails named in an email performance report?

Person’s Web Activity Was Recorded on Another Person Activity Log

Error Approving Email - Token Key not found

Simulated Live webinars on GoToWebinar not syncing

Learn More About Your Success Teams, Team Delta

Time is removed from flow step for a datetime field

Opportunity Analysis report vs. Smart List with same filters

Leads are being deleted automatically upon creation

<g> tags being added to email text

Currency type field is rounding off its value

Personalized URLs are not working for Form Pre-fill

Tout phone calls are not logging to Salesforce

ToutApp: How to customize call outcomes in Salesforce

Exporting contacts in ToutApp

Edit schedule email in ToutApp

ToutApp account under review

Push Notifications not Sent