Knowledgebase

Featured article

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

With the evolving best practices and awareness around data privacy, Marketo will be upgrading how we handle form pre-fill. What change is being made? Starting April 24, 2019, Marketo will only pre-fill form fields if the URL used to navigate to the Marketo landing page contains a valid mkt_tok URL parameter value (which occurs when users click tracked links in Marketo emails). What that means is, any time a person is viewing a Marketo landing page with a form, the URL being used must contain the mkt_tok token in the query string, otherwise the form on that landing page will not be pre-filled. If the URL in the browser window does have a valid mkt_tok tracking token, then the form within the page will pre-fill as expected with data corresponding to the person record associated with that mkt_tok. Also note that if you are embedding Marketo Landing Pages within other web pages using an <iframe>, the mkt_tok would need to be passed from the parent page to the <iframe> URL if you intend for form prefill to work within the <iframe> How did it work before? Previously, Marketo landing pages would rely on Munchkin tracking cookies to identify known person records, and forms would pre-fill based on that cookie. Form pre-fill did not require being linked to a Marketo landing page from a tracked email link. Why is this changing? This upgrade is being made to provide a more consistent and more secure experience with Marketo’s forms. We have identified that, in the past, people have experienced scenarios where data pre-filled into a form didn’t always correspond with the actual person viewing the page. For example, people using a shared computer or those who may have been cookied incorrectly by clicking through a forwarded email, could end up viewing incorrect data associated with a different person. To provide a more consistent customer experience, and as a security enhancement, Marketo is upgrading the conditions under which the form pre-fill will display known customer information. In short, pre-fill will only work when users clickthrough links in Marketo emails, demonstrating that they have ownership of the email address associated with the known person record. Below is a list of different scenarios and how form pre-fill will work moving forward. Please note, these changes to form pre-fill will not affect any other functionality of Marketo Forms, including the progressive profiling feature. Scenario Will the form pre-fill? Notes Clicking a tracked link in a Marketo email to a Marketo landing page with a form which has pre-fill enabled Yes The email link must have mkt_tok enabled. Links that are not tracked or that have mkt_tok disabled will not work. Navigating directly to a Marketo landing page with a form which has pre-fill enabled No A direct link to the landing page will not have the mkt_tok present in the HTTP request. Refreshing a Marketo landing page with a form which has pre-fill enabled No The mkt_tok is stripped from the URL after Marketo Landing Pages load so refreshing the page will not include the mkt_tok in the URL. As a result, pre-fill will not work. Clicking a link in a sample email to a Marketo landing page with a form which has pre-fill enabled No The sample email will not have a valid mkt_tok attached to the link and so will not pre-fill the form. If you wish to test form pre-fill you will need to use a real email from a Marketo campaign. Navigating to a non-Marketo page that includes an embedded Marketo form which has pre-fill enabled No This behavior does not change with the upgrade. Pre-fill has never been supported for Marketo forms that are embedded on non-Marketo pages. Navigating to a non-Marketo page that includes an <iframe> pointing to a Marketo Landing Page that includes a form with pre-fill enabled With custom implementation The form within the Marketo Landing Page that is being loaded in the <iframe> will pre-fill if the mkt_tok value from the original HTTP request is passed along to the <iframe> URL Visiting a Marketo page with a mkt_tok that is not associated with the same person record as an existing Marketo Munchkin cookie currently stored on the browser No This will prevent the wrong person’s information from being displayed in cases where a computer is shared, or an email with a mkt_tok tracked link is forwarded to another person that may already be cookied as a known person in your database. Copying a Marketo tracked link from an email and sharing/pasting it externally (email, blog, chat, social media post, etc.) that enables another individual to click the tracked link Yes The tracked link in a Marketo email will redirect to a URL with the mkt_tok included, so anyone clicking this link will reach a page and see pre-fill data associated with the known person record from the “to” line of the email.

