# Lead Activity and Engagement Date Crosswalk

Keep lead activity and engagement timestamps distinct when preparing an outreach review.

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

## Inputs
Lead IDs, Last Activity and Last Engagement values, activity log with occurred/logged times, associated contact/company and dated field definitions.

## Workflow
1. Match the lead to the exact primary association and source version.
2. Retain activity and engagement timestamps separately; do not treat a completed task as a buyer response.
3. Compare event occurrence and logging times, noting how the supplied field is calculated.
4. Return inconsistencies and unknowns without marking the buyer interested or sending outreach.

## Output contract
lead | activity_date | engagement_date | event_type | occurred_time | logged_time | buyer_response_unverified

## Fictional acceptance test
Fictional rep logs a call onOct 9 that occurredOct 8. The source Last Activity may useOct 8. A completed task onOct 9 is not evidence that the buyer engagedOct 9.

## 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-lead-properties

Checked October 9, 2026. Oct 9 live AIS Search Console through Oct 6: marketing Copilot 37 impressions, Planable/Claude 33, Planable/ChatGPT 23, campaign brief 12, investor agent 19. Social-review/reporting topics follow these parent-query leads. Other professions follow documented workflow needs, not measured exact search intent. Site impressions are not monthly volumes; exact topic volume is unmeasured.