DEV Community
Follow
Don't overwrite browser observations with enriched contact data
Contact pipelines often begin with browser session observations and email addresses from external providers. Combining these into a single email field can be convenient but obscures the origin of the data. This approach explores the trade-offs between pre-built workflows and custom integrations, particularly when browser extractions and enrichment disagree. It emphasizes the importance of preserving evidence, even when data is unavailable or conflicting.A blank observation from a browser, such as an inaccessible page or no visible email, is still valuable data. It signifies that an email was not found through that specific method and should be recorded as such, not mistaken for proof of non-existence. Recording access outcomes and field outcomes separately allows for informed follow-up actions. It is crucial to retain the original browser observation even after a provider lookup, as provider results should augment, not overwrite, initial findings.The text illustrates this with a fictional data structure where a browser observation indicates no visible email, while a provider returns one. This highlights that a deliverable address doesn't inherently confirm identity match. The reverse scenario, where a browser shows an email and a provider yields nothing, also requires preserving the observed address and its source. Different stages of data processing—observation, verification, and acceptance—require distinct fields to maintain clarity and traceability.Explicit outcomes for various scenarios, such as unresolved identity or provider failure, should be defined. Retries should add new evidence without replacing previous observations, preserving timestamps and provider details. This allows for a clear history of attempts and their outcomes. Ultimately, the choice between a dedicated tool and a custom integration depends on the need for source preservation, custom decision-making, and effective exception handling. A reviewer should always be able to trace the origin of data, the checks performed, and any outstanding issues.