How to use this fieldbook
A content syndication program can be operationally successful while commercially ambiguous. This fieldbook offers six worksheets that align audience rules, content relevance, form events, respondent acceptance, and Sales action. Complete them in order for one B2B SaaS offer. Each worksheet ends with an output, an owner, and a test a reviewer can reproduce.
The sequence is an editorial planning tool, not an automated Intent Amplify platform feature. It does not promise that following the checklist will produce a predetermined number of MQLs, meetings, or opportunities. An approved audience, an appropriate campaign channel, and a defined receiving Sales process remain prerequisites to execution.
Worksheet 1: Define the SaaS buyer problem
Purpose: Establish the offer and the business question the content answers. A SaaS product can be relevant to several functions for very different reasons. Start with one use case, a defined account universe, and a reader question rather than an unbounded category such as technology leaders.
Fields to complete: SaaS category ____; target use case ____; company segment ____; operating region ____; relevant role ____; excluded role or industry ____; reader question ____; content answer ____; owner ____.
Acceptance test: Can two reviewers read the audience brief and independently agree whether a sample account and role are eligible? Intent Amplify's Buyer Intelligence describes defining account fit, roles, and exclusions before a program proceeds [1]. Do not add a person to the accepted audience merely because their email domain is recognizable.
Worksheet 2: Write the content-to-role promise
Purpose: Explain why a person in the chosen function would benefit from this specific asset, without inferring active buying intent. A technical comparison answers a different question from a budget justification or a strategic market guide. Assign an asset to the reader question and identify what the asset does not claim to solve.
Fields to complete: Asset ID ____; title ____; reading objective ____; target function ____; source claims verified ____; primary distribution channel ____; public landing page ____; content owner ____.
Acceptance test: Ask a reviewer who knows nothing about the campaign to state what a reader will learn. The promise should still be true if the reader has no immediate purchase project. Reject promotional language that implies every interested reader must be evaluating suppliers.
Worksheet 3: Specify every form event
Purpose: Preserve what actually happened. Microsoft documents separate form submission, record-update, matching, consent, and validation settings in Customer Insights - Journeys [2]. Its form-creation instructions also describe how submissions can create different lead and contact records according to the selected settings [4]. These are examples of product behavior, not evidence that an individual Intent Amplify client uses Microsoft software.
Fields to complete: Form ID ____; publisher or destination ____; mandatory fields ____; exact submit event ____; original timestamp ____; identity-link method ____; partner evidence supplied ____; consent or lawful-use information ____; event owner ____.
Acceptance test: Submit a controlled test entry, verify the recorded event, and confirm the source file distinguishes a new submission from an update to an existing contact. Keep form submission, content delivery, page view, and attendance separate. A successful technical submit is not a commercial lead-stage decision.
Worksheet 4: Build a respondent acceptance contract
Purpose: Decide in advance which records count toward a program's accepted-delivery target. Commercial agreements may differ, so the checklist below is a proposed starting point rather than a universal industry certification.
Fields to complete: Country ____; account eligibility ____; functional relevance ____; verified business contact ____; duplicate window ____; invalid response rules ____; prohibited or excluded sources ____; replacement terms ____; escalation owner ____.
Acceptance test: Review six deliberate edge cases. Include a duplicate person, an irrelevant function, a correctly formed but nonbusiness email, an excluded company, a record with unclear original source, and a valid form with no permitted marketing follow-up. Each case needs an explicit accept, reject, replace, or restrict decision with a reason code. A partner should be able to reproduce the disposition. The FTC explains that US commercial email rules also apply to business-to-business messages [8]. This is a separate channel-eligibility consideration, not a reason to treat an accurate form submission as sales-qualified.
Worksheet 5: Reconcile attribution without inventing a journey
Purpose: Connect the original syndication placement to a defensible campaign record. Google Analytics documents standard UTM campaign parameters for collecting information about referring links [3]. The Lead acquisition report can use recommended lead events to show acquisition information within the product's available data [6]. Neither feature establishes a person-level path when the identity linkage or cross-site evidence is absent.
Fields to complete: Campaign ID ____; utm_source ____; utm_medium ____; utm_campaign ____; partner placement ____; content ID ____; event time ____; CRM ID ____; attribution caveat ____; reporting owner ____.
Acceptance test: Follow one test registration from the permitted placement to the destination and reporting record. If a partner hosted the form outside the vendor's analytics system, record the partner's delivered source fields and their limits. Never invent a first-touch or multi-touch journey from a single recorded response.
Worksheet 6: Design a Sales-ready context handoff
Purpose: Give Sales an accurate starting point, not an automatic stage promotion. Intent Amplify's Managed Demand Generation describes approved audience and content execution with acceptance and replacement review [5]. Its Pipeline Activation scope addresses contextualized delivery, CRM owner, and next action [7]. The organization's Sales team retains qualification authority.
Fields to complete: Account and contact keys ____; campaign and asset ____; original event ____; validated fields ____; accepted status ____; marketing-qualification reason ____; permitted next action ____; Sales owner ____; decision date ____.
Acceptance test: Ask the receiving seller whether the record contains enough context to ask one relevant question. If the person expresses a meaningful business need and accepts an appropriate next step, Sales can record that result under its own definitions. If the record remains an educational inquiry, it should retain that status without being reported as an SQL.
Worked example: A fictional SaaS analytics vendor
Imagine a SaaS company sharing a guide on reporting reliability. A verified Marketing Operations Manager requests the guide through an authorized form. The account fits the agreed segment and the record passes duplicate checks. Those facts support an accepted response. They do not establish that the manager owns the analytics budget or has selected a vendor.
In the handoff, Sales receives the resource topic, the date, the role, the applicable contact rules, and one proposed discovery question. A reply requesting a comparison of reporting approaches may justify a deeper conversation. A polite decline or absence of project detail should not be converted into pipeline. This example is fictional and contains no client-performance figures.
A workable 30-day sequence
Days 1-5: Agree the offer, target accounts, roles, content claim inventory, and exclusions. Output: Approved campaign brief. Days 6-10: Configure or document capture events and run test submissions. Output: Event dictionary and validation evidence. Days 11-15: Confirm the respondent contract, duplicates, permitted channels, and replacement rules. Output: Acceptance decision table.
Days 16-20: Test source tracking and CRM field mapping using synthetic records. Output: Traceable sample handoffs. Days 21-25: Review a bounded delivery sample with Marketing, Privacy, and Sales. Output: Accepted and excluded reasons. Days 26-30: Evaluate Sales dispositions and propose one campaign revision based on observed evidence. Output: A versioned optimization note. Timing is illustrative, not a claim of completed deployment.
Readiness rubric: Four states, not a fictional performance score
For each worksheet, record Not specified; specified; evidence-tested; or in operational use. Count completed evidence tests out of six and show the denominator. Do not describe a filled-out worksheet as an implemented integration. Distinguish technical readiness, contract acceptance, and confirmed commercial results. These measures become meaningful only when owners agree what evidence is sufficient.
Intent Amplify perspective
Buyer Intelligence can assist audience specification. Managed Demand Generation can coordinate the authorized content program and acceptance checks. Pipeline Activation can transfer the relevant source and interaction context to the receiving seller [1], [5], [7]. The receiving organization continues to define MQL, SAL, SQL, opportunity, and revenue criteria.
Companion reviewer ledger
At the end of each worksheet, add a dated line containing the decision, original evidence, reviewer, and consequence. Example: A respondent's company and function meet scope, but the original form version lacks a stated required field; the delivery contract decides whether the response is accepted or replaced. Another example: A valid accepted response is not an MQL because the agreed marketing-qualification test was not met. The examples illustrate decision logic, not real campaign incidents.
Keep previous versions rather than overwriting the record. When the campaign changes its audience definition or duplicate window, preserve the effective date and restate earlier results under their original definition. Only compare like with like. This protects Marketing and Sales from reading improvements in rule design as changes in buyer behavior.
Activate the fieldbook on five accounts
Complete all six worksheets for a small, appropriately authorized sample. Compare acceptance decisions with the source evidence and send only the permitted context to Sales. For a program-design conversation, review Intent Amplify's managed demand approach: https://www.intentamplify.com/solutions/managed-demand-generation.
Evidence notes and references
Bracketed citations identify the public source supporting the adjoining factual claim. Process models, examples, and recommendations are original editorial analysis, not measured customer outcomes. Service delivery varies by approved program scope. Sources reviewed October 29, 2026.
- Intent Amplify, Buyer Intelligence (Official service description). https://www.intentamplify.com/solutions/buyer-intelligence
- Microsoft Learn, Manage Customer Insights - Journeys Forms (Official product documentation). https://learn.microsoft.com/en-us/dynamics365/customer-insights/journeys/real-time-marketing-manage-forms
- Google Analytics Help, URL Builders: Collect Campaign Data with Custom URLs (Official product documentation). https://support.google.com/analytics/answer/10917952?hl=en
- Microsoft Learn, Create Customer Insights - Journeys Forms (Official product documentation). https://learn.microsoft.com/en-us/dynamics365/customer-insights/journeys/real-time-marketing-form-create
- Intent Amplify, Managed Demand Generation (Official service description). https://www.intentamplify.com/solutions/managed-demand-generation
- Google Analytics Help, Lead Acquisition Report (Official product documentation). https://support.google.com/analytics/answer/16376749?hl=en
- Intent Amplify, Pipeline Activation (Official service description). https://www.intentamplify.com/solutions/pipeline-activation
- Federal Trade Commission, CAN-SPAM Act: A Compliance Guide for Business (US federal regulatory guidance). https://www.ftc.gov/business-guidance/resources/can-spam-act-compliance-guide-business
