Website Settings

Website setup and marketing tools sit under Marketing in the sidebar:

• Content: Homepage, Pages, Articles and Enquiries. Legal pages such as Terms & Conditions are ordinary pages. See Legal Pages.
• Marketing: Performance shows site visits, marketing outcomes by campaign and optional third-party analytics integrations. Affiliate Marketing holds affiliate programs, tracked links, commissions and payout records.
• Setup: Website Mode, Course Enrolment (called Website Embeds in Embed mode) for catalogue links, embed code and date and availability display, Branding for logo, favicon, colours, fonts and corner radius, SEO for search engine metadata and Open Graph settings, Navigation for the navbar, header links and footer, and Redirects.

Custom website and email domains are under Settings → Domains. See Organisation Settings.

Access required

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

Branding settings

Go to Marketing → Branding in the sidebar.

Generate branding with AI

If you'd rather not build a palette by hand, click Generate branding with AI to have RTObase create a complete visual identity from your organisation name.

Design preset

A design preset layers a coordinated "feel", shape, shadow, and heading style, on top of your brand colours and fonts (it doesn't change your colours or font families). Choose one from the Preset control:

Logo and favicon

Quick-start colour palettes

Choose from 8 preset palettes (Ocean, Forest, Sunset, Royal, Slate, Rose, Teal, Midnight) to set up your primary and accent colours instantly. You can fine-tune individual colours afterwards.

Brand colours

Button colours

Navigation and footer colours

Shape and borders

Typography

Live preview

The branding page includes a two-tab preview:

• Website: Shows how your public site looks with current settings
• Embed: Shows how the embedded course catalog renders with your brand colours

Navbar style and header links

Go to Marketing → Navigation in the sidebar to configure the website header.

Choosing a navbar variant

Select one of four navbar styles:

Editing header links

Add, remove, and reorder links in the navigation editor:

• Use the arrow buttons to reorder links
• Add child links to create dropdown menus
• For the Mega Menu variant, each child link can have an emoji icon and a short description

Footer style and footer links

Go to Marketing → Navigation → Footer to configure the website footer.

Choosing a footer variant

Select one of four footer styles:

Editing footer links

Footer links are organised into columns (groups):

• Each column has a group label and a list of links beneath it
• Add or remove columns as needed
• Add, remove, or reorder links within each column

Website Mode

Marketing → Website Mode records how you use your website, and RTObase takes care of what is public, what search engines see, and where your web address points. Choose one of three modes:

• RTObase website: your public website is hosted by RTObase, with pages, articles and courses served on your RTObase address or verified custom domain. Search engines can index the site only through a verified custom domain; your *.rtobase.com.au address remains available but is always excluded from search results.
• Embed on my own website: you keep your existing website and embed RTObase enrolment and course content into it; see Embed Code.
• No public website: only the signed-in portals are used; nothing is exposed publicly or indexed.

SEO settings

Go to Marketing → SEO to configure search engine optimisation for your public site.

SEO settings control how pages appear after you connect a verified custom domain. RTObase-hosted *.rtobase.com.au addresses are always excluded from search results.

Individual pages and articles can override these defaults with their own SEO settings via the SEO tab on each page/article editor.

Website analytics

Go to Marketing → Performance. The Overview tab counts visitors, visits and page views for your hosted website. The Campaign results tab reports which tagged campaigns are connected to enquiries, enrolments and successful payments recorded in RTObase, grouped by campaign, source and medium. Choose First touch or Latest touch credit, a 30 or 90 day period, and an optional course. Marked test campaigns are hidden unless you switch Include test campaigns on. Payment value is net of recorded refunds and counts AUD payments only. No external analytics or advertising provider is needed for this report or for visit counts; use a provider when you also want advertising audiences or ad costs.

Analytics integrations

Open the Tracking setup tab to connect optional third-party analytics providers to your public website.

Supported providers

Adding an integration

1. Click Add integration
2. Select the provider
3. Follow the provider-specific checklist and enter the required ID, key, or destination
4. Keep Regional privacy defaults, or choose Always require visitor opt-in if your own policy requires it everywhere
5. Click Add

You can add multiple integrations and toggle each one on/off independently.

Regional defaults show no analytics prompt to Australian visitors. Visitors in the EEA, UK and Switzerland must opt in first, and unknown locations take the same conservative path. An integration set to Always require visitor opt-in stays off until the visitor saves their analytics choices, regardless of region.

Tenant tags never load on portal, sign-in, identity, LLND, payment, credential, or enrolment form routes. If a visitor navigates there after a tagged public page, RTObase reloads the document once so previously executed tenant code is gone. Completion pages can send an authoritative outcome only after one-time credentials have been removed. The website and enrolment flow continue to work when all optional tags are off.

Custom scripts run as tenant-controlled code and can inspect the page. They are not constrained by RTObase's built-in event sanitiser, so review the script and make sure your privacy notice covers its behaviour before enabling it.

A custom script can consume canonical funnel events from the page dataLayer or listen for the rtobase:analytics-event browser event. Its detail contains event, properties, and event schema version.

Tagged links and attribution

Any link carrying 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. RTObase keeps the short-lived browser attribution session for up to 90 days. When an enquiry, enrolment or payment is completed, its first-touch and last-touch campaign details are copied to that operational record and retained with it. Contact details and form answers are not added to attribution.

On hosted sites, provider tags stay off the enrolment, payment and LLND forms, so providers see the public acquisition point and authoritative completion outcomes. For a course that requires LLND, the safe confirmation page reports Enrolment awaiting LLND screening before the private check and Enrolment completed after it. Courses without that requirement report Enrolment completed directly. A verified embed bridge can additionally forward Enrolment started, Payment page viewed, Payment started, and LLND screening completed to the parent site's analytics without loading tenant tags inside the form iframe.

For Google Ads, use a separate integration for each successful milestone you want to optimise. For example, optimise an enquiry campaign for Website enquiry submitted, a paid-enrolment campaign for Payment completed, and a free course for Enrolment completed.

Affiliate marketing

Use Marketing → Affiliate Marketing when another business or promoter earns commission for referred enrolments:

1. Create a program with a percentage or fixed commission and an attribution window. A percentage applies to each successful payment; a fixed amount is earned once per enrolment, even when the learner pays in instalments.
2. Paste the exact hosted page, course page or verified embed page you want to promote, then add each affiliate and copy their unique tracked link. RTObase uses a stable code in the link, not their contact details.
3. Share the link. RTObase connects its first-party visits, enquiries, enrolments and successful live payments to that affiliate.
4. Review commission before approval. Refunds and reversals adjust the visible ledger automatically.
5. After paying the affiliate through your bank or accounting system, record the payout in RTObase for reconciliation. Recording a payout does not initiate a transfer.

General marketing affiliates are separate from regulated CRICOS education agents, which remain under International → Education agents.

Tracked events

RTObase automatically tracks these conversion events for connected analytics:

• rtobase_course_viewed: visitor views a course page
• rtobase_location_viewed: visitor views a training location
• rtobase_enquiry_submitted: a website enquiry is successfully saved
• rtobase_interest_registered: a course or location enquiry is successfully saved
• rtobase_enrolment_started: an enrolment journey begins
• rtobase_payment_page_viewed: the verified enrolment reaches the payment step
• rtobase_payment_started: a real payment gateway session opens
• rtobase_payment_completed: a payment is verified as paid
• rtobase_enrolment_pending_lln: the enrolment is waiting for LLND screening
• rtobase_lln_screening_completed: the screening response is successfully submitted (verified embed bridge only)
• rtobase_enrolment_completed: the enrolment is finalised

Pageviews are tracked automatically on every route change.

When Google Analytics 4 is connected to a hosted RTObase website, eligible course views, saved enquiries and verified payments arrive as GA4 recommended events (view_item, generate_lead, purchase) with the canonical RTObase name carried in the rtobase_event parameter. Ecommerce events include GA4 item data, and verified purchases include value, currency and a stable transaction identifier. This makes the events usable in GA4 ecommerce reporting and Google Ads imports without inventing custom event names; provider-side linking, key-event selection and report configuration are still completed in Google. A saved contextual enquiry produces one GA4 generate_lead; its additional course-interest signal remains a separate canonical event rather than counting a second lead. For the same eligible hosted outcomes, Meta receives ViewContent, Lead and Purchase. Refreshing a success page does not create a new RTObase conversion. The private in-flow events listed above remain available through the verified embed bridge as canonical RTObase events for mapping in the parent website's analytics setup.

Check an integration

After saving at least one integration, click Check setup. The check validates required fields and provider ID formats, then shows whether enquiry, enrolment, and payment events are routed to that provider. It does not load a vendor SDK, execute a custom script, push to the dataLayer, contact the provider or send a live event. A Validated result therefore proves local RTObase configuration and routing only. After publishing, confirm collection in the provider's own DebugView, Tag Assistant, Test Events, or Live Events screen.

Analytics from an embedded enrolment flow

Third-party tenant tags stay out of embedded RTObase iframes. In Embed website mode, go to Marketing → Performance → Tracking setup and copy the optional origin-checked analytics listener into the parent website. It forwards the same canonical RTObase course, enquiry, enrolment, and payment events into the parent page's dataLayer. GTM, or an equivalent listener configured for GA4, Meta, PostHog, or another provider, can map them. The embed script also carries UTM and supported ad click IDs from the parent page into RTObase's first/last-touch record. The listener does not generate events for unrelated parent-site interactions; instrument those in the parent analytics setup.

Where branding appears

Your branding settings are used on:

• Public website: Header, footer, and throughout
• Embedded course catalog: The embed widget on your own website
• Student portal: Login page and dashboard
• Employer portal: Login page and dashboard
• Emails: Enrolment confirmations, payment receipts
• Documents: Statements of Attainment (if enabled)

Your branding applies to the student and employer portals even if you never build a public website. To take it a step further, verify a custom domain (e.g. learn.yourrto.com.au) so those portals are served on your own web address, see Organisation Settings.

Related

• Homepage Builder: Design your main homepage
• Organisation Settings: Edit organisation details

Keep going