Ad Groups are used to configure inventory targeting and pricing within a Campaign. The user defines a variety of targeting parameters such as minimum and maximum OS version, location, inventory, etc and specifies the bid price for that demographic and which Creatives should be shown to that demographic/audience. BidSheet allows a multitude of demographic varieties to be targeted each with a unique Bid Price and Creative. This makes creating and managing hundreds or even thousands of Bids and optimizing ROI exceptionally simple.
BidSheet uses a simple CSV template to interface with all of your Bids. Each row in the CSV represents a unique Bid, which should include the Bid Price, Creatives, and Targeting Parameters. Apply Bid Parameters based on the headers provided in the BidSheet CSV template. Note that for all columns except bid and pricing, if a cell is blank, no specific targeting for that bid parameter will be applied.
Bid Sheet Targeting Parameters
|Column Name||Parameter Description|
|language||Language: target inventory by user specified device language. Use 2 letter country code ISO639-1.|
|country||Country: target inventory by user specified device country. Use 2 letter country code ISO3166-2.|
|app_bundle_id||App (Bundle ID): target inventory by matching app bundle ID. Reference target App Store ID based on platform. Note that only app_bundle_id or hashed_app_id can be used per BidSheet row.|
|hashed_app_id||App (Hashed ID): target inventory by matching hashed app ID. Note that only app_bundle_id or hashed_app_id can be used per BidSheet row.|
|zone_type||Zone Type: target zone inventory based on Zone Type (rewarded, interstitial, banner).|
|zone_skip||Zone Skip: target zone inventory based on Zone Skip properties (true, false).|
|zone_uuid||Zone: target zone inventory by matching hashed zone ID.|
|session_view_position||Session View Position: target zone inventory based on Session View Position. Use an integer to represent the desired position.|
|os||OS Range: target inventory based on device OS. A range of OS versions can be selected or a single version. Use ‘-’ to separate min and max OS versions when specifying an OS range (ie: 10-14). Use ‘x’ to specify no limit when specifying min or max OS within an OS Range.
|device_type||Device Type: target inventory based on device type. Options can be either phone, tablet, or ipad.|
|device_model||Device Model: target inventory based on device model.
Model number lists:
AdColony also uses device atlas to record and store detailed device information, which can be found on the devices_device_atlas table here (coming soon).
|segment_id||Segment: target a group of devices based on matching Device IDs. Use Segment ID. Segment cannot be used alongside any other targeting parameters. Only Creative, Pricing, and Bid can be specified in the same bid as a Segment.|
|creative_id||Creative: per bid, distribute the specified Creative. Use Creative integer ID found in the Creative URL in the Portal (ie: 256693).|
|pricing||Bid Type: bid based on CPM, CPCV, or CPI.|
|bid||Bid Price: bid up to a specified amount for the selected bid (in USD)|
Rule Prioritization and Conflict Resolution
In scenarios where BidSheet targeting rules overlap, BidSheet will choose whichever targeting rule has more defined parameters.
In scenarios where both rules have the same number of defined parameters, BidSheet will prioritize targeting rules which contain parameters with higher specificity. The columns in the schema above (except for pricing and bid) are presented in order of specificity.
In cases where the prioritization is the same across more than one targeting rule, BidSheet will take whichever rule contains the highest bid.
When using segment_id, no other targeting rules can be used.
- Override – replace the existing bidsheet CSV with the new bidsheet CSV
- Add – add new rows to the existing bid sheet CSV
- Remove – remove specific rows from the existing bid sheet CSV
- BidSheets are applied at the Ad Group level within a Campaign.
- In order to blacklist serving Ads to a particular demographic of users, enter 0 for the Bid’s Bid Price.
- Since larger BidSheets generally have longer processing times than shorter BidSheets, it is recommended to use add, override and remove such that the csv you need to upload is the smallest possible. This reduces processing time.