What an Account Passport Solves
A traditional target list captures a point-in-time selection but rarely explains the decision that generated it. A campaign manager may inherit an account tier without knowing its criteria; a provider may enrich a business contact without establishing the correct subsidiary; an account executive may receive a handoff with no reason for follow-up. An Account Validation Passport is a proposed single-record companion that preserves the reasons, sources, limitations and owners behind targeting.
The passport does not certify buyer intent. It documents whether an account is in scope and the quality of the evidence supporting the next authorized action. This distinction reflects Intent Amplify’s published Buyer Intelligence approach, which separates fit, contact validation and engagement context [1].
Field Family A: Canonical Account Identity
Record the business name as supplied, accepted trading name, canonical website, country, applicable parent entity, business unit and internal CRM ID. Do not treat a shared website as proof that two subsidiaries should be collapsed. Salesforce describes parent-child account relationships as a way to represent real-world organizational structure [2]. The passport should note whether the relationship is confirmed by an authoritative source or merely inferred.
Preserve each original record ID for audit. If two sources disagree about the parent, set identity status to review required rather than choosing the version that maximizes campaign reach. A valid identity key must be stable enough for reconciliation while remaining accurate for the product buying center.
Field Family B: Explicit Account Eligibility
Store the ICP policy version and a plain-language fit rationale. Mandatory fields might include region, industry, operating size band, use case and disqualifying conditions. Optional fields might include technology footprint or known initiative, provided their source and method are explicit. An account cannot become eligible simply because a vendor assigns it a high intent score; eligibility follows the product-market definition.
Each account should receive an inclusion or exclusion code, author and decision date. Where an account qualifies for one product but not another, record separate use-case decisions rather than overriding the master record.
Field Family C: Contact and Buying-Role Interpretation
Keep the job title exactly as obtained, then add a normalized function and buyer-role hypothesis. For example, “director of IT infrastructure” might be a technical evaluator for one solution and a program sponsor for another. Validation must distinguish an observed title from the campaign team’s interpretation. Include a role-confidence note based on the available evidence; do not make it a secret predictive score.
Do not transfer inferred seniority into a blanket budget-authority claim. Where no suitable person is confirmed, the account may remain valid while the contact layer is incomplete. This permits account-level research without forcing premature one-to-one outreach.
Field Family D: Observed Engagement and Interpretation Boundary
A useful record gives the exact event type, content ID, channel, timestamp, identifying source and any capture limitation. “Registered for the event” should not be rewritten as “attended.” An anonymous page view cannot be attributed to a named stakeholder without an established identity link. When there is only provider-modeled interest, label it as a modeled signal with the source and permitted interpretation.
The passport’s next-action recommendation should never be mechanically derived from one interaction. It should depend on fit, persona, source quality, permissions and the receiving team’s review policy.
Field Family E: Source Rights, Suppression and Allowed Use
Log the approved purpose, applicable lawful-use or consent basis, geographic constraints, outbound channel, current suppression status and retention owner. The US FTC explains the compliance obligations for commercial B2B email, including truthful message information and opt-out processing [4]. These are not optional CRM metadata fields when the information will be used for outreach.
The passport should identify the person responsible for resolving unclear permission. A contact can be valid and ineligible for activation at the same time. The right response to an uncertainty is to withhold the proposed action, not erase the uncertainty from the system.
Field Family F: Validation Decision and Handoff
Maintain separate statuses for account identity, ICP fit, contact quality, engagement evidence and delivery acceptance. Microsoft documents rule-based duplicate detection for account and contact data [3], but a matching alert still requires the correct business disposition. Define accept, correct, exclude and escalate decisions with clear owners and reason codes.
For a CRM handoff, include the record identifier, source fields, permissible use, responsible Sales queue and reason for the action. Intent Amplify Pipeline Activation positions these as scoped handoff elements; the recipient still determines whether the record is qualified [5]. HubSpot separately documents lifecycle stages such as MQL, SQL and opportunity [6], underscoring the need not to equate them.
Passport Schema Teams can Adapt
Identity: account_id, supplied_name, canonical_domain, parent_id, region, owner, check_date. Fit: icp_version, use_case, inclusion_reason, exclusion_reason, reviewer. Role: source_title, normalized_function, buyer_role, validation_method, uncertainty. Engagement: campaign_id, asset_id, event_type, timestamp, source_id, identity_link_basis. Rights: approved_purpose, permissible_channel, consent_or_basis, suppression_flag, retention_owner. Decision: status, reason, accepted_by, next_action, CRM_destination, disposition_date.
Mark every field mandatory, conditional or optional for the planned program. Restrict free-text fields that would invite unsupported claims about purchasing plans. Store reference links or record IDs instead of pasting unnecessary personal information into campaign briefs.
A Four-Case Acceptance Test
Case one: a verified parent and relevant subsidiary with a documented technical persona can be eligible for the specified content campaign. Case two: a domain collision between unrelated entities needs manual resolution. Case three: a strong account fit with an opted-out contact is account-eligible but not contact-eligible for the prohibited channel. Case four: a guide download from a validated contact supports the observed engagement fact, not automatic SQL classification.
Two reviewers should independently classify each case and explain the evidence. Disagreement is a design signal: the rules need clarification. Once the cases are reproducible, scale to a representative production sample and inspect the accepted, corrected and excluded populations separately.
Versioning and Changing an Account Decision
An account’s eligibility can change when the vendor adds a product module, withdraws support from a geography, learns that the business has reorganized, or receives new reliable role information. The passport should retain previous decisions, source dates, the policy version that applied at the time and the reviewer authorizing a change. Never rewrite yesterday’s campaign audience to make historical conversion appear stronger. Instead, produce a new-version view and explain the delta. This record-level discipline also lets Sales interpret why an account was targeted in an earlier campaign but excluded from the next one.
The Intent Amplify Perspective and Realistic Measure of Success
Buyer Intelligence can frame the field specification; Managed Demand Generation can honor those criteria during scoped delivery; Pipeline Activation can transmit approved data to the receiving owner. The passport is an editorial operating tool that a client can adopt or adapt, not a claim of a built-in software feature or certified control.
Measure sampled completeness of mandatory fields, disputed identity cases, role-mapping uncertainty, suppression exceptions and proportion of handoffs with acknowledged ownership. Disclose denominators and the observation window. The highest score is not the most optimistic account story; it is the most accurate and reviewable one.
Try the Passport on a Real Sample
Choose fifteen accounts from one campaign and complete the identity, fit, role, engagement and permission fields below. Compare the results with your current accepted-account count. Adapt the form to your policies before broader use.
Evidence Notes and References
References below support their specifically cited factual statements. Example workflows, criteria, matrices and test cases are proposed editorial frameworks, not verified client results. The availability of any Intent Amplify service component depends on agreed engagement scope. All links were reviewed during preparation on October 23, 2026.
- Intent Amplify, Buyer Intelligence. https://www.intentamplify.com/solutions/buyer-intelligence
- Salesforce Help, Create Parent and Child Account Relationships (April 2, 2026). https://help.salesforce.com/s/articleView?id=000391142&language=en_US&type=1
- Microsoft Learn, Detect Duplicate Data with Match Codes and Rules. https://learn.microsoft.com/en-us/power-platform/admin/detect-duplicate-data
- US Federal Trade Commission, CAN-SPAM Act Compliance Guide for Business. https://www.ftc.gov/business-guidance/resources/can-spam-act-compliance-guide-business
- Intent Amplify, Pipeline Activation. https://www.intentamplify.com/solutions/pipeline-activation
- HubSpot Knowledge Base, Use Contact and Company Lifecycle Stages (updated October 20, 2026). https://knowledge.hubspot.com/records/use-lifecycle-stages
