Knowledgebase

Featured article

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

Issue Description You need to revert a data value change for a field on multiple leads. Issue Resolution There is no way through the UI to "undo" a data value change (unless it was a boolean field, in which case there are only two possible values.) You can certainly use a Smart List to identify whose values have changed, but there no way to go back to the old value (unless it's stored elsewhere in another field or through another data store, along with the API). However, you can use the API to extract the data value change activity from the activity log, which would include the old and new values, extract the original values, then use the API to rewrite the old values back to the lead record. http://developers.marketo.com/rest-api/endpoint-reference/lead-database-endpoint-reference/#!/Activities/getLeadChangesU… Is this article helpful ? YesNo

Included in this article Overview Do you need to create fields in Salesforce and have them connect to specific fields in Marketo like for Lead Score or Acquisition Program? If so, this document will take you right to the instructions on how to get that done! Step by Step Directions for all Salesforce Editions Adding Custom Marketo Fields to Salesforce Video Overview Here's a video tutorial of the entire process that should make it easy to follow along: Salesforce Connector Setup Enjoy!

Issue Leads are members of a Marketo Program that is synced with a SFDC campaign, but there are some leads that have not synced to SFDC. Solution 1.) First check to see if this was caused by a Salesforce Sync Error. This can be checked in the Admin area under Admin > Salesforce > Sync Errors. Additionally, errors will appear under Notifications, check for the subject 'Salesforce Sync Error: Unable to Add Leads to Campaigns'. This will list the details of the SFDC Error and a list of sample leads along with the Salesforce campaign that they failed to sync to Example error: INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITY: insufficient access rights on cross-reference id Sample Leads: Salesforce Campaign lead1@mail.com Campaign name lead2@mail.com Campaign name 2.) This can also be caused by mismatched statuses between the Marketo Program and the SFDC Campaign. If the status doesn't exist on both sides, leads with the problem status can fail to sync. 3.) This can also be caused by a backlog for the program/campaign sync. Check with Marketo Support to see if a backlog is present. Who This Solution Applies To Customers using Marketo with Salesforce integrated

Issue Issue Description When trying to approve the Launchpoint connection between Marketo and Webex you receive the following error: FailedWebex API call error: validation: Parsing Error : An invalid XML character (Unicode: 0x1b) was found in the element content of the document.?Line : x? Column : xxx? [Webex exception ID = '999999'] Solution Issue Resolution This error is being produced by Webex. To resolve, go into Launchpoint and re-enter the login credentials. If error persists, delete and re-add the Launchpoint service as per documentation: https://docs.marketo.com/display/public/DOCS/Add+WebEx+as+a+LaunchPoint+Service Who This Solution Applies To Marketo customers integrated with Webex

Issue You receive a notification that the Salesforce sync failed with the error "SalesForce Sync Error: UNABLE_TO_LOCK_ROW" Solution This indicates that something else in Salesforce was writing to the record at the moment the Marketo Salesforce sync tried to make the update. Since only one "user" at a time can update a record, Marketo was unable to do so, and the sync failed. Marketo will retry an operation a few times if this keeps being received but will fail and move on if it happens too many times. If these have recently become common, you might want to look into any new API integrations to SFDC that you've deployed or any new AppExchange packages with your SFDC Admin to see if you might be able to tune it to avoid this collision. Who This Solution Applies To Customers integrated with Salesforce.

