Knowledgebase

Sort by:
Adobe Marketo offers a number of ways to contact Marketo Support directly for assistance from our different support regions. Further details about your Adobe Success Plan can be found HERE. Note: If your Marketo Instance and Users have been migrated to Admin Console, refer to this Admin Console Overview page for managing the Adobe entitlements across your organization and to engage Marketo Support.   Marketo Support Portal (https://support.marketo.com)   The Marketo Support Portal features a web form to submit support cases to Marketo Support. The form provides Authorized Support contacts the ability to provide details on the support issue that allows Marketo Support to efficiently and effectively assign your case to the best suited available support engineer. We encourage you to leverage our Best Practices when submitting your case to Marketo Support.   Support Services – Regions, Hours, and Languages Authorized Support contacts can engage Marketo Support by calling one of our Adobe Enterprise Phone Numbers for your region. Live Telephone and Online Technical Support Priority 1 incidents: 24x7x365 via phone or online support case Priority 2-4 incidents: Support available during regional business hours via chat or online support case. Regional Business Hours Applicable regional business hours are based on the billing address in the Sales Order or purchasing documents. If Adobe is contacted for support by someone other than the designated Named Support Contacts, Adobe may request that that the support case be resubmitted by a Named Support Contact. Languages Japanese language support is available during Japanese regional business hours, excluding holidays or Adobe days off. Japanese support is not available for Adobe Commerce. With the above exception, all Support will only be provided in English. Support Access Customer will grant Adobe Support access to applicable customer systems via remote support tools controlled by Adobe for the purpose of troubleshooting and support services. Regional Business Hours for Support Applicable regional business hours are based on the billing address in the Sales Order or purchasing documents.   Americas Europe, Middle East & Africa Asia Pacific Japan 6 am – 5:30 pm 9 am – 5 pm 9 am – 5 pm 9 am – 5 pm  
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
Issue You have integrated Marketo and Facebook Lead Ads in Marketo Admin > Launchpoint, and your test form-fills are not appearing in the Marketo Lead Database. Solution Occasionally the integration between Marketo and Facebook needs to be re-authorized. This is one of the primary troubleshooting steps we start with in these situations. The instructions for re-authorizing are as follows: Navigate to Marketo Admin > Launchpoint, and take note of the Facebook User that is used in the Lanchpoint integration, Log into the Facebook Business Account, and navigate to the settings where the Admins are added/removed Remove the User, and save changes Re-add the User back to the Business Account as an Admin, save changes Navigate back to Marketo Admin > Launchpoint, and edit the Facebook Lead Ads integration, Proceed with 'Next' to view the Facebook Account, and click 'Re-Authorize' The final step after this would be to attempt another form-fill on a Facebook form to see if the activities are appearing in Marketo.
View full article
Issue Clearing cache and cookies in your browser will fix a number of different problems related to page display, browser errors, and login issues.     Solution Here are links to the support articles on how to clear cache and cookies for the most commonly used browsers. Chrome Clear cache and cookies - Computer - Google Account Help   FireFox How to clear the Firefox cache | Firefox Help   Internet Explorer https://support.microsoft.com/en-us/help/278835/how-to-delete-cookie-files-in-internet-explorer   Microsoft Edge Microsoft Edge, browsing data, and privacy – Microsoft privacy    
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 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
  Overview Add Leads to Static Lists Use Custom Fields Overview Lead records have two primary components – lead attributes and activity logs. Lead attributes are the fields and field values within the lead record. For example, Job Title is a lead attribute. Lead Name is a lead attribute. Activity logs record the actions Marketo or the lead themselves have taken. For example, sending an email to a lead is an activity that would show in the activity log. If the lead opens the email or visits a tracked page, those activities would show in the activity log as well.   Activities in the activity log are only retained for 25 months, or 37 if you have purchased the premium data retention option. The main way to store activity data beyond the Data Retention Policy timeframe is to use the Bulk Extract API. There are two other ways you can keep a reference of these activities after the end of the Data Retention period, and they can be referenced within the Marketo UI. This article will show you how that can be done.     Add Leads to Static Lists Static lists will retain lead membership even if the activity of adding the lead to the list has been removed. This will let you have lists dedicated to specific criteria that would otherwise be removed after the data retention time period has been passed.   For example, Smart Campaign membership history is not retained after 25 months. If you are searching for members of a Smart Campaign, but a lead first became a member of the Smart Campaign more than 25 months ago, the search results would not include that lead.   An easy way to work around that is to add your leads to a static list as part of the flow of the campaign. When creating your Smart Campaign, create a new static list with the same corresponding name (makes it easier to identify later). When building the flow of your campaign, add the "Add to List" flow step so that all leads going through the campaign will be logged on the list.         Use Custom Fields Lead attributes and their field values are not affected by the Data Retention Policy. Use Smart Campaigns to populate custom fields with values based on activities your leads take. This will allow you to filter leads by these lead attributes that are not affected by the Data Retention Policy. A side benefit to this is that it is faster to search by lead attributes than by searching through lead activity logs.   Example: This approach can work for many different activities, but let’s use form fill outs as an example.   Let’s say you want to be able to identify leads who have been very active and have filled out more than 5 forms over their lifecycle. You could use the filter “Filled Out Form” with the “Min. Number of Times” constraint set to 5. However, if one of those forms filled out occurred more than 25 months ago, the filter would only be able to access 4 form fill activities in the activity log. Therefore, the lead would not pass the filter.   Instead of using the “Filled Out Form” filter, set up a Smart Campaign to write to custom fields that show you how many forms they’ve filled out, and when the first one was. Here’s how to do it:   1. Create two new custom fields in Marketo, one Score Field, and the second a Date Field.   2. Create a new Smart Campaign   3. Add the trigger “Fills Out Form” set to “is any” to the Campaign Smart List     4. Add these two Flow Steps to the Campaign Flow: Flow Step 1: “Change Score” Score Field Name: your score field name Change: +1   Flow Step 2: “Change Data Value” Add Choice to Flow Step Choice 1: If “your score field name”  “is empty” Attribute “your score field name” New Value: {{system.date}} Default Choice: Do Nothing       This campaign will listen for any time a lead fills out a form, add +1 to your score field, and if it’s the very first form they’ve ever filled out, it will log the date of when it was done. If the lead has ever filled out a form in the past, there will already be a date value in the date field, so the flow choice would just skip over it and do nothing.       Results You’ll See: With the original goal of identifying leads who have filled out more than 5 forms you’ll be able to filter for leads that have filled out at least 5 forms. In addition, this campaign will let you search for leads based on when they had filled out their very first form, regardless of how long ago it was. Since it’s stored in a lead field, it’s a lead attribute that is not affected by the Data Retention Policy at all.      
View full article
Note: Once you have migrated to Admin Console, you can manage your support cases through the feature provided in the Admin Console Platform. To learn more, visit: https://experienceleague.adobe.com/docs/customer-one/using/home.html. Once you have submitted a case to Marketo support, we provide a simple way of staying connected to your case and the cases submitted from your company through the Marketo Support Portal. You can access the support portal through your Marketo instance by selecting Community in the top right corner: This is a article attached image You can also access the support portal directly at https://support.marketo.com and login with your Marketo credentials (login and password). This will not work for users with SSO.   Once you are in the support portal you can Create a Case for Marketo Support or you can also review any cases that are open and being worked on by support or review your case history. Navigate to My Case management: This is a article attached image From the My Cases navigation you can access the following case views: This is a article attached image My Recent Cases* - Cases that you have opened in the past 30 days All Company Recent Cases* - Cases that any authorized support contact has opened in the past 30 days My Open Cases – Cases created by you that are being triaged by Support and pending Support’s response and are more than 30 days old My Closed Cases – Cases that were created by you and are now closed My Awaiting Fix Cases – Cases that were created by you where Marketo is developing a fix which will be implemented at a later date All Company Closed Cases – Cases that were created by you or your colleagues that are now closed All Company Open Cases - All open cases submitted for the account Company Awaiting Fix Cases – Cases that were created by you or your colleagues where Marketo is developing a fix which will be implemented at a later date Management Escalations - Escalations opened by you or your colleagues  Survey Cases - Surveys that are available for you to fill out after a case is closed *Cases that have been opened for more than 30 days will move from Recent cases to Open cases   To view specific case details, click a case number. This is a article attached image From the Case Details, you can perform the following: Close your Case - Select the "My Case is Resolved" button to close your case Add Comments - Provide additional comments to support or respond to a Support question Add Attachment - Provide any screenshots or documents that will help illustrate the issue you are reporting   If your case has been closed there are two options available to you.   Reopen - You can reopen your case if you are not satisfied with the case resolution by adding a comment in the case. Case Survey - Once your case has closed, please consider offering feedback on the level of Support you received.
View full article
If you have submitted a support case and you feel that the case was improperly handled or that the solution being offered does not meet the communicated Marketo support expectations, then we would welcome the opportunity to look deeper at your specific support engagement and work with you on delivering a better resolution. Caution: If the item you're looking to escalate is related to a Production Down incident, please call the support line for your region to receive immediate assistance. Support Manager escalations are only handled during normal business hours. The phone numbers for each region are listed below, follow the prompts for P1: Americas: +1.877.270.6586, Direct: +1.650.376.2303 Europe, Middle East, & Africa: +353 (0)1 242 3030,  UK: 0800 151 3030 Asia Pacific: +61 2 8310 7646  Japan: +81.03.4233.9014 How to Escalate: Step 1. Navigate to the "Case Management" area of the support portal either by mousing over the Support tab and selecting "Case Management" or clicking the Support tab and click on the “My Case Management” button. NOTE: You will need an open or recently closed case in order to escalate to support leadership. This is a article attached image Step 2. From here you will need to click on either an open or a recently closed* case: This is a article attached image *Support Cases that have been closed for longer than 10 days are no longer eligible to be re-opened and we ask that you open a new support ticket for your current issue prior to escalating to a Support Manager. We ask that you have an open support ticket for a Support Manager to be able to address specific issues. Step 3. After selecting a case, click on the Escalate to Manager button: This is a article attached image Step 4. A pop up will display and you will need to the purpose for the escalation and click on the “Escalate” button. This is a article attached image Once your support escalation case has been submitted a Marketo Support Leader will contact you within 1 business day of your support region's support hours to address the issue.
View full article
    Overview Add Leads to Static Lists Use Custom Fields Overview Lead records have two primary components – lead attributes and activity logs. Lead attributes are the fields and field values within the lead record. For example, Job Title is a lead attribute. Lead Name is a lead attribute. Activity logs record the actions Marketo or the lead themselves have taken. For example, sending an email to a lead is an activity that would show in the activity log. If the lead opens the email or visits a tracked page, those activities would show in the activity log as well.   Activities in the activity log are only retained for 90 days, 25 months, or 37 if you have purchased the premium data retention option. The official Marketo Data Retention Policy can be found here: Marketo Activities Data Retention Policy   The main way to store activity data beyond the Data Retention Policy timeframe is to use the Bulk Extract API. There are two other ways you can keep a reference of these activities after the end of the Data Retention period, and they can be referenced within the Marketo UI. This article will show you how that can be done.     Add Leads to Static Lists Static lists will retain lead membership even if the activity of adding the lead to the list has been removed. This will let you have lists dedicated to specific criteria that would otherwise be removed after the data retention time period has been passed.   For example, Smart Campaign membership history is not retained after 25 months. If you are searching for members of a Smart Campaign, but a lead first became a member of the Smart Campaign more than 25 months ago, the search results would not include that lead.   An easy way to work around that is to add your leads to a static list as part of the flow of the campaign. When creating your Smart Campaign, create a new static list with the same corresponding name (makes it easier to identify later). When building the flow of your campaign, add the "Add to List" flow step so that all leads going through the campaign will be logged on the list.   Use Custom Fields Lead attributes and their field values are not affected by the Data Retention Policy. Use Smart Campaigns to populate custom fields with values based on activities your leads take. This will allow you to filter leads by these lead attributes that are not affected by the Data Retention Policy. A side benefit to this is that it is faster to search by lead attributes than by searching through lead activity logs.   Example: This approach can work for many different activities, but let’s use form fill outs as an example.   Let’s say you want to be able to identify leads who have been very active and have filled out more than 5 forms over their lifecycle. You could use the filter “Filled Out Form” with the “Min. Number of Times” constraint set to 5. However, if one of those forms filled out occurred more than 25 months ago, the filter would only be able to access 4 form fill activities in the activity log. Therefore, the lead would not pass the filter.   Instead of using the “Filled Out Form” filter, set up a Smart Campaign to write to custom fields that show you how many forms they’ve filled out, and when the first one was. Here’s how to do it:   1. Create two new custom fields in Marketo, one Score Field, and the second a Date Field.   2. Create a new Smart Campaign   3. Add the trigger “Fills Out Form” set to “is any” to the Campaign Smart List 4. Add these two Flow Steps to the Campaign Flow: Flow Step 1: “Change Score” Score Field Name: your score field name Change: +1   Flow Step 2: “Change Data Value” Add Choice to Flow Step Choice 1: If “your score field name”  “is empty” Attribute “your score field name” New Value: {{system.date}} Default Choice: Do Nothing This campaign will listen for any time a lead fills out a form, add +1 to your score field, and if it’s the very first form they’ve ever filled out, it will log the date of when it was done. If the lead has ever filled out a form in the past, there will already be a date value in the date field, so the flow choice would just skip over it and do nothing. Results You’ll See: With the original goal of identifying leads who have filled out more than 5 forms you’ll be able to filter for leads that have filled out at least 5 forms. In addition, this campaign will let you search for leads based on when they had filled out their very first form, regardless of how long ago it was. Since it’s stored in a lead field, it’s a lead attribute that is not affected by the Data Retention Policy at all.
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
Marketo Support's Mission is: To provide fast and friendly world-class support through creative, flexible solutions to empower Marketo Automation Software success.   Areas of Responsibility: Technical Support Engineers (TSEs) are your initial point of contact for any technical questions or concerns. TSEs are responsible for troubleshooting issues within your Marketo instance and common include:   My Marketo Marketing Activities Design Studio Lead Database Analytics Revenue Explorer (RCA/RCE) Calendar Deliverability Tools Search Engine Optimization (SEO) Web Personalization (RTP) Admin Community   Our TSEs are not web developers and as a result they are unable to troubleshoot most types of custom coding (ie. HTML, JavaScript, XML, etc.). Our support team is able to help with the following types of non-custom code:    Simple Munchkin Code Asynchronous Munchkin Code Asynchronous jQuery Munchkin Code SOAP API REST API   Our TSEs are here to assist you and our support commitment to our customers is to always work towards providing an above and beyond support experience.   Note: Our team is not against looking at custom code and, based on the subject matter expertise, our TSEs might be able to offer suggestions and recommendations, but we do want to make it clear that they are not responsible for fixing or updating any custom code that has been implemented.   Response Time   Our TSEs are bound to responding to your cases and issues within the Service Level Agreements from your account's level of support services.  We track response milestones to ensure that your cases are being handled in a timely manner as dictated by our agreed to Service Level Targets.
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, complete 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
  Full Details of all Marketo Support Offerings:   Support Levels Offered   Service Level Response Targets   Global Contact   https://support.marketo.com:             Online Support Portal for Case management and Knowledgebase search support@marketo.com:                     Email to Case Submission supportescalations@marketo.com:   Contact Support management regarding Support services marketocares@marketo.com:            Questions regarding Support or Community access   Regional Contact Information Americas: Hours: M-F, 6am to 6pm Pacific Toll Free US: +1 877 270 6586 Direct: +1 650 376 2303   Languages Supported: English, Spanish Observed Holidays: New Year's Day Independence Day Thanksgiving Day and the Day After Christmas Day New Year's Eve Europe, Middle East, & Africa: Hours: M-F, 8am to 5pm GMT Europe: +353 (0)1 511 9556 UK: 0800 151 3030   Languages Supported: English, French, German, Portuguese Observed Holidays: New Year's Day Easter Monday Christmas Day St. Stephen's Day Australia Hours: M-F, 9am to 6pm AET ANZ: +61 2 8031 8188   Languages Supported: English Observed Holidays: New Year's Day                           ANZAC Day Christmas Day                             Good Friday Easter Monday                             Boxing Day Japan: Hours: M-F, 9am to 6pm JST JP: +81.03.4233.9014   Languages Supported: Japanese Observed Holidays: New Year's Holiday                      Marine Day Coming of Age Day                      Respect for Senior Citizens Day National Founding Day                National Holiday Spring Equinox Day                     Autumnal Equinox Day Day of Showa                              Sports Day Constitution Memorial Day          Culture Day Green Day                                   Labor Thanksgiving Day Children's Day                             Emperor's Birthday Substitute Public Holiday             Year End After-hours Support for Production Down Issues: Online: Enter a Support Portal Case with Priority=P1 Phone: Call Support Line and follow the P1 prompts   Initial Response SLT We ask that you use the following priority definitions when setting your case priority: Priority Description P1 Critical Business Impact: ​ Customer's production business functions are down or have significant data loss or service degradation and immediate attention is required to restore functionality and usability. P2 Major Business Impact:​ Customer's business functions have major service degradation or potential data loss, or a major feature is impacted. P3 Minimal Business Impact: ​ Customer's business functions have minor service degradation but there exists a solution/workaround allowing business functions to continue normally.   P4 No business impact:​ General question regarding current product functionality or an enhancement request.
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
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
  Welcome to Marketo Support This guide provides individual links that covers the following topics: Marketo Support Policies Service Level Agreement How to Contact Marketo Support How to Submit a Case Tips on Effective Case Submission Managing Authorized Support Contacts (Support Admins) Managing Your Cases How to Escalate    
View full article
Issue Leads in a GoToWebinar event program have a "registration error" status. Solution If this is affecting all new leads registering for the webinar:  This is caused by Marketo losing connection with the GoToWebinar service.  To resolve this Go to Admin > Launchpoint. Open the GoToWebinar service. Re-enter your GoToWebinar credentials. Once this is done, you can go back to the webinar program and change the status of the affected leads from "Registration Error" to "Registered." If this is affecting only specific leads registering for the webinar:  Check the name, email, company, and job title fields for any special characters. GoToWebinar often doesn't allow special characters and will throw an error. 
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 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