# Deal Contacted and Activity Count Bridge

Explain why a deal has more sales activities than contact events.

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

## Inputs
Deal/activity IDs, activity types, association scope, both count exports and capture times.

## Workflow
1. Classify supplied activity types using the documented property definitions.
2. Keep notes and tasks in sales activities but out of times-contacted counts.
3. Deduplicate IDs within the supplied scope.
4. Return a count bridge without claiming each contact reached a buyer.

## Output contract
deal | sales_activities | contact_events | notes_tasks | export_scope | gap

## Fictional acceptance test
Fictional two calls, one email, three notes and two tasks yield 8 sales activities and 3 contact events in complete supplied scope. Three contact events do not prove three unique people.

## 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.