Prevent duplicates for campaign or buyer
Campaign level - lead, call & lead
Prevent lead duplicates for your lead / call & lead campaign by setting the period, during which duplicates won't be sent to this campaign (usually 30 days). This option is available for both Open PX buyers and Private marketplaces.
Perform the following:
1. Go to Campaigns, find the desired lead campaign, and click Action -> Campaign settings (lead or call & lead, depending on the type of your campaign).
2. Navigate to Commercial settings, click Edit, and enter the desired number of days into Duplicate prevention field:
If you have your own lead database, you can also adjust campaign filters based on account details such as email or phone number so that existing records are filtered out.
Deduplication can also be applied for the entire buyer account during the specified date range.
When buyer-level deduplication is enabled, campaign-level deduplication rules are ignored.
To configure deduplication on the buyer level, contact your manager at PX.
Lead duplicates are automatically filtered out on the platform level if the email address+vertical combination in the lead is already stored during the last 24 hours.
In this case, the lead duplicate is not sent to any campaign and has Filtered Duplicate buyer result in Transactions outbound report:
Automatic deduplication based on email+vertical combination can be skipped for certain direct post publishers. Contact your PX manager to know more.
Ping post approach
Ping post includes additional built-in deduplication for cases when the same lead comes to the PX platform from several different publishers in a short period of time.
When PX receives a ping request from the publisher, the system checks the following parameters of the lead:
Then the system checks whether the lead with such a combination of parameters came to the platform during the last 5 minutes.
If no similar leads have been found, the lead is processed according to the usual flow.
If the lead with such a combination (vertical + ZIP code + ping post type + source privateness) is found, it's marked as Duplicate Entry buyer result in Transactions ping post report: