Let’s say you want to track what happens as people browse on different subdomains of your site, and you want to see it all in the same Kissmetrics site.
Notice that all of these are part of
Using Event Manager
If you want to track the subdomains separately in two Kissmetrics sites, you can specify a cookie domain
- However, let’s say you are tracking two different domains:
This is a little more difficult, because now each domain has its own set of cookies to keep track of each visitor.
What do I need to do?
So far, we’ve seen two methods that work:
Maintain their ID server-side. This is most useful when the user can sign in to both domains, typically if you have a Single Sign-On system. That lets you identify a logged-in customer with the same username/email address/database ID, regardless of which domain they’re on.
When someone leaves one domain to go to another, append the destination URL with our URL API, which lets you pass their KM ID from the first domain to the next. This way lets you pass our anonymous IDs from a domain to the next one. Be sure that the same Kissmetrics code block is on both domain’s webpages.
Let’s look at an example of #2:
- Your site is on
www.yoursite.com, but you use
yoursite.3rd-party-checkout.com/as part of a funnel you are tracking.
- There is a link that takes people from
- Adjust the link, using our URL API to tag the current KM ID as part of the destination URL.
Example 1: Known Users
This is what hard-coding a URL would look like, to identify anyone who clicks this as “[email protected]”:
Example 2: Anonymous Users
You can use the
Down the line, if the customer ever goes from being anonymous to providing some identifying info, you’ll have to alias the anonymized and known id’s together, rather than rely on
identify to do the job. (The URL API treats the transferred ID as a “known” ID.)
If you track your different domains separately, as individual sites within your account:
1. (+) It’s easier to see each domain in isolation.
2. (+) You do not have to worry about making sure each person’s identity stays the same across your domains.
3. (-) However, it’s much harder to compare activity across the domains, because of how we keep the data separated.
If you track your different domains as one site within your account:
1. (+) You can see a complete picture of people’s activity from your marketing site to your app or checkout cart.
2. (+) You can still create separate events to differentiate reporting on activity in one domain vs. the other.
3. (-) However, there is extra setup to ensure that people are being represented with the same ID on all of your tracked domains.
Updated almost 2 years ago