The install check fails
The website stays on "Needs the install code" although you pasted the code. Nine causes, from a cache to a tag manager, each with its cure.
The check looks for your code in two ways: the script reports in when a page of your site is opened in a browser, and Tafsee also fetches your homepage and looks for your site key in it. Knowing this explains most failures.
First, try this
- Open your website in a browser, on a page where you pasted the code.
- Go back to the app and click Check my site.
This alone cures the cases where the code is on the site but not in the homepage's own HTML.
The messages you may see
- We couldn't find the install code on this page. Check it's pasted just before </head>.
- We couldn't reach your site. Check the domain and try again.
- This site has a different Tafsee install code, probably from another workspace. Replace it with this site's code, then check again.
Causes and cures
1. The change is not live yet
You saved the code but did not publish the theme, the site or the tag-manager container. Publish it.
2. A cache still serves the old page
A cache plugin, your platform's cache or a CDN holds the page from before. Clear it, then check again.
3. The code is added by a tag manager
The code is then not in the page's HTML, so fetching the homepage cannot find it. Open your site once in a browser and check again.
4. The code is on some pages only
It must be on every page, in the template all pages share. If the homepage has no code, the fetch finds nothing; opening a page that has it lets the check pass, but campaigns still cannot show on pages without the code.
5. It is another website's code
Each website in Tafsee has its own code. If you manage several websites or organisations, copy the code again from this website's card.
6. The domain does not match
The script's report counts only when it comes from the domain you added. If you added yourstore.com and the code runs on another address (a staging address, or the platform's own address such as a myshopify or a preview address), it does not count. Add the address your visitors really use.
7. Your site cannot be reached from outside
A store with a password page, a "coming soon" page, a firewall that blocks unknown visitors, or a site that is not on https cannot be fetched. Open the site in your own browser with the code on it; the script's report is enough.
8. Something blocks the script in your browser
An ad blocker or a privacy extension can stop the script from loading, so it never reports in. Try a private window without extensions, or another browser.
9. A Content-Security-Policy blocks it
If your site sends a Content-Security-Policy header, allow scripts and requests from the host named in the install code. The test panel says when the campaigns could not be loaded.
Check by hand
- Open a page of your site, right-click and choose View page source.
- Search for tafsee. You should find the code once, with your site key starting with pk_.
- If you find it twice, remove one copy.
With a tag manager, look in the browser's developer tools instead: on the Network tab, search for v1.js.
Go live anyway
The check is a help, not a gate. In the Publish step click I'll check later. The campaign starts showing as soon as the code is on the site.
Ask for help
Under the code, Send to my developer writes a message for your developer, and Need help installing? links to us.
