Reconcile duplicate leads and advertising conversions

Separate people, inquiries and events

A duplicate conversion is a repeated count of what the measurement definition intends to treat as one event or outcome. A duplicate contact is a different problem. One person can make several legitimate inquiries, and one inquiry can create several legitimate activities.

Write down the units before merging anything. A customer requesting two separate projects should not lose the second opportunity because their email address matches. At the same time, refreshing a confirmation page should not create a second sale.

Identify where duplication enters

A repeated provider request and a second genuine customer inquiry require different handling. A blanket “remove matching emails” rule can damage the sales history while failing to address duplicate event delivery.

Resolve duplicates without erasing the useful history

A prospect can submit a form and then call about the same request. Those are two interactions, but they may belong to one opportunity. Another form from the same person months later may represent a genuinely new project. An email address alone is therefore not a complete opportunity-deduplication rule.

Begin by naming the object the report counts. Use stable source identifiers for delivery retries and event records where available. Link related interactions to a person and opportunity, preserving their original timestamps and source context. Merge only when the evidence and the written business rule support it.

When you correct a duplicate, retain an explanation of the change so a later review can understand why totals moved. Test both directions: repeated delivery must not create new outcomes, while a real second project must not disappear. If the evidence is ambiguous, flag it for review instead of silently choosing the result that improves the dashboard.

Test these four cases

• The same form delivery is retried with the same source identifier.
• A form and a phone call refer to the same open project.
• An existing customer starts a separate project.
• Two people share contact information or submit on behalf of the same organization.

Preserve history while fixing the counting rule

Keep the activities that explain what happened. A person may submit a form and call later because they have not received a response. The call is valuable workflow evidence even when the report counts one acquired inquiry.

For an illustrative project, record one inquiry, two calls, one quote and one confirmed booking. A report can show those activity counts separately. It should not add them together and call the total five leads.

Test repeated and uncertain delivery

1. Define the stable identity of each counted event.
2. Send the same controlled event twice and check the intended result.
3. Simulate a retry after an uncertain response using the supported test method.
4. Check a genuine new inquiry from the same person.
5. Verify that corrected or cancelled outcomes follow their own documented rules.

The test must cover both false duplicates and missed duplicates. A rule that prevents all repeated records can still be wrong if it blocks legitimate repeat business. Keep uncertain matches visible for review rather than applying an irreversible merge by guesswork.

Reconcile the reporting impact

After a repair, document the effective date and whether historical reports were restated. A sudden drop in conversion count may reflect corrected counting rather than a decline in demand. Compare genuine inquiries and later outcomes to understand the business effect.

Growth Control scopes duplicate handling across intake, CRM and the supported measurement path. The goal is a reliable definition and a process that preserves customer context, not simply a smaller number in one dashboard.

Questions and answers