1. Observe
Collect agreed first-party session events and campaign context.
Data Pulse
Understand more of the traffic you already have.
Data Pulse combines observed website session data with selected matched fields when a reliable match is available.
The distinction that matters
A session is observed. A person or company is matched.
Page views, referrers, campaign parameters, device context, and timestamps can be observed directly. Identity and contact fields require a separate match and will not be available for every session.
2. Attempt a match
Check eligible sessions against configured sources and rules.
3. Deliver
Return observed and matched fields through the delivery method in scope.
Typical output
Know where every field came from
| Field group | Status | Example |
|---|---|---|
| Session | Observed | Landing page, source, campaign, timestamp |
| Identity/contact | Matched when available | Name, business, selected contact fields |
| Priority | Inferred | A rule-based score with its inputs documented |
Match coverage and field availability vary. Data Pulse should be evaluated on eligible traffic, successful matches, usable fields, and downstream outcomes—not total sessions alone.
Next step
Talk through your current setup
Start with the problem, data, and systems you already have.
We will identify what is observable, what may be matchable, and which delivery options fit your workflow.