KnowledgeBaseBackup

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, since 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

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:   https://developers.marketo.com/javascript-api/lead-tracking/configuration/   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:   https://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