AttribIQ
Start free

Understand your traffic. See what drives revenue.

Track visitors, pages, sources, campaigns, goals and funnels in a clear EU-hosted dashboard. Connect Stripe or your payment system when you are ready to tie those journeys to revenue.

Start free trial View live analytics demo
Traffic, goals & funnelsEU-hostedOptional Stripe integration
Sample workspaceOverview
Animated sample

Visitors

7,219

Unique in this period

Page views

18,336

Across all tracked pages

Sessions

9,024

1m 26s average session

Revenue

€1,469

Optional payment data

Visitors over time

Rolling 7 days · All traffic

Sample visitor trendIllustrative visitors over a rolling seven-day window, from Aug 22 to Aug 28. The dashed slate line shows Google Ads, olive shows Search, and dotted sand shows Facebook traffic.51Aug 22Aug 23Aug 24Aug 25Aug 26Aug 27Aug 28Aug 29
All visitors51
Google Ads23
Search8
Facebook12
Sample visitors by date
DateAll visitorsGoogle AdsSearchFacebook
Aug 2290382613
Aug 239836407
Aug 2491204510
Aug 2587123822
Aug 2684192428
Aug 2771261222
Aug 285123812

AI search

328

Visits from AI referrals

Sample AI referral visits328 sample visits over the last 14 days, split into ChatGPT in olive, Google AI in slate, and Claude in sand. Each bar shows one day with a changing mix of referrals.Day 1: ChatGPT 6, Google AI 6, Claude 3 visitsDay 2: ChatGPT 10, Google AI 7, Claude 2 visitsDay 3: ChatGPT 12, Google AI 6, Claude 4 visitsDay 4: ChatGPT 9, Google AI 5, Claude 9 visitsDay 5: ChatGPT 6, Google AI 5, Claude 12 visitsDay 6: ChatGPT 7, Google AI 6, Claude 10 visitsDay 7: ChatGPT 9, Google AI 7, Claude 5 visitsDay 8: ChatGPT 11, Google AI 8, Claude 1 visitsDay 9: ChatGPT 10, Google AI 8, Claude 3 visitsDay 10: ChatGPT 7, Google AI 7, Claude 7 visitsDay 11: ChatGPT 6, Google AI 5, Claude 11 visitsDay 12: ChatGPT 9, Google AI 5, Claude 12 visitsDay 13: ChatGPT 15, Google AI 7, Claude 9 visitsDay 14: ChatGPT 21, Google AI 12, Claude 6 visits
14 days agoToday
ChatGPTGoogle AIClaude

What changed

Search brought the most visitors this period.

2,454 visits came from search. With payments connected, it also accounted for 17 customers and €493 after refunds.

See the details
A sample AttribIQ dashboard showing visitors, pageviews, sessions, optional revenue, a rolling seven-day traffic trend, and visits from AI search referrals.

Web analytics

The website analytics you check every day

Start with the traffic and conversion reports you need even when no payment system is connected.

Revenue attribution

Start with traffic. Add revenue when it matters.

The same analytics setup can stop at goals and funnels or continue through checkout to purchases, subscriptions and refunds.

1

Measure the visit

Keep the source, campaign, page, device and session context needed for everyday website reporting.

2

Track the action

Use a path or custom-event goal, then build a funnel to understand conversion and drop-off.

3

Connect the outcome

Add Stripe or the Payment API when you want to compare channels and journeys by realized revenue.

See when AI referrals turn into revenue

When a referrer hostname or campaign tag identifies an AI service, AttribIQ keeps that evidence with the journey through checkout. If the signal is missing, the visit stays unattributed.

How AI referral tracking works

Understand the value of AI traffic

Connect identifiable referrals to customer journeys and payments.

01

Find your AI referrals

See which AI services send visitors to your site when a referral link or campaign tag identifies the source.

02

Connect visits to revenue

Follow those visitors through checkout and see the payments linked to their journeys.

03

Know where the gaps are

Missing sources stay unattributed, so you can see what is known and what is not. Mentions and citations alone do not count as visits or revenue.

See what matched and what didn’t

Match rate, missing identifiers, duplicate events, and refunds are part of the product, not details hidden in an implementation log.

90%

Journey match rate

Payments connected to a known visitor journey in the sample workspace.

3

Missing journey identifiers

Payments that need a checkout or server-side metadata fix before attribution is reliable.

1

Duplicate payment event

A repeated event caught before it could inflate conversion and revenue totals.

Net

Refund-aware reporting

Gross revenue and refunds remain visible, with net revenue used for decision-making.

From setup to useful answers

Install once, verify the traffic, then add conversion and payment context at your own pace.

  1. 1

    Install the tracker

    Collect source, campaign, landing page, and session context.

  2. 2

    Review your traffic

    Check visitors, pages, sources, campaigns, devices and realtime activity.

  3. 3

    Define conversions

    Create path or event goals and assemble the journeys that matter into funnels.

  4. 4

    Connect payments

    Optionally use Stripe webhooks or the Payment API to add revenue to the same reports.

Analytics guides

Browse all guides
Featured guide

Understand the overview dashboard

Read visitors, pageviews, sessions, acquisition, content, audience, and optional revenue in one place.

Read guide
Featured guide

Create goals and funnels

Turn important paths and custom events into conversion goals, then measure where visitors leave.

Read guide
Featured guide

Connect Stripe revenue

Carry visitor and session IDs into checkout when you are ready to add payment outcomes.

Read guide

EU-hosted analytics

Keep the collection model explicit

AttribIQ is hosted in the EU and uses tab-scoped session storage in its cookieless default. Optional first-party persistence can improve delayed attribution, so the product documents that tradeoff instead of hiding it behind a privacy slogan.

Review data collection

Explore the analytics dashboard

Review traffic, acquisition, content, goals, funnels and optional revenue reporting with sample data.

Start free trialView live analytics demo