Knowledgebase

Sort by:
Issue Description When you copy the URL for an Image asset in Design Studio and put it in your email or Landing Page, the image won't load. Other images with the same dimensions work. Issue Resolution The issue may be that there is a space in the URL. When you replace that space with a %20, the image works.
View full article
Issue Description You are utilizing Forms on Marketo Landing Pages, and want to run reporting on these forms.   Issue Resolution Currently the only asset reporting Marketo has is Email, and a little bit of Landing Page reporting. We would not have this ability to report on Forms.   One option would be to use Web Page reporting  -  this reported information would be limited to Marketo Pages with numbers of records who filled out the form, listed under "conversions." You could then create a Smart List to identify leads who have filled out these forms.     Is this article helpful ? YesNo
View full article
Issue Description Even though the report and smart list may be looking at exactly the same thing (e.g. an email sent to a specific group on a specific day), many times the numbers in the report do not match the results of the smart list. Issue Resolution Reports in Marketo like the Email Performance Report are returning results of activities that occurred in your instance, while smart lists return results of currently existing person records.  When a person is deleted or merged, the activities associated with the person do not get pruned or purged. So a smart list that looks for opened email will return all the currently existing records who have that open activity but will not return results of deleted or merged records.  Conversely, a report looking at the same thing will return all activities, even if the records no longer exist.
View full article
Issue Description When there is a change to a field in your CRM that is mapped to a Marketo score type field, the next time the sync processes the change will be reverted and there will be a "Sync Person Updates" activity logged showing that the original value got pushed back from Marketo to the CRM. Issue Resolution Score type fields are designed to be managed solely by Marketo, since that is a unique field type to our system.  Scoring is intended to be handled by the scoring campaigns that you set up in Marketo, and pushed to the CRM if necessary. If you have a score field that you intend to put processes in place where your CRM will be updating the values, simply make sure that the Marketo field that it is mapped to is an Integer type field. Who This Solution Applies To All instances with a native CRM integration (SFDC or MSD)
View full article
Issue Description When a piece of predictive content is approved the following error appears: "Action failed. Please contact support. Error code:24 Error message: Invalid email title Error message: internal error, reported to support"   Issue Resolution Change the title of the content to less than 48 characters.   This error indicates that the title for the content is too long. The maximum number of characters for a title in content AI is 48 characters.   Who This Solution Applies To Customers with RTP/Web Personalization/Predictive Content/Content AI Is this article helpful ? YesNo
View full article
Issue Description Can a Default program in a nurture stream be changed to the Nurture Channel for reporting purposes? Issue Resolution Program Channels can only be applied to one type of Program. Nurture Channel will only be usable on a Engagement type program. You can however have multiple channels avaliable for a specific type of program! So you can have one program type with multiple channel options, but you cannot have one channel used for multiple program types.
View full article
Issue Description We have a field (Field Label: Account Record Type, Field Name: RecordType, Data Type: Record Type) in SFDC that is visible to Marketo Sync User but it is not syncing the field to Marketo. We are unable to find the specific field in Admin -> Field management.   Issue Resolution We do not have the Record Type field synced to Marketo. Instead, we sync the Record Type ID, which gives the alphanumeric string for the record type.   Marketo Sync user does not have access to Salesforce record type.   There is a work around to get the record type names that is discussed here:   https://nation.marketo.com/blogs/marketowhisperer/2016/04/09/setting-the-sfdc-record-type           Who This Solution Applies To Customers integrated with Salesforce Is this article helpful ? YesNo
View full article
Issue Description After running an A/B test, some Lead records appear to have received both Test and Winner.   Issue Resolution In an A/B test, the sample size of the audience is sent the variants, and then for the winner: the entire audience minus the test audience is sent the Winning email.   So let's say that you received both Test and Winner. This means you have duplicate records in the database.   Marketo is designed to not send duplicate leads the same email at the same time.   So one of the duplicates is qualified for the Test, and then when the Winner is sent, it's the total audience minus the test audience, the Winner is sent to the duplicate record.   This above situation can apply to Lead Records as well, because of duplicates with the same email address, but also duplicate records that may have a FWD set up between them (record B emails FWD to Record A email address).   Because this is expected from the design decision, the resolution is to deduplicate your database. Is this article helpful ? YesNo
View full article
Issue Description You are testing a new Trigger campaign, and your test records are meeting the Filters, but the campaign is still not triggering from the testing.   Issue Resolution A likely reason that Marketo records do not process through Trigger Campaigns (with >1 Filters) when the record is performs the Trigger Action is because the record does not meet the Filter criteria.   Records must have the Filter attributes established prior to the Trigger Action occurring.   For Trigger Campaigns that are not triggering records because there is a delay in the Filter Attributes having the necessary data, Support will generally recommend a daily recurring Batch Campaign with the same Flow to catch and process those records that fall through the cracks, but there's another suggestion I could give you: turning filters into Remove from Flow flowsteps!   Trigger Campaigns happen real time, but occasionally, a daily batch campaign is too long of a wait. But the purpose of this alternative workaround is to allow the attribute data be written on the records, but not to wait so long for the daily Batch Campaign to run.       For example:   You have a Trigger Campaign, with filters: [attribute] is True   1) Then you can take this Filter, remove it from the Smart List and turn it into a Remove from Flow flowstep with a choice:   Remove from Flow: if [attribute] is False, then Remove from This Campaign.     2) This Remove from Flow flowstep will need to follow a Wait Step. The Wait Step needs to be long enough to allow the necessary Filter Attribute data to be written on the Marketo Record. So if the Filter Attribute Data comes through to the record about 45 minutes after the Trigger Action, then the first Flow Step should be Wait 1 hour.   There's a 1:1 ratio for number of filters turned to number of Remove from Flow flowsteps. If there were 4 filters it would be turned into 4 flowsteps with the negative logic (shown in the above example) to then filter out records.   3) Finally, after the Remove from Flow flowsteps, the same Flow Steps will be used to carry out the desired actions on the record.     It's a little complex, but it's a nice middle ground between Trigger, and Daily Recurring Batch.   Who This Solution Applies To Is this article helpful ? YesNo
View full article
Issue Description The "View In Browser" link gives an error "Customer does not belong to any POD" when clicked in the Email Preview or in exported email HTML. Issue Resolution When you Preview an Email you are viewing the layout of the email, but system tokens will not function. This is also true of exported HTML. When you send a Sample Email, you can test the the system tokens {{system.viewAsWebpageLink}} as though you were the customer.
View full article
Issue Description The lead's activity log shows that the 'Sync Person to SFDC' flow step failed because of the following message:   "Failed: INVALID_CROSS_REFERENCE_KEY: Record Type ID: this ID value isn't valid for the user:"   Issue Resolution The issue is the SFDC ID value populated in the "Record Type ID" field is not considered a valid value in Salesforce for the Lead/Contact.  You'll want to work with your SFDC Admin to identify a valid value or try deleting the value in Marketo and then updating this value from the Salesforce side.     Is this article helpful ? YesNo
View full article
Upcoming Change to Chrome Browser In October 2017, the Google Chrome browser will change the notifications it displays for unsecured HTTP web pages. Secured HTTPS web pages will not be affected. In January 2017, Chrome started marking HTTP pages as “Not secure” if they contained forms that included password or credit card fields. With the release of Chrome 62, the browser will show the “Not secure” warning for all HTTP pages containing forms, and all HTTP pages visited in Incognito mode. Because form submittals can contain sensitive information beyond passwords and credit card numbers, Chrome will now warn users that a page is not secure whenever data can be entered/submitted. Eventually, Chrome plans to display the “Not secure” warning for all HTTP pages, regardless of whether they contain forms or are viewed in Incognito mode. Effect on Marketo Landing Pages It is important to note that this affects all HTTP web pages viewed in Chrome, not just Marketo landing pages. However, all Marketo landing pages will be affected if SSL has not been set up for the instance. This will not prevent people from viewing your landing pages or submitting your forms. The only change will be the “Not secure” warning displayed in the address bar. If you already have SSL set up for your Marketo instance, you will not be affected by the change in Chrome’s behavior. Steps to Take There are two options for responding to this change. The first is to do nothing. Your landing pages and forms will continue to work as before. The only difference will be the “Not secure” notification in the browser’s address bar. The second option would be to purchase SSL for your Marketo instance. There are advantages to having SSL set up on your Marketo instance. Not only does it provide increased security for your customer base, but Google has announced that it will give preferential search ranking to HTTPS pages. If you would like add SSL to your Marketo subscription, please contact your Marketo account manager.  Here is some documentation on how to Add SSL to Your Landing Pages
View full article
On August 24, 2017, Marketo and Google Cloud made an exciting announcement about a broader collaboration to transform engagement solutions for the enterprise. We understand you may have questions, and we’ve prepared the following FAQ that provides additional details. 1)  What did Marketo and Google Cloud announce? Today, Marketo and Google Cloud, two technology thought leaders announced a multi-year alliance that will drive innovation and deliver next generation global marketing solutions on the Google Cloud Platform.  2)  Why is this great for Marketo customers and partners? The MarTech and AdTech worlds have remained silo-ed for far too long. This alliance will simplify the technology landscape for the marketer and enable them to more effectively listen, learn, and engage with buyers across all digital channels, including digital ads. In addition, it will provide the scale, reliability, and security required for enterprises to conduct business in today’s digital world. 3)  What does the alliance entail? The alliance between Marketo and Google Cloud includes the following: Marketo and Google Cloud will invest resources in co-innovation in a number of areas. Beginning in 2018, Marketo will run its marketing automation products and data centers entirely on Google Cloud Platform for all customers worldwide. Google will expand its usage of Marketo’s Engagement Platform across its businesses. 4)  Why did Marketo select Google for its public cloud?  We’ve been planning a move to a public cloud infrastructure for some time as we believe it’s necessary to deliver the scale, reliability, and security that our customers and partners demand to succeed in today’s hyper-digital world. We selected Google for a number of reasons, including its industry-leading knowledge and expertise building secure cloud infrastructure and applications at scale as well as the significant strategic and technology advantages we saw versus other clouds. 5)  Will Marketo continue to build and support its own data centers? Until the migration to Google Cloud infrastructure, Marketo will continue to operate, manage, and support its own data centers. 6)  Will this change impact my Marketo subscription or agreement? Moving Marketo’s marketing automation products and data centers to Google Cloud Platform will not change or impact your Marketo subscription. We will update our End User Service Agreement as appropriate to reference any relevant changes.
View full article
Dear valued customer, As you may know, on July 25th, 2017, our main web site, Marketo.com, along with other Marketo domain properties, were rendered inaccessible, preventing access to our application from 4:06am – 10:08am PDT. We apologize again for the inconvenience this caused. On the Marketo Trust site, you’ll find current and past Marketo system performance data including System Uptime and Reliability. This is monitored 24x7 and we have consistently maintained greater than 99.9% uptime. This uptime is calculated based on the length of time that the Marketo systems are functioning properly within our servers (“pods”). While the Marketo systems were functioning and available by 10:08am PDT, we realize that due to third-party DNS propagation timing, some customers may have experienced delays in accessing our systems of up to 48 hours, depending on region. All Marketo back-end processes such as Smart Campaigns were still operational during the DNS propagation, however, the propagation reduced accessibility to Marketo for some users. As a result, we believe the normal calculation of system uptime may not accurately reflect everyone’s experience. To address this, we have decided to make a one-time change to our normal calculation for July to more closely track what our customers may have experienced in terms of accessing our systems regardless of whether the problem lay with us or was due to third party systems/processes. After studying the issue, we think the best way to calculate this is based on customer logins to the system. We looked at the first login time for each pod and used login as a proxy to calculate when customers were able to access Marketo. This one-time calculation is a better reflection of the frustration you may have experienced in accessing Marketo. We will return to using our normal calculation for August. For the month of July, our server pod uptime was 99.997%. All back-end systems, such as smart campaigns, were processing normally while the domain was offline, so when calculated in the normal way, our server pod uptime for July was 99.997% When taking into account the 6 hours when the marketo.com domain was not available, the system uptime for the month of July was 99.17% As mentioned, if we add the full extent of the DNS propagation as discussed above, and take an average of the first logins across the entire customer base, the average user accessibility for July would be approximately 97.77%. For additional information please contact Marketo Support and see our FAQ document and this letter from our CEO Steve Lucas.
View full article
Sometimes you need to give your sales team access to the powerful insight Sales Insight gives into Marketo but would rather some users not be able to take some actions such as sending Marketo Emails or trigger Marketo Campaigns.  You can use SFDC Permission Sets in to give or remove access to the VisualForce pages that power the actions Sales Insight can take. Note: Modifying permissions to Sales Insight components from their documented configuration may cause undesired and unpredictable behavior in your Salesforce instance.  Marketo Support can only support the default documented install configuration MSI for Salesforce - Marketo Docs - Product Docs.  Make these changes at your own risk and fully test any modification in a sandbox environment before deploying to your production environment. Create a new permission set or modify and existing permission set in Salesforce.  Documentation on SFDC Permission Sets can be found here.​ Edit Visualforce Page Access. Remove (if restricting access) or add (if adding access) the desired Sales Insight VisualForce elements.  For example, mkto_si.Send_Marketo_Email - access to the Send Marketo Email feature from an individual Lead/Contact mkto_si.Send_Contact_Marketo_Email - access to the Send Marketo Email feature from a Contact list view mkto_si.Send_Lead_Marketo_Email - access to the Send Marketo Email feature from a Contact list view mkto_si.Marketo_Lead_Detail - access to the View in Marketo feature mkto_si.Add_to_Marketo_Campaign - access to the Add to Marketo Campaign feature from an individual Lead/Contact mkto_si.Add_Contact_to_Marketo_Campaign - access to Add to Marketo Campaign from a Contact list view mkto_si.Add_Lead_to_Marketo_Campaign - access to Add to Marketo Campaign from a Lead list view Assign the Permission Set as desired to your users. SFDC users without permissions to specific Sales Insight features will still be able to choose the associated actions from their drop down menu.  However, they will receive a permissions error after clicking the "Go!" button. Is this article helpful ? YesNo
View full article
Issue Description You want to use a non-English keyboard with your tablet running the Marketo Event Check-In App.   Issue Resolution Currently, the Marketo Event Check-In App only supports English language keyboards. Is this article helpful ? YesNo
View full article
Issue Description You want to prevent a situation where you create or sync a new field on the Lead and Contact objects in SFDC and two fields are created in Marketo, one mapped to Lead and the other mapped to Contact. Issue Resolution You will see this behavior if the an SFDC field is created on two objects across more than one sync cycle, one before a sync cycle starts and the other one during or after the sync cycle completes. To ensure both the lead and contact show up mapped to the same custom field Marketo, do the following Disable the global sync in Marketo. (Admin > Salesforce) Create the field on your desired objects in SFDC.  Make sure they both have the same API name. Re-enable the global sync in Marketo, allowing the field in both objects to sync down to Marketo at the same time. If you find yourself with multiple fields in Marketo after the sync, contact Marketo Support to have the fields merged or remapped as necessary. Who This Solution Applies To Customers integrated with Salesforce
View full article
Issue Description You sent an email using a Smart Campaign and the email performance report for the email shows more Sent than there are members in the Smart Campaign Issue Resolution The email may have been sent by more than one campaign.  You can determine this by looking at the "Used By" info on the email's summary page, to see which campaigns sent the email.  In this case, you can use the Campaign Email Performance Report to view the email's performance within the specific campaign.
View full article
Issue Description Person/Lead Source is empty. Why isn't it populating?   Issue Resolution Marketo does not automatically assign Person Source. We do populate Original Source Type.   Assigning credit for a Lead can only be determined by someone with intimate knowledge of a company's marketing strategies.  If someone fills out a form, Marketo doesn't know if they were brought to that form by an email blast, TV commercial, talked to a salesperson, or any number of other reasons. If they came in through a List Import, they could have attended a Tradeshow and signed up there, they could have been exported by a CRM and are being imported, or any number of other ways.  There are many discussions on best practices for handling Lead Source attribution in the Community.  If you need assistance setting up Smart Campaign to update the Lead Source based on your specific business criteria, please contact Marketo Support. Is this article helpful ? YesNo
View full article
Issue Description You are trying to unapprove or delete an asset and get the following error: [Asset Name] is in use and cannot be deleted/unapproved Issue Resolution Marketo assets (such as emails, templates, forms, lists, smart lists, and programs) cannot be deleted while they are used or referenced by another asset.  If the error does not specify where the asset is being used or referenced, you can find this information in the Used By tab in the asset's summary page. For programs, you can find the Used By section in the program's View drop-down. The Used By section will show where the asset is in use, and you can click on the links to jump directly to that location. Once the asset is no longer referenced anywhere else in Marketo, it can be deleted.  If you are certain the asset is no longer in use but are still unable to delete it, please contact Marketo Support
View full article