Digital measurement field guide
A small event model for B2B content
A useful measurement system should help a team decide what to improve. Start with a few events that describe meaningful steps from content to conversation, rather than instrumenting every click.
Define the outcome before the event names
Write down what a qualified conversation means for the organisation. The definition should include the problem a prospect wants to solve, the fit with the services offered, and an agreed next action. Marketing and sales should use the same definition, otherwise a dashboard can show growth while the pipeline does not improve.
Use five events that people can interpret
| Event | Meaning | Useful property |
|---|---|---|
content_viewed | A visitor opened a substantive page or asset. | Content identifier and topic |
resource_used | A visitor used a guide, case study, or comparison. | Resource type |
enquiry_started | A visitor began a contact or booking flow. | Service area |
enquiry_submitted | The visitor sent an enquiry. | Source and consent state |
conversation_qualified | Sales reviewed an enquiry against the shared definition. | Outcome and reason |
Keep the payload modest
An event payload can carry a stable content ID, campaign source, session ID, timestamp, and service topic. Use an anonymous identifier until there is a lawful basis to attach a known contact or account. Keep names, email addresses, phone numbers, and other private details out of analytics URLs and event names.
{
"event": "resource_used",
"content_id": "b2b-measurement-guide",
"topic": "measurement",
"source": "organic-search",
"session_id": "anonymous-session-id"
}Review a journey without claiming one-touch attribution
Connect the events that can lawfully be connected, then compare two views: how many relevant people engaged, and how many qualified conversations followed. An article appearing in a journey is an association, not proof that the article caused a sale. B2B buying often includes several people and offline decisions.
At each monthly review, choose one change: answer a common sales question in a service page, improve a case study, or remove an unnecessary step from an enquiry form. Record the expected result before making the change, then review it after enough conversations occur.