Integration guide

Step 1

Create a website

Create an account and sign in to the user dashboard. Select “Add website,” then enter the website name, primary domain, and reporting time zone. Tuleer will generate a unique 32-character site ID.

Registering Tuleer Account

Step 2

Install the tracking code

Copy the tracking code from Website settings and place it inside the <head> element on every page.

<script defer src="https://tuleer.com/t.js" data-site="YOUR_SITE_ID"></script>

If your site uses a shared layout template, install the snippet only once.

Step 3

Verify the integration

Visit a page where the script is installed, then open Realtime in the user dashboard. Live visitors and active pages should appear within 15 seconds.

Custom events

Use custom events for key actions such as sign-ups, purchases, and enquiry submissions. Event names must start with a letter and may contain letters, numbers, periods, underscores, colons, and hyphens.

window.tuleer.track('signup_completed', {
    plan: 'pro',
    source: 'pricing_page'
});

Then create an event with the same name under Goals in the user dashboard to manage it as a conversion goal.

Single-page applications

t.js listens to the History API methods pushStateI don't know.replaceState as well as browser back and forward events. Route changes are recorded automatically without repeated initialization.

Collection and privacy

Does not read form content, passwords, or application storage.
Visitor IDs and session IDs are anonymous random identifiers.
Respects the browser’s Do Not Track setting.
Request origins must match the configured primary domain or an allowed origin.
Event properties are limited to 16 KB and the full request to 64 KB.

Troubleshooting

No data on the realtime page

Confirm that the site ID is complete and that the website status is set to “Tracking.”

The request returns 403

Check that the current domain matches the website’s primary domain. Add subdomains under Additional allowed origins.

Local testing is not working

Add the local development address to Additional allowed origins and make sure Do Not Track is disabled in the browser.

A custom event is rejected

Check the event-name format, confirm the properties are valid JSON, and verify that the payload is within the size limit.