Research protocols · Practical guide
Segmentation strategy experiment: study protocol
Does a predefined segmentation policy improve qualified outcomes over a broader eligible policy? Use this proposed protocol to collect and interpret evidence.
Reviewed · Examples are illustrative
Who this helps: Teams collecting evidence. Limited software observations are identified separately from unperformed campaign experiments and participant studies.
Define the decision
This page is a proposed research protocol, not a completed study or a report of findings. The decision is: Does a predefined segmentation policy improve qualified outcomes over a broader eligible policy? The observation unit is one company assigned to an outreach policy. Define the population and owner before collecting records; do not substitute an available convenience dataset without documenting the change.
Work through the procedure
- Freeze segment rules using data available before assignment. Specify exclusion criteria and expected coverage of each policy.
- Randomize comparable companies between policies. Track contacts screened out as well as those contacted; avoid changing rules after seeing replies.
- Before collection, write the primary outcome, observation window, exclusion rules and stopping conditions. Preserve excluded observations with a reason rather than quietly removing them.
- Pilot the procedure with fictional or owned test data, resolve ambiguous fields, and freeze a dated protocol version before the main run.
Worked example
The following is a synthetic example for this procedure, not a customer result or performance benchmark.
policy A: role-only eligibility; policy B: role plus verified workflow signal; compare outcomes per assigned company and per contacted prospect
Suggested record fields: observation_id, condition, evidence_reference, outcome, exclusion_reason, reviewer, protocol_version
Status: illustrative record only; no study has been run for this page.Read the result
Report coverage, research cost and qualified outcomes together. A higher response percentage in a tiny selected subset can hide lower total opportunity. Keep the numerator, denominator and missing evidence visible. If the available observations cannot answer the registered question, report that limitation rather than selecting a more favorable metric after collection.
Collect the evidence
Observation unit: company-policy.
Frozen eligibility rules based on pre-assignment evidence.
Assign comparable companies to policies; preserve excluded and uncontacted assignments.
Analysis: Outcomes per assigned company and per contacted prospect, coverage and research cost.
Download the JSON collection template under Source references. Set an owner, eligibility rules, outcome definition, observation window and sample justification before collecting records. Templates contain no participant data or results; keep original private records outside the public website.
Check before moving on
- Name the person responsible for collection and review.
- Check that the evidence can be inspected without exposing private messages or credentials.
- Record deviations from the protocol and analyze their possible effect.
- Retain a dated, redacted evidence worksheet with the final interpretation.
Limits and next action
This tests a policy bundle. It does not prove that a particular company attribute causes buying intent. Publish results only after the evidence, method and limitations have been reviewed. This protocol provides no benchmark, expected lift or completed-study claim.
Source: Method or workflow reference
Source references
Worked examples are illustrative. Editorial procedures are suggested methods, not measured performance claims or promises of additional product features.
Related guides
- DNS diagnostics: controlled error checks and authentication study protocol →
- Open tracking noise study: study protocol →
- Reply classification study: study protocol →