🌐 Cross-Domain Tracking

Modern browsers block third party cookies. If your tracking link is on yoursite.com and your thank you page lives on a checkout domain, the browser will not share your cookie between them. WP Conversion Tracker AI carries the click ID a different way, in the address itself, so tracking keeps working.

How It Works:

1. A visitor clicks your tracking link.
2. The tracker adds ?wct_click_id=123 (the real number) to the destination address.
3. The recommended pixel on the next page reads that value from the address and saves it in the browser's local storage.
4. When the pixel reports the lead or sale, it sends the click ID along, so no cookie is needed at any point.

The 🌐 How Cross-Domain Tracking Works card on 🎯 Tracking Setup sums this up in four lines.

Pick The Right Approach:

• Same domain, where the tracking link and the thank you page are on one site: the cookie or the address both work, and even the simple one line pixel is fine.
• Cross domain, where they are on different sites: use the recommended lead or sale pixel, which reads wct_click_id from the address. The simple image pixel relies on a cookie and is not the right choice here.
• Multi page funnels, with several pages before the thank you page: the recommended pixel stores the click ID on the first page it runs, so attribution survives even if a page in between drops the parameter, as long as the final page has the same pixel.
• Server to server, where the payment platform sends a postback: the click ID travels in the postback itself, so cookies and domains do not matter.

A Practical Checklist:

1. Open your tracking link in a private window and check that the destination address really ends with ?wct_click_id= and a number.
2. Check that your landing page and checkout keep that parameter. Some page builders and carts remove extra parameters.
3. Use the recommended pixel, not the one line image, on any page that is not on the same domain as your tracking link.
4. If a platform removes parameters whatever you do, switch that platform to a server postback.

When A Platform Will Not Carry The Click ID:

Move the conversion to a page you control. Set your checkout to send buyers to your own thank you page after purchase, and put the sale pixel there. The pixel finds the click ID it stored earlier in the visitor's browser.

A Real Example:

yoursite.com runs its webinar registration on a separate webinar service. The registration button goes through yoursite.com/webinar/fb-group, the visitor lands on the webinar page with ?wct_click_id= in the address, and the webinar service is set to send registrants back to yoursite.com/webinar-confirmed/. The lead pixel on that page finds the click ID in local storage, and the lead is joined to the fb-group click.

Testing Across Domains Step By Step:

1. Open a private window.
2. Click your tracking link. Check the address ends with ?wct_click_id= and a number.
3. Move through each page of the funnel. On the page with the pixel, the click ID is read from the address or from the browser's storage.
4. Complete the opt-in or purchase.
5. Open 💰 Conversions and check the conversion shows the right link and Sub-ID.

Tips:

• Pass Sub-IDs and UTM tags on to the destination when the other site needs them. See Forwarding Sub-IDs To The Destination URL and UTM Tags And Custom Parameters.
• See Lead And Sale Tracking Pixels for the exact snippets.