Thinkific Settings Required for SeaText Integration: A Readiness Checklist
SeaText works on Thinkific when you paste the JavaScript snippet into the Site Footer Code field under Settings → Code & Analytics. The Site Footer Code is the required and recommended field; the Site...
Quick answer: the required Thinkific setting
Thinkific does not have a separate "custom code injection" switch, a "third‑party scripts" toggle, or a domain‑whitelist panel for SeaText. The platform allows JavaScript in one place: the Site Footer Code field on the Code & Analytics tab under Settings. Paste the SeaText snippet there, click Save, and the integration is technically complete. The Site Header Code field exists on the same tab but loads earlier; SeaText expects the footer placement. Use Site Footer Code only.
Readiness checklist
| Check | How to verify | Pass criteria |
|---|---|---|
| Snippet present in page source | View page source on a live page; search for seatext | Script tag with your SeaText ID appears before closing </body> |
| Dashboard shows "Connected" | Open SeaText dashboard; look at top logo area | Your site name displays next to the SeaText logo |
| Variants loading | Open browser dev tools → Network; filter "seatext" | Requests to SeaText API return 200 with variant data |
| No console errors | Dev tools → Console | No red errors referencing SeaText |
Why the Site Footer Code field matters for SeaText
The Site Footer Code field injects content just before the closing body tag on every public page. SeaText’s agent is designed to start after the DOM is ready, so footer placement guarantees the script runs after page elements exist. Thinkific does not strip or sandbox scripts placed in this field, allowing the agent to inject variants, translations, and tracking without extra permissions. Using the footer also avoids race conditions that can happen when scripts load in the head before the page is fully parsed.
How the SeaText script executes on page load
When a visitor loads a Thinkific page, the browser parses HTML top‑to‑bottom. The SeaText snippet in the footer is encountered last. The snippet creates a small bootstrap function that waits for the DOMContentLoaded event, then loads the full SeaText runtime from the CDN. The runtime reads the account ID, initiates a WebSocket connection, and begins listening for variant and translation instructions. Because the bootstrap runs after the DOM is ready, it can safely modify headings, buttons, and forms without causing layout shifts.
Step‑by‑step configuration in Thinkific
- Log in to your Thinkific Admin Dashboard.
- Open Settings in the left navigation.
- Select the Code & Analytics tab.
- Locate the Site Footer Code text area.
- Paste the JavaScript snippet you copied from the SeaText dashboard.
- Click Save at the bottom of the page.
That is the entire Thinkific‑side setup. The snippet loads on every page, including course pages, landing pages, and checkout.
Trade‑offs between Footer Code and Google Tag Manager
Google Tag Manager (GTM) can also deliver the SeaText snippet via a Custom HTML tag set to fire on All Pages. GTM adds a management layer: you can version‑control the tag, preview changes, and disable it without editing Thinkific. However, GTM introduces an extra request and a potential race condition if the tag fires before the DOM is ready. The direct footer paste is simpler, has one fewer network hop, and guarantees execution order. If you already manage all marketing scripts in GTM, using GTM is acceptable; otherwise, the footer field is the recommended path.
Connecting the site in the SeaText dashboard
- Open your SeaText account and go to the website‑linking form.
- Enter your domain in the format
www.example.com(no protocol, no trailing slash). - Submit the form.
- Visit any page on your live Thinkific site and stay for at least 40 seconds. This triggers the initial handshake.
- Wait up to five minutes (ten minutes maximum) for your site name to appear next to the SeaText logo in the dashboard. If it does not appear after ten minutes, contact SeaText support.
Deeper handshake troubleshooting
If the dashboard remains in a waiting state, first verify the snippet is present in the page source. Open the browser console and look for a message like SeaText handshake sent. Absence of that message usually means the script never executed. Common causes: ad blockers stripping the script, a Content Security Policy blocking the SeaText CDN, or the snippet being placed in the Header Code field instead of the Footer. Test in an incognito window with extensions disabled. If the handshake fires but the dashboard still shows waiting, check the Network tab for a POST to api.seatext.com/handshake returning 200. A non‑200 response indicates a server‑side issue; contact support with the request ID.
Common pitfalls and how to avoid them
- Pasting into the wrong field. The Site Header Code field exists on the same tab but loads earlier; SeaText expects the footer placement. Use Site Footer Code only.
- Using a staging or preview URL. The domain you register in SeaText must match the live domain visitors use. Preview URLs (e.g.,
mysite.thinkific.com) will not activate the agent for your custom domain. - Clearing the field during theme changes. Switching Thinkific themes does not erase the Code & Analytics fields, but always verify the snippet is still present after a theme change.
- Ad blockers or browser extensions. They can prevent the 40‑second activation ping. Test in an incognito window if the dashboard stays in "waiting" state.
Verification checklist after installation
| Check | How to verify | Pass criteria |
|---|---|---|
| Snippet present in page source | View page source on a live page; search for seatext | Script tag with your SeaText ID appears before closing </body> |
| Dashboard shows "Connected" | Open SeaText dashboard; look at top logo area | Your site name displays next to the SeaText logo |
| Variants loading | Open browser dev tools → Network; filter "seatext" | Requests to SeaText API return 200 with variant data |
| No console errors | Dev tools → Console | No red errors referencing SeaText |
When this setup does not apply
- Thinkific Sites on a subdomain you do not control. If you cannot edit Settings → Code & Analytics (e.g., a client’s account where you only have course‑author access), you cannot install SeaText.
- Custom CSP headers added via a proxy or Cloudflare Worker. If your team has layered a Content Security Policy that blocks inline scripts or the SeaText domain, the agent will fail even though Thinkific accepted the snippet.
- Legacy Thinkific plans without Code & Analytics access. All current paid plans include the tab; very old grandfathered plans may not. Upgrade or contact Thinkific support if the tab is missing.
Terminology reference
- Site Footer Code
- A textarea in Thinkific’s Settings → Code & Analytics that outputs its contents just before the closing
</body>tag on every public page. - SeaText snippet
- A short JavaScript block unique to your SeaText account that bootstraps the AI agents, variant testing, translation, and analytics.
- Handshake
- The 40‑second visit that sends a ping from the browser to SeaText, linking the live domain to your dashboard.
Frequently asked questions
Do I need to enable "Custom Code" or "Advanced Settings" in Thinkific?
No. Thinkific does not gate the Site Footer Code behind a feature flag. If you see the Code & Analytics tab, you can paste the snippet immediately.
Can I use Google Tag Manager instead of the footer field?
Yes, but it adds a layer of complexity. The direct footer paste is simpler and avoids GTM race conditions. If you already manage all scripts via GTM, add the SeaText snippet as a Custom HTML tag set to fire on All Pages.
What if I have multiple Thinkific sites under one SeaText account?
Each site needs its own domain entry in the SeaText dashboard and its own snippet paste in that site’s Site Footer Code. The snippets differ by account ID, so copy each one from the corresponding SeaText project.
Does SeaText work on Thinkific checkout pages?
Yes. The Site Footer Code loads on checkout, thank‑you, and course‑player pages, so personalization, translation, and bot detection run across the full funnel.
How do I update the snippet when SeaText releases a new version?
SeaText updates the script at its CDN origin; the snippet you pasted references a stable URL. You rarely need to replace it. If SeaText support asks you to refresh, copy the new snippet from the dashboard and overwrite the old one in the same footer field.
Can I restrict SeaText to only certain pages?
Not from Thinkific. The footer field is global. Use SeaText’s dashboard configuration to disable agents on specific URL patterns if needed.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Learn more
Visit the website for more information.