Install traffic.cx & Verify Your First Visit

You need a traffic.cx account, a site you can edit, and access to publish its HTML. Start with the trial or a paid plan, then follow these steps before connecting payments.

1. Add your site

Open the traffic.cx dashboard, select your team and add the website you want to measure. Enter its real domain. Complete the setup flow, or open the site's Settings → Tracking to find its installation snippet.

Each site has its own public ID and script URL. Copy the snippet from the dashboard; the placeholder below will not collect visits for your account.

2. Install the script once

Place the script in the shared HTML <head> so it loads on every page:

<script defer src="https://traffic.cx/js/YOUR_SITE_ID.js"></script>

Replace YOUR_SITE_ID with the complete ID from your dashboard, including its tcx_ prefix. Keep the script hosted at traffic.cx so it receives your site's tracking settings. Do not add a second copy through a tag manager or component.

• Plain HTML: use your shared template, or add it to every HTML page if there is no shared template.
• React or Vue with Vite: put it in the root index.html, inside <head>.
• SvelteKit: put it in src/app.html, inside <head>, alongside the existing head placeholder. Keep the rest of that file intact. See SvelteKit's app template documentation.
• A CMS or website builder: use its shared head-code setting. Publish the change and clear any page cache.

Use a normal external script, not type="module". The tracker already follows history.pushState and browser back/forward navigation. Do not add another pageview call on each SPA route change. Query-string-only changes do not create a new pageview; hash routes need the hash-routing option in Tracking settings.

3. Verify your first visit

1. Publish the site and open its public URL in a normal browser tab. Visit a second page too.
2. In developer tools, open Network. Your site's /js/tcx_….js request should return JavaScript with status 200. An event request goes to https://traffic.cx/api/event.
3. In the site's Settings → Tracking, select Check installation. It checks the homepage for the snippet and reports whether an event has arrived.
4. Open the realtime dashboard. Confirm that your page appears and then check the usual traffic report. Allow a short delay for collection and report updates.

An accepted network request alone does not prove that a visit was recorded: filtered events can also receive an accepted response. Confirm the event in the dashboard. Do not use automated browser traffic as your first-visit check; the tracker intentionally ignores it.

4. Check a custom event

After the script has loaded, run this in your browser console or attach it to a real action:

window.trafficcx?.('signup_started', {
  props: { plan: 'starter' },
});

The custom event uses the current visit. To report it as a goal, create a matching custom-event goal named signup_started in the dashboard. Use non-personal property values; avoid names, email addresses and secrets in URLs or event properties. Pageviews and custom events count toward your event allowance.

Troubleshooting

For additional logging, turn on the site's temporary debug mode in Settings → Tracking and reload the page. Check the console for traffic.cx messages. Debug mode does not bypass the normal exclusions.

Next: connect your payments

Read how revenue attribution works, then follow the guide for Stripe, Dodo Payments, Lemon Squeezy or Polar. Connecting a provider imports payments; passing the visit's identifiers into checkout links those payments to your traffic.

Need another provider? Use the Payments API. If you only control the thank-you page, see purchases from the script.