Update May 2021: Due to the release of CNAME Cloaking Defense with IOS and Safari 14 Munchkin cookies will be capped to a 7 day lifespan in Safari . What’s changing? On February 21, 2019, Webkit announced the new release of Safari’s Intelligent Tracking Prevention (ITP), known as ITP 2.1 and ITP 2.2 shortly thereafter. With ITP 2.x, all persistent client-side cookies, i.e., non-session cookies created via JavaScript through document.cookie, are capped to a seven-day or one-day expiry. Mozilla Firefox and Google Chrome have also announced their intent to conform to these new policies, though no details or dates have been released. How does this impact Marketo? As a result of these changes to cookie policy, 7 days after their initial tracked visit to your domain, the Munchkin cookies of visitors using Safari (or future affected browser versions) created with the existing versions of Munchkin JavaScript will expire, and on subsequent visits they will be tracked as a new visitor. How does Munchkin operate? On a person’s first visit to a page on your domain, a new anonymous person record is created in Marketo. The primary key for this record is the Munchkin cookie (_mkto_trk) which is created in the user’s browser. All subsequent web activity on that browser is recorded against this anonymous record. In order to be associated with a known record in Marketo, one of the following methods should be used: The person may visit a Munchkin-tracked page with a mkt_tok parameter in the query string from a tracked Marketo email link. The person may fill out a Marketo Form. REST Associate Lead call must be sent. Once one of these actions is completed, the cookie and all its associated web activity will be associated with the known record. How is Marketo planning to address ITP concerns? Marketo will implement a new web service to allow Munchkin cookies to be set with a Set-Cookie header via HTTP response, so that they may bypass the 7-day expiry cap imposed when setting cookies via JavaScript. Do I need to do anything to take advantage of these updates? In order to leverage the new behavior and take advantage of the greater expiry period and tracking capabilities, ensure that you have configured the following: A Landing Page CNAME Secured Landing Pages (i.e. HTTPS) For external pages, you must have configured a Landing Page Domain or Domain Alias with a Top-Level Domain (TLD) matching the external domains which you wish to track For example, if you have pages on the domain www.example.com which are tracked, you must have configured an LP Domain or Alias which is a subdomain of example.com, like munchkin.example.com What happens if I do nothing? Munchkin’s ability to track users across sessions on the same domain will remain limited by ITP to either 1 or 7 days based on the browser and browser version used by the visitor. As of this posting, this only affects visitors using the Safari browser, although Chrome & Firefox may follow suit with their own versions. When will the solution be launched? These changes will begin as a staggered roll-out to customers who have opted into the Munchkin Beta channel in conjunction with the January 2020 Marketo release. Once the solution has been released to all beta customers, the roll-out to our entire customer base will begin in mid-to-late February. All customers should expect to have the solution by end of March 2020. Google Chrome Update (Feb. 2020): Google recently announced that the Chrome browser will block all third-party cookies within two years; however, since Marketo uses 1st party cookies, this update regarding 3rd party cookies will NOT affect your Marketo tracking efforts. For further context about 3rd party cookies in general, and the industry shift away from using them, please see the following article for Adobe's stance across the Experience Cloud Solutions: https://medium.com/adobetech/an-adobe-perspective-google-chromes-announcement-on-the-future-limits-of-3rd-party-cookies-bbb7bb257fdb

Issue There are two filters available (Acquisition Program and Acquisition Program Name), but only Acquisition Program Name appears in the lead record and is available as a column in the lead views. What is the difference between these? Solution Acquisition Program is a system-managed field. It isn't available in many picklists, nor in certain filters. Acquisition Program Name is a field that allows you to use this data more freely as it is not locked by the system. Acquisition Program = Master naming for programs Acquisition Program Name = Friendly usable name

