Why It Matters
Modern browsers (Chrome, Safari, Firefox) block third-party cookies by default. If your tracking link is on yoursite.com but your thank-you page is on checkout.com, the browser won't send the cookie.
How WPC Tracker Solves This
When a visitor clicks your tracking link, the plugin automatically appends ?wct_click_id=123 to the destination URL. The recommended pixel snippets read this value from the URL and include it in the tracking request — no cookie needed.
What You Need To Do
|
| Scenario | | Solution |
|
| Same domain (tracking link & thank-you page on same site) | | Cookie or URL — both work. Even the simple image pixel works. |
| Cross domain (different sites) | | Use the recommended pixel snippets (with URLSearchParams). They read wct_click_id from the URL. |
| Multi-step funnel (several pages before thank-you) | | The pixel snippets store click ID in localStorage. As long as the final thank-you page uses the recommended snippet, attribution works. |
| Server-to-server (payment platform sends postback) | | Use the Postback URL — always works regardless of cookies or domains. |
💡 Best Practice: If your checkout platform strips URL parameters, use server-to-server postback URLs instead of browser pixels.
↑ Back to Table of Contents