What鈥檚 new
The following features are new or recently changed.
By default, if a segment ID is specified in the advertiser account settings, then the advertiser-level ID is entered in the placement settings, but you can change the ID to use a different segment or delete the ID to disable the feature.
Within the advertiser-level settings, the option to enable the feature was removed; specifying a segment ID now enables the feature. If the feature was disabled for one of your existing advertisers, the segment ID field is now blank. No user action is needed.
(Beta feature) Three new reports provide deeper insights into which ad interaction paths lead to conversions:
- Path to Conversion Beta: Shows the sequence of interaction points in the same household that lead to each of the selected conversion metrics in the specified data range.
- Path Length Beta: Show the number of conversions by path length (interaction points), such as how many conversions occurred after users had only one ad interaction, two ad interactions, and so on.
- Time to Conversion Beta shows the number of conversions by the length of time in days from the last interaction (ad exposure or click) to conversion.
In addition, the command name for downloading settings for specific packages and placements is now 鈥淒ownload Bulksheet.鈥 You can upload settings for specific packages and placements from the 鈥 > 鈥淯pload Bulksheet鈥 option in the upper right.
Also, the Placements and Ads view for private deals listed at Inventory > Deals now includes a 鈥淣on bid reasons鈥 option on each row. Click the option to open the placement diagnostic report to the Non Bids tab, filtered by the private deal.
Oracle will sunset its advertising business by 30 September. DSP has disabled all services from BlueKai, Oracle Data Cloud (formerly Grapeshot), and MOAT and removed them from advertiser settings, campaign settings, placement settings, and optimization goals. However, any placements with existing BlueKai segments may continue spending for those segments until September 30.
The following alternatives are available:
- Standard third-party and custom segments: eXelate, Eyeota, LiveRamp, Lotame, Neustar, and other available third-party data partners
- Predictive third-party segments: Proximic by Comscore
- Campaign-level brand safety and viewability measurement with Integral Ad Science
- Placement-level pre-bid viewability with DoubleVerify and Integral Ad Science
- Placement-level topic targeting by Proximic by Comscore
CPM pricing for third-party segments is available in the Audience Library, and CPM pricing for services is available at Settings > Fees.
The following enhancements are available for packages and placements with the 鈥淎lways Max Bid & Maximize Reach" and 鈥淟owest Cost per Reach鈥 optimization goals:
- Unique reach data aggregated at the package level, not the individual placement level, is now used to drive maximum incremental reach using bid optimization and budget allocation.
- You can include household reach data from all programmatic guaranteed (PG) placements in the campaign to optimize for incremental reach using the new package setting 鈥淟ink PG Placements for Incremental Reach Optimization."
The following custom report features and enhancements were released:
-
The Reports > Custom Reports view was redesigned:
- Columns now include 鈥淪tatus,鈥 鈥淩eport Run" (which shows dates on which the report was triggered beginning on 22 August 2024),鈥 鈥淩ecurrence,鈥 鈥淐reated By,鈥 and 鈥淒ownload Report鈥 (with a 鈥淒ownload鈥 button so you can immediately download any report instance from the last four months).
- You can filter the list by status, whether the report is recurring or one-time, the report type, the destination type, and the report creator. By default, all unarchived reports created by the user are listed, with the most recent on top.
- The quick action buttons for each report (such as Copy and Delete are now available by clicking 鈥 next to the report name.
-
Report scheduling options are now available at the report level, not at the individual destination level. In report settings, the schedule settings are now available near the top in the 鈥淩eport run schedule鈥 section. If you edit an older report that has different existing schedules for individual destinations, you鈥檒l be prompted to set the schedule and notified that the schedule will replace the existing schedule for all existing destinations.
In the Packages view and the [Package Name] > Flights view, the 鈥淚nterval Goal鈥 column, which shows the current flight goal, includes the rollover budget.
In the Campaigns, Packages, and Placements views, some metrics were renamed based on feedback:
-
In trend charts, 鈥淩equired spend鈥 was renamed 鈥淪pend benchmark,鈥 and 鈥淭arget spend鈥 was renamed 鈥淪pend target.鈥
-
In data tables:
- 鈥淵esterday鈥檚 required spend鈥 and 鈥淭oday鈥檚 required spend鈥 were renamed 鈥淵esterday鈥檚 spend benchmark鈥 and 鈥淭oday鈥檚 spend benchmark.鈥
- The tooltips "Yesterday鈥檚 pacing % and 鈥淭oday鈥檚 pacing %鈥 were changed to 鈥淵esterday鈥檚 gross spend as % of yesterday鈥檚 spend benchmark鈥 and 鈥淭oday鈥檚 gross spend as % of yesterday鈥檚 spend benchmark.鈥
- 鈥淵esterday鈥檚 target spend鈥 and 鈥淭oday鈥檚 target spend鈥 were renamed 鈥淵esterday鈥檚 spend target鈥 and 鈥淭oday鈥檚 spend target.鈥
Oracle will sunset its advertising business by 30 September 2024. This will disable all services from BlueKai, Oracle Data Cloud (formerly Grapeshot), and MOAT. The following alternatives are already available:
- Standard third-party and custom segments: eXelate, Eyeota, LiveRamp, Lotame, Neustar, and other available third-party data partners
- Predictive third-party segments: Proximic by Comscore
- Campaign-level brand safety and viewability measurement with Integral Ad Science
- Placement-level pre-bid viewability with DoubleVerify and Integral Ad Science
- Placement-level topic targeting by Proximic by Comscore
CPM pricing for third-party segments is available in the Audience Library, and CPM pricing for services is available at Settings > Fees.
New support is available for custom goals (objectives):
- The names of objectives created in Search, Social, & Commerce for use with Advertising DSP packages must now be prefixed with 鈥淎DSP_鈥 such as 鈥淎DSP_Registrations.鈥 The prefix isn鈥檛 case-sensitive. Objectives with this naming convention are available as custom goals within DSP.
Your existing DSP objectives were already renamed for you, and no further work is necessary. - Weight recommendations are now generated for DSP-attributed metrics in objectives. When the objective includes at least one goal metric and one assist metric, recommendations are generated for non-mobile weights (which are used for ads on all device types for DSP) for each assist metric in the objective. Weight recommendations are calculated the next morning after you save or edit the objective definition. The recommendations are updated one day after changes to the objective are detected, or otherwise every seven days. When weight recommendations are available, an indicator ( ) appears next to the objective name in Search > Optimization > New Objectives Beta. In one click, you can apply all weight recommendations. All weight changes to objectives prefixed with 鈥淎DSP_鈥 are applied algorithmically in DSP within two days.
For more information about objectives and applying weight recommendations, see the Optimization Guide chapter on 鈥(Beta) New Objectives,鈥 which is available from within Search, Social, & Commerce.
In the Campaigns, Packages, and Placements views:
-
Trend charts can now include the following optional metrics:
- Day pacing: Shows how the 鈥淵esterday鈥檚 pacing鈥 metric is trending over time.
- Flight pacing ahead/behind: Shows how the cumulative pacing (relative to the time elapsed) is trending over time.
-
Data tables can optionally include new pacing-related metric columns:
- Yesterday鈥檚 required spend: The amount that should have been spent yesterday for uniform distribution of the remaining budget through the rest of the flight.
- Yesterday鈥檚 pacing: Yesterday鈥檚 spend as a percentage of yesterday鈥檚 required spend. This is an improved version of 鈥淭oday鈥檚 OTS,鈥 which is now deprecated. When today鈥檚 pacing is consistently less than 100%, the package or placement is struggling with its budget delivery.
- Today鈥檚 required spend: The amount that should be spent today for uniform distribution of the remaining budget through the rest of the flight.
- Today鈥檚 pacing: Today鈥檚 spend as a percentage of today鈥檚 required spend; the value is updated every 30 minutes. This is an improved version of 鈥淵esterday鈥檚 OTS,鈥 which is now deprecated. When yesterday鈥檚 pacing is consistently less than 100%, the package or placement is struggling with its budget delivery.
-
In data tables, the 鈥淵esterday鈥檚 goal鈥 and 鈥淭oday鈥檚 goal鈥 columns are renamed 鈥淵esterday鈥檚 target spend鈥 and 鈥淭oday鈥檚 target spend.鈥
(Open beta; available in US and AUS only) You can now retarget audience segments exposed to a connected TV campaign with additional ads to enhance cross-channel advertising:
- Set up an ad exposure segment and copy the impression tracking tag to the desired connected TV placement or ad to begin tracking for the segment.
- In the retargeting placement, select the connected TV exposure segment in the Audience Targeting section.
New CPA
(cost per acquisition) and ROAS
(return on ad spend) metrics in the package, placement, and related tables provide more accurate performance tracking for packages and placements with related goals. The new CPA metric considers only the final conversion event (such as signups) for computing the cost per acquisition, which gives a more accurate picture of the actual CPA than the legacy custom goal metric, which also included upper-funnel events (such as page visits and shopping cart additions) in its computation. Similarly, the new ROAS metric considers only the final revenue event (such as purchases and purchase values), which is more reliable than the legacy custom goal metric for tracking performance.
Now, when you set up a package with a CPA- or ROAS-based optimization goal, you must specify the final conversion or revenue event, as well as a custom goal that includes the conversion or revenue event; the custom goal can optionally include additional weighted upper-funnel events (such as page visits and shopping cart additions) to be used in addition to the CPA or ROAS metric for package optimization.
In addition, the performance-focused optimization goals were combined for simplicity:
- The new 鈥淗ighest Return on Ad Spend (ROAS)鈥 goal replaces the legacy 鈥淗ighest ROAS - Custom Goal鈥 and Highest ROAS (click focused) - Custom Goal," with options to achieve either legacy scenario.
- The new 鈥淟owest Cost per Acquisition (CPA)鈥 goal replaces the legacy 鈥淟owest CPA - Custom Goal鈥 and Lowest CPA (click focused) - Custom Goal," with options to achieve either legacy scenario.
Your existing packages that used the legacy goals were automatically migrated to the new goals with the relevant settings, and you don鈥檛 need to update anything manually.
In addition, the Campaigns, Packages, Placements, and Ads views include an 鈥淎lerts鈥 column that indicates when an item or any of its components has an issue.
Alerts are available at the campaign, package, placement, ad, and deal levels.
New placement settings allow you specify a) a minimum placement budget to override the package-level budget allocation whenever sufficient budget is available and b) override the bid price algorithm to bid at least the fixed and floor prices for deals:
- In the settings for placements that belong to packages, you can now specify a minimum budget as a percentage of the package budget. To use the feature, select the placement funding option to 鈥淪et a Fixed Minimum or Maximum Budget鈥 (formerly 鈥淪et a fixed budget cap鈥). You can still enter a Maximum Budget in USD (like you could before for the budget cap), and you can also enter a Minimum Budget as a percentage of the package budget. For existing placements, your existing settings are retained using the new field names.
- In the Inventory Targeting settings, a new option for On Demand inventory and private inventory allows you to 鈥淓nsure Fixed or Floor Price for the bid.鈥
You can now quickly customize ad scheduling for multiple placements using a spreadsheet:
- You can download an ad schedule template for placements. You can edit the flight dates and ad rotation in the downloaded file as needed.
- You can then upload the edited ad schedule template.
To download a list of ad names and associated Ad IDs, go to the Ads view, create a custom view that includes the ID metric, and then export the data.
Before a report expires, all specified email recipients receive an email alert seven days and one day before the expiration date. To keep the report longer, change the expiration date in the report settings.
Universal video placements include a 鈥淒evice Environment鈥 setting to specify device type targets (Desktop, Mobile, and Connected TV). Universal video ads can be linked only to universal video placements.
Custom reports include the new placement-level dimension 鈥淒evice Environment.鈥
See also 鈥Universal Video Ad Settings鈥 and 鈥Create an Ad.鈥
Separate pacing controls are now available for flight pacing and intraday pacing. Previously, a single strategy controlled both. Settings for your existing packages and placements were mapped as follows:
- Legacy Pacing fill strategy=Even 鈥 Now configured as Flight pacing=Even and Intraday pacing=Even
- Legacy Pacing fill strategy=Slightly Ahead 鈥 Now configured as Flight pacing=Slightly Ahead and Intraday pacing=Even
- Legacy Pacing fill strategy=Frontload 鈥 Now configured as Flight pacing=Frontload and Intraday pacing=ASAP
- Legacy Pacing fill strategy=Aggressive Frontload 鈥 Now configured as Flight pacing=Aggressive Frontload and Intraday pacing=ASAP
With transparency into bid request data from publishers, you can avoid time-consuming troubleshooting steps.
Your existing reports are still sent to the specified email recipients. To configure delivery to a different report destination, create a report with the new destination.
The Deal ID settings and other places in the user interface reflect new branding for Magnite SSP:
- The SSP 鈥淭remor鈥 (Telaria) is now 鈥淢agnite CTV.鈥
- In the coming weeks, Rubicon" will change to 鈥淢agnite DV+,鈥 where DV+ stands for display, video, and other formats such as audio.