Aurora documentation
Everything you need to install the tracker, describe what a good-fit visitor looks like, and get qualified leads in front of the right person — plus the full API and webhook reference for building your own workflows.
On this page
Start here#
New to Aurora? These four guides take a new workspace from zero to a working queue of qualified leads. Most teams finish all three in under an hour.
How Aurora works#
Aurora is a behavioral lead-scoring platform. A lightweight script on your website records what each visitor does, a rules engine turns that behavior into a score from 0 to 100, and routing rules deliver the visitors who cross your threshold to the people and tools that should act on them. The whole loop runs in real time: a score is recalculated in under 400 ms after every tracked event.
- CollectThe tracking snippet records page views, sessions and any custom events you send. Anonymous visitors are recognized across sessions with a single first-party cookie, and become known contacts when they sign up, log in or submit a form you've connected.
- ScoreEach scoring rule assigns points to a signal — visiting the pricing page, returning within a week, reading the API docs. Recency multipliers boost fresh interest and decay stale interest, so the score reflects intent right now, not six months ago.
- RouteWhen a visitor crosses the qualification threshold, routing rules decide who gets the lead and where the alert appears: Slack, Microsoft Teams, email, the shared inbox, your CRM or any webhook endpoint.
Key concepts#
These terms are used consistently across the dashboard, the documentation and the API. Knowing them makes every other guide faster to read.
| Term | What it means |
|---|---|
| Workspace | The top-level container for one website or product. Tracking keys, rules, team members and billing all belong to a workspace. |
| Visitor | A single person recognized by the tracker. Starts anonymous; becomes identified once Aurora links them to an email address. |
| Session | A continuous period of activity. A new session starts after 30 minutes of inactivity or at midnight in the workspace time zone. |
| Signal | Any behavior Aurora can score: a page view, a repeat visit, a custom event, an email open or a CRM field value. |
| Scoring rule | A signal plus a weight (for example, Pricing page viewed = +24). Rules can be positive or negative. |
| Score | The sum of all matching rules after recency adjustments, capped between 0 and 100. |
| Threshold | The score at which a visitor becomes qualified. The default is 60; each workspace can set its own. |
| Routing rule | A condition and an assignment: which qualified leads go to which person, team or destination. |
| Destination | Where an alert is delivered — Slack, Teams, email, the shared inbox, a CRM or a webhook. |
Browse by topic#
Core concepts#
Understand how visitors are recognized, how scores are calculated and how routing decides who is notified. Read Visitors & identity first if you plan to connect signup or login events.
Integrations#
Aurora pushes qualified leads into the tools your team already uses. CRM sync covers Salesforce and HubSpot two-way sync and field mapping; Webhooks covers event types, payloads, signature verification and retries. The full list of native integrations is on the Integrations page.
Administration#
Workspace owners and admins should read SSO & team access for SAML, SCIM and roles, and Data & privacy for consent handling, data residency, retention and deletion requests.
Developers#
The JavaScript API documents every browser method — identify, track, page and consent. The REST API reference covers authentication, pagination, errors, rate limits and every endpoint.
Plans and limits#
Every plan includes unlimited tracked visitors, the full REST API and SAML single sign-on. The differences are in team features, history and compliance tooling.
| Capability | Starter | Team | Scale |
|---|---|---|---|
| Seats | 1 | Unlimited, per seat | Unlimited, per seat |
| Tracked visitors | Unlimited | Unlimited | Unlimited |
| Visitor history | 30 days | Unlimited | Unlimited |
| Scoring rules | Up to 10 | Unlimited | Unlimited |
| Routing rules & shared inbox | — | Included | Included |
| CRM two-way sync | — | Included | Included |
| Webhooks & REST API | Included | Included | Included |
| SAML SSO | Included | Included | Included |
| SCIM provisioning & audit logs | — | — | Included |
| Uptime SLA | — | — | 99.9% |
Prices and plan details are on the pricing page.
Getting help#
If a guide doesn't answer your question, search the docs with Ctrl K (or ⌘ K on a Mac), check Troubleshooting, or ask in the community. For anything specific to your account, contact support — tickets are answered by the engineers who build the product, with a median first response under two hours.