Invoca supports attribution tracking across sub-domains of the same domain, but not across separate second-level domains without custom development.
Cross sub-domain tracking: supported
Invoca stores all visitor session data in cookies set at the second-level domain (for example, *.invoca.com). Visitor data is 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 is preserved.
Cross-domain tracking: not supported
When visitors move between separate second-level domains (for example, invoca.com to ringrevenue.com), cookies can’t be transferred, since the visitor would have a different Invoca ID and attribution on each domain. This is a common limitation across the industry due to browser visibility and privacy restrictions.
Visitors who navigate to a new domain — even after initially landing with marketing attribution on another domain — are attributed as “referral” traffic from the previous domain. This lets you see how much traffic moves between domains before a call happens. However, the original attribution is lost unless the call is made from within the original domain.
Accounts have the option to implement their own custom workarounds to persist cookied data across second-level domains, but this requires custom development work and isn’t a best practice formally supported by Invoca.
Applies to: Invoca Tag
Where to go next
Last modified on September 21, 2026