To enable Marketo to meet the performance demands of its customers, Marketo has a standardized Data Retention Policy used across the platform. This policy applies to the activities stored in the activity logs of people in your database. Activities and Data Retention There are three components to our data retention policy: a retention period of 14 days for one activity, 90 days for twelve high-volume activities; and a retention period of 25 months for other lead activities. Activity with Retention Period of 14 days Activities Retained for 14 Days Delete Lead Activities with Retention Period of 90 days The high-volume activities listed below will be retained for 90-days. After 90-days, these activities will be permanently deleted. Activities Retained for 90 Days Add to List Change Score Change Data Value Visit Webpage Click Link on Webpage Sync Lead to SFDC Sync Lead to Microsoft Sync Lead Updates to SFDC Update Opportunity Request Campaign Email Delivered* Send Email* * Email Delivered and Send Email activities change from 25 months to 90 days effective August 31st, 2020. More information here. Activities with Retention Period of 25 Months The activities listed below will be retained for 25 months. After 25 months, all such lead activities will be permanently deleted. The only exception is the New Lead activity, which will always be displayed in the activity log. All other activities will be deleted, but the New Lead activity will not, giving you a permanent record of when the lead was created and how. Category Activities Retained for 25 Months Web Click Predictive Content Click RTP Call to Action Fill Out Form Smart Campaign Add to Engagement Program Call Webhook Change Lead Partition Change Engagement Program Cadence Change Engagement Program Stream Change Program Success Change Revenue Stage Change Program Member Data Change Revenue Stage Manually Change Program Status Compute Data Value Enrich with Data.com Execute Campaign Interesting Moment Merge Leads Remove from List Resolve Ruleset Reward Test Group Variant Schedule Test Variants Send Alert Engagement Program Cast Push Lead to Marketo Social Click Shared Link Share Content Vote in Poll Email Click Email Email Bounced Email Bounced Soft Open Email Received Forward to Friend Email Sent Forward to Friend Email Unsubscribe Email CRM - Salesforce Add to Opportunity Add to SFDC Campaign Change Owner Change Status in SFDC Campaign Click Sales Email Convert Lead Delete Lead from SFDC Lead Assigned New SFDC Opportunity Open Sales Email Receive Sales Email Remove from Opportunity Remove from SFDC Campaign Resolve Conflicts SFDC Activity Sales Email Bounced Send Sales Email SFDC Activity Updated SFDC Merge Leads Add to Case Add to SFDC Custom Object Test (Contact) CRM - Microsoft Dynamics Add to Opportunity (Contact) Add to Opportunity (Account) Remove from Opportunity (Contact) Remove from Opportunity (Account) Update Opportunity (Contact) Update Opportunity (Account) Delete Lead from Microsoft Segmentation Add to Segment Change Segment Retaining Data Marketo’s data retention policy gives you a rolling 90-day view of certain high-volume activities and a rolling 25-month view of other lead activity data. To help prevent any actual data loss, Marketo has developed a Bulk Extract API that enables you to export this data directly if desired. Once exported, you will be able to host this information locally and utilize it in any way you deem necessary. Premium Data Retention Option Marketo offers a premium Extended Data Retention subscription option that will allow activity data to be stored for 37 months instead of the standard retention period of 25 months. The high-volume activities, however, will only be retained for 90 days even with the premium option. For more information, contact your Customer Success Manager.

Issue Issue Description You are unable to log into multiple instances at one time so you spend time switching between instances frequently. Solution Issue Resolution Chrome profiles can be used to log into multiple instances at the same time on the same computer in different chrome windows. Rather than logging out then logging into additional instances, you can simply switch between windows. Setup: Here is a 1 minute video that walks through the setup process: https://embed.vidyard.com/share/kpx65nDnwivFuRPyktmJgW? If you have not logged into google chrome: Click the main menu in the upper right corner Click Settings (or navigate to chrome://settings/) Under the people section click Add person Choose an avatar and give your profile a name If you have already logged into Google Chrome: Click your profile icon in the upper right corner of google chrome (next to the main menu button) Click Manage People Click Add Person Choose an avatar and give your profile a name. To access the profiles when you open chrome you can click your profile icon in the upper right corner of chrome then click the name of the profile you wish to access, this should open a new window you can use to log into Marketo.

Issue Issue Description A Smart List using a "Member of Program" or Member of Engagement Program" filter is qualifying people who are not members of the specified program, or not qualifying people who are members of the program. Solution Issue Resolution Check if you have the filter set to "Member of Program/Engagement Program = true, Program is not [program name]". If this is the case, the logic works a little differently than you may think - what this means is that the person can be a member of any program, as long as it's not the specified program. How you may want to set up the filter would be "Member of Program/Engagement Program = FALSE, Program IS [program name]". That indicates that you want people who are not a member of the specified program.

Issue Description When syncing records between Marketo and Dynamics, an error is received of "Marketo is unable to update the following records in Microsoft Dynamics" due to "A record was not created or updated because a duplicate of the current record already exists". Issue Resolution The reason for that error is due to custom de-duplication rules set up in Dynamics, specifically when Marketo inserts a lead record or updates lead and contact records. There are a couple ways this issue can be addressed: 1) Your team can review the custom de-dupe rules in Dynamics and open them up so Marketo can insert/update records. We recommend this step first! 2) There is a Support tool that will allow suppression of the de-duplication rules set up in Dynamics for the sync user. With this tool, the sync user will be able to insert leads for the first time or updating a lead or contact. This process isn't typically recommended as a first step because it can lead to duplicate records being created, but if you'd like the suppression enabled, please reach out to Marketo support with the details of your request. Who This Solution Applies To Dynamics Users

