Knowledgebase

Sort by:
What’s changing? On February 21, 2019, Webkit announced the new release of Safari’s Intelligent Tracking Prevention (ITP), known as ITP 2.1 and ITP 2.2 shortly thereafter. With ITP 2.x, all persistent client-side cookies, i.e., non-session cookies created via JavaScript through document.cookie, are capped to a seven-day or one-day expiry.  Mozilla Firefox and Google Chrome have also announced their intent to conform to these new policies, though no details or dates have been released.   How does this impact Marketo? As a result of these changes to cookie policy, 7 days after their initial tracked visit to your domain, the Munchkin cookies of visitors using Safari (or future affected browser versions) created with the existing versions of Munchkin JavaScript will expire, and on subsequent visits they will be tracked as a new visitor.   How does Munchkin operate? On a person’s first visit to a page on your domain, a new anonymous person record is created in Marketo. The primary key for this record is the Munchkin cookie (_mkto_trk) which is created in the user’s browser.  All subsequent web activity on that browser is recorded against this anonymous record.  In order to be associated with a known record in Marketo, one of the following methods should be used: The person may visit a Munchkin-tracked page with a mkt_tok parameter in the query string from a tracked Marketo email link. The person may fill out a Marketo Form. REST Associate Lead call must be sent.   Once one of these actions is completed, the cookie and all its associated web activity will be associated with the known record.   How is Marketo planning to address ITP concerns? Marketo will implement a new web service to allow Munchkin cookies to be set with a Set-Cookie header via HTTP response, so that they may bypass the 7-day expiry cap imposed when setting cookies via JavaScript.   Do I need to do anything to take advantage of these updates? In order to leverage the new behavior and take advantage of the greater expiry period and tracking capabilities, ensure that you have configured the following: A Landing Page CNAME Secured Landing Pages (i.e. HTTPS) For external pages, you must have configured a Landing Page Domain or Domain Alias with a Top-Level Domain (TLD) matching the external domains which you wish to track For example, if you have pages on the domain www.example.com which are tracked, you must have configured an LP Domain or Alias which is a subdomain of example.com, like munchkin.example.com   What happens if I do nothing? Munchkin’s ability to track users across sessions on the same domain will remain limited by ITP to either 1 or 7 days based on the browser and browser version used by the visitor. As of this posting, this only affects visitors using the Safari browser, although Chrome & Firefox may follow suit with their own versions.   When will the solution be launched? These changes will begin as a staggered roll-out to customers who have opted into the Munchkin Beta channel in conjunction with the January 2020 Marketo release. Once the solution has been released to all beta customers, the roll-out to our entire customer base will begin in mid-to-late February. All customers should expect to have the solution by end of March 2020.   Google Chrome Update (Feb. 2020): Google recently announced that the Chrome browser will block all third-party cookies within two years; however, s ince Marketo uses 1st party cookies, this update regarding 3rd party cookies will NOT affect your Marketo tracking efforts. For further context about 3rd party cookies in general, and the industry shift away from using them, please see the following article for Adobe's stance across the Experience Cloud Solutions: https://medium.com/adobetech/an-adobe-perspective-google-chromes-announcement-on-the-future-limits-of-3rd-party-cookies-bbb7bb257fdb
View full article
Issue Description You have deployed Munchkin tracking on the domain https://www.example.com/ and the tracked domain is showing as ". www.example.com " when it should be ". example.com ". Issue Resolution To resolve this, make sure you have the correct settings on the domainLevel property in the Munchkin code. Details can be found here: http://developers.marketo.com/javascript-api/lead-tracking/configuration/ Just be aware that domain levels are counted from left to right: domain3.domain2.domain1 For: http://www.example.com .com = level 1 .example.com = level 2 www.example.com = level 3
View full article
Issue Description Visit Web Page activity is tracked and showing up for one subdomain on your site, example.marketo.co, on a record but it is not recording activities for a different subdomain, pages.marketo.co.   Issue Resolution The reason that this behavior is taking place is because the domain that is being utilized has a two letter top level domain "example.co". For domains that end with a two letter suffix, “example.co”, the Munchkin script is setting the tracking cookie to the third domain level by default. This is to take into account two letter country codes such as “.jp”, “.us”, “.cn”, and “.uk”. This means that when someone visits “info.example.co”, the Munchkin script will assign a new cookie to “info.example.co” instead of “example.co”. When someone visits or is referred to a different subdomain, such as "pages.example.co” it will create a new cookie for this domain “pages.example.co”.   To prevent this from taking place you will need to add the Munchkin Initialization Parameter setting the “domainLevel” to “2”. This will cause the cookie to be set to the second domain level “example.co” when visiting either the Marketo or non-Marketo hosted landing pages. Details about the Munchkin Initialization Parameters can be found in this Developers Doc:   http://developers.marketo.com/javascript-api/lead-tracking/configuration/#domainlevel_property   Since the Marketo hosted landing pages will, by default, use the same 3 third level domain behavior, you will need to disable tracking at your template level using the steps at the end of this article:   http://docs.marketo.com/display/public/DOCS/Create+a+Free-form+Landing+Page+Template   This will disable the default tracking that all landing pages get in Marketo. Then, similar to external landing pages, your team will need to add the Munchkin tracking code to your Marketo templates, where you would have control to set the domain level to 2 (instead of 3). Once this has been updated on both the external landing pages and Marketo hosted landing pages, the tracking cookies will be set at the second domain level and work across the various sub-domains.   Who This Solution Applies To Customers with two letter domains Is this article helpful ? YesNo
View full article
Issue Description When I navigate to Admin>munchkin, I see option to select workspace. Why is that? Issue Resolution People generally use workspsce either because of their companies geographical location or Business Unit. In each case, the separation is because the marketing assets are completely different.  With that said, If you're using Workspaces in your Marketo account, you probably also have separate web presences that correspond to your workspaces. In that case, you can use the Munchkin tracking Javascript to assign your anonymous people to the correct workspace and partition. This is used to differentiate appropriate leads within workspace with the help of appropriate tracking.     If you don't use the special workspace Munchkin code, the people will be assigned to the default partition that was created when your account was set up. It's named "Default" initially, but you might have changed that in your own Marketo account.   You can only use one Munchkin tracking script for a single partition and workspace on a page. Do not include tracking scripts for multiple partitions/workspaces on your website. I would also like to mention that Landing pages created in Marketo automatically contain tracking code, so you don’t need to put this code on them. Who This Solution Applies To People who use Workspaces and Person Partitions Is this article helpful ? YesNo
View full article
Issue Description Marketo Forms embedded on non-Marketo web page do not show up when using Firefox private browsing. Issue Resolution Marketo forms and Munchkin tracking are inserted into non-Marketo pages via Javascript. If the browser privacy settings block the script from executing, Marketo forms and tracking will not work.  Marketo is not able to override a customer's browser security settings. The alternatives are as follows: Create a non-Marketo form on the web page Use a backend form submission to push the info in the form into Marketo. Instructions for doing so can be found here: http://developers.marketo.com/blog/make-a-marketo-form-submission-in-the-background/ Who This Solution Applies To Customers using Firefox private browsing
View full article
Issue Description External tracked webpages are not showing up in "Visited Webpage" or "Filled Out Form" Smart List filter.   Issue Resolution Munchkin tracked pages will not show up in Smart List filters until a known lead visits the webpage. To make sure the webpage shows up, do the following: Make sure that you have the Munchkin tracking code on those webpages. Use a test lead to visit the page and you may have to fill out a form or send an email to the lead to make sure that the lead is tracking on your machine. Check the test lead's activity history to make sure the visit is logged. Try entering the webpage in the filter again. Is this article helpful ? YesNo
View full article
Issue Description You have the Munchkin tracking code on your non-Marketo web page but visits to the page are not being tracked.   Issue Resolution If you have customized the Munchkin tracking code, it may not work.  Marketo only supports the Munchkin code as it is provided in your instance.  If you need to alter the code, you would need to work with your web developer to determine why the customized code is not working.   To find the supported Munchkin tracking code: Go to Admin > Munchkin. Select the version of Munchkin you intend to use. Place the Munchkin code on your page as outlined in our document on adding Munchkin tracking to your site. Is this article helpful ? YesNo
View full article
Issue Description How does Munchkin tracking work when you have one page inside an IFrame on another page?   Issue Resolution Munchkin will track page visits for whichever pages include the Munchkin tracking code. If you only have Munchkin on the main page, visits will only be tracked for the main page. If you only have Munchkin on the IFramed page, only the IFramed page will record a page visit. If you have Munchkin tracking on both the main page and the IFramed page, visits to both pages will be recorded in the lead's activity history.   If the main page and the IFramed page are on two different domains, the lead must be a known lead on both domains in order to be tracked on both pages.  Please see this this post for more details on Munchkin tracking on multiple domains:  Using Munchkin on Multiple Domains. Is this article helpful ? YesNo
View full article
Issue Description The Smart List in a Campaign gives 'Invalid URL' error for a valid URL (non-Marketo landing page URL).   Issue Resolution To make sure non-Marketo landing page URL will show up in Smart List's filters, the following steps have to be done.   Make sure the Marketo Munchkin Tracking code is implemented and placed within the non-Marketo webpages. The non-Marketo URLs would show in the filter if a known lead/person has visited the web page and tracked into the activity log. Therefore, make a lead/person and visit the webpage to allow Marketo to track and log that URL visit. Is this article helpful ? YesNo
View full article
Included in this article Overview Have you ever tried to enter a web page into a Visits Web Page trigger or filter and gotten an unexplained red squiggly line? It looks like the one you get in Microsoft Word when you have a spelling error. You hover your mouse over it and it says "Invalid URL" even though you know that the web page is a good one. This can be a frustrating one, but here are a few things to look for to troubleshoot this problem. Troubleshooting To Try There are a few different reasons why this could happen. You could have an error in the formatting of the URL entered, you could have a page that isn't being tracked or hasn't had any visitors. Here's what to check for. http:// and https:// Using http:// or https:// in the beginning of the URL can cause the red line to appear. Check if you have it in the URL. If yes, remove it and the red line should disappear. No Munchkin Tracking Code on Web Page If the web page you're entering doesn't have the Munchkin tracking code on it yet, there's no way for Marketo to "see" the page at all. Make sure the Munchkin code is on the page and is actively tracking as it should be. For more details, check out Add Munchkin Tracking Code to Your Website - Marketo Docs - Product Docs No Visitors to the Web Page Yet Another cause for the red squiggly line to appear is if there have been no visitors tracked by munchkin on the targeted page. Filters look through lead record activity logs for the activity they're looking for. If the filter is searching for leads that have visited a particular web page but no leads have logged that activity yet, the filter can read this as an invalid URL, similar to if there were no Munchkin code on the page. Check the page for visits. Make sure you have a munchkin installed on the page you are requesting. Create a test lead and visit the targeted page. Tips for Triggers and Filters Here are a couple of things that may help when using these filters and triggers. Selectors "Is" Selector In Triggers and Filters, if you use the selector "Is", (as in "the web page IS xyz.123.com") then the results returned will only be those from an exact URL match. If you want to also find results for the page xyz.123.com/sales, they won't be returned when using the "is" selector. NOTE : The "is" selector will return results in filters much faster since it is only looking for exact matches. "Contains" Selector If you use the selector of "contains", (as in "the web page contains xyz.123.com"), then this would return results for all pages that have xyz.123.com. Therefore, xyz.123.com/sales would match. The page xyz.123.com/products would match. All variations of that site xyz.123.com would match up. NOTE : The "contains" selector in filters will take a little longer to process because it has to evaluate the entire URL string in every web page visited to identify whether there's a match for the value anywhere within the URL. It's not extremely long of a delay, but you may notice a little slowness.
View full article
Supported CRMs   Marketo has out-of-the-box, bi-directional sync support for the following CRMs: Salesforce.com Microsoft Dynamics CRM 2011 Online, On-Premises and CRM 2013   Boomi Connector   Through our partnership with Boomi, you can sync other CRMs to your Marketo system through one of their connectors.  Contact your account executive or the Marketo sales team to learn more about this. Unsupported CRMs   If you use an unsupported CRMs, here are the methods we have available for your integration: Import/Export Review the following articles to use a CSV spreadsheet to import and export leads from Marketo: Import leads from a spreadsheet into Marketo Export a list Custom Fields If you contact the Marketo Success Team, we can set up custom fields for your account as you need them. Send Alert Using the Send Alert flow step, you can inform your sales team, using email, about noteworthy events, including a link to the lead's details.  You can also format your emails with XML so they can be automatically processed by your system. Using Send Alert Munchkin JavaScript API If you have web development resources, you can use our JavaScript API to integrate your web forms with Marketo. Munchkin JavaScript API SOAP API If you have programmers available, you can integrate our SOAP API to retrieve and update leads among other functionality. Marketo SOAP API Is this article helpful ? YesNo
View full article
Note: Please ensure that you have access to an experienced JavaScript developer, because Marketo Technical Support is not set up to assist with troubleshooting custom JavaScript. If you're trying to use the Munchkin API but not having any success, try these tips: Include the Munchkin JS Make sure you include the required lines of Munchkin Javascript on pages with API calls.  You can find the javascript in the Admin section under Munchkin Setup . Check "Enable Munchkin API" In the Munchkin Setup page, check the box that says Enable Munchkin API , put in a private key (which can be any text), and click Save . Look for JavaScript errors Use Firebug on Firefox or enable IE JavaScript debugging to check for JavaScript errors.  Any JavaScript errors that occur -- anywhere on the page -- could prevent Munchkin from working. Escape special characters Check and make sure that any quotation marks or other characters that require escaping are properly escaped.  See this document for more. Call mktoMunchkin first In your Javascript, you must call mktoMunchkin() before you use any other Munchkin API calls. Try a proxy program Use a web traffic capturing program like Firebug (for Firefox) or Fiddler.  The return code from the API call may have useful information to help you diagnose the issue. Click Link or visit WebPage isn't working Check to make sure you have only a path listed in the url parameter -- no ", no domain, and no URL parameters. Associate Lead isn't working This could be caused by a few issues: Include an email address Email address is required when using the associate Lead call.  If you don't use this, the call will always fail. Check the labels Marketo expects the labels (like "Email" and "FirstName") in a specific format.  You can get these labels in the Field Management page of the Admin section.  When you get there, click the Export Fields button.  The spreadsheet will have the API names for your fields. ‌ Check the hash value The hash value is the SHA1 hash (non-HMAC version) of your API Private Key (not your Munchkin ID) concatenated with the lead's email address, as in your-secret-keyemail@address.com .  The hash value must be lowercase.
View full article
Question   For those who do not want forms to pre-populate and/or track web behavior on a specific page (ie. referral sign-up pages), follow the instructions below to disable the Munchkin tracking JavaScript . Note, forms filled out on a page without Munchkin will not get Fill Out Form activity written to the lead Activity Log.   Solution   Edit a landing page template Go to the HTML Source tab Find the line: <?php echo $mContext['endElements']; ?> Add the highlighted portions: <!-- <?php echo $mContext['endElements']; ?> --> Re-approve the landing page template and any associated landing pages This change only applies to customers with Marketo Versions Released in 2013. Is this article helpful ? YesNo   Please make clear notes for other users that will use this template - this will eliminate confusion on the page tracking behavior.
View full article