Issue You have been receiving form submissions that appear to have bogus/nonsensical data in the fields, such as "kjsag@sm4.to" for email address, or "111-111-1111" for phone number, or in a Comment field other random nonsensical text. Solution Currently, there are no default settings in Marketo that prohibit a form submission if the required fields are filled out. A great workaround for addressing these bogus form submissions in Marketo is to implement a 'honeypot' field on the form. To do this, you will need to create a custom Marketo field, string type, and name it something distinctive (such as "spam" or "honeypot"). After creating this field in Marketo Admin > Field Management, place this new field on the form as a hidden field. Real live end-users do not see hidden fields, but spam bots will see them and fill out all available fields. So now when we see form fills with this honeypot field "not empty," we know that it was a bot fillout. Setting up the Honeypot Field Say that you have a Trigger Campaign that's having some issue with these spam/bogus form fills. In the flow of this campaign, you can add a flow step at the top: Remove from Flow, with a Choice. Choice: If Honeypot field Is not empty, then remove from flow Default: do nothing This way, the lead record is removed from the flow. You can also have other campaigns to handle these bogus form fills, such as a daily recurring batch to delete the record. Other Options Another method of dealing with bot fillouts is to enable a reCaptcha. In fact, a very prolific Marketo user has written custom code that you feasibly could use to enable a reCaptcha on the form! Check this out: https://codepen.io/figureone/pen/meybqN?editors=0110

Issue How "And/Or" logic is applied to constraints in Smart List filters and triggers. Solution In Smart List filters, additional constraints act as "and" logic. Example: Was Sent: [this email asset] between this date range min number of times: 2 will function as Was Sent: [this email asset] -and- between this date range -and- min number of times: 2 When you have multiple values inside a single constraint, that is "or" logic. Was Sent: [this email asset OR that email asset] There is not a way to change the logic of constraints, so if you wish to have some sort of 'Or' between constraints then you would have to use multiple filters with 'OR logic between them.

Issue When attempting to move a folder with a program into a different workspace, the below exception is thrown: Rule is incomplete, '<Field Name> is...' requires value In the below example, the field name is 'New Status ID': Solution This exception is thrown when a smart list within the Folder contains an incomplete filter. To resolve, you can either: 1. Remove the Smart List filter that is incomplete 2. Set a value for the Smart List filter

Issue After creating an Email Program with an A/B test, you create smart lists (or smart campaigns) and would like to use filters such as "Opened Email" for the A/B test email. When starting to type the A/B test email name into the smart list filter, the A/B test email name does not show as available to select (it may show a red squiggly line). Solution The Email Program (with the A/B test) needs to be in "Approved" status before the A/B test email assets can be entered into a smart list filter.

Summary Flow step choice condition for "Person was Deleted from SFDC" with 'in past' "7 days" causes campaign failure Issue This flow step choice type causes a campaign failure because it is not supported. This is expected behavior. Solution Customers have to use Member of Smart List as indirection for the desired filter condition. i.e. Create a new Smart List with the "Deleted from SFDC" filter. Then change this failing flow step choice to use 'Member of Smart List' with the Smart List just created. Example flow step:

Issue My token is not displayed correctly in view as webpage version of email. Environment If customers manually type a {{my.token}} and use uppercase M such as {{My.token}}, then the view as webpage version of email may not render that token as expected. The feature to HTML encode lead tokens (source of external data) for security reasons, applies to my tokens that incorrectly use uppercase M. HTML Encode Tokens Solution Use the token picker to pick the correct lowercase {{my.token}}.

Issue Program member custom fields are not syncing data to Salesforce campaign member fields even though they are mapped. In this setup, the sync for Campaign Members is being performed by 'Add to SFDC Campaign' or 'Change Status in SFDC' flow-steps, but the Program itself is not set to sync with an SFDC Campaign. Environment SFDC Integration Solution This is the expected behavior, as the program member custom fields will only sync data to campaign member fields when the Salesforce Campaign Sync is setup for the Instance/Program in question. Using flow steps to sync SFDC Campaign Members will not carry over data for Program Member Custom Fields. Root Cause SFDC Campaign Sync is not enabled. Enable/Disable Campaign Sync Enable/Disable Campaign Sync | Adobe Marketo Engage Program Member Custom Field Sync Program Member Custom Field Sync | Adobe Marketo Engage

