Meta introduces the ads CLI, a command-line tool for managing Meta ad campaigns without custom code. It simplifies repetitive tasks like authentication and pagination, supports multiple output formats, and integrates into workflows. Users can create, update, and analyze campaigns, ad sets, creatives, catalogs, and datasets from the terminal. Designed for automation, it supports scripting, exit codes, and environment variables. Requires Python 3.12+.
Facebook updates Developer Policies to improve ad-buying transparency and account structure. Advertisers must keep end advertisers in separate ad accounts unless using vendor_id or brand fields properly. From February 3, 2027, ad-buying solutions must disclose ad spend, fees, and campaign details upon end advertiser request. Meta may disclose info if policy violations are suspected, without prior notice. These changes align with industry standards.
Markifact is a no-code marketing automation platform that lets users create AI-driven workflows for automating marketing tasks. Users can trigger workflows, connect apps, and track performance through a visual interface. The platform offers pre-built templates, integrates with various marketing tools, and supports team collaboration.
Instagram API updates enhance branded content workflows, adding partnership ads labels with or without brand tags. New engagement metrics include reposts, saves, shares, and aggregated views, likes, and comments across Instagram and Facebook. Collaborative media endpoints allow tracking co-created content. The API now supports liking/unliking posts and comments via third-party apps with proper permissions.
Starting June 22, 2026, Facebook will replace Nielsen's DMA with Comscore Markets® for automotive ads. Campaigns using Nielsen’s DMA will pause until updated. From March 23, 2026, advertisers can update vehicle offer feeds with Comscore Market IDs using a provided mapping table. Notifications begin April 20, and all Nielsen DMA targeting ends June 22. Updates via Catalog Manager or API are required to resume campaigns.
Threads API now offers richer content options such as cross-sharing to Instagram Stories, long-form text attachments, ephemeral ghost posts, spoiler tags, and GIFs. It supports tokenless embedding, enhanced web intents for posting, and improved search by media or author. New management tools include reply approvals and real-time webhooks for post events. Developers can use documentation, sample apps, and testing tools for integration.
Threads has over 400 million monthly users and now supports App Ads globally via the Marketing API, allowing app install and event optimization campaigns without new creatives. A new reply moderation tool lets advertisers view, hide, and respond to top-level replies on Threads ads, requiring specific permissions. More details and updates are in the developer documentation and changelog.
Facebook Graph API v25 adds Page Viewer Metric replacing legacy reach by June 2026, requiring migration. Webhooks mTLS certificates change to Meta CA by March 31, 2026, needing trust store updates. Ads Insights Async API adds error details. Metadata=1 parameter deprecated. Legacy reach and viewer metrics retire by June 2026, replaced by Media Views. Marketing API phases out ASC and AAC campaigns by Sept 2026. Graph API v19 and v20 deprecated in 2026.
Facebook is phasing out ASC and AAC campaigns in Marketing API starting V25.0 (Feb 18, 2025), with creation and updates disabled, extending to all MAPI versions after 90 days. By V26.0 (Sep 2026), remaining ASC and AAC campaigns will be paused. ECBC campaigns remain editable until V26.0 but must be duplicated or migrated before then. New campaigns get new IDs. Developers should review updated docs for details.
Meta is enhancing error reporting for the Ads Insights Async API GET {AD_REPORT_RUN_ID} endpoint to improve developer experience. With Graph API version V25.0 on Feb 18, 2026, detailed error information will be provided for failed asynchronous reports. New fields will include error_code, error_message, error_subcode, error_user_title, and error_user_msg. Developers should ensure compatibility with these updates.
