How to Use This Fieldbook
Webinars bring together content, audience selection, registration forms, event platforms, and subsequent Sales conversations. The problem is rarely a shortage of metrics. It is the lack of consistent definitions connecting those metrics. This fieldbook provides seven working worksheets to help B2B technology teams build a documented path from relevant registrations to defensible follow-up decisions. It is a proposed operating method, not a software implementation or a promise of conversion improvement.
Complete the worksheets for one event and one defined audience before adapting them to a larger event calendar. Each worksheet identifies a decision, essential fields, an accountable owner, and a review test. The program's commercial terms should specify the actual accepted outcome: Intent Amplify describes verified registrations under contracted audience and validation criteria, with attendance reported separately rather than guaranteed [1].
Worksheet 1: Write the Audience Acceptance Contract
Decision: What counts as one accepted registration? Record the allowed account sectors, territory, company-size or revenue criteria when relevant, business-email standard, job-title groups, duplicate window, consent or other valid outreach basis, suppression exclusions, event identifier, and rejection reasons. Include the contract version and date. Do not use a generic phrase such as qualified attendees when the purchased deliverable is verified registration.
Owner: Campaign Strategy with Revenue Operations. Review test: Give ten sample submissions to two independent reviewers. They should agree on accept, reject, or duplicate without consulting the campaign sponsor. If they disagree, clarify the rule before scaling. Intent Amplify's Buyer Intelligence service describes explicit account and buying-role criteria and source limitations as inputs to audience decisions [6].
Worksheet 2: Create the Event and Content Identity
Decision: Which event does each observed action belong to? Record one stable event ID, event title, intended buyer question, session date and time zone, live or on-demand format, content version, approved landing page, promotional channel, and campaign tracking identity. Keep revised titles and rescheduled dates in history rather than silently overwriting them.
Google Analytics documents source, medium, and campaign parameters in tagged URLs [5]. Those parameters help identify campaign traffic, but cannot prove who watched a webinar or which organization is evaluating a purchase. Owner: Marketing Operations. Review test: Click approved test links from two channels and confirm the resulting event and campaign labels match the intended tracking plan.
Worksheet 3: Reconcile Registration Status
Decision: Which registrations are accepted and unique? Record submission time, normalized contact identifier, organization, stated function, form source, privacy status, acceptance result, duplicate group, and reviewer. Maintain counts for raw submissions, accepted unique registrations, duplicates, exclusions, cancellations, and unreviewed input errors as separate lines in the working file.
Zoom's webinar reporting documents registration details and separate attendance history [2]. The team must check what its own account and export settings actually provide. Owner: Audience Operations. Review test: Reproduce a five-record accepted total from the original registration export and the declared duplicate rule. If the count cannot be reproduced, it should not be reported as verified.
Worksheet 4: Map Live Engagement Without Overclaiming
Decision: Which participation facts are directly recorded? Suggested fields are attendee identifier, join and leave time, net attendance duration, poll participation where attributable, question topic, handout request, and source export. Adobe's webinar engagement dashboard documents registration, attendance, viewing duration, and interactions such as polls and Q&A in supported configurations [3]. Those fields can be useful, but their availability depends on the chosen platform and settings.
Owner: Event Operations. Review test: Compare the event platform's attendance export to the CRM event record for five people, including one reconnect and one guest whose identity cannot be resolved. Keep a separate unknown identity state. A long session does not itself confirm procurement authority or a funded initiative.
Apply the Evidence Checklist to One Event
For a practical first step, complete Worksheets 1 through 4 for a recent webinar and record one owner beside every acceptance and engagement decision. If a managed activation program would be useful, explore Intent Amplify's approach to coordinated event delivery and validation.
Explore the Relevant Intent Amplify Service
Worksheet 5: Treat On-Demand Viewing as a Distinct Journey
Decision: What happened after the live session? Separate recording eligibility, access invitation, new on-demand registration, playback start, observed watch duration, and later resource requests. Adobe's October 2026 on-demand webinar documentation shows that supported configurations can distinguish event modes and capture watch date and duration [4]. That describes a specific platform capability, not a universal event-market data standard.
Owner: Content Operations. Review test: Trace a no-show who later watched the recording and a live attendee who later rewatched it. Preserve both event histories while reporting one person when the metric is unique contacts. Never label a delivered recording link as a recorded view.
Worksheet 6: Establish Qualification and Sales Acceptance Rules
Decision: When does an accepted event record become an MQL, SAL, SQL, or opportunity? Suggested MQL criteria are validated identity, relevant account and role, and a qualifying topical response under an approved definition. SAL means a named Sales owner accepted the record for review. SQL requires a directly established business issue and an agreed next step recorded by Sales. Opportunity creation follows the receiving organization's documented Sales process.
HubSpot's marketing-event guidance describes bringing event information into a CRM through connected applications or import [9]. That establishes the availability of event records, not automatic Sales readiness. Owner: Sales Leadership with Revenue Operations. Review test: Ask a seller to explain why five records moved stages, including one with strong attendance but no business question. If the seller cannot identify the evidence, the stage rule is insufficient.
Worksheet 7: Write the Handoff and Reconciliation Record
Decision: What should Sales receive? Create a short handoff record containing verified account and contact identifiers, role scope, exact webinar, original registration result, live or on-demand evidence, specific question if provided, allowed follow-up channel, next suggested resource, receiving owner, and final Sales disposition. Intent Amplify's Pipeline Activation service describes delivering validated campaign and qualification context to a named Sales owner or queue [8].
Owner: Revenue Operations and Sales. Review test: Ask a colleague unfamiliar with the event to reconstruct the contact's journey from source logs. The colleague should see precisely where interest was observed, where it was only inferred, and where a Sales decision was made.
Negative-Case Exercises
Case A: One contact registers using two spellings of the same business email. Retain both submissions but apply the agreed duplicate rule before counting accepted unique registrations. Case B: A partner shares a webinar with a relevant manager who declines marketing outreach. Preserve permitted reporting but do not authorize direct contact contrary to that preference.
Case C: A person watches a recording after missing the live session. Update the on-demand event only when the source supports the view; do not retroactively call the person a live attendee. Case D: A senior title responds to a poll about a product category but gives no buying need. Record participation without creating an SQL. Each case tests whether attractive performance numbers can be explained without changing their meaning.
A 30-Day Pilot Sequence
Days 1–5: Define the audience contract, tracking dictionary, event IDs, and ownership.
Days 6–10: Configure registration and test sample records, including duplicates and exclusions.
Days 11–15: Promote the event to authorized contacts and reconcile accepted registrations.
Days 16–20: Reconcile attendance and attributable interactions.
Days 21–25: Open the recording, if approved, and capture only supported viewing events.
Days 26–30: Review Sales dispositions, exceptions, and evidence gaps.
This is an illustrative schedule. Keep the source file, time window, and rule version attached to every reported number. Compare actual accepted registrations and completed Sales actions with the campaign plan; do not report targets as achieved results. When the evidence is thin, the responsible conclusion may simply be that further research or a more relevant educational resource is appropriate.
The Intent Amplify Perspective
Buyer Intelligence can establish a defensible audience and buyer-role screen [6]. Managed Demand Generation can coordinate the approved webinar activation and validation [7]. Pipeline Activation can support the receiving Sales team with source-backed context and a recorded next action [8]. A B2B technology vendor can adapt those connected services to its own event calendar, customer data permissions, and Sales-stage definitions without treating attendance or content consumption as guaranteed revenue.
Fieldbook Completion Standard
A complete working version should be understandable to someone who did not attend the planning meetings. Each record needs a source, date, accepted definition, and owner; each status needs a reproducible rule; each Sales-stage claim needs the receiving Sales decision. Mark unavailable measurements as unavailable rather than inventing them. Use the fieldbook to improve the quality of the next decision, not simply the appearance of the event dashboard.
Evidence Notes and References
Numbered references support specific statements beside them. Service and software documentation establish published capabilities, not client results. Frameworks and recommendations are editorial proposals, not measured outcomes. Official sources reviewed November 5, 2026.
- Intent Amplify, Webinar Programs, Webinar Audiences, Measured Honestly (Official pricing and accepted-outcome terms). https://www.intentamplify.com/pricing/webinars
- Zoom Support, Generating Webinar Reports (Official documentation). https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0066245
- Adobe Experience League, Engagement Dashboard (Official Marketo Engage documentation, updated October 7, 2026). https://experienceleague.adobe.com/en/docs/marketo/using/product-docs/demand-generation/events/interactive-webinars/engagement-dashboard
- Adobe Experience League, On-Demand Webinars (Official Marketo Engage documentation, updated October 7, 2026). https://experienceleague.adobe.com/en/docs/marketo/using/product-docs/demand-generation/events/interactive-webinars/on-demand-webinars
- Google Analytics Help, URL Builders: Collect Campaign Data With Custom URLs (Official documentation). https://support.google.com/analytics/answer/10917952?hl=en
- Intent Amplify, Buyer Intelligence (Official service description). https://www.intentamplify.com/solutions/buyer-intelligence
- Intent Amplify, Managed Demand Generation (Official service description). https://www.intentamplify.com/solutions/managed-demand-generation
- Intent Amplify, Pipeline Activation (Official service description). https://www.intentamplify.com/solutions/pipeline-activation
- HubSpot Knowledge Base, Use Marketing Events (Official documentation, updated August 26, 2026). https://knowledge.hubspot.com/integrations/use-marketing-events