Summary Customers may face errors referencing Segmentations when importing programs between instances. Issue Program import fails giving an error message like the example below: "Marketo encountered an error while importing Nurture Program: EXAMPLE - Acquisition NUR B2B [SMB] FY24 - TEST Why: The Segmentation_Type_1003 field exists in the following objects: Person What to do now: Create a field named Segmentation_Type_1003 in the Person object." Environment Marketing Activities Import Program Solution The simplest solution would be to temporarily remove the Segmentation references from the child assets (Smart Campaigns, Smart Lists, etc.) that currently exist in the importing Program within the source instance. Once the import succeeds, references to the Segmentations can be re-added to the source (as well as the destination, if needed) instance's Program's assets.

Issue When trying to clone a Form or Landing page from Design Studio to a specific Program under Marketing Activities, there is no list of programs that appear. Solution This is expected behavior. When you don't see a program listed, this is because the number of programs in Marketing Activities actually exceeds what we're able to display at one time. If you start typing into the Program field in the pop-up window, you should start to see programs listed in the drop-down. For example, you enter the name of the particular program, you will get a result.

Issue You receive the error message of "exceeded limit" for Program Member Custom Fields (the documented limit is 20), but you don't see 20 fields listed in the Admin > Field Management > Program Program Member Info area. Root Cause There may be Program Member Custom Fields in your Marketo instance that are hidden. These hidden fields still count toward your limit of 20. As next steps, in Admin > Field Management, review the Hidden Fields area to find the hidden Program Member Custom Fields, and un-hide them. After un-hiding them, they will appear under Admin > Field Management > Program Program Member Info. To resolve the "exceeded limit" error, unused fields should be deleted. Reach out to Marketo Support to delete Program Member Custom Fields.

Issue Leads are stuck in a smart campaign's Wait Step and have not moved onto next steps, even though the Wait Step has been updated/shortened and the lead should move onto the next step. Solution When a lead enters a Wait Step, it remains in the Wait Step as defined at the moment they entered it. For example, if the lead enters a 1 week Wait Step, it will remain in the step for 1 week. If the Wait Step is updated to be longer or shorter (for example, shortened to 3 days or extended to 2 weeks), the lead that already entered the Wait Step (when it was 1 week) will remain in the Wait Step for the original duration. New leads entering the Wait Step will abide by the new duration.

Issue When cloning an asset from Design Studio into Marketing Activities, there is a box that asks you to select which program to clone the asset into. When clicking into this box, you may see No Results, even though there are programs within Marketing Activities. This is a article attached image Solution Expected Behavior: This happens when there are too many programs in the Marketing Activities tree. To select your desired Marketing Program, begin typing the Program Name, and results will begin to appear in the Program drop-down. This was designed to increase UI performance when cloning assets into Marketing Activities from Design Studio.

Issue Person record's Activity Log shows repeat Company Name changes without any Data Value Change being logged. In this example screenshot, we can see that the person had the Company Name set back to the correct value by the CRM sync, but there is no record of the Company Name being changed in the first place. This is a article attached image Environment Person records showing the change are all part of the same Account. One person on that holding Account fills out a form that updates the field "Company Name" to a value that is different from the Account Name CRM sync corrects the Company Name field back to Account Name Solution STEPS TO RESOLVE: 1. Find the lead that change the Company Name field on the account with a Smart List filter: DATA VALUE CHANGED Attribute: Company Name New Value: [Company Name from form fill-out] Previous Value: [Account Name] This is a article attached image 2. Locate the Data Value Change in the Activity Log 3. Check the date and time of the Data Value Change 4. Check that timeframe on other affected records 5. The timeframe of the Data Value Change back to the Account Name will approximately match the timeframe of the logged Data Value Change, showing that the update to the one person was the cause of the update for all others on that account. Root Cause Marketo uses Company Name as the identifier for the Account object. If you have multiple people on the account and one of them changes the Company Name via a form fill-out, the Company Name is changed for all other people on that Account. This change happens on the back end, so you will not see it until the CRM changes it back to the correct value in the next sync cycle.

