You absolutely should start Munchkin tracking as early as possible.
However, if the individual websites do not share a private parent domain with the new domain -- for example, www.example.org and products.example.org do share example.org, but www.example.com and www.products.com do not share a parent, since .com is public and doesn't count -- the advantages are limited. Anonymous visits to individual websites will not be ported over to the new consolidated website in that case. This is because sessions are tracked using cookies, and cookies are not shared across different private parents.
But if someone has a non-anonymous (i.e. associated/known) session on the individual website, as they would if they clicked through an email, then you don't want to lose that tracking now.
Thanks so much! The individual websites do not share the same domain and each use different CRMs. The tentative plan is to redirect all of the existing websites into one, new, site that (and new domain). This new site will be the one that integrates with Marketo. I am assuming, in this case, whatever we track now will not be passed over? Will redirects cause any sort of issues here that you foresee?
1 of 1 people found this helpful
Will redirects cause any sort of issues here that you foresee?
Redirects won't have any special effect (good nor bad).
This new site will be the one that integrates with Marketo. I am assuming, in this case, whatever we track now will not be passed over?
Out of the box, that's right. With a significant development effort, you could continue your already-associated sessions on the new domain; otherwise, everyone will start anew with an anonymous session and will have to either click an email link or re-convert on a form to be associated again.