Twenty and Chatwoot: connect lead context to revenue
Keep Chatwoot conversation context and Twenty opportunity outcomes as distinct records linked by server-owned identity. ClickTrail provides local mapping examples for both boundaries. Those helpers do not establish a live connection between the products. A conversation with source data is not yet revenue attribution, and a won opportunity needs a verified relationship to the original lead.
By FunnelSheet · Technical guide
Keep Chatwoot conversation context and Twenty opportunity outcomes as distinct records linked by server-owned identity. ClickTrail provides local mapping examples for both boundaries. Those helpers do not establish a live connection between the products. A conversation with source data is not yet revenue attribution, and a won opportunity needs a verified relationship to the original lead.
What should Chatwoot retain?
The Chatwoot adapter documents click IDs in contact custom attributes. Verify the actual attribute names and inspect the stored contact after the handoff. Do not equate a new conversation with qualification or purchase. If the incoming payload contains tenant or identity fields, resolve those through your authenticated integration rather than trusting the browser.
What should Twenty contribute?
The Twenty adapter maps won-opportunity webhook data into conversion records. Verify which event indicates the intended business outcome and where value and currency originate. Preserve the opportunity ID alongside the linked contact or lead ID. A source field on one contact does not automatically establish the source of every associated opportunity.
How can I test the relationship?
Construct one synthetic lead, one conversation and one won opportunity. Document the expected joins before running the mapping examples. Test a missing relationship and two opportunities for the same contact. The system should expose uncertainty instead of allocating all revenue to whichever source record happens to be found first.
What happens on retries?
Replay the same won event and check that its destination event identity remains stable. A later stage change is not necessarily a new sale. The application still owns authenticated webhooks, consent checks, persistent retry handling and provider configuration. Confirm a destination receipt before claiming the revenue was reported.
Source and next step
Source reviewed on 2026-09-15: ClickTrail — twenty-chatwoot-lead-revenue-attribution.
Continue with ClickTrail examples.
Disclosure: FunnelSheet publishes ClickTrail guidance. These instructions describe source-level behavior, not an independent performance benchmark.