Quickstart
Go from a new workspace to your first qualified lead in Slack. This guide takes about 15 minutes and needs access to your website's HTML (or Google Tag Manager) and a Slack workspace.
On this page
Before you begin#
You'll need three things. If you're missing one, you can still complete the steps you have access to and invite a teammate for the rest from Settings → Team.
- An Aurora workspace. Create one for free — the Starter plan is free forever for one seat and has no visitor cap.
- Access to your site's HTML, or publish rights in Google Tag Manager or Segment.
- Permission to add apps to Slack, if you want alerts there. Email alerts work without any setup.
Step 1: Install the tracking snippet#
Open Settings → Tracking in the dashboard and copy the snippet. It already contains your workspace's public key. Paste it once, right before the closing </body> tag, on every page you want to track — usually by adding it to your site's shared layout or template.
="t-c"><!-- Aurora tracking snippet — paste once, right before </body> -->
<script>
window.aurora = window.aurora || function () {
(window.aurora.q = window.aurora.q || []).push(arguments);
};
</script>
<script async src="https://cdn.aurora.io/v2/aurora.js"
data-workspace="pk_live_YOUR_WORKSPACE_KEY"></script>The snippet loads asynchronously, is about 8 KB gzipped and never blocks rendering. If you use Google Tag Manager or Segment instead, follow the matching section in Installation; the rest of this guide is the same.
The key in the snippet starts with pk_live_ and is safe to expose in the browser. Never put a secret API key (sk_live_) in client-side code.
Step 2: Verify that data is arriving#
Open your website in a new browser tab and click through two or three pages. Back in Aurora, go to Settings → Tracking: the status indicator turns green and the Live events panel lists your page views within a few seconds.
As soon as the first event arrives, Aurora starts a 30-day backfill for sources that support it (Segment and Google Tag Manager history, plus any CSV you import). With a direct install, history starts from the moment the snippet goes live.
No events after a minute? The most common causes are an ad blocker in your own browser, the snippet being added to a page template that isn't used, or a Content Security Policy that blocks cdn.aurora.io. See No data after installing.
Step 3: Write your first scoring rule#
Go to Scoring → Rules and choose New rule. A good first rule rewards the single strongest buying signal on most B2B sites: a visit to the pricing page.
- Choose a signalSelect Page viewed and enter
/pricingas the URL. Leave the match type as Path starts with so localized paths such as/pricing/annualalso count. - Set a weightEnter
24. Weights range from −50 to +50; strong buying signals typically sit between 15 and 30. - Add a repeat-visit bonusTurn on Boost repeat visits. A second pricing visit within 24 hours is multiplied by 1.5.
- Preview against historyThe preview panel shows how many visitors from the last 30 days would have matched. Use it to sanity-check the weight before saving.
Add two or three supporting rules the same way — for example Repeat session within 7 days = +18 and Docs page viewed = +11. Then open Scoring → Threshold and keep the default of 60 for now. You'll tune it after a week of real data; Choosing a threshold explains how.
Step 4: Connect Slack#
- Authorize the appGo to Integrations → Slack, choose Connect and approve the requested permissions. Aurora only asks to post messages and read the channel list.
- Pick a channelChoose where qualified leads should appear, for example
#qualified-leads. Private channels need/invite @Aurorafirst. - Send a test alertChoose Send test. A sample lead card appears in the channel with a score, the top signals and a link to the full session history.
Step 5: Route your first qualified lead#
On the Starter plan, every qualified lead goes to the workspace owner and the Slack channel you chose. On Team and Scale, go to Routing → Rules to split leads by territory, language or deal size — see Routing & alerts.
To see the whole loop working, visit your own pricing page twice from a private window and view two more pages. Your test visitor crosses the threshold and the alert arrives in Slack within a few seconds. Delete the test visitor afterwards from Visitors so it doesn't skew your reports.
Next steps#
visitor.qualified events in your own services.