How to Verify SeaText Is Tracking Correctly on Thinkific

You've added the SeaText snippet to Thinkific. Now you need proof it's actually working. The verification path is short: load your own site, linger long enough for the handshake, then watch the SeaText dashboard for the connection badge.

Why verification matters

Without a successful handshake, SeaText cannot receive visitor events. No events means no AI agents, no conversion insights, and no bot‑refund reports. Confirming the badge guarantees that your data pipeline is live.

It also protects you from wasted ad spend. If the script never fires, any paid traffic you send to the site will not be tracked, and you cannot claim refunds for bot clicks.

Understanding SeaText tracking architecture

SeaText uses a lightweight client script (< 15 KB) that loads in the browser. When the page loads, the script waits for a 40‑second dwell period. After the dwell, it sends a ping to SeaText's endpoint, including the domain name and a unique site identifier.

The server matches the domain to the entry you created in the "Linking SEATEXT AI to your website" form. If the match succeeds, SeaText creates a live website object and displays the site name next to the logo in the dashboard.

This process happens in real time, typically within five minutes. The architecture ensures that only genuine human visits trigger the link, reducing false positives from bots.

Prerequisites before you verify

• You have copied the exact JavaScript block from the SeaText integration page (the block labeled SEATEXTCODEINTEGRATION)【S1】.
• You pasted it into Thinkific Admin → Settings → Code & Analytics → Site Footer Code and clicked Save【S1】.
• Your Thinkific site is on a live, publicly reachable domain (not localhost, not a password‑protected staging subdomain)【S1】.
• You are logged into the same SeaText account that generated the snippet【S1】.
• Browser extensions that block scripts (ad blockers, privacy tools) are disabled for the test visit【S1】.

Step‑by‑step verification process

1. Open your live Thinkific site in a fresh browser tab. Use the exact domain you entered in the SeaText linking form (e.g., www.yourcourse.com)【S1】.
2. Stay on any page for at least 40 seconds. This dwell time triggers the handshake that links the domain to your SeaText account【S1】.
3. Open the SeaText dashboard in a second tab. Look at the top of the page next to the SeaText logo.
4. Wait up to five minutes. Your site name should appear next to the logo. This indicates the website is connected and ready for AI activation【S1】.
5. If the name does not appear after ten minutes, contact SeaText support. The integration guide says to do this after ten minutes【S1】.

What the connection badge actually means

When the badge appears, three things have happened:

• The JavaScript loaded without errors on your Thinkific pages.
• The 40‑second dwell ping reached SeaText's servers and matched the domain you registered.
• Your account now has a live website object that can receive AI agent configurations.

The badge does not mean any AI agents are active yet. Activation is a separate step in the Main AI Hub (Configuration → activate agents on preferred pages)【S1】.

Decision criteria for a successful verification

Use this checklist to decide if verification succeeded:

• Badge appears within five minutes of the 40‑second test visit.
• Network tab shows a successful request to seatext.com with status 200.
• No console errors reference SEATEXTCODEINTEGRATION.
• Site name in the dashboard matches the domain you entered.

If any item fails, move to the troubleshooting section.

Common reasons verification fails

Symptom	Likely cause	Fix
No badge after 10+ minutes	Snippet pasted into Header Code instead of Footer Code	Move the snippet to Site Footer Code and re‑save.
No badge after 10+ minutes	Domain in SeaText form doesn't match live domain (www vs non‑www, subdomain mismatch)	Re‑enter the exact domain in the linking form.
No badge after 10+ minutes	Cache serves old HTML without the snippet	Purge Thinkific cache (Settings → Site Builder → Clear cache) and any CDN.
No badge after 10+ minutes	Ad blocker or privacy extension stripped the script	Test in incognito mode with extensions disabled.
Badge appears but agents don't fire	Agents not activated in Main AI Hub	Go to Configuration → select pages → toggle agents on.

Advanced troubleshooting techniques

If basic fixes fail, try these deeper steps:

• Inspect the script URL. Open DevTools → Sources and verify the script loads from https://seatext.com/…. A 404 indicates a copy‑paste error.
• Check Content‑Security‑Policy (CSP) headers. If your site uses a strict CSP, add script-src 'self' https://seatext.com to allow the script.
• Validate DNS resolution. Use nslookup or an online tool to ensure your custom domain points to the correct Thinkific IP.
• Review server logs. If you have access, look for inbound requests to /ping from SeaText IP ranges (listed in the integration docs).
• Test with a different browser or device. Some corporate proxies rewrite scripts, causing failures.

