AttribIQ browser attribution API

The browser attribution API exposes the visit context that should travel into checkout.

Use it when a visitor clicks upgrade, starts checkout, creates a paid account, or begins any flow that can produce revenue.

Read the object

const attribution = window.attribiq.getAttribution()

Expected shape:

{
  "project_id": "proj_123",
  "visitor_id": "v_abc",
  "session_id": "s_def",
  "landing_page": "/pricing",
  "referrer": "https://google.com",
  "utm_source": "google",
  "utm_campaign": "brand-search"
}

Required fields

The minimum useful fields are:

• project_id
• visitor_id
• session_id

Landing page, referrer, and UTM values are useful for debugging, but the stable identifiers are what let AttribIQ join payment events to analytics sessions.

Send attribution to your backend

await fetch("/api/create-checkout-session", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({
    price_id: "price_123",
    attribution
  })
})

Your backend should validate the shape, ignore unknown fields, and decide which values to put into Stripe metadata or your own pending checkout record.

Security boundaries

Do not use browser attribution to decide:

• Payment amount.
• Plan entitlement.
• Billing currency.
• User account ownership.
• Discount eligibility.

The browser attribution object is for reporting. Billing decisions belong on the server.

Next steps

Use pass attribution to Stripe Checkout for a full Stripe flow, or Payment API reference for custom billing.