In result, this visitor also receives new generation on the CG, as all the visitor's history remained inside the identification cookie on the previous domain. So, whenever visitor travels from one domain to another inside one campaign, he or she receives new identification information on the domain he travels to. Travelling between sub-domains ( and ) does not lead to the issue described in this topic.Ĭookies are visible on the host they were set to. The problem lies in maintaining consistent visitor identification information for Maxymiser platform in case of cross-domain user journey.Ī good cross-domain journey example would be visitor's transfer from to. Campaign Design API > Cross-domain visitor ID transfer
