Website Analytics
Understand traffic, behaviour, and known-customer activity across your websites
Website Analytics shows traffic, engagement, and conversions on connected customer websites, booking pages, portals, and content sites.
Website events are collected through the DOM Package and Tiquo-managed content sites. Events flow into Analytics automatically once the site is connected and receiving traffic.
Where website analytics appears
Open Analytics → Website Analytics. In the demo organisation, this tab shows No websites yet and Website analytics will appear here once connected. A populated site report is needed to inspect the metrics described below.
Each connected site is tracked separately by hostname. www.example.com is normalised to example.com, while other subdomains remain separate. This makes it easier to compare a main website, a booking site, a member portal, and campaign-specific subdomains without mixing their traffic together.
What it tracks
Website Analytics records first-party events such as:
- Pageviews and navigation
- Visit sessions
- Referrers and landing pages
- UTM source, medium, campaign, content, and term
- Browser, device type, operating system, language, and viewport
- Engagement events when a visitor leaves a page or becomes inactive
- Known-customer activity after a customer signs in through the DOM Package
- Custom events sent from your website
Anonymous traffic is measured for site performance. Known-customer events are linked to customer profiles only when a customer has authenticated or has been identified through a supported customer flow.
Bot filtering
Tiquo filters common bot and crawler traffic before it appears in Website Analytics.
This keeps reports focused on real visitor behaviour rather than search crawlers, uptime checks, link unfurlers, and automated tools. Filtering is applied automatically and does not require any setup from staff.
Site cards
Connected websites appear as site cards in the dashboard. A site card gives staff a quick view of whether the site is active and when traffic was last received.
Use site cards to confirm that a website has been connected correctly, then open the site analytics view to review traffic, engagement, and customer behaviour in more detail.
Connecting a website
For third-party websites, install the DOM Package or standalone analytics client with your organisation's public key.
import { TiquoAnalytics } from '@tiquo/dom-package';
const analytics = new TiquoAnalytics({
publicKey: 'pk_dom_your_key_here',
});Automatic pageviews are enabled by default. For single-page apps, Tiquo also tracks client-side navigation through history.pushState, history.replaceState, and browser back/forward navigation.
To send a custom event:
await analytics.track('newsletter_signup', {
eventName: 'Newsletter Signup',
eventProperties: {
source: 'footer',
},
});For the full SDK setup, see DOM Package setup.