Knowledgebase

Sort by:
Issue Authorized support admin unable to find a contact to add as authorized support contact.   Solution The contact will need to have logged in to the community (nation.marketo.com) at least once for their profile to be created and recognized in the system. "In order to appear on the list of available contacts, the user must have clicked Community (while logged into Marketo) at least once." docs.marketo.com/display/public/DOCS/Manage+Authorized+Contacts+in+the+Community Once the contact has logged in to the community, the authorized support admin should be able to see the contact to be added as an authorized support contact.  
View full article
Issue In the attempt to create or invite a new user with email address "john@mail.com", the message appears "The user id is in use. Choose another email." even though the user was already deleted from the other instance it was being used in. Solution This message can appear as at the time the user "john@mail.com" was being created or invited to another instance, after deleting "john@mail.com" from another instance, the user was not completely deleted from the other instance. At times it can take about 5-15 minutes for a user to be completely deleted from the system, so allow some time before re-creating the user.
View full article
Issue Authorized support contact unable to access the Support Portal Authorized support admin unable to view and manage list of authorized support contacts Authorized support contact unable to create a support case Authorized support contact unable to view list of cases     Solution Issue Resolution Contact marketocares@marketo.com - they are our dedicated team that handles issues with the Support Portal
View full article
Issue You put a variable inside an email token and when the email was sent, the variable rendered as text rather than as a link: Example: ${queryParameters} Should expand to: {{my.CertainURLHREF}}?utm_source=${utm-source}&utm_content=${utm-content}&utm_medium=${utm-medium}&utm_campaign=${utm-campaign}&ajs_uid={{lead.Email Address}}&ajs_event=Email%20Clicked With the various tokens populated Instead it expands to this: app.fakewebsite.biz/profile/55555555?utm_source=$%7Butm-source%7D&utm_content=$%7Butm-content%7D&utm_medium=$%7Butm-medium%7D&utm_campaign=$%7Butm-campaign%7D&ajs_uid=adam.tow+test@voxmedia.com&ajs_event=Email%20Clicked   Solution Essentially, email template variables are used at design time to make building out an email easier. Tokens are used at send time to make data variable per program without having to edit the asset or lead. Putting email template variables inside tokens won't work for this reason. It is just how the current design works and you will not be able to put email template tokens inside my tokens or lead tokens. Unwrapping variables before you put them within the token will allow them to function properly. This removes the simplicity of the variable, but retains the functionality.
View full article
Issue User not able to see the "Global Reporting" feature within our Email Performance reports in Marketing Activities in non-default workspaces, as described in this product doc: - docs.marketo.com/display/public/DOCS/Report+Email%2C+Campaign+Performance+Across+Workspaces Solution The global reporting option is only available for reports in the Analytics tab and in Marketing Activities in the default workspace.  Reports located in other workspaces will not have this option.   Who This Solution Applies To Customers with Workspaces & Partitions
View full article
Issue How to confirm ZoomInfo integration is working with Marketo.   Solution First, follow the installation guide: help.zoominfo.com/18441-formcomplete/installation-guide#product-overview To check if its working: Go to Marketing Activities. Navigate to the folder and then click on the Smart Campaign that runs your Form Complete. From the Smart Campaign, click the top navigation menu item, “Results”. Find the most recent “Call Webhook” activity type and double click it. The Activity Details window will pop-up (check your pop-up blocker if it does not).   Inside this window will be what you need to diagnose most problems. The easiest way to know if it worked or did not is that the Response Code should read: 200. This means it was successful in terms of sending and receiving the response in a way that the API accepted it. Anything other than 200 you should lookup with a Google search and investigate. Finally, go to the Lead  Database, and in the quick find search for the unique contact record that submitted the form to find the record that went through the Form Complete Webhook. Double click the right record from the view and that person record will load up. From the top navigation click, “Info” and scroll down till you see the custom fields you created in Step 1 (above). You should see the fields populated if all of the steps were completed successfully.   Who This Solution Applies To Customers using the ZoomInfo Integration      
View full article
Issue You are trying to configure Marketo and Okta for SSO, but encounter errors. Solution 1. Log in to Okta and go to the admin section. 2. Click "add applications" then "create new app" (Do not use the community sourced Marketo app) 3. For platform select "web" and for signon method select "SAML 2.0" 4. Name the app "Marketo" (or any name you prefer) and upload the Marketo logo you would like to see displayed on the login tile, then click next 5. In "SAML Setttings" for the Single sign on URL you will want: login.marketo.com/saml/assertion/<YOURMUNCHKINHERE> . For the Audience URI you will want: saml.marketo.com/sp Default Relay State can be left blank. For Name ID format select "email" or "emailAddress" and for application username you will want to select email (Be sure that your Okta user email matches what is in the login field for your Marketo user within Admin > Users & Roles). Leave attribute statements unused. 6. Select finish and you should be brought to a page where you can select either "view setup instructions or identity provider metadata". 7. One of those links mentioned in the last step will take you to a page where you can retrieve the issuer ID which will be put in the Marketo settings (under both Issuer ID and Entity ID) as well as the certificate you will need to download and then upload into your Marketo SSO configuration. 8. Once you have set the issuer id, entity id, and certificate as described above, confirm that your Marketo User ID Location is set to Subject and then enable SSO. When you hit "save" in the SAML settings window in Marketo, the popup may not close, but your settings are retained and the window can be closed (if you would like to confirm it was saved, you can reload the page and will see the new saved settings) 9. When you first setup SSO it is preferable to have all the SSO users available to confirm there are no issues with a particular user in an otherwise operational SSO configuration. However, if SSO works for one user, then the overall configuration is set correctly. Disclaimer: Marketo Support does not support 3rd party products, and cannot configure an SSO Identity Provider on your behalf. This document exists to aid users in configuring SSO, however, no guarantees are made that these setup steps will work.     Who This Solution Applies To Okta Users, SSO users
View full article
Issue There is a DMARC policy bounce in ToutApp for Gmail email addresses.     Solution This is due to a DMARC policy on your organization's name domain which is preventing the emails from being delivered to Gmail email addresses. Visit the Google support portal on this support.google.com/mail/answer/2451690 Have your team check your DMARC policy.      
View full article
Issue Links sent to a customer using AppleMail are not rendering properly. Solution This issue is cause when there is no protocol assigned to a link so AppleMail appends applewebdata:// to the beginning of the url instead of or The work-around for this is to include the protocol in the link. If there's no protocol (e.g. ) then the rendering engine will insert applewebdata:// as the protocol for any links.     
View full article
Issue You need to set up DKIM for deliverability with Marketo, but another system you use already has DKIM set up with the default m1 selector. Solution You can create a Support ticket to request a custom DKIM selector be created (usually m2) for use in the "From Email" field on Email assets. Let support know what selector you want to use, and the domain you're want it to apply to- this is the domain value used in email assets, so for example@company.com, the domain would be "company.com" This will allow your existing integration to utilize the m1 selector, and Marketo can have DKIM under another domain.
View full article
Issue Lead was created but does not appear in the expected Workspace in the Lead Database.   Solution Check if there are any assignment rules that the lead may have qualified for a lead partition associated to another Workspace (e.g. Workspace B) docs.marketo.com/display/public/DOCS/Assigning+Person+Partitions+with+Assignment+Rules Check the lead's activity log to see if the lead's partition was changed after it was created to another partition associated to another Workspace (i.e. single flow action or via a smart campaign)  
View full article
Issue An Email Performance Report in Marketo was exported and opened in Microsoft Excel and the email open percentage and average click percentage is calculated using the AVERAGE function in Microsoft Excel. There is a difference in the average total calculated using the AVERAGE function in Microsoft Excel as opposed to the Total calculated in the Marketo Email Performance report.   Solution Marketo's total is a 'Weighted Average' which is different to a normal average calculation in Microsoft Excel "A weighted average differs from an average in that a weighted average returns a number that depends on the variables of both value and weight." support.microsoft.com/en-us/help/214049/how-to-calculate-weighted-averages-in-excel    
View full article
Issue The deep link in a Marketo email does not redirect to the designated App.   Solution By design in Marketo, when tracking is enabled for a link, the link will be wrapped with a tracking link like 'http://test.website.com/[unique sequence of characters]'. So when a tracked link is clicked, the link 'http://test.website.com/[unique sequence of characters]' is first loaded in a browser then redirects to the actual link in the same browser. Therefore, as some deep link configuration can depend on the actual link first loading, a tracked link in Marketo does not redirect to the App. One workaround here is to disable Marketo tracking link so that the deep link will redirect to the App. However, the trade-off of this is that the click link activity will not be recorded in Marketo.
View full article
Issue Interesting Moments for a specific Marketo record are not showing up in SFDC Sales Insight for the record with the same email.     Solution The most common cause for this is that the record in SFDC is not the same record as the one in Marketo.  This can happen if there are duplicate records in Salesforce with the same email address. To check if the record in Salesforce matches the record in Marketo, compare the SFDC ID.  On the Marketo side, this can be found in a field on the Lead Database record. The SFDC ID for a record in Salesforce can be obtained from the URL. It is generally the the 15 alphanumerical characters near the end of the URL (e.g. 012300000012BYN) - here is an article in Salesforce for more information: help.salesforce.com/articleView?id=000004383&type=1      
View full article
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    
View full article
Issue Issue Description You may see this warning message on your website, "The SSL certificate used to load resources from munchkin.marketo.net will be distrusted in M70. Once distrusted, users will be prevented from loading these resources. See g.co/chrome/symantecpkicerts for more information.     Solution Issue Resolution Marketo's security and operations team are aware of the plans for Chrome to distrust Symantec issued certificates and we are working on the replacement project before this happens.
View full article
Issue An Event Program in Marketo connected with ReadyTalk has some members with the status of "Registration Error" and a Status Reason of "Error registering with webinar provider. exception='Ready Talk API call error: ERROR -> HTTP Code ='403". The LaunchPoint connection in the Admin area may also show this error.   Solution This error is an API call that Marketo is getting back from ReadyTalk, and will apply to the individual record that encounters the error but doesn't impact subsequent records that are attempted to be synced. Additionally the LaunchPoint page displays the status of last API call and, if it failed, it displays that information there, but the error will go away when subsequent registrations are successful. This error can be caused by any of the following: Meeting is in a closed state - this can occur when either people try to register after the event is complete, or the date and time of the meeting is changed in ReadyTalk without using the "Refresh from Webinar Provider" feature in Marketo Meeting is cancelled. First name, last name, or email address is missing on the registration form. The format of a registrants email is invalid. (This usually occurs when a registrant enters something like .con instead of .com) The meeting title length is invalid, it must be between 1 and 300 characters. First name field exceeds 125 characters. Last name field exceeds 125 characters. The answer provided in a registration field exceeds 255 characters (i.e. Title, Company, Address, etc). If people are registering after the event is complete, one possible recommendation would be to have the registration landing page redirect to another landing page after the event has either initiated or completed, which provides people the opportunity to register for subsequent events. This way people that attempt to register for the event after it has concluded will not be able to do so, but they will be provided the option to register for future events. This will prevent people from trying to register for an event that has ended and closed, preventing future 403 errors. This doc walks through how you can do this: experienceleague.adobe.com/docs/marketo/using/product-docs/demand-generation/landing-pages/landing-page-actions/redirect-a-marketo-landing-page-to-another-page.html?lang=en   Who This Solution Applies To ReadyTalk integration users
View full article
Issue Note: If you have been migrated to Admin Console, refer to the Admin Console Overview page at https://helpx.adobe.com/enterprise/using/admin-console.html. When I go to the Support area of Nation, my access to the Portal is incorrect.     Solution Our system is particular about how you need to access the Support Portal before we can authorize you to use it.   The proper steps to take for us to authorize, and for you to submit cases, are as follows:   Log into your instance Click the Community tile (step 1 image) Click Support in the top banner (step 2 image) Click Submit a Case option (step 3 image) Choose from top options depending on what you need to do (step 4 image) Create a case, Manage authorized contacts, edit your Info   Simply going straight to the nation.marketo.com will not have the desired result. You must access the Support Portal from your instance by using these steps so that our system recognizes you properly. If this is your first time following these steps, your view of Step 3 will be different- not to worry, as that will be updated for you manually. Step 1 This is a article attached imageThis is a article attached image Step 2 This is a article attached imageThis is a article attached image   Step 3 This is a article attached imageThis is a article attached image Step 4 This is a article attached imageThis is a article attached image   If you experience issues, please email marketocares@marketo.com
View full article
Issue General recommendations for managing and improving deliverability to China.     Solution If you are looking for general recommendations around delivering to China, here are some resources both from our Community and external sources. Navigating email delivery into China Golden Shield Project overview Sampi China Email Marketing and Chinese Anti-Spam Laws Summary English language version of the Measures for Administration of Email Service on Internet Lehman, Lee & Xu English language version of the Measures for the Administration of Internet E-mail Services 2006
View full article
Issue Marketo forms that are embedded on external web pages see loading errors. Examples of this could be that the fields load with delay, or once submitted the form lags before moving to a follow up page.     Solution Two things to check: Is there custom CSS in your form? Is the embed code on your form customized?   Isolate the cause You can isolate the root of the lag by testing your form on a Marketo Landing Page   1. Locate the embedded form with in your instance 2. Build a landing page to test the form: Landing Page with a Form 3. Place your form on the new testing landing page, approve the page and close it. 4. Load the Landing Page using the URL   If the form loads with no delay, the issue lies with the embed code used to push the form onto the external page. Please work with your custom developer to find a resolution.   If the form is loading with a delay (and there is custom CSS):   1. Clone your form 2. Remove any custom CSS from with in the form 3. Build a landing page to test the form: Landing Page with a Form 4. Place your form on the new testing landing page, approve the page and close it. 5. Load the Landing Page using the URL   If you are not seeing any loading errors, the issue lies with in the custom CSS of your form. Please work with your custom coder to improve the loading speed of your form. Note: Occasionally, incorporating the form embed script into containers (custom coding) and utilizing custom JavaScript may lead to delays in form functionality. In such instances, it is recommended to collaborate with your developer to identify a solution, as Marketo Support does not troubleshoot issues specifically related to custom coding. If you are still seeing lag errors on your form loading on the Marketo Page, please submit a ticket with support@marketo.com    
View full article