Product Communities

Issue How to subscribe to Marketo service interruption and outage notices.       Solution Issue Resolution   Follow the instructions RE: Subscribe to Status page notifications for the latest information on service issues, degradations, or disruptions that may be impacting your Adobe Marketo Engage subscription.   

IssueAn 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.  EnvironmentMarketo>Engagement Program SolutionThere 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 Prog

IssueExecuting a GET API call to retrieve a list of available activity types in the target instance using the '/rest/v1/activities/types.json' endpoint, resolves with an unexpected attribute name for a field with the display name ID in the context of Marketo Custom Objects.An example of that may be a Marketo Custom Object with the following name: '3 to be', as can be shown in the image below:One of the '3 to be' Marketo custom object fields name is 'ID'. (highlighted in red).When performing a GET API call using the '/rest/v1/activities/types.json' endpoint, you will be getting a list of available activity types in the target instance, along with associated metadata of each type, however for a Marketo custom object with an ID field name, you may see it returns back with a slightly different name, in this case, it would be returning the following output for my test Marketo Custom Object activity: { "id": 100019, "name": "Add to 3 to be",

IssueWhen comparing the Engagement Score on the Engagement Dashboard, the scores do not match with the Email Insight Engagement Scores. EnvironmentEngagement ProgramEmail Insight SolutionThe 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 CauseThe 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 MarketoIn comparison, the Email Insight Engagement Score is calculated over a period of time that is set by the user but the data can still

IssueClicking a tracked link in an email either leads to a 404 page or the fallback page. EnvironmentTracked linksTokensSpecific Characters: "#", "$", unbalanced brackets "{" or "}" SolutionDo not use the following characters "#", "$", unbalanced brackets "{" or "}" in a link that is tracked when using a token as well.This is a article attached imageFor example: google.com/ebook-download.html?ebook={{lead.ebook}}#This will not work and will either direct to a 404 page or redirect to fallback page.When hovering over the link you will see that it is not a normal tokenized link, it will contain something along the lines of: $mktEncrypt.encrypt($mkturl2)/<random characters> Root CauseWhen using tokens in the url of a tracked link, the email is processed and the tokens are substituted and populated with the correct information. The engine that assembles this information have some characters reserved for use such as #.

IssueThe format of the landing page is distorted in comparison to the version displayed in the landing page preview.  EnvironmentSSL CertificatesLanding Page DomainLanding Page format is different from previewLanding Page contain unsecure contentLanding page template has http instead of https  SolutionEnsure all the links used in HTML code used in the landing page template is referencing "HTTPS" and not "HTTP". You can follow the steps outlined in the document below on how to edit landing page template. Link: https://experienceleague.adobe.com/docs/marketo/using/product-docs/demand-generation/landing-pages/landing-page-templates/edit-a-marketo-landing-page-template.html**NOTE: If the landing pages is approved, a draft version of the landing page is created for any landing pages which is using the landing page template. You can mass approve those landing pages via following steps outlined in the document below.Link: https://experienceleague.adobe.com

IssueWhen changing Program Status in Admin > Tags > Channel for "Event" result in this error, "Failed: no more information".  EnvironmentChanging 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 CauseOne or more of these statuses "Registered, Waitlisted, and/or Attended" were not mapped as required. 

IssueEmails cannot be delivered from the Marketo instance and the following Soft Bounce code was recorded in the record's activity log.554 5.4.7 [internal] (last transfail: 435 5.7.8 Authentication credentials invalid) EnvironmentDedicated IP AddressSMTP Relay credential invalidSoft Bounce Code: 554 5.4.7 [internal] (last transfail: 435 5.7.8 Authentication credentials invalid)Cannot send emailEmail Delivered not recorded in activity log SolutionProvide Marketo Support with the updated credentials so Support can create an internal request to get the update the credentials on Marketo's end. The process can take up to three (3) business days to complete. Note: Avoid using special characters in the password such as quotation mark (") as it can alter the configuration.   Root CauseThe credentials for the SMTP Relay has been changed and no longer match what is stored in Marketo. In most cases it is the password as it need to be change on an annual basis.

IssueWhen editing the expiration date for a user in Admin by completely removing the expiration date set to null and clicking save. The change is not saved, and the expiration date remain. EnvironmentExpired Date for userExpiration DateChanging the expire date to never in Admin  SolutionThere are two options:1. Change the expiration date to a date in the future. 2. Delete the user in Admin and recreate the user again and set the expiration to never. *Please note that if option 2 is selected, the history of the user is will be lost and this cannot be retrieved. Root CauseThis is a design limitation as it is expected for the user with an expiration date to be deleted from the Marketo Instance after the expiration date has been reached. 

IssueForm in Design Studio will not convert the time format upon language selection. English form with date format dd/mm/yyyy Below is a form using settings with form language selecting German. The date format remains the same "dd/mm/yyyy" when the expected value should be "tt/mm/jjjj" as per language date format EnvironmentMarketo forms and common web browsers such as Chrome, Opera, Firefox. Root CauseThis behaviour is related to the browser language settings. It automatically translates the date in the format of the selected language in the browser. Example of the same form with different browser language selected, the date format is changed by the browser 

The Email Deliverability and Privacy Team always stresses the importance of a strong sending reputation. By keeping an eye on your engagement (opens, clicks, etc.) and reputation (spam complaints, spam traps, unknown users, etc.) metrics you’ll get a good picture of how your emails are being received by subscribers. But if you’re looking for another measure of your reputation you can take advantage of a handful of resources that will let you know where you stand.  Here are 4 sites that will help you check sending reputation:   SenderScore.org​ Like a credit score, a Sender Score is a measure of your reputation. Scores are calculated from 0 to 100. The higher your score, the better your reputation and the higher your email deliverability rate. Numbers are calculated on a rolling 30-day average and illustrate where your IP address ranks against other IP addresses. This service is provided by Return Path and provides reputation from primarily a B2C perspective.   Senderbase

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

IssueWhen working on an event program, Marketo Engage users are unable to select a webinar provider in the event partner selection. EnvironmentEvent program Webinar provider (ON24, Zoom, Cvent) SolutionThe members need to be removed before setting up the event partner.You can remove members from a program by changing their status to "Not in Program". Root CauseMarketo does not allow selecting an event partner in a Marketo event program with members.

IssueThe issue appears when a custom view is created in MSI that contains dependant fields.The error message:  "The dependent picklist '<dependant field name>' requires its controlling field '<parent field>' to be present on the page." will be displayed when you are trying to add the dependant field.For example:  "The dependent picklist 'Sub-Classification' requires its controlling field 'Classification' to be present on the page." EnvironmentSalesforceMSI SolutionNeed to omit the dependant field in the custom view. Root CauseWe curently do not support creating a view in SFDC MSI with a dependant field.

IssueYou may be wondering if it is possible to edit or rename your custom fields in Marketo.  SolutionYes, editing or renaming your custom fields in Marketo is possible.You can do so by navigating to "Admin" > "Field Management" > Click on the field on the right-hand side field list > click on the name of the field in the centre canvas (UI) then edit.Your fields would need to be unused by any asset in order for you to edit/rename them.

IssueWhen looking at Email Insight it is only showing the first email activity (Send, Delivered, Click or Open), even though the email has been sent several times in the past few days/weeks/months. EnvironmentEmail Insight SolutionUse different Smart Campaign to send the email if you want to track statistics of the email. Root CauseEmail insights will only track the first email activity associated with the email if using the same campaign. this is the same as Email Performance report in terms of this note.Multiple sends from the same campaign to the same person are counted only once.

IssueThe Source Campaign field in Microsoft Dynamics is not getting updated when the field is updated in Marketo.The sync from Microsoft Dynamics to Marketo will be working fine. EnvironmentNative integration with Microsoft DynamicsCampaign Sync not Enabled SolutionTo sync Campaign Source from Marketo to Dynamics, the option 'Campaign Sync' needs to be enabled as per this documentation: Enable Campaign Sync | Adobe Marketo Root CauseIf the Campaign Sync is not enabled we will not be syncing over the value of the field to Microsoft Dynamics as it is part of the Campaign Sync.

There is a new Chrome extension for local browser embed code changes is live. This is not an official Adobe product. You can get it here - Launch Command - Chrome Web StoreDirect Link (Copy/Paste)https://chrome.google.com/webstore/detail/launch-command/nkjhamgjeocefocmpbcjfmohkjgildkiOnce it's installed, you can right click on it and select "Options" to view the help docs if you have questions.

IssueLead conversion/qualification through workflows in Microsoft Dynamics CRM resulting to duplicates (i.e. Lead and Contact) in Marketo EnvironmentMicrosoft Dynamics CRMLead conversionSync SolutionWhile lead qualification through workflows is currently not supported, one approach that we saw implemented by a customer that did not result in duplicates is by redeveloping the lead qualification workflow using the msdyncrmWorkflowTools (1.0.54.0): QualifyLead step.Dynamics-365-Workflow-Tools/Qualify Lead.md at master · demianrasko/Dynamics-365-Workflow-ToolsThis was verified to result in no duplicates as the workflow writes the "Create [Qualify Lead]' operation type to the Marketo Log which is like the standard qualify button. Should there be any further assistance needed in developing the lead conversion workflow, it's recommended to engage with our Professional Services / Consulting team Root CauseMarketo's integration with Microsoft Dynamics CRM currently does not support custom q

SummaryYou have set up a campaign or campaigns in the Email Deliverability Tool (250ok), but there is no engagement metric showing Total opens and Unique opens, which should be available in the ‘Engagement Overview’ in the Email Deliverability tool. You would need to ensure that you have configured the necessary setup for the tracking to work in the Email Deliverability tool. IssueCampaigns created in the Email Deliverability tool (250ok) doesn’t show any engagement overview metric such as total opens and unique opens. EnvironmentEmail Deliverability tool (Production/Sandbox) SolutionYou would need to implement the necessary setup for the metric to show in the Engagement Overview in the Email Deliverability tool (250ok)   Follow the steps below to ensure you have configured the setup for campaign tracking.  1. Ensure your DNS CNAME is configured. (All that is required is creating a CNAME DNS entry on this domain that points to 250analytics.com)  For more i

IssueWhen searching or grouping a list of leads based on email address filter ‘Contains’ @ sign, you may encountered the different numbers in the ‘People’ tab (result). EnvironmentThis behaviour is specific to the email filter as it uses two main indexes; we’ll call them Index 1 and Index 2 when using the contains/not contains operator. Index 1 searches for the entire email address value from beginning to end. This Index is used when the @ character is not included in the list of values.Index 2 searches only for the domain half of the address, which comes after the @ symbol. This Index is used when the @ character is included in the list of values. SolutionA suggestion is to create a smart list with two Email Address filters wherein you will have all the ones that do not have the '@' symbol, and for the other, you will include the '@' symbol for the email address and use the logic as 'Any'. That would give you the preferred number of leads in your smart list. Root CauseMarketo

IssuePer our developer page: https://developers.marketo.com/rest-api/assets/programs/#update, it is possible to update tags on your existing programWhen updating a program tag within an existing program, you may encounter an error below given the tag and its values are correct.  {"code": "709","message": "Required tags are mandatory"}]} EnvironmentAny API clients when performing the Web Service API SolutionThe workaround is to have the tag updated via the UI. Root Cause"Updating tags is a destructive operation."Any attempt to update the tags of a program must include valid values for all of the required tags for a program.Unless the 'specific' tag type you are working on is the only required tag type in the instance, then that is possible to update it using the API. Otherwise, you'll encounter the error above as it is a system behaviour.

One of the biggest gains to productivity you can employ with Executable Campaigns is the ability to pass the token context of the parent campaign to child campaigns.  This allows you to template your campaigns to use contextual data from the parent and then put it into practice within reusable executable campaigns.  It also allows you to set up My Token values as defaults, and then override them by setting them in the calling campaign.  Let’s take a look at an example: Evaluating activity scores   Evaluate Activity Score   Most Marketo subscriptions use activity or behavioral scoring to some extent, and executable campaigns make it easier than ever to create an effective activity scoring model.  By using the same My Token keys in the parent and child campaigns we can craft an activity scoring campaign that can be used by any triggered activity in a single workspace.  This is what a basic templated scoring flow looks like.  The interesting moment

Executable campaigns are a powerful new feature designed to allow you to make your campaign logic modular, reusable and maintainable.  However, staying within the limit of three nested executables can be difficult when your campaign trees get complicated.  This article describes a simple method of classifying your executables into three categories to help you stay within the nesting limits while also remaining productive.    Three Categories for Executable Campaigns  This classification system has three categories with simple definitions:  Tier 1: These campaigns may not be executed by other executable campaigns  Tier 2: These campaigns may not execute other Tier 2 campaigns  Tier 3: These campaigns may not execute any other campaigns      By classifying your campaigns in this way, and abiding by their restrictions, you can avoid bumping up against the nesting limit.  Now we have a way to avoid the nesting limit,

What is Changing?Adobe Experience Platform Launch is updating our underlying infrastructure and deployment pipelines.  This requires us to use new egress IPs.The new egress IP addresses are:184.72.239.6823.20.85.11354.226.193.184ImpactIf you are adding Launch egress IPs to an allow list for any reason, you'll need to update your allow list.The most common reason for adding Launch IP addresses to an allow list is when you're using an SFTP host to receive your Launch library builds.If you are not able to quickly update your allow list, and you need to do a deploy in between now and then, one potential workaround is to switch to an Archive build on the Managed by Adobe host, then download that .zip file.When Will This Happen?This change will go into effect on Tuesday, October 27th.