Thinkific
Add Rybbit analytics to your Thinkific site
Thinkific adds custom scripts through the Site Footer Code field under Settings > Code & Analytics. The code runs at the bottom of every page, including the Course Player, and editing it is available on paid plans (Basic or higher). Placing the snippet in the footer rather than the head is fine: it loads with defer, so timing is the same.
Get your tracking snippet
In your Rybbit dashboard, open Site Settings → Tracking Script and copy your snippet. It looks like this:
<script src="https://app.rybbit.io/api/script.js?siteId=YOUR_SITE_ID" defer></script>YOUR_SITE_ID is the numeric ID of your site. If you self-host Rybbit, app.rybbit.io is the domain of your own instance.
Add the snippet to Thinkific
- In the admin dashboard, go to Settings and open the Code & Analytics tab.
- Paste the snippet into Site Footer Code.
- Save.
See Thinkific's Site Footer Code article for the field's current limits. Lesson changes inside the Course Player happen without a page reload; Rybbit tracks them as pageviews automatically as the URL changes.
Verify installation
Open your live site in a new tab and click through a few pages. Within a few seconds the pageviews appear in the Rybbit dashboard.
If nothing shows up:
- View the page source and search for
script.js?siteId=to confirm the snippet is on the page. - Open the browser Network tab and check that
script.jsreturns200and thatPOSTrequests go to/api/track. - Disable ad blockers, or set up a proxy so the script loads from your own domain.
- See the script troubleshooting guide for other common causes.
Troubleshooting
- Field is read-only or missing: editing Site Footer Code needs a paid plan (Basic or higher).
- Checkout is not tracked: Site Footer Code does not run on Performance Checkout pages, so purchases complete outside Rybbit's view. Track the enrolment from the first page a student lands on after checkout, or use a webhook on your side.
- Community pages are not tracked: pages where students post and comment, and direct-messaging pages, are excluded from Site Footer Code by default.
- Per-page footer code: individual site pages also accept footer code in their page settings. Keep the site-wide field as the single place for the snippet so pages are not tracked twice.
Next steps
- Track custom events such as signups, purchases and button clicks.
- Identify users to connect sessions to accounts.
- Proxy the script through your own domain to bypass ad blockers.
- Script attributes let you skip or mask URLs and tag events.