Issue An email program fails to send emails to a large number of leads/people in the Smart List. Solution Sometimes leads/people in your Email Program's Smart List will be skipped in the email send because they already reached their daily/weekly communication limit. You can confirm if this has occurred by following these steps: Open your Email Program. Change your view to Control Panel. Click on View Results in the top left panel to see a list of all activities attributed to the email program. Click on Filter > Custom. Select the Send Email box. Click the Apply button. Scroll to the bottom of the list. If the leads/people have been skipped due to communication limits, you will see that a large number of leads/people listed as "Skipped Lead already used up Daily/Weekly communication limit." You can check or adjust your Communication Limits in the Admin panel of your Marketo instance.

Overview: GoToWebinar will be conducting scheduled maintenance on Saturday, February 20 from 06:00 AM UTC - 10:00 AM UTC and Sunday, February 21 from 02:00 AM UTC - 06:00 AM UTC. During the maintenance window, users will not be able to start or join GoToMeeting, GoToWebinar, or GoToTraining sessions. Affected Marketo Engage Services: During the impacted timeframe, customer-facing webinars and APIs will be unavailable for Marketo Engage customers. Since APIs will be unavailable, Marketo Engage will not be able to sync, refresh, or transition records to “Registered” in GoToWebinar. To identify and resolve these errors, you can create a smart list that filters on any program with a New Status of “Registration Error” for the necessary channels as shown below. You can then navigate to the People tab, view the record details to see the Status Change event which failed for the record, and create a smart campaign to update the Program Status to “Registered”. If you have additional questions or experience any issues, please contact Marketo Engage support at https://support.marketo.com, or through any of the methods listed here.

Issue You may notice that the files under "Images and Files" folder are being crawled and indexed by search engines. Is there a way to ensure that they cannot be indexed? Solution To disable indexing for all assets in Design Studio > Images and Files, please contact Marketo Support. Support can disable indexing for all files in this folder. Please note, this is a global block. Support is not able to selectively block indexing for specific files.

Just joined the Marketo family? Want to learn more about how to use Marketo? Drop by one of our Office Hours! Group Office Hours are one-hour sessions for you to virtually connect with a marketing automation expert when you need personalized guidance and insightful advice. Office Hours are available weekdays at different hours to meet our customers' needs around the globe. Please note these open sessions are open to Launch Pack customers only. If you have not signed up for the service and would like to, please send an email to services@marketo.com. Prerequisites: You must be within 90 days of your Marketo subscription start date or have signed up for the service You must have taken the Marketo Core Concepts class What to expect: Marketo Expert facilitating the open group session Types of questions: How to/Best Practices/Strategy/On-boarding Upcoming Sessions: EMEA EMEA Office Hours: Monday, 2 PM GMT

