How does this impact Marketo?
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?
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:
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
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
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
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
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.