Your First Identified Visitor in Slack, in About 30 Minutes
Somewhere on your site right now, a good-fit buyer is doing something that matters, rereading your pricing page, coming back for a third visit this week, and nobody on your team knows it's happening. By the time anyone notices, if anyone notices, the moment that mattered has usually already cooled.
This guide walks through Bryn's setup wizard end to end: six steps, the same six you'll click through in the product itself, from a blank workspace to a real alert in your Slack channel. Nothing here skips ahead of what the wizard actually asks you to do.
"Your first identified visitor in Slack in about 30 minutes."
— docs.civic.com/bryn/getting-startedBefore you start, you'll want:
- A work email to create the workspace.
- Access to your site's
<head>, or a developer you can hand step 2 to, if you don't have it yourself. - Admin rights on the Slack workspace you want alerts to land in.
Create your workspace
Sign up with your work email. There's nothing to configure yet. This step just gives you a workspace URL and a place for the next five steps to land.
You can log into your new workspace and see the setup wizard waiting on step 2.
Install the pixel
One script goes into your site. It does two jobs at once, in the docs' own words:
"One snippet does two jobs: it reports visits to Bryn, and it receives the payload that lets your site personalize for identified visitors."
— docs.civic.com/bryn/pixelThere's a path for however your site is built, Google Tag Manager, a plain HTML snippet, Webflow, or WordPress, so this rarely needs custom engineering work. If you don't have access to your site's <head> yourself, this is the one step the docs explicitly plan for: a ready-made message you can hand to whoever does.
The wizard confirms it's received a signal from your own site. Once the snippet is live, Bryn starts watching.
Confirm your ICP
Your ICP, Ideal Customer Profile, in plain terms: the kind of account that actually becomes a customer, is what every score Bryn produces gets measured against. Bryn starts you off with a draft based on what it can already see about your business, so this step is editing, not building from zero:
"You are editing a draft, not writing from scratch."
— docs.civic.com/bryn/getting-startedGetting this right matters more than it looks like it should:
"A wrong Ideal Customer Profile (ICP) means alerts about companies you would never sell to; a good one means your Slack channel stays worth reading."
— docs.civic.com/bryn/icp-and-scoringThe good news: the defaults are tuned to be reasonable on day one. The docs are explicit that you don't need to get this perfect before you turn anything on.
"The default scoring weights are good. Change them after you have watched a week of real traffic, not before."
— docs.civic.com/bryn/icp-and-scoringYour ICP draft reads like a description of the accounts you'd actually want to close, not a list of demographic checkboxes.
Map your signals
A raw pageview by itself doesn't mean anything. A signal is Bryn's word for the plain, named read on what actually happened. This step is where you tell Bryn which events on your site or in your product are worth naming:
"A signal is a judgement with a name: pricing_page_viewed, demo_abandonment, trial_wobble."
Everything downstream, scoring, Plays, personalization, only ever reacts to a named signal, never to the raw event underneath it:
"Raw events are noise. Signals are the vocabulary everything else in Bryn speaks: scoring reads signals, Plays trigger on signals, and on-page personalization reacts to signals. An event you never map does nothing."
— docs.civic.com/bryn/signal-mappingA test visit to one of your mapped pages shows up as a named signal in the workspace, not just a raw event count.
Connect Slack
This is where the alerts actually land. Authorize the workspace, pick a channel, and you're done. Bryn is deliberately conservative about how often it posts, because a channel people mute stops being useful to anyone:
"Alerts you mute are worse than no alerts, so Bryn rate-limits itself."
— docs.civic.com/bryn/outputsYou can see the connection listed as active, with the right channel selected, before any real alert has fired yet.
Review and turn on your Plays
A Play is the rule you set once, in plain terms: when this kind of thing happens, on an account like this, do this. Bryn doesn't hand you a blank canvas here. It ships with a small library already built:
"Bryn ships with pre-built Plays: automated workflows that act on qualified accounts... The first three are on for new workspaces; the rest wait for you."
— docs.civic.com/bryn/playsReview the three that are already on, turn on any others that fit how your team works, and the wizard is done. From here, Bryn is watching your traffic on its own.
The setup wizard marks all six steps complete, and the workspace is live: watching your traffic, naming signals, and ready to alert your Slack channel.
Thirty minutes in, this is the message your team actually sees.
No two setups look identical, but the shape is the same: a company name, what it did, and a link to the account. Nothing here is a real customer. It's an illustrative example, the same synthetic-name convention used elsewhere on this site.
The wizard is done. Here's what to look at once alerts start arriving.
The Plays you turned on in step 6 will start running on their own. Two places to go next depending on what you're trying to understand:
Sourced from
- docs.civic.com/bryn/getting-started
- docs.civic.com/bryn/pixel
- docs.civic.com/bryn/icp-and-scoring
- docs.civic.com/bryn/how-bryn-works
- docs.civic.com/bryn/signal-mapping
- docs.civic.com/bryn/outputs
- docs.civic.com/bryn/plays