I'm trying to overcome the limitations of cross-domain tracking, and here's a case I'd like to run by you.
Let's assume I have a user on domain A, that's been identified by
hutk & email address, and then he types in a domain B and visits it. Cross-domain tracking is enabled for both domains, but he didn't navigate via the spiced-up link.
For those two hits, the same
hutk and the same HS account ID for both domains is not enough to tie the sessions, right?
Is there a way I can pass the
__hsfp, __hssc, and __hstc values by myself?