Callra
Getting started

Create your first site

Add a site, configure allowed domains, install the shared script, and get the first deploy check running.

After Callra is running and your account exists, the next goal is simple: create one site and reach the first deploy check.

1. Open the dashboard

Sign in and go to the dashboard home page.

If this is a brand-new instance, you should see the new-site form immediately.

2. Create a site

Fill in these fields:

  • Site name: a clear label such as Marketing Site, Docs, or App
  • Domains: comma-separated hostnames such as www.example.com, app.example.com
  • Timezone: the timezone you want reports to use

Only the listed hostnames are allowed to send analytics for that site.

3. Copy the tracking snippet

After the site is created, open:

Dashboard -> Your site -> Tracking script

Callra gives every site the same cache-friendly script file, with the site selected by its data-site-id value.

4. Install the snippet on a real page

Paste the snippet into the shared layout or HTML shell of the site you want to measure.

For the first test, use a real page on one of the allowed domains.

5. Verify the first pageview

Open a page on the tracked site after the snippet is live.

That real page load proves the site is sending live traffic into Callra.

6. Wait for the first speed sample

Open Speed Insights and give the browser one real page-load cycle to flush Core Web Vitals.

A first speed sample proves the same install path is already feeding the performance inputs used in deploy review.

7. Open Releases and read the first deploy report

After the first pageview and speed sample appear, open:

Dashboard -> Your site -> Releases

Create one manual release or connect a deployment provider so Callra can turn the next ship into a deploy impact report.

Then open the release detail page and read the first Deploy Impact Report end to end.

8. Upgrade from Level 1 to Level 2 later

Level 1 is the fast path:

  • site
  • script
  • pageview
  • speed
  • release
  • first deploy report

Level 2 adds stronger evidence to the same report:

  • connect GitHub for suspect commits
  • define key conversion events
  • connect a revenue source when you want revenue signals
  1. Releases
  2. Impact Analysis
  3. Reports and incidents