Skip to main content

Try kenbun With Sample Data and Test Events

A brand-new workspace is empty by design. Before your real data starts flowing, two activation tools let you see exactly how kenbun works in just a few minutes:

  • Sample data generates a realistic, fully scored pipeline — leads, accounts, events, scoring rules, levels, and a fired alert — so your dashboard "lands alive." When you're done exploring, you remove it for a clean slate.
  • Fire a test event sends one synthetic action through real scoring so you can watch a lead's score jump in real time, see an alert fire, and optionally send a real test message to your Slack channel.

Neither tool affects your billing or usage. Sample and test activity are tracked separately and never count against your plan's event limits.

Sample Data​

Why It Matters​

Scoring rules, engagement levels, and triggers are easiest to understand when you can see them working on real-looking data. Sample data builds a complete demo workspace in about 30 seconds — no integration to connect, no import to run, no configuration to write by hand. You get a ready-made scoring model and a set of leads at different stages of engagement so you can explore every part of kenbun before your own data arrives.

What Gets Created​

Generating sample data populates your workspace with a self-contained demo:

CategoryWhat you get
LeadsA handful of demo leads at different engagement levels, from cold to hot
AccountsA few demo companies the leads belong to
EventsRealistic activity (page views, form submissions, webinar attendance, email opens) spread over the past few weeks
Scoring rulesA populated scoring model so events actually move scores
LevelsEngagement, profile, and account levels so leads sort into warm/hot bands
TriggersExample milestone and sequence triggers
SegmentsA couple of example segments (such as High-Value Leads)
A fired alertOne milestone alert that has already fired, so you can see what an alert looks like

One of the demo leads, Avery Quinn at Lattice Fintech, is intentionally a hot prospect: she views the pricing page repeatedly and submits a demo request, which pushes her engagement score high enough to cross a milestone. She's a good place to start exploring how a lead's activity adds up to a score.

Generating Sample Data​

Sample data is offered only on an empty workspace — one with no real leads or events yet. This keeps the demo cleanly separated from your real data.

  1. Go to Analyze > Overview.
  2. If your workspace is empty, a Generate Sample Data prompt appears as a banner near the top of the dashboard. You can also use the Generate Sample Data button in the toolbar.
  3. Click Generate Sample Data.

Generation runs in the background and usually finishes within about 30 seconds. When it's done, refresh the Overview dashboard to see your demo pipeline: KPI cards, the activity heatmap, top leads, and the rest all fill in.

Removing Sample Data​

When you're ready to start with your own data, remove the sample data to return your workspace to a completely clean slate. This deletes everything the sample generator created — the demo leads, accounts, and events, and the demo scoring configuration (rules, levels, triggers, segments) — and restores your original scoring setup.

  1. Go to Analyze > Overview.
  2. Click Remove Sample Data in the toolbar.
  3. Confirm the action in the dialog.

Removing sample data is permanent and cannot be undone, but because everything is tagged as sample data, your workspace is left exactly as it was before you generated it — ready for your real leads and events.

Good to Know​

  • One demo at a time. A workspace can hold a single sample data batch. If sample data already exists, the Generate option is replaced with a summary and a Remove Sample Data option.
  • It won't touch real data. Generating is only available on an empty workspace, and removing only deletes sample data — never anything you've added yourself.
  • It's free. Sample leads and events are excluded from billing and usage, so exploring the demo never affects your plan limits.

Fire a Test Event​

Why It Matters​

kenbun reacts to lead behavior the moment it happens. Fire a test event lets you prove that to yourself: send one synthetic action and watch a lead's engagement score update live, see whether it crosses a milestone, and confirm your alerts are wired up correctly — all without waiting for a real visitor to do something.

It's the fastest way to answer questions like:

  • "Does my scoring rule actually award points for this action?"
  • "Will my milestone alert fire when a lead reaches this score?"
  • "Is my Slack channel set up to receive notifications?"

Firing a Test Event​

  1. Open any lead from Analyze > Leads.
  2. In the lead's header, open the ⋯ (More Actions) menu and choose Fire Test Event.
  3. Choose the event type to simulate (for example, Form Submit or Page View).
  4. Click to fire it.

The lead's Engagement Score updates in real time as the event scores, and a short explanation shows which signals contributed. If the new score crosses an active milestone threshold, a trigger fired alert appears in the live feed right away — exactly as it would for a real lead.

Sending a Real Test to Slack​

By default, a test event only shows up inside kenbun — it never messages your team. When you specifically want to confirm your Slack channel is connected, you can opt in to a real test send:

  1. Open the ⋯ (More Actions) menu on a lead's detail page and choose Fire Test Event.
  2. Open the options and turn on Send a real test to my Slack/Teams.
  3. Fire the event.

This delivers a real test message to your configured Slack channel using the same delivery path as your live alerts. It's a one-extra-click, deliberate choice, so a test never accidentally pings your workspace.

Microsoft Teams: Real test sends to Teams channels aren't supported yet. The in-app alert still works, and the response will let you know Teams test sends are unavailable.

Good to Know​

  • It uses real scoring. Test events run through the same scoring engine your real events do, so the score change you see is exactly what a real lead would get.
  • No surprise notifications. External messages are only sent when you explicitly opt in for that single test.
  • It's free. Test events are excluded from billing and usage.
  • "No matching rule" is normal. If you fire an event type that none of your scoring rules cover, the event still lands but the score won't change, and you'll see a note that no active rule matched. That's a useful signal that you may want to add a rule for that event type.

Frequently Asked Questions​

Will sample data or test events count against my plan? No. Both are tracked separately and are excluded from billing and usage limits.

Can I generate sample data after I've already added real leads? No. Sample data is only offered for an empty workspace so the demo stays cleanly separated from your real data.

What happens to my real scoring rules if I generate sample data? The sample generator sets up its own demo scoring model while you explore. When you remove the sample data, your original scoring setup is restored.

Does firing a test event change a real lead's history? A test event applies to the lead you choose and runs through real scoring, but it's flagged as a test and excluded from billing. To return a lead to a clean state, you can reset their scores from the lead view.