API DocsKnowledge BaseSystem StatusContact SupportContact Sales
Announcements
Back to All

Release Notes: February 21, 2025

about 1 month ago by Nico Staple

This release introduces several enhancements across Self Serve, campaign management, reporting, forecasting, and audience capabilities. In Self Serve, advertisers can now configure attribution based on brand and merchant IDs, access category-level performance reports, and view selected products separately from performance data in campaign reports. In the Ad Serve, the Campaign Management API allows creating product ads dynamically based on query criteria; and reporting now supports selecting specific dimensions and metrics for downloads. The Forecast API improves pacing accuracy and supports targeting empty user properties. Audience supports new user attributes for segmentation and deeper insights. Additionally, Kevel Relay now integrates with StackAdapt for video ads.

Self Serve

Advertiser UI & Advertiser API

Added

  • Attribution based on advertiser catalog access settings: In some retail media use cases, retailers find it advantageous to consider any product purchase that is associated with an advertiser's brand or merchant ID to be eligible for attribution back to that advertiser's campaign. Now, retailers can configure a campaign template to automatically set ad-level attribution for an advertiser's brand ID(s), merchant ID(s), or both. Learn more on the self-serve customization page.
  • Category report: Publishers who use Kevel Catalog can now choose to equip advertisers with a performance report broken down by category. Learn more on the self-serve customization page and advertiser user guide for reports .
  • Selected products list: For sponsored listings campaigns created in self-serve, campaign report pages now show two tabs within the product table: Selected Products and Product Performance.
    • The Selected Products tab shows all products that are being promoted on this campaign, without performance data. The "status" column indicates whether the product is currently active as an ad on this campaign.
    • The Promoted Products tab shows performance data for the selected date range. Products will only appear if there was performance data for the selected time period.
    • Learn more on the advertiser user guide for campaign reports.

Ad Server

Campaign Management API

Added

  • Create product ads using a query — it is now possible to specify a set of product criteria on a per-Flight basis and Kevel will fill each Flight with product ads that match that criteria. When Catalog data changes, Kevel will automatically re-evaluate ads in Flights to add new products that match the criteria and remove ads for products that are no longer available. Learn more on the Creating Product Ads via API knowledge base page.

Reporting

Added

  • Report downloads include only selected dimensions and metrics — it is now possible to specify an explicit list of columns or fields to include or exclude from CSV and JSON reports. Use the new fields CsvColumns (columns to include) and ExcludeCsvColumns (columns to exclude) in report generation requests. See Create Queued Report parameters for more details.

Forecast API

Added

  • Forecast-specific custom targeting now supports using the $empty variable to refer to empty objects. This can be used, for example, to target all users that have no properties in UserDB (via $user.custom = $empty). Note that rules using the $empty variable can't be used in the ad server.

Changed

  • The forecast pacer implementation now attempts to be more even in the presence of gaps in the delivery schedule (which can be caused, for example, by day & hour parting rules). It does that by transferring unmet caps in a given pacing interval to the next pacing interval. This allows the pacer to catch-up quickly in the presence of intervals that don't meet their goals.

Relay

Added

  • Relay demand integration with StackAdapt (DSP) for Video ads

Audience

Added

  • Support new user attributes based on intra-event aggregation. These attributes can then be used to create segments or serve as key data points for deeper insights, such as Spend by Category. For more details and instructions on common use cases, please refer to the documentation on value extractors.