Issue New person records are missing data and only contain Email Address. Environment On24 Event Partner Launchpoint Integration Solution When Marketo pulls the Attendance Report, for On24 Events through the On24 Launchpoint Event Partner integration, as documented here: ON24 Event Registration Updates | Adobe Marketo Engage For any net new records to Marketo (people who registered and attended the event outside of Marketo), Marketo will only sync the Email Address and Attendance Status. This will result in records in Marketo that do not have complete data from On24, such as First and Last Name. To avoid this scenario, it is recommended that all records are properly registered for the Event through Marketo, using Marketo Forms and Registration Campaigns as documented here: Create Child Campaigns and Local Assets | Adobe Marketo Engage

Issue After declaring a champion for your Champion/Challenger test, you notice that the test (ex: "Whole Emails" test) in the Marketing Activities asset tree under your Email Asset is missing. Root Cause When you declare a champion, you select a Declare Date. Once this date/time is reached, only the new champion will be sent. After the test is over, it is expected behavior that the test (ex: "Whole Emails" test) will no longer be shown in the tree. This is because the test is no longer active. If you would like to retain your test data, it is recommended that you save this outside of Marketo.

Issue An email was expected to sent out on a specific cast of Nurture Program but a specific lead or couple of records did not receive it. Environment Marketo>Engagement Program Solution There are a number of steps to begin troubleshooting this query and here is a flowchart how to proceed. 1). Check if engagement program is turned on from its setup up. Also check if at the time of email cast, the program status was on (this can be checked from Admin>Audit Trial) 2). Check if the email asset which was expected to send was present in the Nurture Stream at the time of cast. Also check if that email asset was activated (having green arrow). Both of these can be checked from Audit trail where you will find the log of "Add Email" and "Activate Email" along with its date/time. 3). Check if the lead is present in that specific stream using the smart list filter "Member of Engagement Program > Stream = <required stream>" 4). In the same smart list, use filter of "Engagement Program Cadence Changed" and set "New Value = Paused" and see if that lead qualifies it or not. A paused cadence would mean the lead has been temporarily restricted to move in the flow of nurture stream and hence will not received any email content. 5). Most important step- Go to the activity log of lead and search for the engagement program's name in the quick find bar. Look for all logs along with their dates when the lead performed any activity related to that engagement program like added to program, changed cadence, removed from program, etc. 6). In continuation of step 5, check in the activity log if the lead was added to engagement program in less than 25 hours before the next cast by looking at the time of log "Added to Engagement Program". This is because as per the doc, the lead must be added atleast 25 hours before the cast to abide by the recipient time zones otherwise it will skip that current cast and will qualify for the next cast. Schedule Engagement Programs with Recipient Time Zone | Adobe Marketo Engage 7). In continuation to step 5, check if the lead was moved to a different stream via getting qualified into transition rules. Transition rules are present in stream of those engagement programs that have more than one stream and are used to move leads from one stream to another. Transition People Between Engagement Streams | Adobe Marketo Engage 8). Check if the lead is unsubscribed, email invalid, email suspended (this one is only valid for 24 hours), marketing suspended or block listed because any of these 5 conditions would block the lead from receiving any communication from any of the Marketo's program or campaign. 9). Check if the record has hit the communication limit. Go to Admin>Communication limit and see what we currently have setup. If limit is 2 emails per day, then create smart list "Was sent email>Email Is ANY> Minimum Number of times 2" and see if lead qualifies in it. Alternatively you can go into lead's activity log and manually count number of "Send Email" logs in last 24 hours and in last 7 days and match it with the communication limit of Admin tab. Using programs as stream content: We can also use programs (default and event) in nurture stream instead of direct email assets. 10). In case of using a program, the email can be sent out to the required audience only if that program have a smart campaign with filter "Member of Engagement Program>Name of Program" and flowstep of "Send Email". So make sure the smart campaign has these configurations. (Make sure the campaign has to be a batch campaign and not trigger) 11). If above pointer is true still record is not present in the result tab of the campaign, then check all steps from step 1- step 9. If nothing is found then check if smart list has more than just "Member of Engagement Program" filter and if the lead is failing to qualify any of the other filter. 12). Check in the schedule tab if qualification rules says "Each Lead can qualify only once". If yes then go to campaign member tab and search if lead is already a member, if yes then lead will not qualify again and this is why email was not sent. 13). Check if flowstep has a wait step and the lead is stuck there because wait step does not create any log in the results tab. People in waitstep can be checked from dashboard of the smart campaign. 14). For any other possible reason why the lead did not qualify the smart campaign, you can look for the knowledge base "Lead not qualifying smart campaign- Universal Checklist" under heading of Batch Campaign: marketo.my.salesforce.com/articles/en_US/Article/Lead-not-qualiying-smart-campaign-Universal-Checklist?popup=true 15). If all above pointers have been checked still unable to figure out why the email was not sent on a specific cast, escalate the case to Tier 2.

