Knowledgebase

Sort by:
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 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 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.
View full article
It's one of the most common calls we get in Support - "This lead should have qualified for this campaign, but it didn't. Why?"  Here's how we go about answering this question, and you can do it too.   Did the lead actually qualify? Sometimes the leads do qualify for the campaign but don't go through the flow.  One quick way to check this is to look at the campaign membership.  If the lead qualified, it will become a member of the Smart Campaign, even if it doesn't go through the flow. Has the lead gone through the flow before?  We can check this in the campaign results. If it has, we need to see if the campaign allows the leads to go through the flow more than once. If the campaign is set up to allow leads to run through the flow multiple times, then we need to proceed with troubleshooting. But if it is not, we have our answer - the lead didn't go through the campaign because it had done so previously and couldn't go through again.   Did the trigger have constraints? If it didn't, we move along, but if it did, we need to check and see if the lead met the requirements of the constraints at the time the lead hit the trigger. This is very important.  If, for instance, there was a constraint that required a value in a field, and that field was not populated before the trigger went off, then the lead wouldn't qualify.  The timestamps in the activity log for the trigger activity and the value change might be the same, but if the value change for the field happened even a fraction of a second after the trigger event, it's still too late. The lead will not qualify.  Looking at the lead now, it looks like it qualifies, but at the moment the campaign was triggered, the lead had different information, so check to see when the required values were written to the lead.   Did the Smart List have filters in addition to the trigger? Just like the constraints, we need to confirm the lead satisfied the filter requirements before the trigger fired.  This can get complicated if one of your filter requirements is "Member of Smart List" because you are going to have to go into the referenced Smart List and confirm the lead met all those requirements, and if that Smart List also contains a "Member of Smart List" filter, then will have to check that one as well and, well, you will see why we in Support recommend against nesting Smart Lists.   Has the campaign been changed since the lead hit the trigger? We tend to assume that the campaign we are looking at today is the same as it was when the lead hit the trigger, but this is often not the case.  Check through the Audit Trail to see if there have been any changes.  Maybe a constraint was added, removed, or changed.  Maybe the filter logic was changed from AND to OR.  Maybe it used to only let leads go through the flow once.  If the campaign was changed, you will need to go through the troubleshooting steps above all over again, checking against what the campaign used to have, rather than what it has now.  If you have nested Smart Lists, it may be that the campaign didn't change at all, but a filter criteria in a the secondary Smart List did.  This is another reason why nested Smart Lists should be avoided if possible.   If you go through these steps and still can't figure it out, open a case in Support and include the results of the troubleshooting above so we can look into it further.
View full article
Issue How to test Facebook lead generation form functionality without viewing the advertisement on Facebook Solution Use the lead ads testing tool by clicking on the link - https://developers.facebook.com/tools/lead-ads-testing   to create a test lead. You should use this tool with a valid Facebook Ad Account. Login to Facebook with the same account you used to set up the integration with Marketo. Select the Page and Form you want to create a test lead from. Ensure the Marketo app (APP ID 1480829408843427) is diplayed on "WEBHOOK SUBSCRIPTION FOR THE SELECTED PAGE" section. Click on the "Create Lead" button. In the "WEBHOOK SUBSCRIPTION FOR THE SELECTED PAGE" Click on "Track Status" button which updates real time until you get a response from Marketo. If you do not have the "WEBHOOK SUBSCRIPTION FOR THE SELECTED PAGE" in Facebook, c omplete the following: Go into the Facebook Lead Ad Launchpoint service in Marketo and unselect all the pages. Finish the setup and save. Do not delete the Launchpoint service but de-select the pages Go back into the Facebook Lead Ad Launchpoint service and re-select the list of pages. Finish the setup and save. This will kick in the code that registers the webhooks on the pages again. It is important to go through step 1 first or the code will not re-register the page. Try creating a lead using the lead ad testing tool. In Marketo, the email address "test@fb.com" should be created.    
View full article
In your email link performance reports, you may see a "malformed link."     This occurs when invalid or empty URLs are present in an email asset.   These links are transformed into a branded tracking link and if clicked will appear on this report.    In the email editor, check for empty links or tokens that do not populate a full link. 
View full article
In your email link performance reports, you may see a "malformed link."     This occurs when invalid or empty URLs are present in an email asset.   These links are transformed into a branded tracking link and if clicked will appear on this report.    In the email editor, check for empty links or tokens that do not populate a full link. 
View full article
Issue You are having issues with Single Sign On and Support requests for you to provide the SAML Response. How can you find this information?   Solution There are multiple ways to capture a SAML Response, but the easiest one is by using SAML Tracer ( https://addons.mozilla.org/en-US/firefox/addon/saml-tracer/ ), a Firefox plug-in or other similar plug-ins or add-ons for Chrome such as SAML Chrome Panel ( https://chrome.google.com/webstore/detail/saml-chrome-panel/paijfdbeoenhembfhkhllainmocckace?hl=en ) which adds a SAML tab to the built-in Developer Tools. As with any third-party integration, make sure you're comfortable with the permissions they request and you fully trust them before you proceed. Many teams also use networking tools like Fiddler - these should also work just fine. Once you or the user having the log-in issues have one of these tools installed, you'll need to attempt to login via SSO on the appropriate browser and the plug-in/add-on will capture the SAML response. The result should look similar to XML with many references to saml in the tags.    
View full article
Issue Several types of fields in Marketo have requirements for the type of data that can be stored, as well as the limit to how much data can be contained in that field type. The Custom Field Type Glossary can tell you what fields are available, and this article will show you details on the type and maximum limits for those fields.    Field Types & Limits Boolean Can only be set to “true” or “false” (stored in the database as 1 or 0).   Currency Maximum value of 9223370000000000000.  Will be displayed with the currency set in your instance under Admin -> Location.   Date Must be formatted “MM/DD/YYYY”.   Datetime Must be formatted “MM/DD/YYYY HH:MM:SS”.   Email Must be a properly formatted email (user@example.com).   Float Can include decimals up to the hundredths place.  The value will round to the nearest hundredth (eg. 99.999 rounds to 100, 99.985 rounds to 99.99).  Maximum value of 10000000000.   Formula See this guide: Create and Use a Concatenated String (Formula) Field    Integer Values are limited to between -2147483647 to 2147483647.   Percent Must be a full number without decimals.  Maximum value of 9223370000000000000.   Phone Can have letters, numbers, or characters.  Maximum of 2,000 characters.   Score Maximum score of 2147483647.  If the score is increased higher than that, the score will reset to -2147483647.   String Can contain letters, numbers and special characters.  Limit of 255 total characters   Text Area  Can contain letters, numbers and special characters.   Limit of 65,535 total characters   URL "http://"  will automatically be appended to the value if the value doesn't have that prefix or "https://" already.  Does not have to be formatted any further (Generic top-level domain not required).  
View full article
Issue You receive the below sync error notification which states "CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY: [process/workflow name]: System.LimitException: Apex CPU time limit exceeded"   Solution The error means that you have one or more triggers running when the leads are inserted that consume too much CPU time. You are hitting what are called SFDC Governor limits . This is really something you need to review with your SFDC admins and developers. Consider moving some workflows from Triggers (synchronous) to batches (asynchronous).    
View full article
Issue Issue Description If a page is not loading in your browser for Marketo, this can sometimes be due to network related issues. We can help troubleshoot by using a HAR file from the browser to see network traffic.   Solution Issue Resolution Instructions to generate a HAR file broken down by browser version: Chrome In Chrome, go to the page within Marketo where you are experiencing trouble. At the top-right of your browser window, click the Chrome menu ( ⋮ ). Select Tools > Developer Tools . The Developer Tools window opens as a docked panel at the side or bottom of Chrome. Click the Network tab. Select Preserve log. You will see a red circle at the top left of the Network tab. This means the capture has started. If the circle is black, click the black circle to start recording activity in your browser. Refresh the page and reproduce the problem while the capture is running. After you successfully reproduce the issue, right click on any row of the activity pane in the Network and click Save as HAR with Content. Save the HAR file. Select the Console tab. Right-click anywhere in the console and select "Save as...". Name the log file Chrome-console.log. Send both files as shared links in a reply to your case. Firefox In Firefox, go to the page within Marketo where you are experiencing trouble. Click the Firefox menu (Three horizontal parallel lines) at the top-right of your browser window. Select Web Developer > Network. The Developer Tools window opens as a docked panel at the side or bottom of Firefox. Click the Network tab. Select Persist logs. After you successfully reproduce the issue, right-click any row and select Save all as HAR. Firefox typically takes a few seconds to prepare the download. A slight delay on this step is normal. Select the Console tab. Right-click any row and select Select all. Paste the content in a text file and name it console-log.txt. Send both files as shared links in a reply to your case. Safari In Safari, go to the page within Marketo where you are experiencing trouble. In the menu bar at the top, click Develop and select Show Web Inspector. Click Preserve Log. Click the Console tab and select Preserve Log. Go back to the Network tab. Refresh the page and reproduce the problem while the capture is running. Once you have reproduced the issue, select Export. Save the HAR file. Click the Console tab. Right-click any row and select Select all. Paste the content in a text file and name it console-log.txt. Send both files as shared links in a reply to your case. Internet Explorer 11 (IE 11) In Internet Explorer, go to the page within Marketo where you are experiencing trouble. Click the gear icon in the top right. Select F12 Developer Tools. Click the Network tab Clear the Clear entries on navigate option, which is selected by default. The icon looks like blue arrow with a red X. The green play button (Start Profiling Session), should be selected by default. This means the capture function is running. Refresh the the page and reproduce the problem while the capture function is running. Once you have reproduced the issue, click the Export as HAR icon. The icon looks like a floppy disk. Click the Console tab. Right-click any row and select Copy all. Paste the content in a text file and name it console-log.txt. Send both files as shared links in a reply to your case.
View full article
Issue Executing 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", "primaryAttribute": { "name": "3 to be ObjRef", "dataType": "integer" }, "attributes": [ { "name": "3 To Be Person Id", "dataType": "integer" }, { "name": "ID (3)", "dataType": "string" }, { "name": "Linkfield4", "dataType": "string" } ] } ], Here's an image of what it may look like when making the call using POSTMAN: In fact, the character in the brackets next to the ID field represents the very first character of your Marketo Custom Object name.    Environment Customers who have Marketo Custom Objects where one of the custom object fields is named 'ID'. Solution If this is interrupting your business, you may want to select a different name for the ID field under your Marketo Custom Object. (ie. ID number, Transaction ID etc.) Root Cause This behavior is expected and is a result of the 'ID' field being a unique field in the context of Marketo custom objects world and while it may be possible to create a Marketo Custom Object field with the name 'ID', it may be better to give it a distinct name that will be better describing what kind of ID field it is.   
View full article
When a new lead enters Marketo from a  form fillout or  List Import,  Marketo automatically searches for a lead with the same email address.  If that lead exists, the existing lead is updated instead of creating a duplicate. However, Marketo does not automatically de-duplicate leads who are already in your database. This is especially a problem for new customers who often have many duplicate leads in their database. Also, if you add a new lead directly into Salesforce ( through the Salesforce import process or web-to-lead forms) Salesforce will create a duplicate lead that gets synced into Marketo. When this happens, you can use Marketo to find and fix those duplicates.   How Marketo handles duplicates   The primary consequence of duplicates is that one lead record could have the most relevant information about that lead while your sales rep is looking at the incomplete duplicate.   For example, say that you have a duplicate lead in your database and that lead fills out a form on your website. Marketo generally updates the lead record that was most recently updated. In another case, say you run a campaign to email your lead database and two duplicates are included in your campaign run. Marketo automatically detects the duplicate email address and ensures that only one email is sent to that lead. That Email send and subsequent activity will be attributed to the Lowest Lead ID.   When you merge leads, their entire history is combined, and you can control which fields are kept in the final lead. You won't lose any information or tracking.   Most customers have many duplicates when they start with Marketo. After initially de-duplicating your database, the work to keep your database de-duplicated is usually very small. You should work to stop the sources of duplicate leads and make Marketo your single point of entry for all new leads.   Finding Duplicates   Go to the Lead Database section of the app. Then click on the Possible Duplicates list in the tree. Click the grid header that says Email .  You can sort by email address to see the duplicates next to each other. Selecting multiple leads Select two leads that have matching email addresses.  You can do this by holding the "control" key down while clicking on the two different leads.  (You can merge more than two at a time, but start with two.) Tip: Sometimes clicking too fast will make the grid select incorrectly.  Clicking a little slower usually helps. When you have two rows selected or highlighted, click the Merge Leads button in the toolbar.   The Merge Dialog A dialog will appear showing you all the fields that differ between the two leads.  You need to pick which values to keep in the merged lead.  Not every field is displayed -- just the ones that you need determine appear. By default, the values from the most recently updated lead will be selected (with a check and highlighed yellow). To pick a different value for the merged lead, click the checkbox next to that value. If you want to enter your own values for the merged lead, click the Custom field for that row then type in your own value: When you're done, click Merge .  The winning values will be kept in the merged lead; the other values will be discarded. Important : Clicking merge will instruct Salesforce to merge the records properly.  All Salesforce and Marketo activities are merged into the remaining lead.  Nothing is lost.  Campaign History is also kept.   Duplicate pattern matching You will notice that the Possible Duplicates list has a Smart List tab.  Click on the Smart List and you will see it's using the "Possible Duplicates" filter on the "Email Address" field. You can change this filter to search other fields for duplicates. Click the little green plus in the definition. Note : You should use only one Duplicate Fields filter in your Smart Lists.  If you want to check multiple fields, always use the green plus button to add multiple fields; don't drag in a second filter. When you change the Duplicate Fields filter, you should sort the Leads grid by the column you're checking to put the duplicates next to each other. EasyMerge Program Marketo offers a service for mass-merging of duplicates.  Please contact your Customer Success Manager to inquire about this service. What happens when I merge two leads in Salesforce? When you merge leads or contacts in Salesforce, Marketo will also merge the matching leads in your lead database. See this article to learn more about how that works: https://docs.marketo.com/display/public/DOCS/Find+and+Merge+Duplicate+People#FindandMergeDuplicatePeople-EffectinSalesforce    
View full article
Issue Clicking a tracked link in an email either leads to a 404 page or the fallback page. Environment Tracked links Tokens Specific Characters: "#", "$", unbalanced brackets "{" or "}" Solution Do not use the following characters "#", "$", unbalanced brackets "{" or "}" in a link that is tracked when using a token as well. For example: www.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 Cause When 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 #.
View full article
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.
View full article
Issue Form 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 Environment Marketo forms and common web browsers such as Chrome, Opera, Firefox. Root Cause This 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 
View full article
Summary This document explains how to generate a .HAR file for support purposes. Issue Sometimes Marketo support may request that you capture a HAR file for troubleshooting purposes. This document will explain what this means, what a HAR file is, and how to create/capture one for support (or any other purpose you need them for!) HAR means 'HTTP Archive Format'. It is a JSON file format which archives the response and request headers from network communications made to and from your browser.  A HAR file (the extension is '.har') saves the information of all web requests which your browser tab makes. Think of it as 'hitting the record button' on your browser session. These files are very useful as they can identify errors, vulnerabilities, or network performance bottlenecks. For some cases with Marketo support it may be necessary to create such a file. Solution The steps for creating a HAR file vary depending on which browser you are using. Below are the steps for generating a .har file with some commonly used web browsers. Google Chrome: Open your Chrome browser and navigate to the page where the issue needs to be captured. Open the developer tools (F12 or CTRL+Shift+i on Windows, CMD+alt+i for Mac). Select the Network tab of the developer tools. Go to the left of the developer tools UI to start the recording a HAR file. There is a small round 'record' button in this section. If it's gray, click it so that it turns red and begins recording. Click on 'Preserve Log' so the recording persists if you change browser page.  Click the to 'Clear' icon to delete any previous log records kept in the browser, so you have a clean slate for the reproduction. Reproduce the issue so the browser can record it. Once done, right click on the various network traffic and select 'Save as HAR with content', to save the HAR file you recorded. Firefox: Open your Firefox browser and navigate to the page where the issue needs to be captured. Open the developer tools (F12 or CTRL+Shift+i on Windows, CMD+alt+i for Mac) Select the Network tab of the developer tools. Make sure to select 'Clear' (the garbage can icon) before you begin reproducing the issue. Look for a pause button in the tab, and click on it to Play and Record to start recording. Once done, right click on the various network traffic and select 'Save all as HAR', to save the HAR file you recorded. Microsoft Edge: Open your Microsoft Edge browser and navigate to the page where the issue needs to be captured. Open the developer tools (F12 or CTRL+Shift+i on Windows). Select the Network tab of the developer tools. Make sure the small green 'Recording' square is red, or click it if not so you are capturing network traffic. Reproduce the issue so the browser can record it. Click the 'Export HAR' icon to save your recording, and select '.har' as the file extension. Safari: Open your Safari browser and navigate to the page where the issue needs to be captured. Open the 'Develop' menu. Open the Network tab of the Develop menu. Recording is always on in Safari, go ahead and reproduce the issue. Click the 'Export' icon on the right side of the Develop menu UI to save the .har file. Once you have the .har file, please upload it to the support ticket through the support console so we can take a look and help with your issue.
View full article
Issue Emails 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) Environment Dedicated IP Address SMTP Relay credential invalid Soft Bounce Code: 554 5.4.7 [internal] (last transfail: 435 5.7.8 Authentication credentials invalid) Cannot send email Email Delivered not recorded in activity log Solution Provide 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 Cause The 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.
View full article
Issue When 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. Environment Expired Date for user Expiration Date Changing the expire date to never in Admin   Solution There 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 Cause This 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. 
View full article
Issue New program status created in CRM did not sync to Marketo.  Environment Program status did not sync to Marketo New Program status is missing in Marketo Solution Create the corresponding status in Marketo by navigating to Admin > Tags > Channel > Select the corresponding channel > Add new status > Save.  Create a Program Channel | Adobe Marketo Root Cause This is an expected behaviour as program statuses created in CRM do not sync to Marketo. 
View full article
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. 
View full article
Issue The format of the landing page is distorted in comparison to the version displayed in the landing page preview.  Environment SSL Certificates Landing Page Domain Landing Page format is different from preview Landing Page contain unsecure content Landing page template has http instead of https   Solution Ensure 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/docs/marketo/using/product-docs/demand-generation/landing-pages/landing-page-actions/approve-multiple-landing-pages-at-once.html?lang=en Root Cause Once you secure your Marketo landing pages to be served over "HTTPS", you should have not links referencing "HTTP" (unsecured) assets or pages. 
View full article