Who this was forA client whose CRM automatically clones deals from one pipeline into others as they move along.
Deals we sourced were tagged on the original record. Then the client's own automation cloned those deals into other pipelines, and the clones didn't carry the tag.
So two honest ways to count our deals gave two different answers. A filter on the tag found fewer. A walk through the linked records found more. Our fee is calculated from that count, so both sides needed one number they could check.
A function that walks the chain of linked records and stamps every clone with the tag. A daily job reruns it, because the cloning automation never stops. Then a monthly audit report that checks the tag has propagated before it reports a single number.
It runs daily rather than once, because the cloning automation keeps creating new records, and a one time pass would go stale the next time it fires.
Once both counts agreed, comparing them stopped telling us anything. We kept the two columns side by side anyway, so month to month reports still line up.
The propagation function and its daily job run unattended in the client's CRM. We run the monthly audit.
If your CRM copies records between pipelines, check whether your attribution fields travel with them. If the numbers from a filter and a report don't match, send us both and we'll find where they split.
Related tools: Salesflare
Some of the links on this page are affiliate links.
Client names are always kept confidential at MMG, so they have been removed from this case study.
Published June 9, 2026
Last updated November 2, 2026