Portfolio demonstration with synthetic data

Tracing CRM acquisition sources

A fictional SaaS team wants to report how contacts entered its CRM. Some contacts have verified campaign evidence, others have only an import label, and some have conflicting records.

My role

I added acquisition source to qualified-lead reports, contributed to campaign attribution reporting, and drafted requirements for tracking how contacts entered the CRM.

How a source gets assigned

Gather evidence for each contact
Compare verified source claims
Assign a source or queue for review
Report coverage and exceptions

A verified record takes precedence over an import label. Conflicting verified records go to review. The optional fallback accepts an import label when verified evidence is missing and marks the assignment provisional.

Compare evidence policies

Allow provisional assignments from import labels

Coverage by policy

Source decisions for six fictional contacts
Contact	Verified evidence	Import label	Assigned source	Decision

The reporting trade-off

Accepting import labels gives one more contact a source in this example. Mark that assignment as provisional so readers can see how much of the report is verified. Route conflicting records for manual review and track how many provisional assignments are later confirmed or corrected.