Knowledgebase

Sort by:
Issue Users for your Marketo instance are unable to log into the instance. Solution Check your landing page URLs and email links. If these are also unavailable, your Marketo instance may have been shut off. Marketo Support can confirm whether your instance has been deactivated, but are not able to reactivate it.  In this situation, please contact your Marketo Account Representative to discuss the status of the instance and regaining access.        
View full article
Issue When I go to the Support area of Nation, I do not have full access to all the areas and tools.   Solution Our system is specific 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 Step 2   Step 3 Step 4   If you experience issues, please email marketocares@marketo.com
View full article
Summary Unable to update Person Source as expected for records created with the LinkedIn Lead Gen Forms and Facebook Lead Ads integrations. Issue New records created through LinkedIn Lead Gen forms as well as Facebook Lead Ads results in the records not updating the Person Source field as expected.  Solution Person Source may be set to block updates to the field as noted in the example for Block Updates to a Field - Marketo Docs - Product Documentation.  To resolve the issue ensure the field is not set to block updates for the desired update method.  Alternatively the Person Source values populated by the integrations can be kept and expected values can be updated to include these sources.  Root Cause The LinkedIn Lead Gen Forms and Facebook Lead Ads integrations automatically update the Person Source to preset values when a new record is created in Marketo through the integrations. Blocking field updates to the field may prevent the value from changing to pre-configured values as a value already exist for the integration created records.  Environment LinkedIn Lead Gen Forms Facebook Lead Ads
View full article
Issue Description Is it possible to integrate multiple social media accounts with Marketo? Issue Resolution There is  only one LaunchPoint service for each, but multiple accounts can be referenced in : Lead gen forms - Linkedln Custom audiences - Facebook
View full article
Issue The webhook error type "The remote server's SSL certificate or SSH fingerprint was rejected" occurs when the SSL certificate is being used on the main domain and not Sub-domains.     Solution Check the URL in Admin > Webhooks Click on the webhook in the right corner. For example, if the URL is, https://onlineservices.test.marketo.com, the certificate needs to be valid on *.test.marketo.com and not just *.Marketo.com. Check this by verifying the certificate on "https://www.sslshopper.com" and all the certificates will be listed as Subject Alternative Name's if the certificate is valid on the sub-domains. For example: For Google.com "https://www.sslshopper.com/ssl-checker.html#hostname=google.com", the certificate is valid on *.Google.com as well as all the subdomains as listed in SAN's.    
View full article
Issue Discrepancy between Marketo webinar atttendance and webinar provider attendence report Solution Compare Webex report with Marketo Program members list to determine which leads are involved. Check to see if the leads involved have the same email address but used different names to register/attend. Workaround: Upload Webex final report to a static list and use the list to update the program attendance.   Root Cause Webex issues two reports, a preliminary when the webinar is finished and a final report approx. 12 hours later, which may have updated attendance info.  Marketo Engage uses the preliminary report to set the attended status in the program and does not update when the final report is released. Environment Webex Marketo Event Program synced to Webex webinar Final attendance report from Webex, not preliminary
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: https://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 Do webhook calls contribute to the daily API limit/quota visible in [Admin > Integration > Web Services > API Call Information] ?   Solution No, webhook calls are not counted as part of the daily API limit. Webhooks do not have any execution limits.  
View full article
Summary Smart campaign utilizing the 'Fills Out Facebook Lead Ads Form' trigger does not generate any results for people created as a result of filling out a Facebook Lead Ads form. Issue Smart campaigns utilizing the 'Fills Out Facebook Lead Ads Form' Trigger does not trigger for people created as a result of filling out a Facebook Lead Ads form. Solution If you have Workspaces and Partitions set up on your instance, it is important to remember that people created in the database as a result of filling out Facebook Lead Ads form, will be automatically created in your Default partition per design.  In a scenario where a trigger campaign is hosted under a workspace that does not have the appropriate visibility to your default partition - the person filling out the Facebook Lead Ad form would not be triggering the campaign.    Solution Make sure your trigger campaign lives under workspace which has visibility over the default person partition. To check the workspace configuration go to Admin > Workspaces & Partitions and make sure your default partition is assigned to the workspace where your trigger campaign lives under.  Root Cause New people which are being created in Marketo as a result of filling out a Facebook Lead Ads Form will be created by default in the Default lead partition. Environment Customers who have Workspaces and Partitions set up in their instance. Customers who have set up the Facebook Lead Ads integration and have utilized the  'Fills Out Facebook Lead Ads Form' Trigger
View full article
Issue LinkedIn leads generated through LinkedIn Lead Gen form does not populate Inferred State/City/Country values. Solution Use field mapping between Marketo and LinkedIn to make sure inferred State/City/Country fields are mapped to respective LinkedIn fields so that they are captured in Marketo. Root Cause The inferred State/City/Country is populated via the person tokens and that information is normally captured when a lead fills out a Marketo form. If instead, the form used is a LinkedIn form, then that information is not passed over to the Marketo lead fields. Environment Marketing Activities LinkedIn Lead Gen
View full article
Issue: When creating an event the WebEx connector may throw the message: Error registering with webinar provider. exception="WebEx API call error; Self registration is not supported by this service type or current meeting. [WebEx exception ID = '110051'] "   Solution: Please make sure the event in WebEx is set up to receive registrations. To do this you need to go to the event in WebEx and check the registration required checkbox. References Create an Event with WebEx - Marketo Docs - Product Docs WebEx Event Center guide    
View full article
Issue Webinar integration is giving an error "Invalid Username or Password" during setup, even though the username and password are correct. The webinar provider uses your Single Sign-On (SSO) provider for login.     Solution Marketo is not able to access the SSO provider and will not be able to log into the service if SSO is used. Use the following workaround for your integration. Disable SSO for the webinar service so that a user with login and password can be used in the Marketo Launchpoint service.  Create the integration user in the webinar provider and complete the integration Re-enable SSO for your webinar service after the webinar is over.   Who This Solution Applies To Clients leveraging SSO for Launchpoint services    
View full article
Issue Is it possible to integrate multiple social media accounts with Marketo for integration with services such as Facebook and Google? Solution There is  only one LaunchPoint service for each, but multiple accounts can be referenced in : Lead gen forms - Linkedln Custom audiences - Facebook    
View full article
Issue When attempting to import an audience through the Facebook Custom Audience integration an error is received with a variation of the following error text: "error_code": 1870068, "error_summary": "Contains a Disabled Audience", "error_message": "Contains a Disabled Audience: This ad set was paused because it contains at least one audience that was disabled. Disabled audiences were shared by accounts that are no longer active. To fix this issue, remove the affected audiences: <affected_audience_names>" Solution Facebook allows for audiences to be shared across multiple business managers. In the past, if one business manager was disabled after sharing an audience, the remaining mangers would still have access to that shared audience. Facebook made a policy change December 11th, 2018 which has removed the ability to access those shared audiences owned by disabled accounts.       To resolve this error, the disabled account must be reinstated by Facebook or an alternate audience with an active Facebook account must be chosen     Who This Solution Applies To Clients Utilizing Facebook Custom Audiences
View full article
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
View full article
Issue The GoToWebinar integration is not able to see a webinar that has been set up as a "Simulated Live" record type. Solution GoToWebinar requires v2 for the GoToWebinar API for the "Simulated Live" webinars.  Marketo is still on v1 of the API so "Simulated Live" webinars are not supported at this time.    Who This Solution Applies To Customers integrated with GoToWebinar
View full article
Issue Issue Description When attempting to add an additional Facebook or LinkedIn Launchpoint service, it does not appear as an option in the drop down.     Solution Issue Resolution While we only support one Launchpoint service for each integration type, we support multiple accounts through the Launchpoint service that the customer adds. The user account that is used to authenticate the service will need to have the appropriate permissions to each business page that is going to be used by the instance.
View full article
Issue Google Adwords gives the error message " This Google AdWords account is already connected to Marketo and can only be used once. Revoke access in your Google account settings and try again." Solution 1. Click on the Gear Menu in Adwords and Click on "Account Access" tab under account settings. 2. Under Actions menu, Select "Edit Google accounts info" for the Adwords user credentials used in Marketo 3. That will bring up a separate page -  myaccount.google.com. 4. In the "Sign-in & security" page there's a "Connected apps & sites" section that lists all of the apps connected to the account - one of them should be Marketo. 5. Clicking the "Manage Apps" link should bring up a list of apps, and clicking on the Marketo app should give you the option to Remove. 6. Once removed, you should be able to reauthorize the account in Marketo.    
View full article
Issue What type of formats are accepted for uploading data to Facebook custom audiences from Marketo?   Solution Note: The phone numbers must always have the country code included even if they are in the same country as your business.. The endpoint for facebook allows the following formats: 1-234-567-8910 12345678910 +44 123 456 7890 With or without punctuation is allowed.          
View full article
Summary Adding Webinars from Additional Users Issue After setting up the Marketo/Zoom integration and attempting to connect a Webinar to an Event Program, you may see the message "This Account has no Webinars" or certain webinars may be missing as an option.  Environment Zoom/Marketo Solution When setting up the Marketo/Zoom integration an Admin user must be connected to the Launchpoint integration. By default, only webinars created directly by this Zoom user will appear as options. If other users have shared webinars with this admin, additional steps must be taken to make them visible in Marketo. In this article you will find the steps to add additional Zoom users to the Marketo integration configuration. Once those users have been added, webinars they own will be available as options in Marketo. Webinars owned by users not added with the instructions above will not be available in Marketo.   
View full article