At a glance
A repeated person, a second content request and a new colleague at an existing account are different cases. Your campaign agreement should say which count towards delivery and which are excluded. This guide helps buyers review lead files and recognise genuine buying-group coverage without paying twice for the same agreed output.
Your syndication partner sends a lead file, and your sales team recognises several company names. Are those leads duplicates? You can’t decide from the company column alone. A new contact in a relevant function may add useful coverage at an account you already know.
Equally, an existing contact requesting a second asset has created a new response, but may not count as a new lead under your agreement. If you haven’t specified what “new” means, both sides can review the same file and reach different conclusions.
Turn zero-duplicate delivery into a reproducible test
Our media-house campaign reports zero duplicate leads alongside full lead acceptance. That campaign met its agreed duplicate rules. Yours may use a different comparison set, so agree exactly what will be checked before treating the result as a useful comparison.
A usable clause might say: “Count unique accepted people across this campaign, checked against the supplied suppression file effective on the agreed date; additional eligible people at the same account are permitted.” This is illustrative wording to agree with the provider, not a quotation from that client’s contract. If the objective is new accounts instead, the clause and counting unit must change.
Test the rule on awkward records before delivery: a second email for the same person, a new colleague at an existing account, a former employee now at another company, and a contact added to suppression after capture. Record the decision and the version of the rule used. Keep the engagement event even when it is excluded from the billable count.
Our verification and delivery methodology provides the wider acceptance process. The useful assurance is that both parties can reproduce the result from the record and agreed rules. “No duplicates” without those rules is an incomplete specification.
Agree whether you’re buying responses, people or accounts
An event is a recorded action, such as a registration. A person is a distinct individual. An account is the eligible business entity. A buying responsibility is the role in a particular decision that the person may cover.
One person can generate several events. Several people can belong to one account. Several people may also share the same function, while one person can hold more than one responsibility. None of those relationships should be assumed from the row count alone.
For a campaign concerned with account breadth, count distinct accounts. For a campaign seeking new stakeholders, count distinct relevant people and the responsibilities they add. For a content test, repeated engagement may be useful history even when it isn’t a new billable lead.
Put the duplicate rules in the campaign brief
| Case | Reporting treatment | Commercial question to agree |
|---|---|---|
| Same person repeated in one file | One person, multiple rows to reconcile | Is the repeated row rejected? |
| Same person requests a second asset | New event, existing person | Does the campaign buy responses or unique people? |
| New person at an existing account | Additional person, same account | Is buying-group expansion in scope? |
| Existing CRM contact responds again | Existing person with new activity | Is the campaign restricted to net-new contacts? |
| Person changes employer | Same individual, changed employment context | Does eligibility and suppression need review? |
| Two brands under one parent | Depends on the approved account unit | Are operating businesses counted separately? |
Write down where the duplicate check applies. Within this batch? Across the whole campaign? Across several partners? Against your CRM? “No duplicates” sounds clear until two teams use different comparison sets.
Also define the identifiers and review process. Exact email matching is useful but may miss secondary addresses or job changes. Name similarity alone can incorrectly merge different people.
Distinguish data deduplication from campaign counting
HubSpot’s deduplication documentation describes email, domain and record identifiers used to manage records. Those mechanics don’t determine whether a repeated response is billable under your campaign agreement.
Keep engagement events when consolidating person records. Otherwise, cleaning the database can erase useful evidence about the journey. Preserve source campaign identifiers and timestamps so the team can reconstruct what happened.
Account matching also affects the count. A group domain may conceal several operating businesses, while several domains may belong to one account. Use the campaign’s approved entity rules rather than allowing the import format to decide account coverage.
How one lead file can produce several valid counts
Consider a fictional file containing 100 response rows. Ten rows repeat people already present in the same file, leaving 90 unique people. Those people belong to 50 eligible accounts. Twenty of the 90 people already exist in your CRM.
The report can show 100 events, 90 unique people, 70 people new to that CRM and 50 represented accounts. None of these counts is inherently the correct billable total until the agreement specifies the unit and exclusions.
Suppose twelve new contacts add a previously unreached function at their accounts. That may be useful buying-group expansion even though it adds no new companies to the reach total. Verify their responsibilities and report the gain separately, so your team can see what the campaign added.
If the contract requires net-new people only, the existing twenty need the agreed treatment. Their new engagement can still be useful to the account team even if it doesn’t count towards the delivery commitment.
Check what the new contact adds to account coverage
A new name at an account doesn’t automatically fill a new buying responsibility. Two marketing managers may do similar work. A finance contact may not be involved in the relevant purchase.
Use separate statuses for identified role, verified responsibility and substantive engagement. This prevents the campaign from claiming committee coverage merely because it collected varied job titles.
LinkedIn’s buyer-identification guidance emphasises relevant stakeholders and relationships within accounts. The practical counting lesson is to measure the coverage the evidence supports, rather than treating every added contact as a decision-maker.
Our guide to buying-group coverage in ABM explains how that distinction relates to progression.
Apply suppression at the right level
A person-level suppression excludes the individual under the agreed rule. An account-level suppression can exclude colleagues as well. A parent-group suppression may be broader still.
Record the file version and effective date used for each delivery. If you supply an updated suppression list halfway through a campaign, agree with the provider when the new version applies. Retrospective disputes are harder to resolve when neither side can reproduce the comparison.
You may deliberately want to re-engage known contacts or reach another function at an existing customer. Record that choice in the brief. A documented exception makes the campaign more precise; an informal exception after delivery makes the rules harder to apply.
Resolve disputed leads against the agreed rules
For a disputed record, retain the delivery ID, person identifier, account association, response timestamp, suppression version and applicable counting rule. That evidence should allow both teams to reach the same conclusion.
Use reason codes that distinguish repeated person, ineligible account, existing-contact exclusion and insufficient qualification. Combining every rejection under “duplicate” prevents the team from fixing the actual issue.
Before launch, agree how disagreements are reviewed and what constitutes an accepted replacement. Talk to ABM Logic about delivery specifications so buying-group expansion and duplicate control support the same campaign objective.
