Learn how to control the frequency & deduplication of data points in a buy order
Within a buy order, users can control how often they see & buy the same data point(s), and if so, in what time frame.
Define the Frequency
Uncapped: an uncapped frequency will buy every data point that fits the constraints of their order, no matter how often it is seen
- i.e. buy all MAIDs with In-App Purchase on GameApp in the past 30 days
- MAID 1234 <> IAP on 9/1
- MAID 1234 <> IAP on 9/10
- MAID 1234 <> IAP on 9/20
- MAID 1234 <> IAP on 9/30
- MAID 1234 will be bought 4 times using an uncapped frequency
Once per: choose the timeframe that you want to apply the deduplication
- select between [minutes, hours, days, weeks]
Deduplication Strategy: select data point(s) to deduplicate against, can select more than one, available data points will change depending on the buy order data package
Example
- buy all MAIDs with In-App Purchase on GameApp in the past 30 days
- Frequency = once per 30 days
- Deduplication Strategy (data point) = ID
- MAID 1234 <> GameApp <> IAP on 9/1
- MAID 1234 <> GameApp <> IAP on 9/10 -- duplicate MAID
- MAID 1234 <> GameApp <> IAP on 9/20 -- duplicate MAID
- MAID 1234 <> GameApp <> IAP on 9/30 -- duplicate MAID
- MAID 1234 will only be bought once given the frequency setting & deduplication strategy, even though there were 4 instances of an in-app purchase within the 30 day period
RELEVANT UI SCREENSHOT
Additional Examples
- Buy all MAIDs with a digital consumption type of In-App purchase or App Uninstall across all apps in the past 30 days
- Frequency = once per 30 days
- Deduplication Strategy (data points) = ID + URI (App)
- MAID 1234 <> GameApp <> IAP
- MAID 1234 <> GameApp <> App Uninstall
- MAID 1234 <> BookApp <> IAP
- MAID 5678 <> GameApp <> IAP
- MAID 5678 <> GameApp <> App Uninstall
- MAID 9999 <> RecipeApp <> IAP
- MAID 9999 <> BookApp <> IAP
- There are 2 instances that match the deduplication strategy of ID + URI, which will result in MAID 1234 & MAID 5678 to be removed in the bolded instances.
Deduplication Logic Between Line Items
Within a Buy Order can be multiple Line Items. Below are examples of the deduplication logic when using multiple line items under a single buy order.
Example 1
Orders with multiple line items that have both the same deduplication strategy AND frequency settings will deduplicate across each other, meaning one will consider what the other has already delivered and adhere to a single strategy between the line items with the same settings.
- Consider a Buy Order with two Line Items, each buying MAIDs against an app list with the same dedupe & frequency settings
- Frequency = once per 30 days
- Deduplication Strategy (data points) = ID
- Line Item 1: MAID 1234 <> GameApp
- Line Item 2: MAID 1234 <> BookApp
- In this instance, MAID 1234 will only be bought once between the two line items since dedupe & frequency rules are the same
Example 2
Orders with multiple line items that do NOT have the same deduplication strategy and frequency settings will be treated as distinct and not consider/respect the delivery of the other line items.
- Consider a buy order with two Line Items, each buying MAIDs against an app list with varying dedupe & frequency settings
- Line Item 1
- Frequency = once per 30 days
- Deduplication Strategy (data points) = ID
- Line Item 2
- Frequency = once per 30 days
- Deduplication Strategy (data points) = ID + URI (app)
- In this instance, both line items have the same Frequency but different Deduplication Strategies, meaning deduplication happens within each individual line item
- Line Item 1: MAID 1234 <> GameApp
- Line Item 1: MAID 1234 <> BookApp
- Line Item 2: MAID 1234 <> GameApp
- Line Item 2: MAID 1234 <> GameApp
- For Line Item 1, MAID 1234 will be bought once as the dedupe strategy is based on ID only
- For Line Item 2, MAID 1234 will be bought once as the dedupe strategy is based on ID +URI
Summary of Deduplication Logic Between Line Items
Line Items will be deduped based on the combination of [deduplication strategy + frequency + order id]. Line items with that same string will be deduplicated together, and line items with a different string will be deduplicated independently.
Strategy/Settings | Behavior with Multiple Line Items |
Different dedupe strategy and/or different frequency settings | Each line item will be deduplicated on its own regardless of the behavior of the other line items |
Same dedupe strategy AND same frequency settings | The line items with the same dedupe strategy AND the same frequency settings will deduplicate across each other, meaning one will consider what the other has already delivered and adhere to a single strategy between the line items with the same settings. If line item A and B have the same strategy, and line item C has a different one, line items A and B will respect each other, and line item C will run its own independent logic |
Different dedupe strategy, same frequency settings | Each line item will be deduplicated on its own regardless of the behavior of the other line items |
Different frequency settings, same dedupe strategy | Each line item will be deduplicated on its own regardless of the behavior of the other line items |