Describe a journey before joining data
Choose a concrete sequence, such as selection guide → demo request → sales conversation. Define a qualified enquiry. Existing customers should not be counted as new acquisitions without justification. Personal identifiers should never appear in public links.
Collect what the response requires
A contact form may need a topic and reply address rather than every detail about a prospect. Explain purpose and recipients. Limit data access and document retention. Consent and applicable requirements need a review suited to the actual service.
Reconcile without overinterpreting
Separate observed origin, estimated attribution and the customer’s own explanation. Missing data does not justify invented attribution. Report qualified enquiries, topics and useful responses without publishing identifiable people in an accessible dashboard.
- Journey
- Purpose
- Collection
- Reconciliation
Worked example
An enquiry from a compatibility guide can retain its topic and permission to reply without copying the reader’s entire browsing history into a sales record.
Check before moving on
These checkboxes are not saved.
Sources & method
Sources reviewed on 1 October 2026. Worked calculations use explicitly hypothetical inputs.
Topic provenance: Pourquoi SEO et eCRM sont faits pour travailler main dans la main… (2010-02). Search Engine Feng Shui. Byline retained in the publication feed: fhouste.
This guide is newly written in 2026. It does not reproduce the earlier text and is not attributed to its historical author.