DocumentationAPI ReferenceChangelog
Changelog
Back to All

25.11.0 November 1, 2025 Release Notes

October 20th, 2025 by Joel Basart

Features and Changes

  1. Support for Asset ID on All Device Types [ENG-1448] – An editable Asset ID field has been added for all non-ChromeOS devices, allowing administrators to manage unique identifiers directly within the Device Management page. Previously, only ChromeOS devices supported Asset IDs (managed through Google Admin).
    1. The Asset ID field is now available for Android and other non-ChromeOS devices.
    2. Users with access to devices can manually assign or modify Asset IDs through the Administrator Interface by selecting a device and editing its settings.
    3. This enhancement enables additional device identifiers.
    4. Note: This update does not affect ChromeOS devices or their existing Google Admin Asset ID integration.

Fixes

  1. Inaccurate media file counts [ENG-2091] - Some accounts displayed incorrect media counts, causing them to hit the media limit even though they had fewer items uploaded. This was due to inaccurate playlist association data in the media repository, which inflated the total count. The calculation logic has been updated to correctly reflect each media item’s actual usage, ensuring that all media counts now accurately match the number of uploaded files within account limits.
  2. Ad Campaign “Export All” [ENG-2245] - The “Export All” feature for ad campaigns was failing to complete due to timeouts. The export query and timeout threshold have been optimized to ensure that full ad campaign exports now complete successfully. This fix applies only to the “Export All” functionality and does not affect other export features.
  3. Improved Validation and Logging for CAP Trigger URLs [ENG-2151] - Previously, TelemetryTV allowed non-CAP protocol URLs to be entered when configuring CAP Trigger Overrides. These invalid URLs were accepted without clear error messages, which could cause unexpected display behavior. CAP Trigger URLs are now properly validated to ensure only valid CAP feeds are accepted. In addition, the Admin App’s Settings log area now provides detailed error messages when CAP data retrieval or parsing fails, giving administrators clearer insight into any issues.