Applies To
Invoca TagAnswer
Cross sub-domain tracking: Supported
Invoca stores all visitor session data in cookies set at the second-level domain (e.g., *.invoca.com).
Visitor data will be retained when navigating across sub-domains within a given domain. For example, if a visitor lands on blog.invoca.com and then goes to careers.invoca.com, all visitor attribution will be preserved.
Cross-domain tracking: Not supported
When visitors move between second-level domains (e.g., invoca.com --> ringrevenue.com), cookies cannot be transferred since the user would have a different Invoca ID and subsequent attribution for each domain. This is a common limitation in internet visibility and privacy.
Visitors who navigate to a new domain, even after initially landing with marketing attribution on another domain, will be attributed as "referral" traffic from the previous domain. This behavior enables customers to determine the amount of traffic between domains before making a call.
However, please note that the original attribution will be lost unless the call is made from within the original domain.
Customers have the option to implement their own custom workarounds to persist cookied data across second-level domains. However, this necessitates custom development work on the customers' part and is not a best practice formally supported by Invoca.
