Release Version: 24.8.14

Release Date: August 28, 2024





Added

New Search Integration with Google Ads

What is it? OneStrata enterprises can add an integration with Google Ads, Google's advertising platform for search advertising.

Enterprises integrated with Google Ads can do the following:

  • Link a OneStrata Cost Line to an existing Google Ads campaign
  • View the delivery metrics of a linked Google Ads campaign within OneStrata

For more information, see the following articles:

Where is it? This new feature affects the External Integrations tab.

Do I need to do anything? External integrations are managed by FreeWheel. To set up or manage an integration with Google Ads, contact your OneStrata representative.

New Social Integration with Meta Ads Manager

What is it? OneStrata enterprises can add an integration with Meta Ads Manager, Meta's platform for social media advertising.

Enterprises integrated with Meta Ads Manager can do the following:

  • Create a Meta campaign (for advertising on Facebook or Instagram) while in OneStrata
  • Link a OneStrata Cost Line to an existing Meta campaign
  • Create a new Meta campaign while in OneStrata

For more information, see the following articles:

Where is it? This new feature affects the External Integrations tab.

Do I need to do anything? External integrations are managed by FreeWheel. To set up or manage an integration with Meta Ads Manager, contact your OneStrata representative.

Create Concatenated Formulas For Ad Server and DSP Campaign Names

What is it? Concatenated formulas can be created for ad server and DSP campaign names.

  • Previously, when creating a new ad server campaign or DSP campaign within OneStrata, the external campaign name (the campaign name that is pushed to the ad server or DSP) defaulted to the OneStrata campaign name, but could be manually specified or edited as desired.
  • Now, you can create concatenated formulas that automatically create ad server and DSP campaign names according to the specified naming convention. The new concatenated formulas make it possible to apply different naming conventions to OneStrata campaign names, ad server campaign names, and DSP campaign names.

For more information, see Create a Campaign Name Formula for Ad Server or DSP Integrations.

Where is it? These new formulas affects the following areas:

  • The Link Campaign widget on the Ad Server dashboard
  • The Link Campaign widget on the DSP dashboard

How am I affected? The ad server and DSP campaign name concatenated formulas are optional. If these concatenated formulas are not created, the name of a new ad server or DSP campaign defaults to the name of the OneStrata campaign.

Do I need to do anything? No — these new formulas are automatically available for all OneStrata enterprises.

Enable Financial Order Revisions Based on Estimate Updates

What is it? There is a new FreeWheel-managed setting that specifies whether or not an update to an estimate automatically triggers a revision of all associated financial orders.

  • If this setting is enabled, any changes made to the name, dates, or custom field values of an estimate causes all financial orders associated with the estimate to be revised (a new version of the financial order with the updated estimate information is created).

    Depending on financial order export settings, the new financial order version is either automatically exported to the Financial Bridge, or must be manually exported.

  • If this setting is not enabled, changes to an estimate do not cause a revision of any associated financial orders.

This setting is helpful for enterprises that use estimate information from the financial order to keep OneStrata and the financial system in sync.

Where is it? This new setting affects the Financial Order Management grid, located on the Finance > Financial Orders page.

Do I need to do anything? By default, this setting is not enabled. To enable this setting, contact your OneStrata representative.

View the External Provider IDs of Linked Cost Lines in the Order Details Grid

What is it? The external provider IDs of Cost Lines that are linked to external entities through a DSP, search, or social integration can now be displayed on the Order Details grid, in the new External Provider ID column:

  • For a Cost Line that is linked to a DSP insertion order, the External Provider ID is the DSP insertion order ID used by the DSP provider.
  • For a Cost Line that is linked to a search campaign, the External Provider ID is the search campaign ID used by the Search provider.
  • For a Cost Line that is linked to a social campaign, the External Provider ID is the social campaign ID used by the Social provider.

Being able to view the external provider IDs of linked Cost Lines in the Order Details grid makes it easier to identify which OneStrata Cost Lines correspond to which external entities, especially if different teams are working within and outside OneStrata.

Note: In the DSP grid, Search grid, and Social grid, the External Provider ID column is called the External ID column.

Where is it? This new column affects the following areas:

  • The Order Details grid located on the Order Details page
  • The Order Details grid that is included with the PDF or Excel export of the Order Details page
  • The Order Details grid that is sent to Vendor Inbox, if using an In-System Order Partner

How am I affected? The External Provider ID column is only displayed if:

  • The ID field is included in the Order Details template. This field also controls whether or not the ID column (the OneStrata ID of the Schedule grid line) is displayed; and
  • At least one external provider ID exists (at least one Cost Line in the order is linked to a DSP insertion order, search campaign, or social campaign).

By default, all Order Details templates contain the ID field. However, if an Order Details template does not include the ID field, any Order Details grids generated from that template will not display the ID or External Provider ID columns.

Do I need to do anything? No — this new column is automatically available for all OneStrata enterprises.

Changed

Additional Date Format Options For Concatenated Formulas

What is it? There are four new date formats for name concatenation formulas that contain date fields:

  • yy: The year of the date, as a two-digit number from 00 to 99
  • yyyy: The year of the date, as a four-digit number
  • yyyy-MM: The four-digit year of the date and the two-digit month of the date, separated by a hyphen
  • yy-MM: The two-digit year of the date and the two-digit month of the date, separated by a hyphen

Previously, all date formats included the day of the month. For more information, see Concatenated Formula Date Options.

Where is it? This change affects concatenated formulas, which are managed on the Administration > Data Fields & Templates > Data Fields tab.

Do I need to do anything? No — this change is automatically applied to all OneStrata enterprises.

General Updates to Fee Record Client Rates

Some of the backend logic used for client rate details on Fee records was updated, making Fee records easier to use and more flexible:

