Kajabi
Add Rybbit analytics to your Kajabi site
Kajabi has a site-wide Header Page Scripts field under Site details that puts code in the <head> of every page, but it deliberately skips Offer checkout and upsell pages. Those have their own Checkout Tracking Code setting, so a full install is two pastes.
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 Kajabi
Site-wide pages
- From the Dashboard, open Settings.
- Under Site settings, click Site details.
- Scroll to Page scripts and paste the snippet into Header Page Scripts.
- Save.
Checkout and upsell pages
- From the Dashboard, open Settings.
- Under Payment settings, click Checkout.
- In the Checkout Tracking Code section, click to edit the Header tracking code and paste the same snippet.
- Save.
Do not paste the snippet into a page's Custom Code section (under Customize > Settings). That field is for CSS and JavaScript without <style> or <script> tags, and it only applies to that one page.
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
- Checkout pages missing from the dashboard: Header Page Scripts do not run on Offer checkout or upsell pages. Add the snippet under Settings > Checkout > Checkout Tracking Code as well.
- Both fields filled, one visitor, two sites? Use the same site ID in both places so a visitor who browses your site and then buys is one session, and funnels can follow them through checkout.
- Snippet added to a page's Custom Code block instead: the Add block > Custom Code block does accept
<script>tags, but it only covers that page. Keep the site-wide field as the source of truth.
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.