{"Status":true,"Message":"","Response":{"post":{"postuid":"cd435b1b-b1ab-42bd-a9ef-3e23d2fd2ce4","tenantuid":"d8b744fc-2e70-4089-bb80-dd1d08f6c7b2","projectuid":"239698c5-f7eb-4574-8cc8-c6568f08b3a0","title":"Cross-Domain Tracking","slug":"article/cross-domain-tracking","html":"\u003Cp\u003ECross-domain tracking enables DailyStory to maintain visitor identity when a known contact navigates between multiple domains that you own. When configured, DailyStory automatically appends tracking parameters to outbound links that point to your other domains, ensuring a seamless visitor experience across your web properties.\u003C/p\u003E\u003Ch2 id=\u0022how_crossdomain_tracking_works\u0022\u003EHow Cross-Domain Tracking Works\u003C/h2\u003E\u003Cp\u003EDailyStory identifies visitors using a unique identifier called a \u003Cb\u003EDsID\u003C/b\u003E. When the \u003Ca href=\u0022/article/ppg0z9xv1v-installing-the-daily-story-tracking-tag\u0022\u003EDailyStory beacon\u003C/a\u003E is installed on your website, it stores this identifier in the visitor\u0027s browser. However, browsers restrict access to stored data across different domains. This means that if a visitor moves from one of your domains to another, the second domain cannot read the DsID that was stored on the first.\u003C/p\u003E\u003Cp\u003ECross-domain tracking solves this by automatically appending the visitor\u0027s DsID and campaign information to outbound link URLs when a visitor clicks a link to one of your configured domains. The receiving domain\u0027s DailyStory beacon then reads these values from the URL and associates the visitor with their existing contact record.\u003C/p\u003E\u003Ch2 id=\u0022when_to_use_crossdomain_tracking\u0022\u003EWhen to Use Cross-Domain Tracking\u003C/h2\u003E\u003Cp\u003ECross-domain tracking is useful when your business operates across multiple domains and you want to track a visitor\u0027s journey across all of them. Common scenarios include:\u003C/p\u003E\u003Cul\u003E\u003Cli\u003EA main website on one domain with an online store on a separate domain\u003C/li\u003E\u003Cli\u003EMultiple brand websites that share a common customer base\u003C/li\u003E\u003Cli\u003EA marketing website that links to a separate application or booking platform\u003C/li\u003E\u003Cli\u003ERegional or product-specific websites under different domains\u003C/li\u003E\u003C/ul\u003E\u003Ccite class=\u0022recommended\u0022\u003E\u003Cspan class=\u0022title\u0022\u003ERecommended\u003C/span\u003E\u003Cp\u003ECross-domain tracking only works for known visitors. If a visitor has not been identified through a DailyStory campaign link, web form, or other identification method, outbound links are not modified. This prevents anonymous visitor IDs from being unnecessarily passed between domains.\u003C/p\u003E\u003C/cite\u003E\u003Ch2 id=\u0022what_gets_appended_to_urls\u0022\u003EWhat Gets Appended to URLs\u003C/h2\u003E\u003Cp\u003EWhen a known visitor clicks a link to a configured cross-domain tracking domain, DailyStory appends the following parameters to the URL:\u003C/p\u003E\u003Ctable border=\u00221\u0022 style=\u0022border-collapse: collapse; width: 100%;\u0022\u003E\u003Cthead\u003E\u003Ctr\u003E\u003Cth\u003EParameter\u003C/th\u003E\u003Cth\u003EDescription\u003C/th\u003E\u003C/tr\u003E\u003C/thead\u003E\u003Ctr\u003E\u003Ctd\u003Edsid\u003C/td\u003E\u003Ctd\u003EThe visitor\u0027s unique DailyStory identifier\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003Eds_campaign\u003C/td\u003E\u003Ctd\u003EThe campaign token associated with the visitor\u0027s current session (only included when a campaign is active)\u003C/td\u003E\u003C/tr\u003E\u003C/table\u003E\u003Cp\u003EFor example, if a visitor on \u003Ccode\u003Eexample.com\u003C/code\u003E clicks a link to \u003Ccode\u003Eshop.example.net\u003C/code\u003E, the URL is automatically updated to include the tracking parameters: \u003Ccode\u003Eshop.example.net/products?dsid=abc123\u0026amp;ds_campaign=Summer_Sale\u003C/code\u003E.\u003C/p\u003E\u003Cp\u003EThese parameters are cleaned from the browser\u0027s address bar after they are read by the DailyStory beacon on the destination domain, so visitors will not see them in their URL bar.\u003C/p\u003E\u003Ch2 id=\u0022how_links_are_evaluated\u0022\u003EHow Links Are Evaluated\u003C/h2\u003E\u003Cp\u003EDailyStory evaluates every link click on your page and applies the following rules:\u003C/p\u003E\u003Col\u003E\u003Cli\u003E\u003Cb\u003ESame-domain links are ignored.\u003C/b\u003E Links to pages on the current domain (including relative links like \u003Ccode\u003E/about\u003C/code\u003E) are never modified.\u003C/li\u003E\u003Cli\u003E\u003Cb\u003EOnly configured domains are modified.\u003C/b\u003E Outbound links are only modified if the destination domain is in your cross-domain tracking list. Links to external sites like Google or Facebook are never modified.\u003C/li\u003E\u003Cli\u003E\u003Cb\u003EOnly known visitors trigger tracking.\u003C/b\u003E If the visitor has not been identified (their DsID was generated locally rather than received from a DailyStory campaign), no parameters are appended.\u003C/li\u003E\u003Cli\u003E\u003Cb\u003ECampaign is optional.\u003C/b\u003E If no active campaign is associated with the visitor, only the DsID is appended.\u003C/li\u003E\u003C/ol\u003E\u003Ch2 id=\u0022requirements\u0022\u003ERequirements\u003C/h2\u003E\u003Cp\u003EFor cross-domain tracking to work correctly:\u003C/p\u003E\u003Cul\u003E\u003Cli\u003EThe \u003Ca href=\u0022/article/ppg0z9xv1v-installing-the-daily-story-tracking-tag\u0022\u003EDailyStory beacon\u003C/a\u003E must be installed on all domains involved in cross-domain tracking.\u003C/li\u003E\u003Cli\u003EAll domains must belong to the same DailyStory tenant account.\u003C/li\u003E\u003Cli\u003EThe domains must be configured in your cross-domain tracking settings.\u003C/li\u003E\u003C/ul\u003E\u003Ch2 id=\u0022example_scenario\u0022\u003EExample Scenario\u003C/h2\u003E\u003Cp\u003ESuppose your business operates three domains: \u003Ccode\u003Eexample.com\u003C/code\u003E, \u003Ccode\u003Estore.example.net\u003C/code\u003E, and \u003Ccode\u003Eevents.example.org\u003C/code\u003E. All three are configured for cross-domain tracking.\u003C/p\u003E\u003Cul\u003E\u003Cli\u003EA visitor on \u003Ccode\u003Eexample.com\u003C/code\u003E clicks a link to \u003Ccode\u003Eexample.com/about\u003C/code\u003E \u2014 the link is \u003Cb\u003Enot modified\u003C/b\u003E (same domain).\u003C/li\u003E\u003Cli\u003EThe same visitor clicks a link to \u003Ccode\u003Estore.example.net\u003C/code\u003E \u2014 the link \u003Cb\u003Eis modified\u003C/b\u003E with tracking parameters.\u003C/li\u003E\u003Cli\u003EOn \u003Ccode\u003Estore.example.net\u003C/code\u003E, the visitor clicks a link to \u003Ccode\u003Eevents.example.org\u003C/code\u003E \u2014 the link \u003Cb\u003Eis modified\u003C/b\u003E with tracking parameters.\u003C/li\u003E\u003Cli\u003EThe visitor clicks a link to \u003Ccode\u003Efacebook.com\u003C/code\u003E \u2014 the link is \u003Cb\u003Enot modified\u003C/b\u003E (not a configured domain).\u003C/li\u003E\u003C/ul\u003E\u003Cp\u003EIn each case, DailyStory recognizes the visitor across all three domains and attributes their activity to the same contact record. This enables accurate \u003Ca href=\u0022/article/conversion-funnels\u0022\u003Econversion tracking\u003C/a\u003E and \u003Ca href=\u0022/article/rm60szpufp-tracking-link-metrics-and-reporting\u0022\u003Ereporting\u003C/a\u003E across your entire web presence.\u003C/p\u003E\u003Ch2 id=\u0022performance\u0022\u003EPerformance\u003C/h2\u003E\u003Cp\u003ECross-domain tracking has minimal impact on page performance. The click listener runs a few lightweight checks on each click and only modifies the URL when all conditions are met. There is no impact on page load time, and the URL modification happens instantaneously before the browser navigates to the destination.\u003C/p\u003E\u003Ch2 id=\u0022privacy_considerations\u0022\u003EPrivacy Considerations\u003C/h2\u003E\u003Cp\u003ECross-domain tracking only shares the visitor\u0027s DailyStory identifier and campaign token between domains that you own and have configured. Anonymous visitors are never tracked across domains. The DsID is validated to ensure it is a legitimate identifier before being accepted by the receiving domain, and tracking parameters are removed from the URL after being read.\u003C/p\u003E\u003Ch2 id=\u0022setting_up_crossdomain_tracking\u0022\u003ESetting up Cross-Domain Tracking\u003C/h2\u003E\u003Cp\u003ETo setup cross-domain tracking, navigate to Account Settings \u0026gt; Website Setup. At the bottom is the configuration for Cross-Domain Tracking. Add/remove the domains to configure.\u003C/p\u003E\u003Cimg class=\u0022lazy-load\u0022 data-width=\u00221208\u0022 data-height=\u0022291\u0022 data-src=\u0022https://graffiti-auf7e6dwhxhcbwek.z03.azurefd.net/d8b744fc-2e70-4089-bb80-dd1d08f6c7b2/239698c5-f7eb-4574-8cc8-c6568f08b3a0/faac3dc2-88c4-4ec0-83ef-4f4547ca0ed7.png?v=-1159946526\u0022 style=\u0022\u0022 alt=\u0022\u0022/\u003E\u003Cp\u003E\u003C/p\u003E","publish_status":0,"post_type":"Article","authoruid":"3dde8c16-763a-4a2b-ae0b-1d8c50c62e3d","author":{"authoruid":"3dde8c16-763a-4a2b-ae0b-1d8c50c62e3d"},"featured_image_updating":false,"meta_description":"Cross-domain tracking in DailyStory keeps visitor identity across your domains by appending IDs to outbound links, enabling seamless user journey tracking.","display_toc":true,"has_workingcopy":false,"allow_indexing":true,"sort_order":14,"total_views":7,"date_published":"2026-04-10T17:19:00","date_updated":"2026-04-10T20:37:14.593","date_created":"2026-04-10T17:17:59.707"}}}