# Install AttribIQ

> Install the AttribIQ tracker, verify visitors and pageviews, and start measuring traffic, content and conversions. Add Stripe attribution when needed.

Canonical page: [https://attribiq.com/guides/install-attribiq](https://attribiq.com/guides/install-attribiq)

Category: Implementation Guides

Last updated: 2026-10-02

Topics: install, tracker, stripe, payment api, cli

## Summary

Add your project’s tracker and verify pageviews in Realtime. You can use traffic, acquisition, content, audience, goals and funnels without connecting a payment provider. Stripe or the Payment API adds revenue to those reports when you need it.

## What this guide covers

- Install and verify the web tracker
- Read visitors, sources and pages
- Define a conversion goal and funnel
- Add payment attribution when needed

Start by collecting web analytics. Add a payment integration when you want to connect visits to revenue.

The tracker records visits, sessions, sources, referrers, UTM campaigns, pages, and goals. The payment integration connects those sessions to purchases, subscriptions, renewals, refunds, and churn.

## Add the web tracker

Place the tracker on pages where visitors arrive, evaluate the product, sign up, or start checkout.

```html
<script async src="https://edge.attribiq.com/i/a7K4mN2qR8tP.js"></script>
```

Use the project-specific script URL from your AttribIQ project settings. The install key in the URL maps browser events to your project.

If you want the browser to load the tracker from your own domain, use a [first-party tracker proxy](https://attribiq.com/guides/first-party-tracker-proxy) and proxy both the script path and the event endpoint.

## Content Security Policy

If your site uses Content-Security-Policy, merge the AttribIQ edge origin into the page's existing directives.

```http
script-src 'self' https://edge.attribiq.com;
connect-src 'self' https://edge.attribiq.com;
```

The direct tracker loads JavaScript from `https://edge.attribiq.com` and sends events back to `https://edge.attribiq.com`. It does not require `unsafe-inline`, `unsafe-eval`, or an AttribIQ `img-src` origin.

AttribIQ cannot override a customer's CSP from the edge domain. The browser evaluates the page owner's policy before fetching the tracker script.

For nonce-based policies, add the page's nonce to the external script tag and keep the same nonce in the CSP header:

```html
<script nonce="RANDOM_NONCE" async src="https://edge.attribiq.com/i/a7K4mN2qR8tP.js"></script>
```

With a first-party proxy, the browser-facing CSP usually only needs your own origin for the tracker paths, because the server-side proxy forwards requests to AttribIQ.

## Verify your first pageview

Open a page with the tracker installed and then open **Realtime** in the same AttribIQ project. Confirm the page path appears. Navigate to another tracked page and check the next event.

If nothing arrives, check that the project script loaded, your Content Security Policy allows its requests and the page is using the correct project snippet. Avoid adding the tracker twice through both a site template and a tag manager.

## Start using web analytics

You now have a useful website analytics setup without payment events:

| Question | Report | Guide |
| --- | --- | --- |
| How much activity does the site receive? | Overview | [Visitors, pageviews and sessions](https://attribiq.com/guides/visitors-pageviews-sessions) |
| Where do visitors come from? | Acquisition and Campaigns | [Sources and referrers](https://attribiq.com/guides/traffic-sources-referrers) |
| Which content do they visit? | Pages | [Content and landing pages](https://attribiq.com/guides/content-and-landing-pages) |
| Which audiences reach the site? | Countries and devices | [Audience reports](https://attribiq.com/guides/country-and-device-reports) |
| Do visitors take the next step? | Goals and Funnels | [Create goals](https://attribiq.com/guides/create-goals) |

Allow collected events to reach the reports and keep the date range and reporting timezone aligned. Visitors are measured identifiers, not a count of known people. The default tracker keeps those identifiers within a browser tab; see [tracker behavior](https://attribiq.com/guides/web-tracker) when comparing tools.

## Define a conversion

Choose one action that matters to the site: a signup confirmation, a completed form or a request for a demo. A path goal works when the action has a dedicated destination page. Use a custom-event goal when the action happens within a page.

Then use a [funnel](https://attribiq.com/guides/build-and-read-funnels) to compare the measured steps leading to that goal. Start with one journey you can test yourself before adding more.

## Add payment attribution when you need it

To measure revenue by source or campaign, carry the visitor and session IDs from the browser through your backend into the payment record. A successful payment must be matched to that earlier context; installing the tracker alone does not provide that link.

- **Stripe:** follow [Stripe revenue attribution](https://attribiq.com/guides/stripe-revenue-attribution), [pass attribution to Checkout](https://attribiq.com/guides/pass-attribution-to-stripe-checkout), then [connect the webhook receiver](https://attribiq.com/guides/connect-stripe-to-attribiq).
- **Other billing systems:** normalize payment events on your backend and use the [Payment API](https://attribiq.com/guides/generic-payment-api-revenue-tracking).

This is a separate setup step. Traffic, content, audience, goal and funnel reporting remain useful without it.

## Query reports from the CLI

Use the CLI when you want revenue reports in scripts, release checks, or automation.

```sh
attribiq revenue --project proj_123 --from 30d --group-by campaign --json
attribiq overview --project proj_123 --from 90d --json
attribiq funnels inspect signup-to-paid --project proj_123 --json
```

Read [CLI reports](https://attribiq.com/guides/cli-reports) for the first commands to support.

## Next steps

Read the [overview dashboard](https://attribiq.com/guides/overview-dashboard), review your [traffic sources](https://attribiq.com/guides/traffic-sources-referrers), and choose one [conversion goal](https://attribiq.com/guides/create-goals). Explore the [live demo](https://attribiq.com/demo-dashboard) to see the reports before connecting your own data.

## Frequently asked questions

### What is the fastest install path?

Add the project script, open a tracked page, confirm it appears in Realtime, then review Overview and Pages. Payment setup is optional.

### Do I need Stripe?

No. The web analytics reports, goals and funnels work without Stripe. For revenue reporting, connect Stripe or send normalized events through the Payment API.

### Should the tracker run on the marketing site or app?

Install it wherever attribution-relevant sessions happen: marketing pages, pricing pages, guides, signup pages, and app pages that can lead to checkout.

### Can I install the tracker without revenue events?

Yes. The tracker provides the analytics base layer. Revenue reports become useful once Stripe webhooks or Payment API events are connected.