Learn what fields are included when you set up a data destination to load user-level ad monetization data into your database.
- For general and setup info about data destinations, see Singular Data Destinations (ETL) FAQ.
- To export data about user-level ad monetization, you first have to configure Singular to gather that data. See Setting Up User-Level Revenue Reporting.
- Note: This schema is only relevant when using user-level API data from the mediation platform. If you're using Ad revenue from the SDK, see Data Destinations: User-Level (Event-Level) Data Schemas.
When you use Singular data destinations to export user-level ad monetization data, the exports include the following fields:
| device_id device_id_type platform app_longname app_version custom_user_id os_version ip attribution_event_timestamp attribution_event_timestamp_unix_utc is_reengagement is_view_through city country install_source state touchpoint_timestamp touchpoint_timestamp_unix_utc tag_id passthrough partner affiliate_id affiliate_name bid_type campaign_id campaign_name click_id creative_id creative_name publisher_concatenated publisher_hashed_id publisher_id publisher_name sub_campaign_id sub_campaign_name sub_publisher_id sub_publisher_name singular_campaign_name tracker_name revenue ad_impressions date currency ad_partner |