ChangeDescription
Client Rates Are Displayed on the Fees Grid

What is it? Previously, a Fee record had to be opened in order to see its client rate details.

Now, the client rate(s) of a Fee record are displayed on the Fees grid, making it easier to identify Fee records at a quick glance. 

  • If the Fee record is simply applied to all clients, the All Clients rate is displayed directly on the Fees grid, in the Client column.
  • If the Fee record is applied to specific Clients or Client Groups, the Client and/or Client Group columns on the Fees grid contain a link that, when clicked, opens a widget with client rate details. Users can only see the client rate details for Client and Client Group entities that they have access to.

For more information, see Client Rate Widget Reference.

Add Client-Specific Rates To Enterprise-Level Fee Records

What is it? Previously, an enterprise-level Fee record could only apply to All Clients (all Clients and Client Groups), and it was not possible for an enterprise-level Fee record to apply different rates to different clients. Only Fee records created at the Business Unit level could have client-specific rate details.

Now, individual Clients and Client Groups can also be added to enterprise-level Fee records, making Fee records more flexible and reducing the overall number of necessary Fee records. Each Client or Client Group added to the Client Rate Details section can have its own Client Net Rate (if fee margins are enabled) and Commission values.

How am I affected? Any existing enterprise-level Fee records can be edited to add client-specific rate details.

Where is it? These changes affect Fee records, which are managed on the Administration > Reference Data > Fees & Tech Rate tab.

Do I need to do anything? No — these changes are automatically available for all OneStrata enterprises. 

General Updates to Schedule Validation Logic

Some of the backend logic used for schedule validation was updated, helping ensure better data integrity:

Validation ChangeDescription

Cost Line Dates Are Validated Against Campaign Dates

What is it? Previously, the start and end dates of a Cost Line could be changed freely.

Now, the start and end dates of a Cost Line are bounded by the start and end dates of the campaign:

  • The start date of the Cost Line must be the same day or later than the start date of the campaign.
  • The end date of the Cost Line must be the same day or earlier than the end date of the campaign.

The Cost Line date validation occurs during commit. If a Cost Line with invalid dates is committed, the commit process fails and a warning is displayed.

How am I affected? For any existing, committed Cost Lines with dates that are now invalid:

  • The dates of the Cost Line are not automatically updated to fit the new date validation rules. Its dates must be fixed manually.
  • The Cost Line cannot be actualized until its dates are fixed.
  • If changes are made to the Cost Line, it cannot be re-committed until its dates are fixed.

Updated Vendor Contract Field Validation

What is it? Previously, vendor contract field validation only occurred when the field was selected directly by the user in the Schedule grid.

Now, Schedule grid fields related to vendor entities and contracts (the Supplier, Order Partner, Payee, Vendor Currency, and Cost Category fields) are also validated against Contract records when:

  • The value is copied from one Cost Line to another, either by copy-and-pasting (using Ctrl + C and Ctrl + V) or by drag-and-filling (using the mouse).
    • For each Cost Line that the value is pasted to, the copied value is grouped with any other contract field values in the Cost Line that have already been selected.
    • If the combination of contract field values matches an active Contract record and the campaign dates overlap the Contract record dates by at least one day, the copied value is pasted successfully.
    • Otherwise, the pasting fails and a warning is displayed.
  • The Cost Line is committed for the first time.
    • If the combination of selected contract field values matches an active Contract record and the campaign dates overlap the Contract record dates by at least one day, the Cost Line is committed successfully.
    • Otherwise, the commit process fails and a warning is displayed.
    • Vendor contract field validation only occurs on the first commit, meaning that if a Cost Line is committed and the associated Contract record is subsequently deactivated or its dates are changed, the Cost Line can be re-committed even if it no longer matches an active Contract record.

Where is it? This change affects the Schedule grid, located on the Schedule tab.

Do I need to do anything? No — these validation changes are automatically applied to all OneStrata enterprises.

General Updates to Viewing and Editing Data in Grids

What is it? Some of the backend logic used for interacting with grids was updated, making it easier and faster to view and edit data on grids.

ChangeDescription
All Rows Are Expanded By Default

What is it? The following grids now expand all rows to the lowest level by default:

  • The Advertiser View Schedule grid, located on the Advertiser View Page
  • The Order Details grid, located on the Order Details page
  • The Ad Server grid, located on the Ad Server dashboard

Previously, rows with children rows (like Media Package or Package lines) were collapsed to the parent row by default.

Note: The Schedule grid already expands all rows by default.

All Rows Can Be Expanded or Collapsed

What is it? The following grids now have the option to expand all collapsed rows, and collapse all expanded rows:

  • The Schedule grid, located on the Schedule tab
  • The Advertiser View Schedule grid, located on the Advertiser View Page
  • The Order Details grid, located on the Order Details page
  • The Ad Server grid, located on the Ad Server dashboard
  • The Standard Actualization and Margin Actualization grids, located on the Actualization tab

Previously, any collapsed rows had to be individually expanded, and any expanded rows had to be individually collapsed. This new expand all / collapse all option greatly reduces the number of manual clicks.

Do I need to do anything? No — these grid changes are automatically applied to all OneStrata enterprises. 

Maximum Length of Ad Placement/Package Names Increased to 512 Characters

What is it? The maximum character length of the Name / ID column on the Ad Server grid was increased to 512 characters, meaning that Ad Placement and Package lines can now have longer names. Previously, the name of an Ad Placement lines was limited to 300 characters and the name of a Package line was limited to 255 characters.

The increase in name length applies to manually entered names and names created by a concatenated formula.

Where is it? This change affects the Ad Server grid, located on the Ad Server dashboard.

Do I need to do anything? No — this change is automatically applied to all OneStrata enterprises.