We track every ad platform API change so you don't have to. Published weekly — every issue includes Avergo's response status.
Get this in your inbox every Monday
Free. No spam. Unsubscribe anytime.
Week of March 24, 2026
Meta Ads API v22 removes the "reach" objective from campaign creation, requiring a migration to "awareness" with reach-optimised delivery settings. Separately, Google Ads completed the forced migration of Smart Shopping campaigns to Performance Max — any campaigns still using the legacy endpoint now return a hard error.
| Platform | What Changed | Impact | Avergo Status |
|---|---|---|---|
| Meta | Ads API v22 removes `objective: REACH` — replace with `objective: AWARENESS` + `bid_strategy: REACH` | Any campaign creation call using the REACH objective returns a 400 error on v22+. | Updated |
| Meta | v21 sunset date confirmed: June 30, 2026. All v21 calls will return 410 Gone after that date. | Agencies still on v21 adapters have 90 days to migrate. Avergo is already on v22. | Updated |
| Smart Shopping campaign type removed from Campaign Management API. Endpoint returns `CAMPAIGN_TYPE_DEPRECATED` error. | Any automation creating Smart Shopping campaigns is now broken. Must use Performance Max. | Updated |
Avergo: This week, we updated 3 adapters — Meta campaign creation and both Google Shopping endpoints. Zero action required from you.
Week of March 17, 2026
TikTok Business API now requires `app_id` as a mandatory parameter on all ad create and update calls — previously optional, now a hard validation failure if omitted. LinkedIn quietly changed how Campaign Group targeting inherits audience segments, causing audience size estimates to return incorrect values for approximately 15% of campaigns.
| Platform | What Changed | Impact | Avergo Status |
|---|---|---|---|
| TikTok | `app_id` field promoted from optional to required on `/open_api/v1.3/ad/create/` and `/ad/update/` | Any ad creation or update call without `app_id` returns a 40002 validation error. | Updated |
| TikTok | Pixel API v2 deprecation notice issued — v1 calls will stop working July 1, 2026. | Pixel-based conversion tracking on v1 API will silently drop after deprecation date. | Monitoring |
| Campaign Group audience inheritance logic changed — child campaigns no longer automatically include parent-level audience exclusions. | Audience size estimates for ~15% of Campaign Group structures are now overstated. Actual delivery unaffected but forecasts are inaccurate. | Investigating |
Avergo: TikTok adapter patched and deployed within 4 hours of the changelog hitting. LinkedIn investigation ongoing — we will update next week.
Week of March 10, 2026
Meta pushed a silent attribution model change for iOS 14.5+ traffic — the 7-day click / 1-day view window is now enforced differently for SKAdNetwork events, causing conversion count discrepancies between Ads Manager and third-party attribution platforms. Amazon DSP has bumped their endpoint base version from v3 to v4, with v3 returning deprecation warnings (not yet errors) on all reporting calls.
| Platform | What Changed | Impact | Avergo Status |
|---|---|---|---|
| Meta | SKAdNetwork attribution window enforcement tightened — conversions outside the 24h view window are now excluded from the 7d click window calculation for iOS 14.5+ events. | Reported conversions may appear lower by 5-18% for iOS-heavy audiences. Not a bug — a model change. | Monitoring |
| Meta | Conversions API (CAPI) event deduplication window changed from 48h to 72h. | Duplicate event filtering is more aggressive. Server-side event volume may appear lower in Events Manager. | Not Affected |
| Amazon | DSP Reporting API base version bumped to v4. v3 returns `X-Deprecation-Warning` header on all responses. | No functional breakage yet — v3 still works. v3 end-of-life expected Q3 2026. | Updated |
Avergo: Amazon DSP adapter migrated to v4 proactively — no disruption. Meta attribution change requires no code fix, only awareness. We have updated our reporting layer to flag the model change in data notes.
Week of March 3, 2026
Google Analytics 4 now enforces measurement ID validation on server-side event imports — previously accepted any string format, now rejects IDs not matching the G-XXXXXXXXXX pattern. Snapchat has deprecated Story Ads v1 endpoint with an immediate hard error, completing the migration they announced in Q4 2025.
| Platform | What Changed | Impact | Avergo Status |
|---|---|---|---|
| GA4 Measurement Protocol now validates `measurement_id` format — must match `G-[A-Z0-9]{8,10}`. Invalid formats return 400. | Any server-side event tracking using legacy numeric IDs (pre-GA4 format) will silently fail without a code update. | Updated | |
| Google Ads API v15 sunset completed. All v15 calls return 404. | Adapters on v15 are completely broken. Current API version is v17. | Not Affected | |
| Snapchat | Story Ads v1 endpoint (`/v1/adaccounts/{id}/ads` with `type: STORY`) returns 410 Gone. | Story Ads must use v2 endpoint with `ad_type: STORY_AD` parameter format. | Updated |
| Snapchat | Dynamic Ads product catalog sync frequency limit reduced from 6 times/day to 3 times/day. | High-frequency catalog sync automation may hit new rate limits silently — check sync logs. | Monitoring |
Avergo: Snapchat Story Ads and GA4 measurement ID adapters were updated before the Snapchat sunset deadline. Google v15 — we have been on v17 since Q4. Zero disruption.