Before you set up data destinations to load aggregating marketing data into your database or platform, learn about the different data schemas that are available.
For the data schemas for user-level data, see Data Destinations: User-Level Data Schemas.
For an introduction to Singular data destinations and how they work, see Singular Data Destinations (ETL) FAQ.
When you use Singular data destinations, Singular standardizes data from different sources into the same data schema so you can easily query on it in your database.
Singular offers a choice of data schemas. Each schema defines a different set of dimensions and metrics that the Singular data destination will load into your database. Use the table below to help you choose the data schema that best fits your needs.
Data Schema Options
Note: For more information about each field, see Metrics and Dimensions.
The available data schemas are:
- Campaign data: Useful for campaign- and network-level optimization. Keeps your data footprint small and manageable.
- Campaign and keyword data: Supports keyword-level optimization for search campaigns.
- Campaign, keyword, and publisher data: Helps you optimize publisher-based bids, whitelists, and blacklists. May create large volumes of data!
- Campaign and creative data: Supports creative-based optimization.
- Ad monetization data: Helps you track your ad revenue.
| Campaign data | Campaign and keyword data | Campaign, keyword and publisher data | Campaign and creative data | Ad monetization |
|---|---|---|---|---|
| Dimensions: data_connector_ source_name data_connector_ id data_connector_ username data_connector_ timestamp_utc app source os platform country_field adn_sub_adnetwork_ name adn_account_id adn_account_name adn_campaign_id adn_campaign_name adn_sub_campaign_id adn_sub_campaign_ name adn_campaign_url |
Dimensions: data_connector_ source_name data_connector_ id data_connector_ username data_connector_ timestamp_utc app source os platform country_field adn_sub_adnetwork_ name adn_account_id adn_account_name adn_campaign_id adn_campaign_name adn_sub_campaign_id adn_sub_campaign_ name adn_campaign_url keyword_id keyword |
Dimensions: data_connector_ source_name data_connector_ id data_connector_ username data_connector_ timestamp_utc app source os platform country_field adn_sub_adnetwork_ name adn_account_id adn_account_name adn_campaign_id adn_campaign_name adn_sub_campaign_id adn_sub_campaign_ name adn_campaign_url keyword_id keyword publisher_id publisher_site_id publisher_site_name |
Dimensions: data_connector_ source_name data_connector_ id data_connector_ username data_connector_ timestamp_utc app source os platform country_field adn_sub_adnetwork_ name adn_account_id adn_account_name adn_campaign_id adn_campaign_name adn_sub_campaign_id adn_sub_campaign_ name adn_campaign_url creative_type adn_creative_id adn_creative_name creative_url creative_image creative_text creative_width creative_height creative_is_video asset_id asset_name |
Dimensions: data_connector_ source_name data_connector_ id data_connector_ username data_connector_ timestamp_utc date etl_query_ timestamp_utc app source os platform ad_country ad_type_id ad_type_name ad_placement_id ad_placement_name instance_id instance_name original_revenue_currency |
| Metrics: adn_cost adn_original_cost adn_original_currency adn_impressions adn_clicks adn_installs |
Metrics: adn_cost adn_original_cost adn_original_currency adn_impressions adn_clicks adn_installs |
Metrics: adn_cost adn_original_cost adn_original_currency adn_impressions adn_clicks adn_installs |
Metrics: adn_cost adn_original_cost adn_original_currency adn_impressions adn_clicks adn_installs |
Metrics: ad_requests ad_impressions ad_clicks ad_revenue original_ad_revenue |
FAQ
Can I change the data schema in the future?
Once you create and save the data destination, you cannot switch to another data schema. This is because changing the table structure in a live database with existing data comes with a number of dangers and complications.
If you need a data schema change, simply create a new destination. You can either delete the old table before creating the new destination or configure the new destination to load data to a new table with a different name. This process will ensure that your data stays safe and existing queries and work-loads continue working.
Can I create a custom data schema?
Singular supports custom schemas for premium customers. Any field supported in Singular's API is also supported in Singular data destinations (see Metrics and Dimensions for a full list). If you need a specific combination of fields that is not found in the existing schemas, discuss it with your Singular Customer Success Manager or contact Singular's support team.
