Knowledgebase

Sort by:
Summary Mismatch between "Added to [custom object]" and "Has [custom object]" filters for a SFDC Custom object Issue You build a Smart List for "Added to [custom object]" for your SFDC Custom object and you notice the number of records qualifying is lower than expected. The "Has [custom object]" filter pulls more records, however, and matches what you see in SFDC. Environment SFDC/Marketo Solution This is expected behavior if you have records that were already associated to the SFDC Custom object before they were pushed to Marketo. If you have records that were already associated to the SFDC Custom object before they initially synced to Marketo, those records would not have an "Added to [SFDC Custom Object]" activity on their record in Marketo, which means they would not qualify for the "Was added to [SFDC Custom Object] Smart List filter" In this scenario, it is recommended to use the "Has [SFDC Custom Object]" filter to get the accurate numbers, as this should include all Marketo records that are associated to the Custom Object, even if they were added to it prior to being synced and created in Marketo. Root Cause Records already being associated to the SFDC Custom object before they were initially synced to Marketo.
View full article
Issue Leads are stuck in a smart campaign's Wait Step and have not moved onto next steps, even though the Wait Step has been updated/shortened and the lead should move onto the next step. Solution When a lead enters a Wait Step, it remains in the Wait Step as defined at the moment they entered it. For example, if the lead enters a 1 week Wait Step, it will remain in the step for 1 week. If the Wait Step is updated to be longer or shorter (for example, shortened to 3 days or extended to 2 weeks), the lead that already entered the Wait Step (when it was 1 week) will remain in the Wait Step for the original duration. New leads entering the Wait Step will abide by the new duration.
View full article
Summary The customer wants to know if a nurture email was not sent to a recipient due to communication limit, then will it be sent in the next cast, or that email will not be sent again? Issue Individual(s) were supposed to get an email from a Nurture (Engagement) Program cast but failed to receive the email due to hitting the communication limits set in the instance. Do you need to manually send the email to the individual(s) via a separate Smart Campaign or will it be sent, automatically, on the subsequent cast for the Nurture Program? Environment Marketing Activities Nurture Programs Engagement Programs Admin Communication Limits   Solution You don't need to act on these scenarios as the individual(s) impacted by the Communication Limits will be sent the applicable email in the next cast for the Nurture Program. The only reason that the individual wouldn't be sent the email in the subsequent cast for the Nurture Program would be if the person would hit their Comm Limit again. Should that happen, you might want to review your Communication Limits settings or review the individual(s) impacted and see why they keep hitting the Comm Limits. Reference: How Do Communication Limits Work? - Marketing Nation (marketo.com) Root Cause Communication Limits being hit during Nurture Program cast execution
View full article
Issue When using the Merge Lead(s) REST API end-point and merging multiple leads, which field values would be copied to the winning record? In the below example, the winning lead record has a blank value for Job Title. When merging all 4 leads, which field value will get copied to the winning record from the list of losing records?  This is a article attached image Solution The field values that will be injected to the winning lead record are directly impacted by the order of leadID's in the Lead array parameter of the call, where the FIRST leadID listed in the parameter array will be the winning value IF the field on the winning Lead record is blank.  URL Example {{baseUrl}}/rest/v1/leads/4231/merge.json?leadIds=2232,1323,1455 RESULT  Based on the above excel chart, LeadID 4231 (Winner) would have their Job Title field updated = 'electrician'. URL Example #2 {{baseUrl}}/rest/v1/leads/4231/merge.json?leadIds=1323,1455,2232 RESULT Based on the above excel chart, LeadID 4231 (Winner) would have their Job Title field updated = blank/empty.   Root Cause This is the expected behavior when merging multiple leads via the REST API Merge Leads end-point.  
View full article
Article Text Included in this article: Navigate to the Clickstream module How is Visit Duration Caluclated 00:00 Visit Duration Single page viewed Session timed out   Navigate to the Clickstream module        Go to the Visitors page        Click on a visitor to find the Clickstream module in the bottom right     How is Visit Duration Caluclated When a visitor visits a website being tracked by an RTP campaign, it records clicks in the Clickstream module in the RTP platform. Clicking on a visitor allows you to view their viewing information in the Customer Journey section, including: Links clicked Time stamp of each link click Total visit duration     Visit duration is calculated by subtracting the first time stamp from the last time stamp. In other words: visit duration = last time stamp - first time stamp. See the image above for an example of this calculation.   00:00 Visit Duration Single page viewed Both RTP and Google Analytics rely on clicks to determine visit duration. This means that if a visitor only views a single page, neither RTP or GA can track when the visitor leaves the page, since there is only the initial time stamp without a time stamp to mark the exit from the page. The visit duration for viewers that didn't view more than one page during the session is recorded at 00:00 since it cannot be calculated.   Session timed out Another way that a visit duration can be recorded as 00:00 is if a visitor's session times out. By default, a session will end after 15 minutes of inactivity. For example, if a visitor stays on a page without making any clicks for 25 minutes (perhaps they are reading an article or watching a long video), that session will time out and be recorded with a duration of 00:00. If the visitor finally makes a click after the 25 minutes of inactivity, a new session will begin. In Google Analytics, the session timeout can be customized to be longer or shorter than the default 15 minutes.
View full article
Article Text Included in this article   Overview The Background The Problem The Solution Overview RTP gives a dashboard that provides lots of valuable information about your RTP instance and how everything is performing. One of the widgets in this dashboard is Top Industries. This widget is designed to give you a breakdown of the top performing industries, but sometimes the industry widget is empty:   The Background When a segment is saved in RTP, it is automatically assigned a type.  If the segment contains only the Industry filter, then it is assigned the 'Industry' type and is included in the Industry widget on the dashboard. So, this widget only contains information on Industry segments. If it is not an Industry segment, it will not be included here.   The Problem You can obviously add more filters to the segment other than Industry. However, if the segment contains other filters, then it is assigned the 'Complex' type and is not included in the Industry widget. The only information that will display in the Industry widget is what comes from segments that use only the Industry filter and that alone.   The Solution If you'd like a particular segment to display in the Industry widget, there are two options: 1. Remove the other filters other than Industry. 2. Create different additional Industry-only segments.
View full article
Issue You created a Smart List, but did not define the filters (example: "Member of Smart List" with no Smart List named) and are wondering if this will cause no leads to show up in the results.     Solution If you create a Smart List and you do not define any filters, this will cause all leads in your database or leads visible in the partition and workspace to appear in your results. This can create problem if you have nested Smart Lists. For example, if you have a Smart List with the filter "Member of Smart List = Lead not in" with Smart List A selected, and Smart List A has no filter, this logic will cause you exclude all leads in your database.    
View full article
Issue You sign up for ToutApp and receive a notice that your account is under review or your account is not verified. Solution If you sign up for ToutApp using a generic email address such as Gmail, Yahoo, Hotmail, Outlook or other email providers your account may require verification by Marketo Support. Please contact Marketo Support with the following information. Company Name: Business Address: URL(s) of your primary Web site(s): What is your average weekly and/or monthly email volume? Do you purchase, or have you ever purchased lists of leads? If yes, which providers have you used and when was your last purchase?    
View full article
Issue How to disable Niko from ToutApp extension. Solution To remove Niko, simply click on the blue Tout envelope at the top right of your browser, then manually uncheck the box next to "Show Niko as I browse the web". Refresh the page, and Niko should disappear.  
View full article
Issue How is syndication ID set up while setting up a referral offer? Solution For a referrer to be given credit they must have a Marketo Syndication ID assigned. This can be done manually (directly on the lead record) or via the social campaigns' Offer Details > Fulfillment Goal > should be set to Referred Sign-Ups. Once you set that up, the referrer will get issued a "syndication id" and be part of that social campaign's participant's list.    
View full article
Summary New checkbox for query parameters available when adding new content or editing current content. Issue You were previously unable to specify query parameters for predictive content, and query parameters were not used when adding new content, editing current content, and reporting on URL clicks.  Autodiscovery works by adding a new URL to the DB, and later on, clicking counts are accumulated against the newly found asset. The asset is determined based on the URL (and there, it previously didn't account for anything that followed the ? in the URL. The same was used as a validation when a user added new content. The rule to determine this part of the URL, minus the query parameters, was a requirement back then and was taken into account during design.   Solution As you add predictive content from the predictive content page, you need to have the checkbox on this page to allow the user to decide whether they want to include/exclude the query parameters while adding it. The same thing should be followed for editing predictive content as well. Engineering built a nuanced approach that provided flexibility to include or exclude query patterns in determining a unique URL and added a feature to include query parameters when manually creating a piece of content. It should rightly identify the right asset to record clicks/views against as well. 
View full article
Article Text Included in this article   Overview Editing Labels Deleting Labels Overview RTP will allow you to add labels to your Segments and Campaigns. Here are the directions on how to do so: Label Your Segment - Marketo Docs - Product Docs Label Your Campaigns - Marketo Docs - Product Docs Sometimes Labels need to be changed or removed.     Editing Labels Currently it is not possible to edit labels   Deleting Labels You can delete labels using following process: 1. Filter the the page by the label you want to remove. 2. For each segment or campaign displayed, click the select box and then click Set Label 3. In the Set Label list, uncheck the label you want to delete.  When the label is removed from all segments/campaigns, it will be removed automatically  
View full article
Article Text Included in this article   Overview Troubleshooting Steps Verify Global Settings Check for CRE Excluded URLs Verify Content Being Recommended Make Sure the Page Has the RTP Tag Running Clear Your Browser's Cache and Cookies Overview The Content Recommendation Engine allows content assets to be promoted to visitors on your website. But what happens if it stops working? This doc will show you the common things to check and troubleshooting steps to try to get it working again.     Troubleshooting Steps   Verify Global Settings The CRE can be switched on or off for your entire RTP instance whenever you want. It's possible that another user may have switched it off and not turned it back on again (it happens more often than you'd think). To enable or disable the CRE globally, go to the Account Settings page and look for the Recommendation toggle switch. Full directions can be found here.     Check for CRE Excluded URLs You have the ability to prevent the CRE from being added onto specific pages. If you have URLs excluded from allowing the CRE to be displayed, that would cause the CRE to no longer display on those pages. Many times the exclusion can be set and then forgotten, or set by a different user on accident. Directions on how to set up the exclusions can be found here Web Personalization (RTP) - How To Exclude or Include the CRE on Specific Pages     Verify Content Being Recommended Content assets can be switched on or off to designate whether that content should be included in the CRE recommendations or not. Each piece of content can be enabled or disabled individually, but if you don't have any enabled at all, there's nothing for the CRE bar to recommend, so it won't even show up on the page.     To check whether content is enabled, from the menu, select Recommendations     In the Content Recommendations page, look for the Recommendations column. This will list out all pieces of content you have in RTP and display whether they are enabled or disabled. The Red box means it is turned Off and is disabled. The Green circle means it is turned On and is enabled.     Make Sure the Page Has the RTP Tag Running The CRE is a feature of RTP, so if the RTP script tag isn't running on the page, there's no way for the CRE to work. The RTP tag can be implemented in many different ways besides by having it directly in the page's HTML, like having it in a tag manager. These other implementation methods can cause problems so be sure to follow the directions in the documentation here when setting it up: RTP Tag Implementation - Marketo Docs - Product Docs   If you know for sure that the RTP tag is on the page, here's documentation on how to troubleshoot what could be keeping it from loading properly: Troubleshooting Web Personalization (RTP) - RTP Tag   Clear Your Browser's Cache and Cookies Web browsers store cached data from websites, which can frequently cause old versions of webpages to continue showing even if a different newer version of the page should be loading instead. Try clearing both cache and cookies in your browser and then testing the page again. You can also test using a different browser.  
View full article
Issue How to edit the schedule email in ToutApp. Solution The way to change the time of a scheduled email: Go into your on the conversations page. Click the Edit button next to the scheduled email. From here you will be able to change the time of the delivery of the email.       
View full article
Summary Email previews by list can only view the first 25 people. Issue When previewing an email and viewing people by 'List', you are only able to generate a preview for the first 25 people on that list. Environment This occurs in email previews. Root Cause This is the expected behaviour for email previews. The intention of email previews is to allow for a quick confirmation that the email is compiling as expected, rather than to confirm it is correct for every recipient.
View full article
Issue You want to understand how Company IDs work within Marketo and how you can interact with these IDs, particularly when dealing with the Person's Company Object. You want to know: The nature and standard of the Company ID in Marketo. Can the Company ID be checked or modified by users without CRM or API integration? If people belonging to the same company share the same Company ID. How to update the Company Object information via the API for multiple leads associated with the same company? Clarification on which field should be used as the basis for updating Company Object information. Solution Marketo manages Company IDs using two distinct identifiers: Company ID: This is a Marketo-specific identifier that is used to organize the link between companies and people within Marketo. External Company ID: A hidden system field used in non-native company object integrations. The Company ID can be accessed through the {{company.Id}} token, while the External Company ID is not directly viewable in the UI. Note: The Company Object API endpoints are disabled when a native CRM integration is enabled in a Marketo instance. Accessing and modifying Company ID You cannot manipulate the Company ID or External Company ID fields from the Marketo UI. Any interaction or modification of these fields must be done through the Marketo API. Updating Company Object information via API When updating the Company Object for multiple leads belonging to the same company: Use the External Company ID or company ID to update the Company Object. Updating the Company Object with the External Company ID will apply the changes to all leads associated with that company. You can also update Company Object fields using the lead API endpoints. These changes will apply to all leads associated to the company. Steps for updating Company Object Create Company: Use the Marketo API endpoint `{{base_url}}/rest/v1/companies.json` to create a company with the necessary data. Create Person: Use the Marketo API endpoint `{{base_url}}/rest/v1/leads.json` to create a person associated with the company. Field Inheritance: Once a person is linked to a Company Object via the External Company ID, certain fields like Billing City, Address, and Postal Code are inherited from the Company Object and are no longer editable from the UI. Creating Fields on the Company Object: Contact Marketo Support to request the conversion of these person fields to company fields.  
View full article
If the user makes changes to the my tokens, snippets, etc during the processing of the an email that is using head start, will those changes be reflected—No If someone unsubscribes during the processing of the an email that is using head start, will they receive the email—Yes Can you cancel a head start program once the processing of the an email that is using head start has begun—Yes What happens to the processing data when someone cancels a program during the processing of the an email that is using head start—It is deleted (I.e. Program membership, etc.)  
View full article
Issue My token is not displayed correctly in view as webpage version of email. Environment If customers manually type a {{my.token}} and use uppercase M such as {{My.token}}, then the view as webpage version of email may not render that token as expected. The feature to HTML encode lead tokens (source of external data) for security reasons, applies to my tokens that incorrectly use uppercase M. HTML Encode Tokens Solution Use the token picker to pick the correct lowercase {{my.token}}.
View full article
Issue Email won't be approved due to too many custom tokens Solution Sometimes when approving an email with a large number of of tokens, the following error message will appear: 'The number of custom tokens in the email exceeds the limit '   This is a article attached image   This means that you have too many custom tokens in the email and that if you wish to approve the email, you will need to remove one or more of your custom tokens in the email.    Its important to note that this only applies to custom tokens, which are tokens based on a custom field in Marketo.  This means that while you will be allowed to add more of the standard tokens to the email and approve it, you will not be allowed to go beyond the 40 custom token limit we have in place for the non-standard tokens. Here you will find all the standard tokens in Marketo
View full article
Summary When renaming a field in a CRM Custom/Entity it does not reflect the change in the constraint of filters/triggers/ Issue I renamed a field in my CRM Custom Entity/Object (MSD/SFDC) and I refreshed the schema. I can see the field name change reflected in the CRM Custom Entity/Object, but when I look for the field in constraint for filter/trigger I only see the old name. Environment Smart List Solution The workaround is that the customer can create a new field on the SFDC side and copy all the values from the old field to the new one. Then, this field can be used in smartlist filters. Old field can be disabled after that. Root Cause We are not propagating field name changes from SDFC to Marketo.
View full article