If you’re here, you probably want your sales or marketing team to know when someone worth talking to is on your site. Not just anyone, but folks showing real buying intent. This guide walks you through setting up real-time alerts for high-intent website visitors using Getsignals. It's for anyone who’s tired of missed opportunities, clunky workflows, or chasing cold leads.
You’ll get step-by-step instructions, some honest advice about what actually matters, and a few warnings about common pitfalls. Whether you’re a marketer wanting to pass better leads, or a founder who just wants a Slack ping when a whale lands, you’re in the right place.
What Counts as “High Intent” (and Why Real-Time Alerts Matter)
Before you start wiring up alerts, you need to know what you’re actually looking for. “High intent” isn’t just someone who loads your homepage; it’s the folks taking actions that suggest they’re close to buying, booking, or reaching out. Examples:
- Visiting your pricing page (and not bouncing in 2 seconds)
- Returning multiple times in a week
- Viewing case studies, demo pages, or product docs
- Filling out part of a form, then hesitating
Without real-time alerts, your team’s flying blind. Sales can’t reach out while someone’s interested. Marketing can’t tweak campaigns based on what’s actually happening. But real-time alerts only help if they’re set up thoughtfully—otherwise, you’ll get spammed and start ignoring them.
Step 1: Get the Getsignals Tracker Running
First things first: none of this works if Getsignals can’t see what’s happening on your site.
- Install the Tracking Script
- In your Getsignals dashboard, look for the tracking script. It’s a small JavaScript snippet.
- Add it to your website, just before the
</head>tag. If you use a tag manager (like Google Tag Manager), you can deploy it there instead.
Pro tip: If you’re not sure the script’s firing, use your browser’s developer tools to check for network requests to Getsignals after you reload the page.
- Verify Data’s Coming In
- Give it a few minutes, then refresh your Getsignals dashboard.
- You should start seeing visitor data, even if it’s just you testing.
Don’t bother setting up alerts until you see data flowing in. Otherwise, you’ll waste time troubleshooting later.
Step 2: Define What “High Intent” Really Means for You
Getsignals is only as smart as you make it. If you set your alerts too broad, you’ll get pinged every five minutes. Too narrow, and you’ll miss the good stuff.
Here’s what to do:
- List your high-intent actions.
- Pricing page visits? Free trial sign-ups? Time spent on product videos?
- Check what data Getsignals actually collects.
- You’ll usually get page views, company info (if reverse IP lookup is working), session duration, and sometimes UTM/source data.
- Don’t expect: perfect individual identification, or deep behavioral analytics (unless you’re connecting other tools).
Example: If you sell B2B software, you might care about: - Companies with >50 employees - Multiple page views per session, especially pricing or demo pages - Returning visitors from the same company within 3 days
Write these down. You’ll need them to build your alert logic.
Step 3: Set Up Your First Alert
Time to get practical. Getsignals lets you create alerts based on filters—think “if this, then notify me.”
- Head to the Alerts/Signals Section
-
In your Getsignals dashboard, find the “Alerts,” “Signals,” or “Notifications” area. (They keep renaming it, but it’s usually obvious.)
-
Create a New Alert
- Click “Create Alert” or similar.
-
You’ll see a filter builder. This is where you define your conditions.
-
Build Your Condition
- Example: “Notify me when a visitor from a company with more than 50 employees views the pricing page.”
-
In the filter builder, select:
- Company size: “Greater than 50”
- Page viewed: Contains “/pricing”
- (Optional) Session count in past week: “Greater than 1”
-
Choose Notification Type
- Slack, email, webhook, or sometimes Microsoft Teams.
-
Pick whatever your team actually checks. (If nobody reads email alerts, don’t bother.)
-
Test the Alert
- Visit your own pricing page in an incognito window (or have a teammate do it).
- Make sure the alert fires.
- If it doesn’t, check your filters. Are they too strict? Is company data missing?
Pro tip: Start with a broader filter while you test. You can always tighten it later.
Step 4: Fine-Tune to Avoid Alert Fatigue
The #1 reason real-time alerts get ignored? Too many useless pings. Here’s how to avoid that fate:
- Don’t set alerts for every single visit.
- Focus on patterns, not one-off events.
- Use company-level filters.
- Target by industry, company size, or even specific target accounts.
- Add frequency limits.
- Most tools let you say “only alert me once per company per day.”
- Combine multiple signals.
- Example: Only alert if someone visits both the pricing page and the demo page in one session.
What to ignore: Don’t bother alerting on visits from ISPs, universities, or overseas traffic you never sell to. You’ll just clutter your feed.
Step 5: Connect to Slack (or Wherever Your Team Lives)
Real-time alerts are only useful if they land where people actually see them.
- Choose your notification channel.
- Slack is the most common. Email works, but gets buried. Webhooks are for connecting to custom dashboards or CRMs.
- Follow Getsignals’ integration instructions.
- There’s usually a simple “Connect to Slack” button. You’ll need to pick a channel.
- Send a test alert.
- Make sure the format’s readable. If it’s a wall of JSON, fix it or nobody will read it.
Pro tip: Set up a dedicated channel like #signals-high-intent so alerts don’t get lost in general chatter.
Step 6: Decide Who Should Get Which Alerts
Not every alert needs to go to everyone. Here’s how to keep things focused:
- Sales team: Send them pings about target accounts or hot leads.
- Marketing: They might want to know which campaigns are driving repeat visitors.
- Founders/Execs: Maybe just the truly big fish.
Most tools (including Getsignals) let you set different recipients per alert.
Step 7: Review, Adjust, and Actually Use the Data
Don’t “set and forget.” Real-world usage will show you what’s working and what’s noise.
- Check alert volume after a week. Are you getting too many? Missing the good stuff?
- Ask the folks getting alerts: Are they acting on them, or just ignoring?
- Tweak filters. Change up which pages or behaviors trigger alerts.
- Consider adding exclusions (e.g., block your own company’s visits, known bots, etc.).
What works: Tight, focused alerts that give reps an excuse to reach out—while the visitor’s still interested.
What doesn’t: Blanket alerts for every hit, or complex logic nobody understands.
What to Watch Out For
Let’s be honest: no tool is magic, and Getsignals is no exception.
- Company identification is hit-or-miss. Reverse IP lookups can’t ID every visitor. You’ll miss some; that’s normal.
- Don’t expect perfect timing. “Real-time” usually means within a minute or two. That’s fast enough for sales, rarely instant.
- Privacy and compliance: If you’re in a regulated industry or have EU visitors, double-check your privacy notices.
- Integration limits: Getsignals plays nicely with Slack and email, but fancier stuff (like auto-enriching CRM records) might need Zapier or API work.
- People may ignore alerts over time. Keep an eye on alert fatigue—if nobody acts, you need to change your filters or process.
Wrapping Up: Keep It Simple, Iterate, and Ignore the Hype
Setting up real-time alerts for high-intent website visitors in Getsignals isn’t rocket science, but it does require some thought. Start simple. Focus on the actions and companies that actually matter to your team. Get alerts where people will see them. Don’t be afraid to tweak or even turn off alerts that aren’t helping.
There’s no perfect formula—just keep tuning things so your team gets value, not noise. The goal isn’t “more data,” it’s “actionable info, right when you need it.” Good luck, and don’t let perfect get in the way of useful.