# Deal Source Association Fallback Register

Explain a deal traffic-source field using associated-record scope rather than the deal label alone.

## Scope
Preparation and review only. No account action or professional decision.

## Inputs
Deal ID, contact/company associations, original/latest source fields, source dates and capture times.

## Workflow
1. Separate Original source from Latest source.
2. Record the documented contact-based selection rules and company fallback when no contact exists.
3. Keep association changes and absent historical snapshots unresolved.
4. Return field provenance; no attribution or customer records are changed.

## Output contract
deal | source_field | associated_record | selection_rule | fallback | time | missing

## Fictional acceptance test
Fictional deal has no associated contact and company source Organic. Label this as company fallback, not a proved buyer first-touch. Adding a contact later does not reconstruct a missing historical snapshot.

## Review gates
Keep original values, source IDs and version dates. Unknown facts stay held. Use qualified review for hiring, legal and accounting conclusions. No send, share, sign-in, scheduling, ledger change or payment. Fictional contract review is not a live account compatibility test.

## Method source
https://knowledge.hubspot.com/properties/hubspots-default-deal-properties

Checked October 12, 2026. Oct12 live AIS Search Console: marketing Copilot37 impressions, Planable/Claude38, Planable/ChatGPT24, campaignbrief12, investoragent19, MuseIndia100. Social calendar/reporting topics follow parent-query leads; other professions follow documented workflow needs, not measured exact intent. Site impressions are not monthly volumes; exact topic volume is unmeasured.