.svg){kind=icon}
Overview
When you use Everflow’s JavaScript SDK, the EF.click() function stores a cookie with the click ID on the same domain where it runs.
But here’s the catch:
If your EF.conversion() code runs on a different domain, it won’t have access to that cookie — and as a result, the click ID won’t be tracked properly.
This happens because cookies are domain-specific. So for example, if someone clicks on an So for example, if someone clicks on an ad that takes them to everflow.io (where EF.click() runs), and then they take an action like submitting a form or requesting support on everflowclient.io (where EF.conversion() runs), the click ID cookie doesn’t automatically follow them — because those are two different domains.
What You Need To Do: Pass the Click ID Across Domains
You need to manually transfer the click ID from the domain where EF.click() runs to the domain where EF.conversion() runs.
Still Need Help?
If you're unsure about your site's setup, or you're not seeing the click ID pass properly, don’t worry—contact our support team and we’ll help you troubleshoot.
