How should PartnerStack leads be deduplicated?
Short answer: Define the account and contact matching rules in your CRM, preserve PartnerStack's lead and partner identifiers, and make the outcome visible to both sales and partnership teams. A duplicate submission should not automatically create a second opportunity or second reward. It should also not silently discard a legitimate referral to a different business unit or product.
PartnerStack's lead submission testing guide explicitly tells implementers to test duplicate leads if duplication checks were configured with the integration specialist. That wording matters: it does not establish a universal, default deduplication algorithm for every PartnerStack account. This guide describes a defensible merchant workflow, not a claimed built-in rule.
Know the difference between Lead, Deal and CRM Account
A PartnerStack Lead typically represents a referral submitted for vendor follow-up. A Deal is often more suitable for reseller or co-selling activity where the partner updates pipeline progress. Access to both objects is plan-dependent, as documented in PartnerStack's Leads and Deals introduction. A CRM Account is your internal company identity, while Contact and Opportunity records may be linked to it.
Deduplication should operate across those objects without treating them as identical. Two contacts at one company might be one buying committee; two opportunities at that company may be genuinely different purchases. See our PartnerStack Leads versus Deals guide before designing the mapping.
Create a tiered matching policy
| Signal | Suggested action | Caution |
|---|---|---|
| Exact CRM account ID or verified company identifier | Strong match to existing company | Still check product and opportunity scope |
| Exact normalized contact email | Check contact and linked account | One person can consult for multiple companies |
| Verified corporate domain | Potential account match for review | Shared domains and subsidiaries exist |
| Company name similarity | Manual-review candidate | Names and abbreviations are ambiguous |
| Existing open opportunity for same product | Likely competing submission | Review original sourcing and registration dates |
| Different product or subsidiary | May be a valid new opportunity | Apply the published program scope |
Never use domain matching as an irreversible auto-rejection rule. A large group can have separate buying teams and subsidiaries, and generic email domains provide weak company identity. Keep an auditable manual-review state for ambiguous cases.
Preserve PartnerStack keys in the CRM
PartnerStack's Lead to CRM integration guide recommends CRM string fields partnerstack_partner_key and partnerstack_lead_key. Its example maps the PartnerStack Lead key into CRM, then uses it to update the originating Lead when the CRM stage changes. These keys are essential for idempotent synchronization and attribution history.
Store an additional internal account key and, where applicable, an opportunity key. If a second submission matches an existing record, attach the new submission as a review event rather than overwriting the original partner key. Retain both timestamps and the reviewer decision.
A practical duplicate decision workflow
- Receive: accept the referral with the submitting partner, submitted timestamp, company and contact information.
- Normalize: normalize email casing and company-domain formatting without discarding the original fields.
- Search: match existing contacts, companies and open opportunities in the CRM using your tiered policy.
- Classify: mark as new, possible duplicate, existing customer, existing open opportunity or valid new expansion opportunity.
- Assign: route ambiguous cases to a partner operations owner before the SLA expires.
- Decide: approve, merge with preserved history, reject with a documented reason or open a separate eligible opportunity.
- Sync: write the final status back to PartnerStack using the original Lead key.
- Audit: keep the decision, source records, reviewer and effective program rule version.
When a Lead moves to Closed Won, PartnerStack's lead submission guide describes checking that the associated customer record was created. Your commission system must still confirm the separate reward eligibility and billing events; a Closed Won CRM stage is not proof that cash was collected.
Worked example: two partners submit the same prospect
Partner A submits a referral for Acme Labs on 3 November. Sales accepts it on 4 November and creates Opportunity 100. Partner B submits another contact at the same company on 6 November for the same product and buying project. Under a hypothetical first-accepted-qualified-lead policy, Partner A retains sourcing credit, and Partner B's submission is logged as a competing referral. A human can review whether B materially influenced the deal, but the system should not generate two acquisition rewards by default.
If Partner B instead refers a separate Acme subsidiary purchasing a different product six months later, the record may be a legitimate expansion or new opportunity. The program must decide based on account hierarchy, product scope and published eligibility, not simply the corporate domain. Our partner deal registration rules discusses ownership windows and conflicts.
Avoid over-collecting personal information
Only collect information necessary to qualify and route a referral. Follow the consent and lawful processing requirements applicable to your markets, especially when a partner supplies third-party contact details. Restrict partner visibility to the fields and statuses their role requires. Duplicate detection should not leak the existence or details of another partner's confidential opportunity.
Integration acceptance tests
- Submit the same contact twice from the same partner and confirm one actionable opportunity.
- Submit the same company from two partners and verify a reviewable conflict, not silent reassignment.
- Test different contacts at the same company, and subsidiaries with similar names.
- Confirm Lead keys survive CRM updates, merges and retries.
- Verify New to Qualified, New to Unqualified, and Qualified to Closed Won or Lost mappings.
- Confirm the partner sees an appropriate status without private CRM notes.
- Test a previously rejected lead that returns after the ownership window expires.
- Reconcile reward eligibility independently from CRM stage and duplicate classification.
Frequently asked questions
Does PartnerStack automatically reject every duplicate email?
Do not assume so. The documented integration flow treats duplicate checks as something to configure and test with the integration specialist.
Can two partners receive credit for one company?
Possibly, for different opportunities or under a defined influence-sharing program. Do not create duplicate acquisition commissions accidentally.
Should a duplicate Lead be deleted?
Usually an audit trail is safer. Keep the original submission, status, matching evidence and decision rather than erasing a disputed source.
Sources and editorial disclosure
Sources checked 2 November 2026: PartnerStack Lead Submission Flow, Sync Leads to CRM, and Introduction to Leads and Deals. Suggested matching rules are editorial recommendations, not assertions of default PartnerStack behavior or independent account testing.