---
title: "About Data Fields and Templates"
canonical: "https://hub.freewheel.tv/space/OS/113737783/About%20Data%20Fields%20and%20Templates"
format: markdown
---
Overview OneStrata provides a large number of pre-defined data fields that can be reused and combined to cover a wide range of media buying scenarios. Users can also create their own data fields as needed, enabling customized and flexible workflows. Templates define the layout of important OneStrata data grids, like the Schedule grid and Ad Server grid, by specifying which data fields are displayed and in which order. Data Fields Terms and Concepts This section contains information about terms and concepts related to data fields. Data Field Categories There are two categories of data fields: Data Field Category Description System Data fields provided by OneStrata that cannot be deleted. Depending on the system data field, different levels of user customization are allowed: No customization is allowed; or Renaming the data field is allowed Custom User-created data fields that can be edited and deleted. Data Field Types Data field restrictions Changes to picklists are applied to existing campaigns. Newly created picklists are only available for campaigns created after the picklist was created. For all other data field types, newly created data fields and edited data fields are only available for campaigns created after the data field was created or edited.  There are nine types of data fields: Data Field Type Description Calculated Formula A numeric value that is derived from one or more existing numeric fields. Concatenated Formula A text value that is concatenated from one or more existing fields. Currency A currency value. Date A date value. Number A numeric value, with up to 16 decimal places. Percentage A numeric value formatted as a percentage, with up to 16 decimal places. Picklist A dropdown list with one or more selectable options. Text A free-form text field. Only available if the schema level of the data field is Media Line Conversion Rate A percentage that converts from one  unit type  to another, like Click Through Rate (CTR) and View Through Rate (VTR). Conversion rates operate in both directions. For example, imagine a conversion rate that converts from impressions to clicks (CTR) at a rate of 0.7%: If the number of impressions is entered as 1,000, the number of clicks is automatically calculated as 7 (= 1000 x 0.007). If the number of clicks is entered as 50, the number of impressions is automatically calculated as 7,142 (= 50 / 0.007). Campaign Name Concatenated Formula Types A concatenated formula data field for a campaign name automatically generates a campaign name according to the defined naming conventions, making it easier and faster to create standardized campaign names. Four types of campaigns can have a concatenated formula for the campaign name: Campaign Type Description Media campaign The naming formula of a OneStrata campaign. Campaign Group The naming formula of a OneStrata Campaign Group. External Ad Server campaign The naming formula of an external Ad Server campaign (the name that the Ad Server provider uses for the Ad Server campaign). External DSP campaign The naming formula of an external DSP campaign (the name that the DSP provider uses for the DSP campaign). External Search Campaign The naming formula of an external Search campaign (the name that the Search provider uses for the Search campaign). External Social Campaign The naming formula of an external Social campaign (the name that the Social provider uses for the Social campaign). Data Field Versioning There are two levels of data field versioning: Versioning Level Description Data field schema Saving a change to any data field creates a new version of the entire data field schema. The most recent data field schema version is displayed on the  Manage Data Fields and Templates  >  Data Fields  tab, in this format:  Last Modified on <Month Day, Year> by <User>. Version (<N>) Picklist Saving a change to a picklist creates a new version of that picklist at that entity level. Edits to any other data fields (including other picklists at the same entity level) do not create a new version. Picklist Data Field Versioning OneStrata version 25.4.22 (released on May 7, 2025) introduced an update that  allows edited picklists to be available for existing campaigns : Editing a picklist creates a new version N of that picklist. New campaigns inherit the latest version N of this picklist. Any existing campaigns that were using the N-1 version of this picklist are updated and inherit version N of the picklist. This versioning restriction only affects campaigns created before the release of OneStrata version 25.4.22, as summarized in the table below: Creation Date Description Campaigns created before the release of OneStrata version 25.4.22 May inherit the latest version of a picklist. Campaigns created after the release of OneStrata version 25.4.22 Always inherits the latest version of a picklist. The following table provides examples of campaigns created before the release of 25.4.22 that do and do not inherit the latest version of a picklist. Description "Custom Picklist" Version The  Custom Picklist  data field is created → v1 The possible options in v1 are  A  and  B . v1 Campaign #1 is created and inherits  Custom Picklist  v1. v1 Custom Picklist  is edited (a new value is added) → v2 The possible options in v2 are  A ,  B , and  C . v2 Campaign #2 is created and inherits  Custom Picklist  v2. v2 The  Custom Campaign Name  concatenated formula data field is created and later edited. These actions do not affect the version number of  Custom Picklist . v2 OneStrata version 25.4.22 is released (May 7, 2025). v2 Custom Picklist  is edited (a new value is added) → v3 The possible options in v3 are  A ,  B ,  C , and  D . Campaign #1 was using  Custom Picklist  v1, which is more than one version ahead of the new v3. Campaign #1 continues to use  Custom Picklist  v1. The changes to  Custom Picklist  are not applied to this campaign. Campaign #2 was using  Custom Picklist  v2, which is the version immediately preceding the new v3. Campaign #2 inherits  Custom Picklist  v3. The changes to  Custom Picklist  are applied to this campaign. v3 Campaign #3 is created and inherits  Custom Picklist  v3. v3 Custom Picklist  is edited (a value is removed) → v4 The possible options in v4 are  B ,  C , and  D . Campaign #1 was using  Custom Picklist  v1, which is more than one version ahead of the new v4. Campaign #1 continues to use  Custom Picklist  v1. The changes to  Custom Picklist  are not applied to this campaign. Campaign #2 was using  Custom Picklist  v3, which is the version immediately preceding the new v4. Campaign #2 inherits  Custom Picklist  v4. The changes to  Custom Picklist  are applied to this campaign. Campaign #3 was using  Custom Picklist  v3, which is the version immediately preceding the new v4. Campaign #3 inherits  Custom Picklist  4. The changes to  Custom Picklist  are applied to this campaign. v4 Templates Terms and Concepts This section contains information about terms and concepts related to templates. Template Types There are five types of templates: Template Type Description Templates Per Entity Advertiser View The Advertiser View template defines the information included on the following items: The Advertiser View page, located on the  Schedule  tab. The downloaded Advertiser View page, which is exported as an Excel file. One Campaign Goals The Campaign Goals template defines the fields and parameters of a campaign's  Goals  section. One External Integrations  (Ad Server) The External Integrations template defines the columns and column order of the Ad Server grid, located on the Ad Server Provider dashboard. One Media Schedule The Media Schedule template defines the fields and field order of the Schedule grid, located on the  Schedule  tab. A Schedule template defines two classes of fields, default and hidden: Default fields: Displayed on the Schedule grid by default, but can be manually removed or re-added via the column picker Hidden fields: "Hidden" from the schedule; cannot be added to the Schedule grid Fields that are not explicitly classified as default or hidden are not displayed on the Schedule grid by default, but can be manually added or removed via the column picker. One Order Details The Order Details template defines the information included on the following items: The Order Details grid is located on the Order Details page. The Order Details grid is included with the PDF or Excel export of the Order Details page. The Vendor Order Details grid is located on the Vendor Order Details page, in Vendor Inbox. The Vendor Order Details grid is included with the PDF or Excel export of the Vendor Order Details page. Multiple If an entity has one Order Details template, that template is the default template If an entity has multiple Order Details templates, the user can define one of them as the default template If an entity has no Order Details template, it inherits the default template of the nearest higher-level entity with a default About System Default Templates The system default templates are a set of templates that are pre-defined by OneStrata and automatically available for all enterprises. System default templates provide a quick, out-of-the-box foundation that can be used or customized as desired. Enterprises can create their own custom templates, but do not have to. If there is no custom template for a particular template type, the system default template is applied instead. There are four system default templates (there is no system default Campaign Goals template): Template Type System Default Template Advertiser View template See  System Default Advertiser View Template . External Integrations template See  System Default External Integrations Template . Media Schedule template See  System Default Media Schedule Template . Order Details template See  System Default Order Details Template .