Knowledgebase

Sort by:
Issue Leads are not syncing from SFDC to Marketo after the sync user has gained access to them.     Solution Make a change to the lead records to queue them to sync. SFDC has permissions that allow specific users to access some leads but not others. Your Marketo SFDC sync user is a user that can have this setting applied. The sync user can also have that restriction removed to allow access to those leads. When Marketo checks Salesforce for people to update, it is looking for leads who have had record updates since the last sync. Changing visibility rules in SFDC to allow the sync user access to those leads does not update the records themselves, only the accessibility to those leads by the sync user. This means that if the sync user couldn't access the leads before but now can, they still won't sync to Marketo until they have a field update. You can change a field value, but another option is to run the Data Loader in SFDC for those affected leads. That will create a new modification indicator, which will trigger Marketo to sync those records down.    
View full article
Issue Description We have a custom landing page template and we were able to see that landing page is not rendering perfectly on the editor but works as expected when published.  How can I troubleshoot on this issue? Issue Resolution As you are facing the issue on a custom template, we suggest you to follow the below steps. Download a template form the URL- https://docs.marketo.com/display/DOCS/Guided+Landing+Page+Template https://docs.marketo.com/display/DOCS/Guided+Landing+Page+TemplatesIn Marketo, navigate to the Design Studio. Click Landing Pages in the left-hand tree, then select Templates. In the menu bar, click Import Template. Choose the downloaded file, enter a template name, then click Import (make sure to pick a descriptive name and indicate that editing mode is Guided). Create a new Landing page with the recently downloaded template without making any changes. If the default background image works on this landing page as expected, it confirms that the issue lies with the custom coding that was added to the template. Marketo Support is not set up to assist with troubleshooting custom code. The best point of contact will be your web developer who should be able to resolve the issue for you. Please be aware that the landing page editor may not load all external resources in the editor or previewer, which can cause them to look different than the published version. If the background image doesn’t render on this newly downloaded template as well, contact support and we will be able to troubleshoot your issue.
View full article
By default exported reports are limited to 100 rows but it can be changed by navigating to 'User Settings' > “Number of Rows in Excel Export”   The maximum number allowed is 10,000 rows       Is this article helpful ? YesNo
View full article
In some cases, you may want an iframed Marketo form to open in the parent page.   Note: Please ensure that you have access to an experienced JavaScript developer. Marketo Technical Support is not set up to assist with troubleshooting JavaScript. Is this article helpful ? YesNo FORMS 1.0 Add the following script to the src iframed page within a custom HTML block. <script type="text/javascript" src="/js/public/jquery-latest.min.js"></script> <script type="text/javascript">      // set no conflict mode for jquery    var $jQ = jQuery.noConflict();    $jQ(document).ready(function(){        // all form submits will open in a new window      $jQ('.lpeRegForm').attr('target','_top');    }); </script>   FORMS 2.0   <script > MktoForms2.whenReady(function (form) {     var form = MktoForms2.getForm(FORM_ID_HERE);     form.onSuccess(function (values, followUpUrl)     { window.top.location.href = followUpUrl; return false;     }); }); </script> To figure out what the form id is, the easiest way is to look at the embed code. It is the 4 digit number on the second line.
View full article
Issue Issue Description Persons do not trigger Smart Campaigns as expected when using the REST API 'Push Leads to Marketo' endpoint.     Solution Issue Resolution Marketo utilizes a special trigger for persons pushed to Marketo using REST API. The 'Person is Pushed to Marketo' trigger will qualify persons upserted by the 'Push to Marketo' endpoint.    
View full article
Issue You need to mass update Salesforce records to get them to sync into Marketo. Solution Use the Salesforce provided Data Loader! This is a tool Salesforce provides for such occasions. Here's an article from Salesforce with more information. For any questions regarding this tool, please seek your Salesforce Admin or Salesforce Support as they will be the best resource to answer those questions! https://developer.salesforce.com/tools/data-loader
View full article
The Charter of Fundamental Rights of the European Union recognizes in Article 8 the right to the protection of personal data. This fundamental right is developed by the European legal framework on the protection of personal data consisting mainly of the Data Protection Directive and the ePrivacy Directive. They lay down several substantive provisions imposing obligations on the data controller and recognizing rights to the data subject, prescribing sanctions and appropriate remedies in cases of breach, and establishing enforcement mechanisms to make them effective.   Although strictly speaking it is data controllers who bear legal responsibility for complying with data protection rules, also those who design technical specifications and those who actually build or implement applications or operating systems bear some responsibility for the data protection aspects from a societal and ethical point of view.   The law applies to all Member States of the European Union. However, even websites outside the EU are required to comply with the law if they are targeting Member States. For example, a site based in the USA that sells products to consumers in the UK, or that has a French-language version of its site aimed at users in France, will still have to comply.   Anonymous cookies, those that do not contain information that would enable you to identify a user, do not infringe the law anonymity and therefore are not a problem. The directive’s core requirement is to define how consumer’s "opt-in" or "opt-out" to cookies, and what level of information the consumer must be provided when cookies are used so they are sufficiently informed.   Support Browser Do Not Track Settings docs.marketo.com/pages/viewpage.action?pageId=2951124   Visits to web pages do not reflect actual activity https://nation.marketo.com/docs/DOC-1300
View full article
Issue How to identify records in Marketo that have not synced to Salesforce. Solution Create a smart list using the filter "SFDC Type is empty", as if the record in Marketo has synced to Salesforce, the SFDC Type will either be 'Lead' or 'Contact.' Be aware that there is also an 'SFDC Type' on the Opportunity object, so make sure you are looking at the Person object and not Opportunity.
View full article
Issue Issue Description You are attempting to send a list to Google via your Google Customer Match integration, but when you open the dropdown to select the destination list, none of the lists you have prepared are visible.   Solution Issue Resolution For Marketo to see a list and present it as an option, the user that was used to set up the Customer Match Launchpoint service needs to have visibility of that list. Only lists that this user can see will be available.  It is not possible to check which user was used for this setup from Marketo's Launchpoint menu, however you can alter which user is being used to connect to Google by opening the associated Launchpoint service and selecting 'Re-authorize', and then follow steps 6 and onwards from the following article: Add Google Customer Match as a LaunchPoint Service Who This Solution Applies To Users making use of Google Customer Match
View full article
Issue Description You are sending password reset links, but not receiving those emails, or you are trying to login with what you thought was the correct login without having success. Issue Resolution By default, the Marketo login is an email address.  If you needed to reset password for a User, you enter the login which happens to be the email address associated. However, there is a feature that separates the login and email address, where the login could be test@test.com, but the associated email address for this login is your.name@company.com.  If this feature is enabled and you needed to reset a password, you would still enter the login (test@test.com) and the reset password email would be sent to the associated email address (your.name@company.com). If you would like the feature that allows for separate login and email addresses, please contact Marketo Support.
View full article
Here's how you can use tokens and URL parameters to automatically assign leads to Salesforce campaigns after filling out a form.  These tokens work in all of the Salesforce campaign flow steps:   Add to Salesforce Campaign Change Status in Salesforce Campaign Remove from Salesforce campaign   Get the Salesforce campaign ID and status   You need two things to begin this process -- the name or ID of the Salesforce campaign you want to sync to and a valid status in that campaign.  You can get the ID for the campaign by opening that campaign in Salesforce and copying the last 15 characters from the URL.  Here's an example campaign URL; the ID is highlighted:   naX.salesforce.com/701F00230001Z9z   To get the valid statuses, click on "Advanced Setup" on the campaign's page     The status should be listed there:     Create new fields   First, you need to create two new fields -- "SFDC Campaign ID" and "SFDC Campaign Status" -- both of type "string".  You can create these on your lead and contact records in Salesforce, or contact Marketo support to add those custom fields in your Marketo account.   Create or edit the form   After you create those fields, the next step is to incorporate them into your forms.  Create a new form or edit an existing form, then drag those two fields into your form.  Make them both hidden fields and set them to populate from a URL.  If you're unfamiliar with them, this article on hidden fields has details on how they work. Making a Field Hidden on a Form When setting the values for those fields, use a real Salesforce campaign ID and status as the default value.  Here's how you might edit the settings for those fields:   SFDC Campaign ID: Default Value: [a real Salesforce campaign ID or name] Populate from: URL Parameter Parameter name: campaignID   SFDC Campaign Status: Default Value: [a real Salesforce campaign status for the campaign you chose] Populate from: URL Parameter Parameter name: status   And here's what your form might look like when done:   Now you have a form that automatically add leads to the default Salesforce campaign you selected and that you can override with URL parameters.   Create a Smart Campaign   Next, you need to create a campaign that will add these leads to the selected (or default) Salesforce campaign.  We'll trigger this campaign to launch whenever someone fills out your form: In the flow, first you need to sync the lead to Salesforce so that you can add it to a campaign.   Then you can add it to the Salesforce campaign using the values in the SFDC Campaign ID and SFDC Campaign Status fields.  To do this, use the tokens for those fields in your flow step:  {{Lead.SFDC Campaign ID}} for the campaign name and {{Lead.SFDC Campaign Status}} for the status.  If you type "{{" in the fields, the auto-suggest will help you enter that text correctly:     Your finished flow should look like this:     Finally, in the schedule tab set this campaign to run every time and activate it.     Launch your landing page   If you modified a form already in use, you can now go to that landing page, fill out the form, and watch as your lead gets synced to the Salesforce campaign you chose.  If this is a new form, create and approve a new landing page which uses that form.  After filling out the form, you should see the lead added to the default Salesforce campaign specified in your form:     Use URL parameters to override the default campaign and status.  For our forms, the campaign is set by the "campaignID" URL parameter and the status by the "status" URL parameter.  For example, this URL:   offers.marketo.com/offers.html?campaignID=701A00000009K3l&status=Responded will assign the lead to the Salesforce campaign "701A00000009K3l" (the Salesforce internal ID) with the status "Responded."  If either value has spaces or special characters, make sure that you URL encode them before adding them to your URL.   Using tokens in other Salesforce campaign flow steps   These tokens work in all of the Salesforce campaign flow steps -- Add, Remove, and Change Status in SFDC campaign.  Follow the same directions as above but substitute the appropriate flow step in place of the Add to SFDC Campaign step.   Diagnosing errors   If your leads are not syncing to your Salesforce campaigns, first go to the Activity Log for that lead and double click the line that has the failed flow step. The information that appears will help you figure out what the problem might be. The most common errors you'll encounter are: Spelling errors in your tokens -- use the autosuggest to help Using an SFDC campaign ID or name that doesn't exist -- check the spelling of the campaign or ID The lead doesn't exist in salesforce -- sync the lead to Salesforce before adding him/her to your campaign Using a status that doesn't exist for that campaign -- change the status to one that does exist for the campaign, or add a new status to the campaign in Salesforce
View full article
This article describes how to verify if your active Marketo Sales Insight configuration is properly setup via the Sales Insight tab in the Admin section of Marketo Lead Management. If you see an MSI Status of Configuration Problem, a configuration error in your Marketo Sales Insight setup was detected, meaning that one or more of the required fields for synchronization were not properly configured. In the admin area, go to Microsoft Dynamics and click Edit on Field Sync Details. All required fields will be refreshed and configured. Click Save. Caution The following fields must be checked for Sales Insight to work properly: Priority, Relative Score, and Relative Urgency. Go to Sales Insight and confirm that MSI Status shows Configured.
View full article
A tagging campaign is designed to entice your leads to click your emails.  Once they do that, you can track their future web activities.  You can also use it to scrub your mailing lists of leads who don't want to receive your marketing material. The hardest part is coming up with an offer that encourages them to click your email. What's in a tagging campaign? At a high level, you'll need: An email offering a prize for people who click Include a link to unsubscribe people to clean out your DB A thank you landing page for people who click through A smart campaign to send the emails mailing A smart campaign to handle the unsubscribe clicks   As leads click through the email, they get cookied so that all their subsequent web activity is tracked (whether they enter or unsubscribe).  Include the unsubscribe link so you can get uninterested leads off your mailing lists. The campaign is quick to set up, fun for your recipients, and great for you to identify anonymous leads. Pick a hook First, choose an offer that will compel people to click a link in your email.  Some examples of offers that get high click-through rates include: Prize Only Example: "Hi, we are giving away a free iPod.  Click here to enter to win!..." Charitable donation Example: "We'll donate $1 to Habitat for Humanity for each recipient who clicks this link." Cleaning up DB Example: "Hi, we are cleaning up our DB.  If you want to receive updates from us, click here.  Otherwise, click no thanks."  (Either one they click is a cookied customer)   Best Practice: It is more important to have a cookied customer than one who is subscribed to receive marketing emails. Create the assets You'll need to create and approve a few Design Studio items to make this work: Email: use the hook you picked in the first step Landing Page: a Thank You page relevant to your offer Prize: "Thank you for entering!" -- you don't even need an entry form! Cleaning up DB: One for, "thanks for your continued support." Another for, "we'll unsubscribe you immediately." Create the campaign(s) Pick any segment of your lead database to receive the email. Send Email Smart List: (pick any DB s segment) Flow: Send Email -- [your  email] You may need some other campaigns to handle your prize and unsubscription clicks.  For example: Prize -- create a static list called "Prize Entries" Smart List: Trigger on "Clicks link in email -- [your email]" constraint on Entry Link Flow: Add to List -- Prize Entries Cleaning up DB Smart List: Trigger on "Clicks link in email -- [your email]" constraint on Unsubscribe Link Flow: Change Data Value: Unsubscribed is True   That's all you need to do in Marketo. A week or two later, if you're giving away a prize, use the Random Sample filter to dig up a lead to receive the prize. Is this article helpful ? YesNo
View full article
Issue Issue Description Using a token in the Smart List of a Smart Campaign yields unexpected results, an error, or the campaign to not trigger.    Solution Issue Resolution Tokens cannot be used in the Smart List section of Smart Campaigns. Tokens can be used in the Smart Campaign Flow, in the following steps: Interesting Moments Change Data Value Salesforce Campaign Steps (add, remove, change status) Create Task
View full article
How do I verify that my tracking link domain is secure? There are two primary methods for verifying that your domain is secure; by testing within a web browser and using a third-party SSL checker. Verifying Domain Security Through Web Browser 1. In your Marketo instance, navigate to Admin --> Email 2. In this link https://<your_tracking_domain>/trk?=ping, replace <your_tracking_domain> with your actual tracking domain. 3. Enter this link into your browser and click Enter. 4. Click the padlock at the left of the URL in the address bar. 5. In the pop-up box, verify that the certificate is valid and shows no security warnings. Verifying Domain Security Through Online Service You can also verify your SSL certificate to make sure it is correctly installed, valid, and trusted using the SSL Shopper SSL Checker tool. This is a third-party tool not owned or operated by Marketo, but it is a useful resource many utilize. 1. Navigate to https://www.sslshopper.com/ssl-checker.html 2. Type in your branded tracking domain you wish to verify. 3. Click "Check SSL". 4. Ensure that all check marks are green. If all check marks are green the certificate is valid and your domain is secure.
View full article
Issue Your Marketo program has successfully synced with a Salesforce Campaign and you have been sending email, but have not been seeing any history sync to the Salesforce Campaign.     Solution Only when there are Marketo program members will activity sync to SFDC, so your first step should be to check the Marketo program membership. If there are no members of the Marketo program, then that will signify the issue is just that. Depending on the program and its setup, there may be lead activity that is not being associated with the Marketo program. For example, imagine there's a default program synced with Salesforce. In the program, there's a child asset smart campaign sending emails, and you aren't seeing this email activity in the SFDC campaign. The child asset smart campaign needs to have a Flow Step: Change Program Status [for the specific program]. (It is recommended that this is flow step #1). Even though the smart campaign is a child asset of the program, these 2 assets are still independent of each other, so the flow step is needed to sync the activity.
View full article
Issue Issue Description A field cannot be hidden, renamed, remapped, or merged into another field while it is being used by any assets in the system - where do you find what is using that field?   Solution Issue Resolution Go to the Admin section in Marketo Click on Field Management in the left sidebar Locate the field through the Search on the right There is a "Used By" section that shows the forms, smart lists, and smart campaigns, and any other assets using that field Go to those assets and remove the field name from it.  Sometimes the asset is a Smart Campaign with an unusual name, which may indicate is a background campaign for something like an Engagement Program, Segmentation, or Revenue Cycle Model.  In that case, you will need to go to the program or model using the background campaign and remove references to the field there.   If you are certain that the field you are trying to hide is not being used by any assets, yet it is shown as being used by other assets in Marketo, please raise a support ticket. Marketo Support can verify if the field still has any references within an asset. If not, Marketo Support can delete the dependency in the database so that the field can be hidden.
View full article
Included in this article Note: This post will be updated to reflect changes made to activity records returned by the API due to migration to new infrastructure. Overview With the rollout of Marketo’s next-generation Activity Service beginning in May 2017, we will be unable to enforce the uniqueness or presence of the integer “id” field in activities, data value changes, or lead deletion records returned by Marketo’s APIs.  This change will begin rolling out to all subscriptions over the remaining first half of 2017. To avoid service disruptions for integrations which retrieve activity records, the id field should be treated as optional.  Cutover of this change will begin to affect subscriptions with the September (Q3) 2017 release. This change will affect the following endpoints: REST API Get Lead Activities​ Get Lead Changes​ Get Deleted Leads​ Add Custom Activities​ SOAP API getLeadActivity​ getLeadChanges​ The affected SOAP types are ActivityRecord and LeadChangeRecord. Examples The following examples show record types which will be affected.  In both examples, the effected field is called “id.” Example REST Field: id ​ Example SOAP Field: id ​ FAQs Do I need to update my WSDL version if I'm using SOAP integration? Yes. The marketoGUID field will only be returned in activities when using the WSDL version 3.1 or later.  The new URI will follow this pattern: https://{munchkinId}.mktoapi.com/soap/mktows/3_1  It may also be obtained through the Admin->Web Services menu in your subscription When can I expect to see each change? Beginning with our Q1 Minor Release on April 7th, activity records retrieved via Marketo’s SOAP or REST APIs will include a new field called “marketoGUID”.  The value of this field will match the value of the “id” field, but will be a string type field.  Some time after the Q2 release beginning May 17th 2017, the “id” field will stop being returned as part of these records, and the value of marketoGUID will become a 128-bit string. What do I need to do? If you are responsible for code that deals with Marketo activities, you should determine whether your code relies on the presence or uniqueness of “id” field for Marketo activities, and then remove that requirement.  In an upcoming release, an additional string field called “marketoGUID” will be added.  “marketoGUID” should be considered the unique ID for retrieved activities when it becomes available.  If you are not, you should consult with your team and relay this message to the appropriate stakeholders. Who will this change affect? This change should only affect client and partner integrations which retrieve activity records from Marketo, and only if the integrations rely on either the presence and/or type of the “id” field in the response, or rely on the uniqueness of the field.  After the rollout of Orion AS, and the disabling of activity writes to MySQL, the “id” field will no longer be available and will be supplanted by a unique string id field. Check out our documentation on the Marketo Developers Site here: https://developers.marketo.com/blog/important-change-activity-records-marketo-apis/
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 Issue Description Is there a way I can populate a field with the system date token, plus a certain amount of days? ie. Change Data Value = Date + X days. Solution Issue Resolution As long as the field type is date or datetime, you can add simple syntax in the Change Data Value flow step to accomplish this: {{system.date}} + X days. This is for times that you would like a date immediately populated for purposes such as sending an email; "Thanks for signing up to our 20 day trial, you have access to this content until the [use lead token populated by the date + x syntax here]..." *note that a wait step of a few minutes might be needed before an email send to ensure the field has time to get populated. Other times, when immediate action is not required and/or a field type is not date/datetime, you could use a Wait Flow step before a Data Value change: 1. Wait X days 2. Change Data Value = {{system.date}}
View full article