Version 2026.32
1 new13 changed2 fixed
Infegy Starscape¶
With this release, a new Infegy Starscape connector has been added, allowing users to automatically retrieve social intelligence data, including sentiment, emotions, and demographics, directly into Adverity.
Database¶
With this release, the Database connector’s configuration interface has been improved.
Facebook Ads¶
With this release, Facebook Ads users can now access detailed information about ‘Special Ad Categories’ including campaign_special_ad_categories, campaign_special_ad_category, and campaign_special_ad_category_country directly within their reports, enabling more granular analysis and compliance tracking.
File Connector¶
With this release, File connector users can now benefit from automatic detection of CSV/Excel file formats and delimiters, reducing manual configuration, preventing parsing errors, and improving data onboarding efficiency. For more information, see File: Setup guide.
Reddit Ads¶
With this release, Reddit Ads users can now access campaign_goal_type (Budget Type) and its corresponding campaign_goal_value directly within the Analytics report, providing more detailed insights into campaign performance and budgeting.
Smart Schedule multi-range support¶
With this release, Smart Schedule now supports up to four independent fetch ranges per datastream, each with its own frequency and refresh window, allowing users to combine a frequent daily check with a wider periodic refresh. New datastreams default to a daily fetch of the last 3 days plus a weekly fetch of the last 40 days, or a single daily fetch of the previous day for file and datalake connectors. For more information, see Manual, Smart, and Custom fetches.
Connection metadata sync scope¶
With this release, the POST /api/connection-types/{type_id}/connections/{id}/update/ MAPI action has been updated to scope metadata sync to the caller’s workspace, enhancing security and data integrity. The action now returns an HTTP 404 error when the authorization is not accessible to the API key, when the ID does not belong to the authorization type in the URL, or when the authorization is scheduled for deletion. For more information, see Creating and configuring authorizations in Management API.
Custom monitor workspace ID cap¶
With this release, a length cap has been applied to the workspace_id parameter in GET /api/v1/custom-monitors/ to prevent excessively long lists in the query parameter, ensuring more reliable API performance.
Datastream scheduled deletion filter¶
With this release, a new optional scheduled_deletion query parameter has been added to the following endpoints, allowing MAPI users to filter datastreams that are scheduled for deletion:
GET /api/datastreams/GET /api/v1/datastreams/PATCH /api/v1/datastreams/POST /api/v1/datastreams/custom-monitors/DELETE /api/v1/datastreams/custom-monitors/OPTIONS /api/v1/datastreams/custom-monitors/PUT /api/v1/datastreams/pulling/smart/
For more information, see Managing pulling mode and smart schedule in Management API and Bulk assigning custom monitors in Management API.
Infegy Starscape endpoints added¶
With this release, the following endpoints are now available in Management API:
GET /infegy_starscape/infegystarscapedatastream/channels/GET /infegy_starscape/infegystarscapedatastream/country/GET /infegy_starscape/infegystarscapedatastream/language/
MAPI error response standardization¶
With this release, MAPI error responses have been standardized across the legacy /api/ endpoints, such as GET /api/datastreams/, providing more consistent and predictable error structures for developers. Error responses now always contain a detail field, and contain an errors field when a request fails validation. For more information, see Getting started with the Management API.
MCP authorization creation¶
With this release, the MCP manage_authorization.create action now requires a two-phase confirmation step, enhancing safety and consistency for users.
MCP datastream deletion filter¶
With this release, the MCP manage_datastream tool’s list action now supports filtering datastreams by their scheduled_deletion status, providing better control and visibility when managing datastreams via GET /api/datastreams/ and GET /api/v1/datastreams/.
Multi-range smart-pulling (v2)¶
With this release, a new Management API v2 surface (/api/v2/) is available for datastream smart-pulling configuration, supporting up to four independent fetch ranges per datastream with lossless read and write. The existing /api/v1/ smart-pulling endpoint remains available, but now reports and accepts only a single range per request. For more information, see Managing pulling mode and smart schedule in Management API and Getting started with the Management API.
Resolved issues¶
With this release, issues have been resolved for the following connectors and destinations:
Google Cloud Storage destination
Google PageSpeed Basic
Line Ads
Magnite CTV
Shopee
MCP bulk target mapping fix¶
With this release, an issue has been resolved where the MCP bulk mapping tool failed when PUT /api/datastreams/{id}/columns/map/ returned a list-shaped error, ensuring users can now reliably use the tool.