CRM sync & attribution
How captured leads become CRM contacts with session context, lead scoring, and UTM attribution.
Capture to contact
Every popup submission and concierge capture becomes a GrowthLead, then syncs into your ThorStack CRM as a contact. Because Growth is part of the same operating system, there's no integration to maintain, the lead arrives with:
- the session history that preceded it (pages, events, the funnel step it converted on),
- the UTM source that brought the visitor,
- a server-side lead score.
Why one tenant matters
In a typical stack, the popup tool, the chat tool, the analytics tool, and the CRM each hold a fragment of the visitor. Here they're one record. The deal in CRM, the inbox thread, the order in Commerce, and the invoice in Finance all attach to the same contact the embed captured, so "which campaign produced this closed-won deal?" is one report, not a reconciliation exercise.
Attribution
Because the captured lead carries its UTM source and session history into the CRM, marketing-sourced pipeline is reportable end to end, from the ad click, through the page and popup that converted, to the deal that closed.
Sync log
CRM syncs are recorded (a GrowthCrmSyncLog) so you can audit what synced and when, and retry failures.
Next
- Funnels & segments, turn captured behaviour into cohorts.
- CRM module, what the lead becomes once it lands.