Practical scenarios and examples

Scenario 1: New custom domain. You switched from mysite.thinkific.com to www.mybrand.com. After updating the domain in the SeaText linking form and repasting the snippet, the badge appeared in three minutes.

Scenario 2: CDN caching. A Cloudflare page rule cached the HTML for 24 hours. Purging the cache resolved the missing badge.

Scenario 3: Multiple Thinkific sites. Each site required its own snippet and domain entry. The dashboard displayed two site names after separate 40‑second visits.

After successful verification: what to do next

• Open Main AI Hub → Configuration and enable the agents you need (CRO Optimizer, Bot Protection, Translation, etc.)【S1】.
• Use Variants Edit in the left panel to review or manually adjust automatic translations and copy variants SeaText generated【S1】.
• Set up Google Ads tracking templates with ValueTrack parameters ({keyword}, {matchtype}) if you want the Google Ads Landing Page Agent to rewrite headlines per search term【S1】.

Key facts

Item	Detail
Install location	Thinkific Admin → Settings → Code & Analytics → Site Footer Code
Required dwell time	At least 40 seconds on any page
Connection indicator	Site name appears next to SeaText logo in dashboard
Normal appearance window	Within 5 minutes
Escalation threshold	Contact support if not visible after 10 minutes
Next step after connection	Activate agents in Main AI Hub → Configuration
Variant editing	Variants Edit panel → select URL and language

Limitations and when this advice doesn't apply

• This verification only confirms the JavaScript snippet loads and the domain handshake succeeds. It does not validate that specific AI agents are rewriting content correctly — that requires checking the Variants Edit panel or viewing a live page with the agent active【S1】.
• If your Thinkific site uses a proxy (Cloudflare Workers, CloudFront Functions), the ping may originate from a different hostname, breaking the match. Whitelist the SeaText endpoint or contact support.
• The steps assume a standard Thinkific plan with access to Code & Analytics. Legacy or restricted plans may hide that tab.

FAQ

Can I verify tracking without waiting 40 seconds?

No. The 40‑second dwell is the trigger SeaText uses to confirm a real human visited the domain. Shorter visits are ignored to filter bots.

Does the verification work on Thinkific's free mysite.thinkific.com subdomain?

Yes, as long as you enter that exact subdomain in the SeaText linking form and the site is publicly accessible (not password‑protected).

What if I manage multiple Thinkific sites under one SeaText account?

Each site needs its own domain entry in the linking form and its own snippet paste. The dashboard will show each connected site name once verified.

Why does the badge appear but my conversion numbers stay at zero?

The badge only means the script is connected. Conversions require active agents (CRO Optimizer, Google Ads Agent, etc.) and enough traffic to generate measurable events. Check Main AI Hub → Configuration to ensure agents are toggled on.

Can I use browser dev tools to see if the script fired?

Yes. Open the Network tab, filter for "seatext", and reload the page. You should see the JavaScript file download with a 200 status. If it’s blocked or 404s, the snippet URL is wrong or a CSP is blocking it.

Does SeaText have a Live View or real‑time event stream for Thinkific?

The source documentation does not mention a Live View feature. Verification relies on the connection badge and subsequent agent activation in the Main AI Hub.

What should I tell support if the badge never appears?

Provide the exact domain you entered, a screenshot of the Thinkific Code & Analytics page showing the pasted snippet, the time you performed the 40‑second test visit, and whether you used incognito mode. This lets support check server‑side logs for the handshake ping.

Will ad blockers always prevent the badge?

Most ad blockers block third‑party scripts, including SeaText. Disable them or test in a clean browser profile.

Is there a way to speed up the badge appearance?

The handshake runs after the 40‑second dwell. You cannot shorten it, but you can ensure the script loads instantly by placing it in the footer as instructed.

Do I need to clear Thinkific cache after each change?

Yes. After moving the snippet or updating the domain, clear the Thinkific cache (Settings → Site Builder → Clear cache) to serve the latest HTML.

Further reading

• Thinkific Troubleshooting Guide
• Thinkific Order and Signup Tracking Code
• Google Site Verification on Thinkific

Further reading and comparison sources

These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.

• Troubleshooting Guide for Student Issues – Thinkific
• Order and Signup Tracking Code – Thinkific
• Google Site Verification – Thinkific

Learn more

Visit the website for more information.