Table of Contents
Overview
Cross-Device amplification allows customers to leverage person- and household-level links during targeting to expand the available inventory and reach for a given segment. Our cross-device partners, FreeWheel ID Network and LiveRamp, are able to unify devices around two types of ‘link’:
Person Links grant the ability to connect the User IDs of devices that belong to a single individual. For example, a Chrome cookie linked to an IDFA would suggest that the user of both those devices is the same physical person.
Household Links connect all devices residing in the same physical household. For example, a Chrome cookie linked to a Safari cookie, two IDFAs, and three CTV IDs would suggest that all these devices reside at the same address (but could be used by different individuals within the household).
Cross-device can be applied at the Campaign or Line Item levels, and can be used to extend the reach of targeted segments. For example, if a user’s cookie ID is in a segment being targeted, then Beeswax will enable the Line Item to identify and target bid requests coming from any of the devices that FreeWheel ID Network or LiveRamp has linked to the cookie ID in question.
Cross-Device Amplification functionality can be applied using a number of settings:
| Setting | Description |
| None | (default) No change from existing behavior |
| Person | Line item will match on requests where the user id is a member of the targeted segment (standard behavior) AND requests where the user id is person-linked to another user id that is a member of the targeted segment |
| Person Extend Only | This ensures that only the cross-device functionality is leveraged when using a segment. Line item will match on requests where the user id is person-linked to another user id that is a member of the targeted segment, but will not target the source user IDs that exist in the segment. |
| Household | Line item will match on requests where the user id is a member of the targeted segment (standard behavior) AND requests where the user id is household-linked to another user id that is a member of the targeted segment |
| Household Extend Only | Line item will match on requests where the user id is household-linked to another user id that is a member of the targeted segment, but will not target the source user IDs that exist in the segment. |
Costs and Billing
A CPM fee is incurred for the use of cross-device amplification, which will come through as a Vendor Fee, which you can see in the Vendor Report. Current fees are indicated within the Buzz UI.
Getting Started with Cross-Device
If you’re interested in using Cross Device with Beeswax, please reach out to Beeswax Support to enable Cross-Device Amplification for your Buzz key. You can be enabled for FreeWheel ID Network, LiveRamp, or both. Please also let Support know if you would like to be enabled for cross device extension on 1st party segments or both 1st and 3rd party segments
Once it has been enabled:
1.To confirm a Beeswax Segment is eligible for use with cross-device, ensure the “Extensible” toggle option is set to “Yes” in the Edit Segment screen:
2. To set the default cross-device setting for an entire Campaign (and therefore all child Line Items), navigate to the Edit Campaign screen, select the desired "Extension Vendor," and set the “Segment Extension” field to the desired setting. Or, to set the cross-device setting for a specific line item, navigate to the Edit Line Item screen, select the desired "Extension Vendor," the “Segment Extension”, and the "Segment Type" fields to the desired setting.
Note: Segment Type will only be an option if you have 3rd party segment extension enabled.
Segment Type Options
| Option | What it means |
| None | Do not extend any segment |
| All Segments | Extend all 1st party and 3rd party segments |
| 1st Party | Extend 1st party segments only |
3. Set the Campaign or Line Item to Active and then Save & Close it to traffic the changes. The Line item(s) will serve as normal, and cross device will be applied in real time to any first party segments targeted by the line item.
Extension to Connected TV
In order to extend to Connected TV, select Household or Household Extend Only options and your line item will begin to target CTV connected device IDs as well.
When a customer selects Household or Household Extend Only options, below are the expected behaviors for CTV:
- Starting with Web (Cookies and/or device IDs for mobile web) → Extends to In-App Households AND CTV Households
- Starting with In-App (MAIDs) → Extends to Web Households AND CTV Households
- Starting with CTV (CTV IDs) → Extends to Web Households AND In-App Households
If a customer selects Person or Person Extend Only option it will work as follows:
- Starting with Web (Cookies an/or device IDs for mobile web) → Extends to In-App Persons
- Starting with In-App (MAIDs) → Extends to Web Persons
- Starting with CTV (CTV IDs) → Will not extend to any additional Persons as CTV IDs are not mapped to Person IDs
Vendor Details
- LiveRamp -- LiveRamp's graph is based on their Identity Link ID (IDL) and is deterministic, which requires multiple data points to say an ID is the same person or household. It is recommended for campaigns that require high accuracy.
- FreeWheel ID Network - Rapid privacy changes such as increased regulations and the depreciation of third-party cookies, device IDs, and IP addresses make it difficult for marketers to reach their target audiences, manage delivery, and measure outcomes. To overcome such challenges, FreeWheel’s Identity Network creates interoperability across various industry ID solutions, third-party IDs, and customer first-party identity assets to simplify workflows and enable privacy-safe, identity-enabled transactions.
Beeswax users utilizing FreeWheel’s Identity Network get a unified view of audiences across all supply pools and have the ability to scale addressable campaigns, accurately manage reach and frequency, and measure outcomes.
FAQ
Q: Can I use cross-device in Advanced QPS Filtering?
A: Yes! If you are contracted for Advanced QPS Filtering, ensure your Beeswax Customer Success Manager enables your traffic to include Cross-Device extended traffic.
Q: Can I use cross-device for attribution? Frequency capping? Reach reporting?
A: Yes, we support Reach Reporting and Frequency Capping for LiveRamp and FreeWheel ID Network. See here to learn more.
Q: How does cross-device work with bid modifiers?
A: If you are using segments in their bid modifier terms, the bid modifier will be applied to segments linked via cross-device as if those segments were associated with the original user id on the bid request.
Q: Are there geographic restrictions? What about GDPR?
A: Cross-device is only available in North American (NAM) data centers.
Q: Do we plan on adding other cross-device vendors? Can I use Drawbridge?
A: As of now, only LiveRamp and FreeWheel ID Network is supported, but other vendors may be added in the coming quarters.
Q: What is the use case for "Person Extend Only"?
A: Customers may want to bid differently or have different budgets for first party data vs extended data. This capability allows you to set up a line item that only has extended data.
Q: Do customers need any additions to their Beeswax contracts to access this feature?
A: No, all Beeswax customers can utilize this feature under their standard agreements. Contact your Beeswax Customer Success Manager to have this feature enabled.
Q: Why does CTV only extend to households and not persons?
A: Connected TVs exist in concept only at the household level. There are no plans for support at the person level.
Q: When targeting CTV, what if I extend on a line item without video creatives?
A: Standard matching will apply. If you don’t have video creatives on your line item you will be unable to match CTV inventory.
Q: What if I have video creatives but do not want to extend to CTV?
A: If you extend your audience, you should exclude “Connected TV” in Device Type targeting.
Q: Can I use cross device extension to extend the reach of IP segments?
A: No; you cannot use cross device extension from IP address segments to cookies/device IDs. Our integration only allows you to take segments of cookies/device IDs and extend them to IPs, not vice versa.