AttribIQ
Start free

CLI Reporting Reference

By AttribIQUpdated Intermediate

Run AttribIQ overview, revenue, campaign, goal, and funnel reports from scripts, release checks, and internal tools.

Quick answer

The CLI is for revenue questions in scripts, agents, and release workflows. Start with overview, revenue by campaign, and signup-to-paid funnel inspection.

On this page
What you’ll learn
  • Run revenue reports from the command line
  • Group revenue by campaign, source, or landing page
  • Inspect funnels in JSON
  • Use CLI output in automation

The AttribIQ CLI is for teams that want revenue reports outside the dashboard.

It is useful in release checks, weekly reporting scripts, internal agents, and operational workflows where JSON output is easier to consume than a browser dashboard.

Overview report

sh
attribiq overview --project proj_123 --from 90d --json

The overview report should return visitors, pageviews, events, goals, conversions, revenue, and paid conversion rate for the selected date range.

Revenue by campaign

sh
attribiq revenue --project proj_123 --from 30d --group-by campaign --json

Useful groupings include:

  • source
  • campaign
  • landing_page
  • referrer
  • country
  • device
  • goal

Use campaign reports when deciding which launch, newsletter, ad, or partner effort deserves more work.

Funnel inspection

sh
attribiq funnels inspect signup-to-paid --project proj_123 --json

Funnel output should include step counts, conversion rates, drop-offs, and attributed revenue when payment events are connected.

Automation pattern

Use CLI reports for questions like:

  • Did revenue by campaign drop after a release?
  • Which landing page created the most MRR this week?
  • Did a launch email create paid conversion?
  • Which funnel step lost the most revenue?

The CLI should not replace the dashboard. It should make the same revenue model available to scripts.

Next steps

Install the tracker with Install AttribIQ, then connect payments through Stripe revenue attribution or the Payment API reference.

Frequently asked questions

Is the CLI required?
No. The dashboard is the primary interface. The CLI is useful for developers who want reports in scripts and automation.
Should CLI output be JSON?
Use JSON for automation and table output for humans. The examples here prefer JSON because it is easier to pipe into tools.
What project identifier should I use?
Use the project public ID from AttribIQ project settings.
Can the CLI query funnels?
Yes. Funnel inspection should return conversion rates, step counts, and attributed revenue when configured.

Continue learning

API Reference

Web Tracker Reference

Install the AttribIQ tracker and record sessions, pageviews, referrers, UTMs, goals, events, and checkout context.

Read guide API Reference

Browser Attribution API Reference

Read visitor, session, landing-page, referrer, and UTM context in the browser before signup or checkout begins.

Read guide API Reference

Revenue Payment API Reference

Send custom purchases, renewals, refunds, and subscription events with idempotency and optional journey identifiers.

Read guide

Put it into practice

See traffic and revenue in the same dashboard

Explore traffic sources, campaigns, goals and matched payments in the demo, then connect your own site.

Explore the live demo Install the tracker