Issue When comparing the Engagement Score on the Engagement Dashboard, the scores do not match with the Email Insight Engagement Scores. Environment Engagement Program Email Insight Solution The Engagement Score from the Engagement Dashbaord will hold the most accurate information as this is direct information, rather than for example with RCA/RCE and Email insights where the data source is different. If you want to see Engagement Score over a period of time more accurately, use the Engagement Stream performance report: Engagement Stream Performance Report | Adobe Marketo Root Cause The Engagement Score on the Engagement Dashbaord only calculates the last 3 casest, it is also important to remember that the engagement score only includes emails that were cast more than 72 hours ago. As per this documentation: The Engagement Dashboard | Adobe Marketo In comparison, the Email Insight Engagement Score is calculated over a period of time that is set by the user but the data can still be mismatching, this is due to the fact that the data source is not the same from the Engagement Dashboard.

Issue When changing Program Status in Admin > Tags > Channel for "Event" result in this error, "Failed: no more information". Environment Changing Program Status Failed: no more information Solution "System mapping for Registered, Waitlisted, and Attended statuses is required." Therefore, ensure the status is mapped to Registered, Waitlisted, and Attended. Root Cause One or more of these statuses "Registered, Waitlisted, and/or Attended" were not mapped as required.

Knowledgebase

Maintaining a Directory of Leads Bouncing Emails

Top Blocklists - What You Need to Know

Form Pre-Fill Feature Upgrade

Dealing with Spam or Bot Form Fillouts

And/Or Logic in Trigger and Filter Constraints

"Rule is Incomplete" Error When Attempting to Move Program Into New Workspace

Unable to reference AB test email in smart list or campaign

Flow step choice condition for "Person was Deleted from SFDC" with 'in past' "7 days" causes campaign failure

My token not displayed correctly in view as webpage version of email.

Program Member Custom Field Data Not Syncing To SFDC Campaign Members

Error During Program Import

Unable to Clone form from Design Studio into Marketing Activities

Error exceeded limit for Program Member Custom Fields

MyToken used in Email not reflecting correctly

Leads stuck in Wait Step after Wait Step Change

No Programs To Select When Cloning Assets From Design Studio To Marketing Activities

Person record's Activity Log shows repeat Company Name changes without any Data Value Change being logged

Newly Created Records from On24 Missing First/Last Name

Champion/Challenger Test Disappears from Marketing Activities tree after declaring winner

Engagement Program not shooting email

Why is my Engagement Score not matching with the Engagement Score in Email Insights?

Failed: no more information