CAR-607 · cur8-mob

Deal Details V3 Analytics Plan

Tracking plan for the DDV3 screens under src/screens/deal, following the onboarding conventions and the shared @ifgengineering/client-analytics package.

How analytics works in cur8-mob today

Single source of truth: all event names and payload types live in packages/client-analytics (types.ts AnalyticsActions map + the switch in index.ts that maps action keys to wire names). No local constants files.
Wire naming: cur8:<camelObject>_<action> (e.g. cur8:dealDetails_pageViewed, cur8:onboardingQuiz_passed). Properties are snake_case.
Firing: useAnalytics / useTrackEvent for interactions, useScreenView for focus-based page views. track() fans out to Mixpanel (EU) and Customer.io. app: "Cur8" and channel: "mobile" auto-attach.
Privacy: method, screen, action, outcome, reason only. No email, phone, address, free text, or other PII in properties.

What DDV3 already fires

Event	Props	Where
`cur8:dealDetails_pageViewed` / `cur8:portfolioDetails_pageViewed`	`investment_name`, `source: "DDV3"`	Main screen on mount
`cur8:dealDetailsTab_clicked`	`deal_name`	Details tab selection only (Activity direction untracked)
`cur8:dealDetailsInvest_clicked`	`cta: "investNow"\|"addMoney"`, `deal_name`	Sticky CTA, add money, new commitment
`cur8:dealDescription_read`	`deal_id`, `max_scroll_depth_pct`, `time_on_page_seconds`	Description screen on unmount
`cur8:earningsCalendarEntryPointClicked`	`deal_name`, `deal_id`, `is_investor`	Earnings calendar CTA
`cur8:dealDetailsEditCommitment_clicked`	`deal_name`, `entity_name`, `type: "oneOff"`	Payment receipt modify action
Activity timeline card clicked	`dealName`, `activityType`	Payment + reallocation rows only
Document page viewed	`source: "Timeline"`, `page: "deal docs"`	Manage drawer documents

Legacy parity check

The old screen (home/dealDetails/) fires: page view, invest clicked, watchlist toggle, earnings calendar, generate statement, deal tour. DDV3 keeps page view, invest, and earnings calendar. Watchlist, statement, and tour don't exist in DDV3, so nothing to port.

The source: "DDV3" prop on shared events is what lets dashboards compare old vs new conversion. It must stay on every shared event.

Gaps and proposed events

P0Funnel and parity: do before rollout

Fix cur8:dealDetailsTab_clicked: fire on both directions, add tab: "details"|"activity". Also fire on swipe, not just toggle tap.
cur8:dealDetailsInvestBlocked_shown { deal_id, deal_name, reason: "kyc"|"cooldown"|"onboarding"|"closed" }: fired when a blocker/verify/24h modal intercepts the invest CTA. This is the funnel drop-off we currently can't see.
cur8:dealDetailsDocument_opened { deal_id, deal_name, document_title, document_category, action: "view"|"download" }: DocumentsSection rows and manage-drawer docs.
cur8:dealDetailsWhyWeInvest_pageViewed { deal_id, deal_name }: supporting screen currently has no event.
Extend activity row tracking to all 8 receipt categories via the existing triggerActivityTimelineCardClicked in use-activity-routing.ts (today only payment/reallocation rows fire).

P1Engagement

cur8:dealDetailsCalculator_used { deal_id, deal_name }: first interaction with the embedded calculator per screen view (once per mount). Full-calculator link reuses existing cur8CalculatorEntryPointClicked with entry_point: "deal_details".
cur8:dealDetailsVideo_played { deal_id, deal_name, video_type: "deal_video"|"webinar_replay" }
cur8:dealDetailsWebinar_clicked { deal_id, deal_name, action: "register"|"replay" }
cur8:dealDetailsGlossary_opened { deal_id, deal_name, term_key }
cur8:dealDetailsManageHolding_opened and cur8:dealDetailsManageHolding_optionClicked { option: "manageEarnings"|"moveToIsa"|"documents"|"liquidate" }
cur8:dealDetailsShariaCta_clicked { deal_id, deal_name }
Investment updates: reuse existing cur8:investmentUpdate_viewed / cur8:investmentUpdatesTab_clicked with a source: "DDV3" prop rather than new events.

P2Deliberately not tracking (noise)

Pull-to-refresh, back buttons, glossary dismiss, per-tick calculator slider changes, "Show all activity" expander, holding carousel swipes, bank account prompt (child already receives analyticsLocation), Dealbot open (existing cur8:dealBot_* family covers it), IF-ISA card (existing ISA funnel events cover the next screen).

Property conventions for new events

Every new event carries deal_id and deal_name (snake_case). Existing events keep their historical names (investment_name on page views); do not rename shipped events.
Shared events (fired by both legacy and DDV3 surfaces) must carry source: "DDV3".
Where useful, add is_committed: boolean and view: "details"|"activity".

Implementation approach

Package first: add payload interfaces to packages/client-analytics/src/types.ts (AnalyticsActions) and wire-name mappings to the switch in src/index.ts. Workspace symlink means no publish step for local dev.
One DRY hook: add use-deal-analytics.ts in src/screens/deal that pre-binds { deal_id, deal_name, source: "DDV3" } and exposes typed trigger functions, mirroring useCommitmentAnalytics.
Wire the P0 events, then P1, keeping each trigger at the interaction site (component/hook), never in redux.
Tests: jest contract tests asserting each trigger fires the right action key with the right props, matching the existing analytics test pattern.
QA: verify events in Mixpanel EU with the source: "DDV3" filter before enabling FF_DEAL_DETAILS_V3 more widely.

Open questions

Do we want watchlist in DDV3? If it returns, cur8:watchlist_buttonClicked already exists.
The cur8:dealDetailsTab_clicked change (both directions + tab prop) is additive but will shift existing dashboard counts; flag to whoever owns the dashboard.

Source: cur8-mob/src/screens/deal/ANALYTICS.md on branch CAR-607--Deal-Details-Mobile.