This table explains the Group By options in the Stats section of the Bidease UI - the fields you use to slice a report by country, publisher app, creative, exchange, device or time. Look an option up here before you act on the numbers, so you know exactly what each breakdown measures.
Time & Date
| Date | The calendar date of the record. Combine it with the date-range selector to break a report down day by day. |
| Day of Impression | The day the impression was served. Use it when the report should follow ad delivery rather than installs. |
| Day of Install | The day the attributed install happened. Use it for cohort views, where installs - not impressions - define the row. |
| Day of Week | The weekday of the record (Monday-Sunday). Useful for spotting weekly delivery and performance patterns. |
| Hour | The hour of the record, in the time zone shown in the UI. |
| Hour of Impression | The hour in which the impression was served. |
| Hour of Install | The hour in which the attributed install occurred. |
| Week | The calendar week of the record. |
| Month | The calendar month of the record. |
| Month of Impression | The calendar month in which the impression was served. |
Campaign & Product
| Campaign | The Bidease campaign that delivered the traffic. Autopilot campaigns are marked with [autopilot] in the name. |
| Custom Campaign | The custom campaign title set in the campaign settings. Use it when your own naming convention differs from the Bidease campaign name. |
| Product | The advertised app or product inside the advertiser account. All campaigns for one app roll up to it. |
| Advertiser Bundle | The store bundle or package identifier of the advertised app, for example com.example.app. |
| Engagement Goal | The specific user interaction within an interactive ad that is tracked as a desired engagement event, like Start, Unmute, Mute etc. |
| Goal ID | The unique identifier of the conversion/funnel event configured in the MMP and used as the campaign optimization or measurement goal. |
| Currency | The currency of the monetary values in the report. |
Creative
| Creative ID | The internal Bidease identifier of the creative. |
| Creative Name | The name of the creative as set in Bidease. |
| Creative Concept | The concept label that groups related creative variations - all sizes, languages and cuts of one idea. Lets you compare creative ideas rather than individual assets. |
| Creative Format | The ad format of the creative: banner, video, native, playable or interstitial. |
| Creative Hash | A technical fingerprint of the creative asset. Identical assets share one hash even if they were uploaded several times. |
| ERID | The ORD advertising token (ERID) attached to the creative, where required by local advertising regulation. |
Supply & Inventory
| Bundle ID | The bundle or package identifier of the publisher app - or the site domain - where the ad opportunity originated. |
| Bundle Name | The human-readable name of that publisher app or site. |
| Bundle IAB Category | The IAB content category assigned to the publisher app. Use it to review performance by content vertical rather than by individual app. |
| AdPlacement ID | The publisher's identifier of the specific ad slot inside the app, as passed in the bid request. |
| Exchange | The ad exchange or SSP that supplied the impression opportunity through the auction. |
| Deal ID | The identifier of the private marketplace (PMP) or programmatic deal used to buy the impression. |
| HasPMP | Whether the impression was bought through a PMP deal: 1 = PMP, 0 = open auction. |
| Rewarded | Whether the impression came from a rewarded placement, where the user gets an in-app reward for watching: 1 = rewarded, 0 = non-rewarded. |
| Impression Width | The width of the ad slot in pixels, as declared in the bid request. |
| Impression Height | The height of the ad slot in pixels, as declared in the bid request. |
Auction & Pricing
| BidCPM | The CPM value Bidease bid in the auction, including bids that did not win. |
| Publisher Bid Floor | The minimum CPM the publisher or supply partner was willing to accept for the impression. |
Geo
| Country | The country the ad request came from. |
| Region | The state, province or region of the ad request, when available. |
| City | The city of the ad request, when available. |
| ZIP Code | The postal code of the ad request, when passed by the supply partner. |
| Latitude | The latitude of the ad request, when the publisher passes location data. |
| Longitude | The longitude of the ad request, when the publisher passes location data. |
Device & User
| Device OS | The operating system family of the device: iOS or Android. |
| OS Version | The operating system version reported by the device, for example 17.5.1. |
| Device Brand | The manufacturer of the device, for example Apple or Samsung. |
| Device Model | The device model reported in the bid request. |
| Device Version | The hardware generation or variant of the device, for example iPhone 15 Pro Max. |
| Device Type | The device category: smartphone, tablet, desktop or connected TV. |
| Device Language | The language setting reported by the device. |
| Connection Type | The network connection used by the device - Wi-Fi or cellular. |
| Carrier | The mobile network operator or ISP of the user, when passed in the bid request. |
| Device Age Days | The number of days since Bidease first saw this device. Low values indicate new or recently reset devices. |
| Device Age Decay | A score derived from device age, used by the models to weight how long a device has been known to the platform. |
| IFA Traffic | Whether a device advertising identifier (IDFA/GAID) was present in the request: 1 = available, 0 = not passed. |
Traffic Quality
| Reject Reason | The normalised reason the MMP rejected an attributed install or event - bots, click flooding, short click-to-install time, anonymous IP, invalid signature and similar. Values are mapped to a single set of labels across Adjust, AppsFlyer and other MMPs. |
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article