FAQ

Answers to common questions about first deploy checks, deploy reports, releases, impact analysis, reports, and agent workflows.

Why is my dashboard empty?

Check the basics first:

The tracking snippet is installed on the real page.
The current hostname is listed in the site's allowed domains.
You loaded a real tracked page after the snippet went live.
If this site respects DNT or GPC, the browser is not advertising those signals.
You are not expecting localhost traffic to appear automatically.

What is the fastest way to prove Callra's value?

Use one site and complete this loop in order:

Create the site.
Install the shared script.
Verify one real pageview.
Wait for one speed datapoint.
Create one manual release or connect a deployment provider.
Read the first deploy impact report.

That first cycle is enough to show how Callra turns a ship into a readable post-deploy review.

What is the first deploy check?

The first deploy check is the smallest useful Callra loop:

one real pageview
one speed sample
one release
one understandable verdict about the latest ship

You do not need GitHub, conversion events, or revenue signals on minute one.

How do releases fit into onboarding?

Open Releases from the site dashboard after the first pageview and speed sample land. You can create one manual release immediately, then replace it with automated provider webhooks later.

What is Impact Analysis for?

Impact Analysis is the cross-surface view for release context, traffic, conversion, speed, revenue, and incidents.

Use Releases first when the question is "did the latest ship regress?" Use Impact Analysis when the question becomes "what changed around this report, and what else happened around the same time?"

What are Reports, Worry Inbox, and incidents?

They are the proactive follow-up surface for the same site:

Daily reports summarize a recent window on a schedule.
Worry Inbox is the higher-signal digest for teams watching regressions or unresolved risk.
Incidents are anomaly records that can be acknowledged, ignored, or resolved.

Does Callra support single-page apps?

Yes. The installed script tracks SPA navigation through the browser History API by default.

For Next.js, React Router, Remix, and Nuxt apps, the recommended path is to use the framework adapters:

@callra/analytics-next
@callra/analytics-react-router
@callra/analytics-remix
@callra/analytics-nuxt

If you stay on the raw script snippet, send route templates yourself with window.va('route', { route: '/docs/[slug]' }).

Can I track custom product events?

Yes. Use:

window.va('event', 'Signup', { plan: 'pro' });

Then use the event breakdowns and event-property drill-downs in the dashboard.

Can I separate staging and production traffic?

Yes. Send an environment label such as staging or production and then filter by environment in the dashboard.

See Tracker API.

What does the public dashboard show?

Public share links expose aggregate-only analytics such as pageviews, visitors, sessions, trend charts, and common breakdowns.

They do not expose private dashboard controls, settings, or the recent-events view.

Does the same script handle Speed Insights?

Yes. The installed analytics script also sends page-load performance data used by the Speed Insights tab.

Can I investigate from CLI or MCP instead of the dashboard?

Yes. Callra supports site-scoped agent tokens plus CLI and MCP workflows for repeatable release and impact investigation.

The recommended starting point is the release workflow in Agent, CLI, and MCP workflows.

Why would a technical team upgrade?

Growth and Business package the strongest day-two workflows:

proactive deploy warnings
deeper release investigation and baseline evidence
reports, Worry Inbox, and incident review loops
agent-native CLI and remote MCP access for repeatable investigation