Install the tracking and prove it fired before you invite anyone
After this lesson you can
Get the tracking script and signup snippet live on your own domain and confirm with a test referral that a click, a signup and a conversion are all recorded.
Install the tracking and prove it fired before you invite anyone
Two pieces of code make the whole program work: a tracking script in the header of your website, and a signup snippet that fires once when a new account is created. The script records the click and drops the attribution cookie. The snippet tells Reditus that the person who clicked has become a signup. Everything downstream, the referral, the trial, the paid customer, the commission, depends on those two firing.
Install, then prove it
Most installations finish in under 30 minutes. The script goes into the site header, or through a tag manager. The snippet goes into the code that runs after a successful registration, once per new account. If people can sign up in more than one way, put it just after the signup step that every path shares, such as the first onboarding screen, so it fires regardless of how they arrived.
Then run the check that decides whether this program starts with data or without it: open your own affiliate link, sign up as a new user through it, and look at the dashboard. You are looking for one thing, a referral that shows as verified. Until you have seen that, you do not know your tracking works. You believe it.
What the two failure modes look like
Clicks recorded, no referrals: the script is fine and the snippet is not firing, or it fires before the account actually exists. Nothing recorded at all: the script is not on the pages affiliates link to, or the signup happens on a domain the script does not run on. Subdomains are fine. A second domain is not, and no amount of snippet work fixes that; the answer is Track 0, lesson 1.
Before you leave this lesson
Add whoever owns your codebase as a user on the account. There is no seat limit, and the person who installed the snippet is the person who should see the first verified referral. If you are going to connect payments through the API rather than Stripe, do your testing on the staging environment first and switch the endpoints to production only once a test referral has been paid end to end.
The record for a full installation is two and a half minutes. Nobody needs to beat it. Everybody needs the verified test referral.
Key takeaways
- Two components: the tracking script in your site header, and the signup snippet that fires once per new account.
- The install is done when you have seen a test referral show as verified, not when the code is pasted.
- Test every signup path separately. A snippet that fires on one path and not another looks healthy and loses referrals.
- Clicks without referrals means the snippet; nothing at all means the script or a second domain.
The detail lives in the help centre
This lesson tells you the order and the judgement. The clicks are in the articles below. Open one, do the step, and you will find a way back to this lesson at the top of the article.
Step-by-step: do this now
The exact clicks live in the help centre. Open the article, do the step, come back.
- How to install Reditus? Full installation guide.The complete install, screen by screen. Do this now.Help centre · Tracking, Attribution & Integrations
- Installing the tracking scriptThe script itself, with the placement rules.Help centre · Tracking, Attribution & Integrations
- Installing sign up snippet (into code) to send us referral data.The signup snippet, for whoever owns the code.Help centre · Tracking, Attribution & Integrations
- Testing the Sign Up SnippetThe "did it actually fire" check. Do not skip this.Help centre · Tracking, Attribution & Integrations
Reference: read if you need the detail
Background you can skip on a first pass.
- Intro into Reditus installationThe ten-minute overview of what gets installed and why.Help centre · Tracking, Attribution & Integrations
- Adding the sign up snippet in BubbleIf your app is built in Bubble.Help centre · Tracking, Attribution & Integrations
- FAQ InstallationEvery installation question we have been asked.Help centre · Tracking, Attribution & Integrations
- SaaS Affiliate Program Checklist: 10 Steps to Launch Successfully (2026)The ten-step launch checklist, if you want the whole setup on one page.Help centre · Strategy & Basics
- Updating tracking script from V1 to V2If you installed an older script version.Help centre · Tracking, Attribution & Integrations
- Why you typically don't need to ask for cookie consent for the Reditus cookieWhy the attribution cookie needs no consent banner.Help centre · Privacy & Security
- Reditus Demo (SaaS & Affiliate)A recorded walk-through of the SaaS side, if you prefer to watch first.Help centre · Strategy & Basics
Do this before the next lesson
Each step says how much counts as done. Doing a third of it and moving on is how programs stall.
Logged in? These open the right screen in your Reditus account. Not a customer yet? They take you to signup first.
Questions we hear at this point
How long does the installation take?
Typically under 30 minutes for the tracking script, the signup snippet and the Stripe connection. Connecting a different payment processor through the API takes longer, around four hours depending on the processor. The record for a full installation is two and a half minutes, which is a fun fact rather than a target.
Do we need cookie consent for the tracking script?
No. The cookie records only whether a signup came through an affiliate; it does not build a visitor profile, so it is an attribution cookie rather than a tracking cookie in the consent sense.
Can we use a tag manager?
Yes for the tracking script, which can be installed through Google Tag Manager. The signup snippet belongs in the code that runs after a successful registration, so it fires exactly once per new account.
Finished this lesson?
Saved in this browser only. No account, no certificate, nothing sent anywhere.