Traditional Bounce Codes When you add the Email Invalid Cause to display as a Column to any of your Deliverability Smartlists, you will see a code value, and potentially a suffix as well, to help you understand the reason for the Bounce. Codes in the 400 range are generally Soft Bounces Codes in the 500 range are generally Hard Bounces Mail server administrators can create custom messages that accompany bounce codes Code Explanation 250 Mail accepted by receiving network 421 <domain> Service not available, closing transmission channel 450 Requested mail action not taken: mailbox unavailable (e.g., mailbox busy) 451 Requested action aborted: error in processing 452 Requested action not taken: insufficient system storage 500 The server could not recognize the command due to a syntax error. 501 A syntax error was encountered in command arguments. 502 This command is not implemented. 503 The server has encountered a bad sequence of commands. 504 A command parameter is not implemented. 550 User’s mailbox was unavailable (such as not found) 551 The recipient is not local to the server. 552 The action was aborted due to exceeded storage allocation. 553 The command was aborted because the mailbox name is invalid. 554 The transaction failed for some unstated reason. Enhanced Bounce Codes If a suffix appears after one of the codes above, it is an enhanced Bounce code Mail server administrators can crate custom messages that accompany bounce codes Code Explanation 5.0.0 Address does not exist 5.1.0 Other address status 5.1.1 Bad destination mailbox address 5.1.2 Bad destination system address 5.1.3 Bad destination mailbox address syntax 5.1.4 Destination mailbox address ambiguous 5.1.5 Destination mailbox address valid 5.1.6 Mailbox has moved 5.1.7 Bad sender’s mailbox address syntax 5.1.8 Bad sender’s system address 5.2.0 Other or undefined mailbox status 5.2.1 Mailbox disabled, not accepting messages 5.2.2 Mailbox full 5.2.3 Message length exceeds administrative limit. 5.2.4 Mailing list expansion problem 5.3.0 Other or undefined mail system status 5.3.1 Mail system full 5.3.2 System not accepting network messages 5.3.3 System not capable of selected features 5.3.4 Message too big for system 5.4.0 Other or undefined network or routing status 5.4.1 No answer from host 5.4.2 Bad connection 5.4.3 Routing server failure 5.4.4 Unable to route 5.4.5 Network congestion 5.4.6 Routing loop detected 5.4.7 Delivery time expired 5.5.0 Other or undefined protocol status 5.5.1 Invalid command 5.5.2 Syntax error 5.5.3 Too many recipients 5.5.4 Invalid command arguments 5.5.5 Wrong protocol version 5.6.0 Other or undefined media error 5.6.1 Media not supported 5.6.2 Conversion required and prohibited 5.6.3 Conversion required but not supported 5.6.4 Conversion with loss performed 5.6.5 Conversion failed 5.7.0 Other or undefined security status 5.7.1 Delivery not authorized, message refused 5.7.2 Mailing list expansion prohibited 5.7.3 Security conversion required but not possible 5.7.4 Security features not supported 5.7.5 Cryptographic failure 5.7.6 Cryptographic algorithm not supported 5.7.7 Message integrity failure Not all mail servers adhere to these standards.

Issue Issue Description "${button-link}" appears on the Email Link Performance report in place of the URL the buttons point to. Solution Issue Resolution To stop this "${button-link}" from appearing on the reports, edit the text version of the emails to replace the "${button-link}" with the URL the button points to. This occurs because the text version of the email didn't get edited to provide a valid button link. The "${button-link}" value is part of HTML templates and if the setting 'Copy HTML to Text version of email' is checked then those values get copied across. From there, if the text version doesn't get edited or reviewed after that copy over happens, tracked links for "http://${button-link}?mkt_tok=..." will be sent out for those leads that get the text version of the email in place of the URL the button points to. The next question after hearing this solution is often, "If this is just for the text version, who is reading the text version of emails?", and the answer is that it's probably automated link scanners or security software visiting the link and triggering the click to show on reports.

Issue Issue Description Unable to limit user access specific to certain programs or assets Solution Customization of user roles for assets (such as landing pages, emails, etc.) or programs is currently unavailable. However, you can control user access by limiting their permissions to specific workspaces, provided that Workspaces are enabled for your Marketo instance. Configure Protocols for Marketo

Knowledgebase

Maintaining a Directory of Leads Bouncing Emails

How to revert Data Value Changes

Adding Marketo Fields to Salesforce

Leads Not Syncing from Marketo Program to SFDC Campaign

FailedWebex API call error: validation: Parsing Error

SalesForce Sync Error: UNABLE_TO_LOCK_ROW

Browser Cookie Updates: How Marketo/Munchkin Is Affected

Difference between the Acquisition Program and Acquisition Program Name

Marketo Activities Data Retention Policy

Log into Multiple Instances with Chrome Profiles

Member of Program or Member of Engagement Program Filter Not Qualifying People As Intended

Dynamics Sync Error - "A record was not created or updated because a duplicate of the current record already exists"

Email Program Fails to Send Emails

GoToWebinar Maintenance Impact

Preventing Search Engines From Indexing Images and Files

New Customer Group Office Hours

Email Bounce Codes

Email Link Performance Report Shows "${button-link}" Instead of URL

Can We Customize User Roles Specific to Certain Programs or Assets?

Email Dashboard not Displaying Accurate Data

Using Tokens in Smart Campaigns