Pixel tracking breaks on my custom domain / thank-you page
You don't need a custom domain to use tracking pixels — the free Dropify subdomain works fine. But if you've connected a custom domain and your ads still point traffic to the old Dropify subdomain (or the two get mixed), your pixel data will be split across both, making tracking look broken.
Steps
- Confirm your custom domain is fully connected and set as primary in your domain settings — see How to connect a custom domain to your Dropify store for the connection steps.
- Update every ad campaign link (Facebook, TikTok, Google, etc.) to use your custom domain, not the Dropify subdomain. Any ad still linking to the subdomain will report separately from ads linking to your custom domain, even though pixel IDs are the same.
- Place a test order from an ad-style link (i.e. the actual URL structure your ads use) and check the checkout and thank-you (order-confirmation) page load on your custom domain throughout, not just the landing page.
- If the thank-you page reverts to the Dropify subdomain after checkout, note where in the flow it happens (product page, checkout, or right after payment) — this affects whether the Purchase event is attributed to your verified domain.
Common problems
- Pixel receives data from both the custom domain and the subdomainthis means some ad links or shares still point to the subdomain; audit and update all campaign URLs to the custom domain.
- Thank-you page loses the custom domain and drops back to the subdomainthis is a domain-configuration issue rather than a pixel setting; contact support with a screenshot of your domain settings so it can be checked.
- Trying to link a pixel but blocked because there's no custom domainnot actually required; pixels link fine on the free subdomain, a custom domain is only needed for branding and for some platforms' separate domain-verification requirement (see How to connect a custom domain to your Dropify store).