Website Analytics and Campaign Tracking

Marketing → Performance has three tabs. Overview shows visits to your hosted website. Campaign results shows which tagged links produced enquiries, enrolments and payments. Tracking setup connects an analytics or advertising provider your organisation owns. Dashboard and Reports summarise operational records instead.

Access required

Choose the task you are doing. Each row is a separate action.

Site analytics (Overview)

RTObase counts approximate daily visitors, visits and page views for your public hosted pages and shows a daily trend, top pages, traffic sources, tagged campaigns, devices and countries for the last 7, 30 or 90 days or 12 months. Periods are whole Australian Eastern days ending today. A daily visitor is a browser and network combination counted once that day; shared networks and similar browsers can make this lower than the number of people. A visit starts when someone opens a page after 30 minutes away. Sources and campaign traffic are credited once per visit (the first page in the visit that carried a referrer or campaign tag, otherwise the page it arrived on), so one visitor who reads five pages after clicking a Google result counts as one Google visit, not one Google view and four direct views. Last visit recorded under the metric cards tells you counting is working even when the chosen period is quiet.

Below the traffic figures, Recorded in RTObase, all channels shows every enquiry and enrolment in the period however it arrived (website, phone, staff entry, imports). It is not a conversion rate for the traffic above; use the Campaign results tab for what tagged links produced.

What to tell visitors

"This website counts page views without cookies. It does not store names, IP addresses or full browser strings. It keeps a daily visitor key, sanitised path and broad traffic context for up to 400 days, and shows the training provider aggregate totals only." Shared office or classroom networks may count as fewer visitors, because devices behind one network address that use the same browser share a daily key.

Counting is cookieless and first-party. The site sends one small message per public page view. The server uses the network address and browser string transiently to derive a daily-rotating visitor key and a short-lived abuse-limit key, then discards the address and browser string. A retained page-view row contains only the visitor key, sanitised page path, referring host, bounded utm tags, device class, country and whether the view was embedded. Identical beacons within five seconds are ignored and each pseudonymous network key is limited to 60 attempts per minute.

Raw page-view rows are kept for up to 400 days so the report can cover 12 months, but authorised members receive only aggregate totals and top lists. The daily salt is discarded after two days, so the visitor key cannot be recomputed later, and a visitor who returns tomorrow counts as a new visitor. The student portal, pages inside a form and any page carrying a token or credential are never counted. The enrolment entry page and scrubbed enrolment and payment success pages are counted by path only, with the query string dropped. Payment and enrolment form screens remain excluded. In Embed mode only the RTObase pages inside your website are counted. Views from the backoffice preview are not counted.

Provider tools you connect under Tracking setup keep their own numbers. RTObase does not send those providers its first-party page-view records.

Supported providers

You can add up to 10 integrations across:

• Google Analytics 4
• Google Tag Manager
• Google Ads
• PostHog
• Meta Pixel
• Custom Script

Each integration can be enabled, disabled, edited, or removed without deleting the other integrations.

Add an integration

Website modes

RTObase-hosted website

Enabled integrations run on the public pages hosted by RTObase. The analytics page lists any configuration problems and the conversion milestones that the hosted website can emit.

Embedded enrolment

When the website is embedded in another site, saved hosted integrations do not run inside the enrolment flow. Configure analytics on the parent website and use the generated, origin-restricted listener from Embed setup if the parent needs to receive RTObase milestones.

Conversion milestones

The hosted website can report these stable milestones:

• Website enquiry submitted
• Course interest registered
• Enrolment awaiting LLND screening
• Enrolment completed
• Payment completed

The events identify the milestone and relevant course or campaign context without sending a learner's name, email address, phone number, or form answers.

Tag your own campaign links

Any link that carries standard utm_source, utm_medium and utm_campaign parameters is attributed on the Campaign results tab. Google Ads auto-tagging and affiliate links are picked up the same way; you do not need to build links inside RTObase.

Organisation reports

Keep going