By default, the site footer code does not apply to the Learner Hub or the New Course Builder. However, you can opt in and enable the site footer code in the Learner Hub and the New Course Builder by following these instructions.
Applies to:
- Plan: Basic, Start, Grow, Expand, Pro, Pro + Growth, Premier, Plus
- Role: Site Owner, Site Admin
How the Site Footer Code works on the Learner Hub and New Course Player
The Learner Hub and new Course Player are built differently from the classic Thinkific site, so Site Footer Code does not run on them automatically. You can enable it from your Code & Analytics settings, but because not all code behaves the same way on these surfaces, you should validate your code before relying on it.
When enabled, your scripts execute when a learner views a page in the Learner Hub or interacts with a course in the new Course Builder. Your scripts do not run while you or an admin are in course editing mode of the new course builder, only in the learner-facing experience and in admin course preview mode. The scripts will run in the Learner Hub, regardless of whether it is an admin preview or a student view.
How to Enable Site Footer Code on the Learner Hub and New Course Player
- Go to Settings
- Select the Code & Analytics tab
- In the Site footer code section, check the Also run this code on the learner hub and new course player checkbox
- Click Save
This single checkbox controls both the Learner Hub and the new Course Player together. It is off by default.
Custom code doesn't always work as expected on the learner hub and new course player. Validate your code and review how it behaves before relying on it: How to Check If Your Code Is Working.
What Tends to Work and What Might Not
Because Site Footer Code is a free-form field, always validate your specific code. The information below provides guidance and general patterns, but does not guarantee that your specific code will work.
Usually Works
These types of code do not depend on Thinkific's page structure and typically run as expected:
- Analytics and tracking that load and fire on a single page view, such as Google Analytics 4, Google Tag Manager, Meta (Facebook) Pixel, and LinkedIn Insight Tag.
- Third-party widgets that render their own container, such as live chat tools (for example, Intercom or Crisp), cookie consent bars, and support beacons.
- Self-contained scripts that do not read or modify existing Thinkific page elements.
May Not Work, or May Behave Unexpectedly
These types of code are most likely to break because they rely on the page being structured in a specific way:
- Code that targets specific elements by ID, class, or data attribute to hide, move, restyle, or inject content. The Learner Hub and new Course Player use a different structure than the classic site, so these targets may not exist — the code may silently do nothing or affect the wrong element.
-
Code that uses broad or generic selectors — for example, targeting all
iframeelements. This can unintentionally affect the Hub's own elements. - Code that assumes a full page reload on every navigation. The Learner Hub is a single-page app, so scripts run once on initial load and may not re-run as a learner moves between pages. Pageview-based analytics can undercount unless configured for virtual or history-change pageviews.
- Visual or branding customizations written for the classic site or classic Course Player. These were built for the old pages and generally will not carry over to the new experience.
How to Check If Your Code Is Working
After enabling the checkbox and saving:
- Open your Learner Hub and a course in the new Course Player as a learner.
- Confirm your script does what you expect — for example, your chat widget appears or your analytics records a visit.
- Open your browser's developer console and check for errors related to your code.
- If something looks wrong, uncheck the box to disable the code on these surfaces, fix or update your code, and try again.
Important Considerations
- This setting controls both the Learner Hub and the new Course Player together — they cannot be enabled or disabled separately.
- If you are adding analytics or tracking, check whether a built-in Thinkific integration exists for that platform before adding it manually via Site Footer Code. Built-in integrations are configured to work across the full site experience and avoid many of the issues described above.
Related Articles:
- Prerequisites: Site Footer Code
- Related: Cookie Consent Bar