The Intelligence Stream: The Complete Record Behind Every Summary
A summary is a decision someone else made about what matters. That's exactly what you want when a rep has ten seconds before writing an email. It's exactly what you don't want when you're trying to work out why deals close.
The Intelligence Stream is the Intelligence Brief plus everything the Brief was built from. Every session, every page, the engagement score for each one, the events they triggered, and the attribution behind each individual visit. Nothing condensed, nothing dropped.
In short: the Intelligence Stream is the Intelligence Brief plus the complete raw record behind it, every session, every page with its engagement score, and full attribution for each individual visit rather than just first and last touch. It's built for warehouses and BI tools rather than CRM fields, and it's delivered only through Zapier and Webhooks. Most teams run the Brief into their CRM and the Stream into their warehouse side by side.
The Problem With Reading Summaries
Your analytics tool tells you a page got 4,000 views. It can't tell you that eleven of those views came from the same person over six weeks, that their engagement climbed each time, and that they closed two months later at three times your average deal size.
That pattern is sitting in your data right now. You just can't query a paragraph.
If you're trying to answer questions like these, you need the underlying record:
- Which page sequences actually predict a closed deal, rather than the ones we assume do?
- How many sessions does a typical buyer need before converting, and does that differ by channel?
- Which content brings people back, versus which content merely gets clicked once?
- Does engagement depth on our documentation correlate with deal size?
- What does the journey look like for the deals we lose?
None of these can be answered from written context, however good it is. They need raw sessions, joined against your own revenue data, in a tool built for querying.
What Makes the Stream Different
It's the complete record, not a selection. Where the Brief includes the most recent session summarised, the Stream includes every session the lead has ever had, in full. Where the Brief describes their top pages in prose, the Stream lists every page with its engagement score and time on page.
It's built to be joined, not read. The Stream is structured for a database. Numbers arrive as numbers, lists arrive as arrays, and every session carries its own timestamp and attribution, so you can join it against your CRM, your revenue tables, or anything else you already model.
It's living, like the Brief. Every time a lead returns and their session closes, we regenerate and push the updated payload, now with the session that just ended appended to their history. The enrichment fields are re-researched on each return as well, so a new role, a change of company or fresh company news arrives in the same push.
What's Inside
The Stream contains the entire Intelligence Brief, so nothing is lost by choosing it. On top of that, it adds three things.
Full session history
An array covering every session, not just the latest. Each one carries its entry page, exit page, duration, and the Focused Score for that specific visit, so you can watch intent build across a relationship rather than reading a single moment.
Page-level engagement
For every page in every session: the URL, an engagement score, and time on page. This is our proprietary heatmap data expressed as numbers you can query rather than a picture you have to interpret. It's what lets you find out which pages genuinely hold attention, and which ones people open and abandon.
Per-session attribution
Rather than only first touch and last touch, you get complete attribution for each individual visit. That means you can trace the actual path: paid search brought them in, a blog post brought them back a month later, a direct visit closed it. Multi-touch attribution stops being an estimate and becomes a record.
Expanded enrichment
The Stream also carries the deeper enrichment fields held back from the Brief, including company overview, history, products and services, employee lists, press mentions, specialties, and profile highlights on the individual.
Where It Goes
The Stream is available through Zapier and Webhooks only.
That isn't an arbitrary restriction. A CRM field expects a value; the Stream delivers nested arrays that can run to thousands of rows for a well-engaged lead. Salesforce and HubSpot have nowhere sensible to put that, and forcing it in produces an unreadable blob in a text field that helps nobody.
The natural destinations are the tools your data team already runs:
- A data warehouse such as BigQuery or Snowflake, joined against your CRM and revenue tables
- A BI or visualisation layer, for cohort and funnel analysis
- Your own internal database or analytics pipeline
- Any of the thousands of Zapier destinations, if you'd rather not build a receiver
If your team doesn't have somewhere to put a payload like this, the Intelligence Brief is almost certainly the better choice.
Choosing Between Them
|
|
Intelligence Brief | Intelligence Stream |
|---|---|---|
| Built for | Reps writing outreach | Analysts measuring what works |
| Lives in | Your CRM, beside the compose window | Your warehouse or BI tool |
| Sessions | The most recent one, summarised | Every session, in full |
| Pages | Top pages, described in prose | Every page, with engagement scores |
| Attribution | First touch and last touch | Every individual visit |
| Delivered through | Slack, Salesforce, HubSpot, Pipedrive, Zapier, Webhooks | Zapier and Webhooks |
| Read in | About ten seconds | However long your query takes |
Most teams end up running both: the Brief into the CRM so reps have context where they work, and the Stream into the warehouse so analysts can measure what's actually driving revenue.
Before You Connect It
Payload size grows with the lead. Someone who visited twice last week produces a small payload. Someone who has been researching you across forty sessions produces a considerably larger one. Plan your receiver for the second case, not the first.
Test with a high-activity lead. Some Zapier destination apps flatten or truncate deeply nested data. A fresh lead with one session won't reveal that; a lead with thirty will.
Choose the trigger. Like every integration, the Stream fires on the funnel you choose when you set it up: a lead stage, or a custom funnel built from a saved filter. Most teams trigger it on Engaged Lead, since completeness is the point, but you can narrow it to a stage further down or to a custom funnel if your warehouse only needs a subset.
For how the Stream is metered, see How do Credits work across storage, syncing, and profile enrichment?
Why This Matters
Every company says it's data-driven about marketing. Most are working from aggregates: sessions, bounce rate, conversions by channel. Useful, but they describe traffic rather than people.
The Stream gives you the individual record behind the aggregate, already filtered down to visitors who were genuinely engaged rather than passing through. That's the difference between knowing your blog gets traffic and knowing which three posts appear in the journeys of customers who actually bought.