From Your Advertorial to Your Shop. Same Session.

When the funnel spans more than one domain you own and you want the conversion to be credited to the original ad. Classic examples:

• Blog or advertorial on example.com, Shopify store on shop.example.com or a fully separate shop.com
• Pre-lander on one domain, ThriveCart or SamCart checkout on another
• Multi-region stores: brand.com, brand.fr, brand.co.uk
• Cart-on-subdomain setups where store.com and store.cart.com are treated as different domains by browsers

In all of these, the buyer crosses a domain boundary and would otherwise start a brand-new session on the destination, losing attribution to the original ad.

No. If your CTA sends traffic to an external affiliate network or merchant you don't own, cross-domain tracking doesn't apply. You can't add the AnyTrack Tracking Tag to a domain you don't control. Use Postback URLs↗ and the network's click-ID forwarding instead. That's a different mechanism for a different problem.

The buyer clicks your Facebook ad and lands on advertorial.com with a fresh session and the fbclid in the URL. When they click your CTA to shop.com, the browser treats it as a brand-new domain. Cookies stay behind. The Shopify shop logs the session as source=advertorial.com / medium=referral. Facebook sees zero conversions, its AI bids lower on the audience that actually converts, and the original ad gets no credit.

The flow follows the property setup:

1. You create one property per domain in the journey (one for the advertorial, one for the shop).
2. You install the AnyTrack Tracking Tag on each property.
3. On the source property (the advertorial), you open Cross-Domain Settings and add the destination domain.
4. On the destination property (the shop), you toggle Sync Conversions with the source property.
5. Connect your shop's integration to the destination property (Shopify, WooCommerce, ThriveCart, etc.).

From then on, every CTA on the source pointing to the destination is auto-tagged with the atclid parameter. When the buyer lands on the destination, AnyTrack continues the original session. When they convert, the shop's integration captures the sale and forwards it to the source property too.

It depends on where the session started.

Session starts on the advertorial:

• Source property (advertorial) campaign report: source=google / medium=cpc (or whatever drove the ad click). AnyTrack sends the conversion to Google Ads, Facebook, TikTok, etc. via Conversion API.
• Destination property (shop) campaign report: source=advertorial / medium=referral.

Session starts directly on the shop:

• Only the destination property reports the conversion. The source is whatever drove the visitor to the shop directly.

Each property has its own ad-platform integrations, Conversion API pixels, and tag-manager settings. The advertorial property sends to Google Ads, Facebook, and whichever channels drive its traffic. The shop property sends to its own ad accounts if you also run direct-to-shop campaigns. The cross-domain settings only govern session continuity and conversion sync; they don't merge the ad accounts.

atclid is the AnyTrack click ID generated on the source property. When cross-domain settings are enabled, AnyTrack auto-tags every CTA pointing to the destination domain with ?atclid=<id>. The destination property reads it on landing, continues the original session, and preserves attribution back to the ad that started the journey.

1. Create one property in AnyTrack for each domain in the journey.
2. Install the AnyTrack Tracking Tag on each domain (one tag per property).
3. On the source property settings, scroll to Cross-Domain Tracking and add the destination domain. Save.
4. On the destination property settings, scroll to Cross-Domain Tracking and toggle Sync Conversions with the source property. Save.
5. Connect the destination's conversion source (Shopify, WooCommerce, ThriveCart, etc.) and your ad platforms.
6. Verify with AutoScan that CTAs to the destination are auto-tagged with atclid.

Typical setup: 15-30 minutes per pair of domains.

No. Add only the root domain. AnyTrack handles subdomain routing automatically.

No. That would generate self-referral traffic and corrupt your attribution. Add only the destination domain on the source property.

Many cart and funnel platforms have their own AnyTrack integration that already covers cross-domain requirements. Check the Integration Catalog setup guide for the specific cart system; it will tell you whether cross-domain settings are needed or whether the integration handles it natively.

Technically yes, but you'd still need a way to sync conversions back to your account from that domain. Without the Tracking Tag installed there, AnyTrack can't capture the session or the conversion. For domains you don't own, you're usually looking at server-side capture via webhook or postback, not cross-domain tracking.

Yes. AnyTrack uses first-party data and the atclid URL parameter rather than third-party cookies or fingerprinting. Both are aligned with GDPR, CCPA, and modern browser privacy frameworks. You control what data flows where based on user consent on each property.

Ad platforms optimize on the conversions they see. When the buyer's full journey is preserved across domains and the conversion is reported back to the original property's ad platform via Conversion API, the algorithm learns which ads drive sales, not just which ads drive landing-page visits. Better signal in, better targeting out.

Less than it affects pixel-only tracking. The atclid parameter rides in the URL, not in a third-party cookie, so iOS restrictions don't strip it. Combined with server-side conversion capture from your shop integration (Shopify, WooCommerce, etc.), the conversion reaches your ad platforms even when the buyer's browser is locked down.