AttribIQ connects visits, UTMs, signups, and payment events so your revenue reports show the pages and campaigns that led to paying customers.
Keep the visit, signup, checkout, payment event, and revenue report connected without turning analytics into a data warehouse project.
Campaign revenue
Revenue attachedEach handoff stays visible as source data moves through signup, checkout, webhooks, and reports.
Normalized revenue
Rank channels by revenue, paid conversion rate, and unattributed revenue.
Most analytics tools stop at visits, signups, or trials. AttribIQ keeps the path connected until payment, then shows which channel, page, and campaign produced the revenue.
Track where visitor and session identifiers are present, missing, or dropped before revenue reaches a report.
Use Stripe webhooks when payments happen there, or post normalized revenue events from your own billing system.
POST /v1/revenue
{
"provider": "custom",
"transaction_id": "txn_319",
"event_type": "purchase",
"amount": 31900,
"currency": "EUR",
"visitor_id": "v_abc",
"session_id": "s_def"
}
Short guides for the parts teams usually get wrong: tracking visits, passing attribution into checkout, and reconciling payment events.
Add the tracker and start collecting source, session, and landing page context.
Read guide 2Attach visitor and session IDs to Stripe Checkout or your own billing flow.
Read guide 3Group Stripe revenue by campaign, source, page, and attribution model.
Read guideConnect traffic to payments and see which sources create customers.