Measurement Platform Change Velocity Report 2026

Executive Summary

Whoever runs a measurement architecture runs it on someone else’s ground. Google, Shopify, Meta, Apple, Mozilla and Microsoft change defaults, shut down access paths, move attribution rules and introduce features that alter the flow of data. The question of this report is not whether that happens, but how often, with how much warning and with what effect when nobody reacts.

The report dates and codes 69 measurement-relevant platform changes from ten platforms with an effective date between 1 January 2025 and 25 September 2026. Every change is recorded with announcement date, effective date, change type, measurement layer, automation, opt-out, actor and effect if nobody acts. For 65 changes both dates are available, so a notice period in days can be computed. All values come from official documentation, announcement or changelog pages of the platforms.

[CALCULATED] The median notice period across all 65 dated changes is 6 days. 31 changes were made public on the day they took effect or afterwards, two of them only six days after taking effect. Among the 34 changes with genuine advance notice the median is 63 days.

[CALCULATED] 57 of the 69 changes apply automatically, 49 provide no opt-out, 47 both at once. 38 changes alter reported numbers without the operator doing anything. For 19 of those 38 there is nobody who could act: the effect simply lands.

[CALCULATED] Notice and change type are tightly linked. Sunsets have a median notice of 357 days, default changes of 0 days. All 9 changes with 180 days of notice or more are sunsets of interface versions or runtime features. Not a single default change in the register had 180 days of notice.

[OBSERVED] Google Ads API, Google Analytics, Google Tag Manager, Shopify and Meta publish changes on permanently addressable, dated pages. The Google Analytics what’s new page is a release log: all 13 changes in the register dated there carry the day they took effect as their announcement date. [19][20]

[OBSERVED] For two of the three changes with the widest reach in the register, the sunset of script tags in Shopify stores without Plus on 26 August 2026 and Consent Mode becoming the single control for ads data from Google Analytics from 15 June 2026, the official pages carry no publication date. The notice period can therefore only be determined as a lower bound. [23][27]

[CALCULATED] In the exposure model a pure browser architecture is exposed to 34 of the 69 changes, a hybrid architecture with backend upload to 53. More paths mean more surface for changes. The difference lies in the response: without controls all 34 stay open. With monitoring, tests and shared identifiers every exposed change is detectable but none is correctable. Only a persisted backend event makes the 6 data losses correctable, only source-of-truth reconciliation the 32 silent shifts.

[CRITICAL] The register counts documented changes. It measures neither revenue impact nor frequency in real accounts and cannot be complete. A platform with a clean changelog appears in the register more often than one that changes quietly.

[INTERPRETATION] The greatest danger to a measurement architecture is not the announced sunset. It comes with a date, a notice period and a migration path. The greatest danger is the default change without an actor that shifts reported numbers and looks like a business trend while doing so.

[RECOMMENDATION] Organisations should treat platform changes as an operational event: with subscribed change feeds, ownership of accounts and projects, test transactions around every effective date, source-of-truth reconciliation in a window of two weeks before and after and break markers in every time series.

Citable key findings

1. [CALCULATED] 69 measurement-relevant platform changes from ten platforms took effect between 1 January 2025 and 25 September 2026, 32 of them in 2025 and 37 in 2026 up to the cutoff.
2. [CALCULATED] The median notice period is 6 days across all 65 dated changes and 63 days across the 34 changes with advance notice.
3. [CALCULATED] 31 of the 65 dated changes were made public on the day they took effect or afterwards. That is 48 percent.
4. [CALCULATED] Sunsets have a median notice of 357 days, required migrations of 27 days, policy changes of 30 days, default changes and new capabilities of 0 days.
5. [CALCULATED] 38 of the 69 changes alter reported numbers without the operator’s involvement. 28 of them are default changes. 19 of them have no actor.
6. [CALCULATED] 26 of the 69 changes affect the layer identity and attribution. It is the most-moved layer of measurement.
7. [OBSERVED] Since 15 June 2026 the Google Ads API no longer accepts offline conversion imports including enhanced conversions for leads from new connections. The announcement came on 15 May 2026, 31 days earlier. [11]
8. [OBSERVED] Google sunset the developer tokens of the Google Ads API on 9 September 2026. The documentation states the date as completed, the blog post about it appeared on 10 September 2026. [15][16]
9. [CALCULATED] In the exposure model a hybrid architecture is exposed to 53 changes, a browser architecture to 34. Only the complete architecture with source-of-truth reconciliation can correct 38 of them.
10. [RECOMMENDATION] Every effective date of a platform change belongs as an annotation in analytics and the ad account and as a break marker in every time series that is compared before and after the date.

---

1. Research question and protocol

How many measurement-relevant changes did the platforms in use let take effect between January 2025 and September 2026, with how much warning, with what degree of automation and with what effect on reported numbers if the operator does not react?

1.1 Unit of analysis

The unit of analysis is a platform change: a change documented by the platform to behaviour, access, default value, rule or feature scope that influences whether and how a business event is generated, transmitted, accepted, attributed, filtered, retained or reported.

Not units of analysis are price changes, interface redesigns without measurement effect, reporting features without influence on data collection or attribution and changes that concern campaign control only without feeding back into measurement data.

The second unit is the platform. Ten platforms are represented: Google Ads, Google Ads API including the Data Manager API, Google Analytics, Google Tag Manager including the Google tag and server containers, Shopify, Meta, Chrome, Safari, Firefox and Microsoft Advertising.

1.2 Inclusion criteria

A change was included when all three conditions hold:

• an official page of the platform describes the change: documentation, help page, changelog, developer blog, release note or company announcement;
• the effective date lies between 1 January 2025 and 25 September 2026 or the change was documented as already in effect within that window;
• the change touches at least one of the six measurement layers from FDR-2026-08: consent and governance, event generation and semantics, identity and attribution, transport and endpoint, platform and integration, operations and reconciliation.

1.3 Exclusion criteria

Not included were:

• changes whose date is documented only in trade or vendor media and not on an official page;
• changes with an effective date after 25 September 2026, even when announced within the window; they are listed separately in section 11;
• withdrawn changes; the initially announced requirement for the conversion_environment parameter on app conversions, withdrawn in June 2025, is therefore not in the register;
• beta features without general availability;
• regional policy changes outside the EEA, the United Kingdom and Switzerland;
• monthly version sunsets of the LinkedIn Marketing API as well as TikTok and Pinterest changes whose official pages carry no announcement date or whose content cannot be read without script execution.

1.4 Source hierarchy

All 55 numbered sources are Tier 1 in the sense of this edition: official vendor, browser or standards pages. Vendor pages document the behaviour of the vendor’s own system and its own dates. They do not document an independent effect size. Trade and vendor media were used only as pointers, never as evidence.

1.5 Coding rules

Eight fields are coded for every change:

• Change type: sunset, default change, new capability, migration required or policy change. Exactly one type per change, by the dominant effect.
• Measurement layer: one of the six layers from FDR-2026-08.
• Automation: 1 when the change applies without action by the operator, otherwise 0.
• Opt-out: none when the source names no way to decline or reverse the change; partial when only aspects can be switched off; full when the change stays voluntary.
• Actor: site owner; developer or tool provider; nobody when no action can prevent the effect.
• Effect if nobody acts: data loss, double counting risk, silent shift, feature unavailable or no effect.
• Silent number change: 1 when reported numbers change without action by the operator, otherwise 0.
• Components: which building blocks of a measurement architecture the change touches: browser tag, browser engine, first-party gateway, backend upload, platform account or shop runtime.

1.6 Notice period and date precision

The notice period is the difference in days between announcement date and effective date. The announcement date is the date the official page carries or the date the page names for the announcement. For interface versions it is the release date of the version, because the platforms publish the sunset date with the release.

Four precision rules:

• When a source names only the month, the first day of the month is recorded and the field is marked as a month value.
• When a source says “later this month”, the last day of the month is recorded and marked.
• When a page carries no date, the announcement field stays empty. The change counts in the register but not in the notice calculation. This affects 4 changes.
• A notice period of 0 days or less counts as “no advance notice”. It covers announcements on the day of taking effect and announcements afterwards.

Six notice classes are formed: no advance notice, under 30 days, 30 to 89 days, 90 to 179 days, 180 days and more, unknown.

1.7 Reproducibility and quality assurance

Four CSV files represent the register, the key figures, the exposure model and the response protocol. One script generates all four from the register and computes every number cited in the report. Automated checks ensure:

• exactly 69 unique change identifiers;
• every type, layer, actor and effect from the defined value set;
• every component from the defined set;
• notice period only where both dates exist;
• exposure values derived from components and controls, not maintained by hand.

[LIMITATION] The coding was produced as a single-author model. No independent double coding exists. Register and rules are disclosed so that every assignment can be reviewed externally and coded differently.

---

2. The change model

2.1 Five change types

Sunset. Something that used to run stops running from a date: an interface version, a script path, a cookie, a diagnostic field. Sunsets have a date and a replacement path. 17 changes in the register.

Default change. The platform behaves differently from a date without anyone changing a setting: a new attribution rule, a new channel, an automatically loaded tag, an automatic campaign migration. 31 changes.

New capability. Something becomes possible that was not possible before. The feature is voluntary, but using it can have permanent consequences. 11 changes.

Migration required. One path is closed for new users and another is required, usually with legacy access for active users. 5 changes.

Policy change. A condition of use changes: consent signal, retention period, authentication, data access. 5 changes.

2.2 Three actors

A change can address the site owner, who has to check a setting, maintain a list or set a filter. It can address the developer or tool provider, who switches an interface, raises a version or applies for a permission. Or it addresses nobody: the effect lands and no action in account, container or code prevents it.

[CALCULATED] 31 changes address developers or providers, 17 site owners, 21 nobody.

[INTERPRETATION] The actor “developer or provider” is the most dangerous for site owners, because the change concerns a tool the site owner does not see: the agency’s upload connector, the app in the shop, last year’s script. The site owner notices the change in the numbers, not in a notification.

2.3 Effect if nobody acts

For every change it is coded what happens when nobody reacts:

• Data loss: business events no longer arrive in the destination. 6 changes.
• Silent shift: numbers change without an event being missing or duplicated. Attribution, channel, value or counting rule are different. 32 changes.
• Feature unavailable: an access path, a version, a field or a diagnostic path is no longer available, usually with a visible error. 15 changes.
• No effect: without action everything stays as before. 16 changes.
• Double counting risk: no entry in the register. According to the sources, duplicates do not arise from the platform change itself but from the way the own migration is done; FDR-2026-08 covers that.

2.4 Silent number change

This field is the central metric of the report. It is set when a change alters reported numbers and the operator has to do nothing for that. The reason is simple: a number that changes without action is read as business development when nobody knows the date.

[CALCULATED] 38 of the 69 changes are silent number changes. 28 of them are default changes, 6 sunsets, 2 required migrations, 2 policy changes. No new capability changes numbers without involvement.

---

3. Register of the 69 changes

The full table with layer, automation, opt-out, actor, effect, components, sources and notes is in FDR-2026-09_platform_change_register.csv. Dates in ISO form. A notice of 0 means announcement on the day of taking effect, a negative value announcement afterwards, an empty field an undated source.

ID	Platform	Change	Announced	Effective	Notice in days	Type	Silent number change
C01	Google Ads	Customer Match: maximum membership duration of 540 days	2025-02-12	2025-04-07	54	Default change	yes
C02	Google Ads	Enhanced conversions: one unified setting for web and leads	unknown	2026-06-01		Default change	no
C03	Google Ads	AI Max: automatic upgrade of campaign-level broad match and automatically created assets	2026-04-15	2026-09-01	139	Default change	yes
C04	Google Ads API	debug_enabled removed from UploadClickConversions, CLICK_NOT_FOUND no longer returned	2025-06-26	2025-08-06	41	Sunset	no
C05	Google Ads API	gclid and gbraid accepted together on one ClickConversion	2025-07-22	2025-10-03	73	New capability	no
C06	Google Ads API	Account-default behaviour for automatically created conversion goals changed	2025-09-25	2025-11-17	53	Default change	yes
C07	Google Ads API	Data Manager API generally available	2025-12-09	2025-12-09	0	New capability	no
C08	Google Ads API	No new adopters of session attributes and IP address in conversion imports	2026-01-07	2026-02-02	26	Migration required	yes
C09	Google Ads API	No new adopters of Customer Match uploads through the Ads API	2026-03-04	2026-04-01	28	Migration required	no
C10	Google Ads API	Offline conversion import infrastructure changes	2026-03-26	2026-04-01	6	Default change	yes
C11	Google Ads API	37-month retention for granular performance data	2026-05-01	2026-06-01	31	Policy change	no
C12	Google Ads API	No new adopters of offline conversion imports including enhanced conversions for leads	2026-05-15	2026-06-15	31	Migration required	yes
C13	Google Ads API	Passkey required for new OAuth authorisations	2026-07-27	2026-08-05	9	Policy change	no
C14	Google Ads API	Developer tokens sunset, access level bound to the Google Cloud project	2026-09-09	2026-09-09	0	Sunset	no
C15	Google Ads API	Google Ads API v19 sunset	2025-02-26	2026-02-11	350	Sunset	no
C16	Google Ads API	Google Ads API v20 sunset	2025-06-04	2026-06-10	371	Sunset	no
C17	Google Ads API	Google Ads API v21 sunset	2025-08-06	2026-08-05	364	Sunset	no
C18	Google Analytics	Traffic source value “(data not available)” instead of “(not set)“	2025-03-31	2025-03-31	0	Default change	yes
C19	Google Analytics	Aggregate identifiers (gbraid, gad) used for attribution	2025-04-24	2025-04-24	0	Default change	yes
C20	Google Analytics	Automatic key events for the lead generation business objective	2025-06-12	2025-06-12	0	Default change	yes
C21	Google Analytics	Conversion completeness with two or more linked ad accounts	2025-08-06	2025-08-06	0	Default change	yes
C22	Google Analytics	User-provided data no longer part of the reporting identity	2025-11-05	2025-11-05	0	Default change	yes
C23	Google Analytics	Attribution settings per conversion	2026-01-16	2026-01-16	0	New capability	no
C24	Google Analytics	Data Manager API as an alternative to the Measurement Protocol	2026-05-07	2026-05-07	0	New capability	no
C25	Google Analytics	Channel “AI Assistant” with medium ai-assistant	2026-05-13	2026-05-13	0	Default change	yes
C26	Google Analytics	Source Group dimension, Source Platform reclassified retroactively	2026-06-11	2026-06-11	0	Default change	yes
C27	Google Analytics	Hostname exclude data filters	2026-06-11	2026-06-11	0	New capability	no
C28	Google Analytics	Consent Mode as the single control for ads data, Google Signals narrowed	unknown	2026-06-15		Default change	yes
C29	Google Analytics	Campaign data import requires a currency field	2026-07-28	2026-07-28	0	Migration required	no
C30	Google Analytics	Custom conversion windows	2026-08-11	2026-08-11	0	New capability	no
C31	Google Analytics	Hostname include data filters	2026-09-21	2026-09-21	0	New capability	no
C32	Google Tag Manager	Containers automatically load a Google tag before Google Ads and Floodlight tags	2025-03-10	2025-04-10	31	Default change	yes
C33	Google Tag Manager	Google tag gateway for advertisers generally available	2025-05-02	2025-05-08	6	New capability	no
C34	Google Tag Manager	Server container: GA client no longer serves Google scripts	2025-06-30	2025-06-30	0	Sunset	no
C35	Google Tag Manager	Server container: Floodlight sends unconsented requests server-to-server	2025-07-28	2025-07-28	0	Default change	yes
C36	Google Tag Manager	Google Ads automatically collects a broader range of website events	2026-02-04	2026-02-04	0	Default change	yes
C37	Google Tag Manager	Server container: conversions joined with parallel browser signals	2026-05-01	2026-05-01	0	Default change	yes
C38	Google Tag Manager	Container behaviour governed by container ID instead of load path	2026-07-09	2026-07-09	0	Default change	yes
C39	Google Tag Manager	Google tag and Tag Manager unified, visual tagging	2026-08-20	2026-08-20	0	Default change	no
C40	Shopify	Plus: checkout.liquid, script tags and additional scripts removed from thank-you and order status pages	2023-11-07	2025-08-28	660	Sunset	yes
C41	Shopify	Non-Plus: thank-you and order status pages upgraded automatically, script tags end	unknown	2026-08-26		Sunset	yes
C42	Shopify	ScriptTag API: no new tags with display_scope order_status or all	unknown	2025-02-01		Migration required	no
C43	Shopify	Web Pixels: checkout.subtotalPrice.amount net of order-level discounts	2025-04-30	2025-04-24	-6	Default change	yes
C44	Shopify	Web pixels load on customer accounts and the order status page	2025-07-21	2025-07-15	-6	Default change	yes
C45	Shopify	Protected customer data: approval enforced for personal fields in app pixels	2025-11-10	2025-12-10	30	Policy change	yes
C46	Shopify	Cookies _tracking_consent, _landing_page and _orig_referrer no longer set	2025-08-04	2025-09-15	42	Sunset	yes
C47	Shopify	Cookies _shopify_y and _shopify_s no longer set	2025-08-04	2026-01-01	150	Sunset	yes
C48	Shopify	Legacy Meta pixels and UA tags removed from preferences and converted to custom pixels	2025-02-01	2025-02-01	0	Default change	yes
C49	Meta	Graph API v16.0 sunset, last version with the Offline Conversions API	2023-05-23	2025-05-14	722	Sunset	yes
C50	Meta	Graph API v17.0 sunset	2023-05-23	2025-09-12	843	Sunset	no
C51	Meta	Graph API v18.0 sunset	2023-09-12	2026-01-26	867	Sunset	no
C52	Meta	Graph API v19.0 sunset	2024-01-23	2026-05-21	849	Sunset	no
C53	Meta	Graph API v20.0 sunset	2024-05-21	2026-09-24	856	Sunset	no
C54	Meta	Insights API: parameters for attribution setting and report time ignored	2025-03-10	2025-06-10	92	Default change	yes
C55	Meta	Attribution windows 7d_view and 28d_view removed	2025-10-16	2026-01-12	88	Sunset	yes
C56	Meta	Click attribution restricted to link clicks, engaged view becomes engage-through	2026-03-03	2026-03-31	28	Default change	yes
C57	Meta	AI-enhanced Meta Pixel sends additional page context	2026-04-15	2026-05-15	30	Default change	no
C58	Meta	Meta-enabled Conversions API with one click	2026-04-15	2026-04-15	0	New capability	no
C59	Chrome	Third-party cookies stay, no new standalone prompt	2025-04-22	2025-04-22	0	Policy change	no
C60	Chrome	IP Protection in Incognito mode	2025-04-22	2025-08-27	127	Default change	yes
C61	Chrome	Privacy Sandbox ad APIs retired, deprecation from Chrome 144	2025-10-17	2026-01-13	88	Sunset	no
C62	Chrome	Bounce tracking mitigations trigger without storage access	2024-12-01	2025-03-04	93	Default change	yes
C63	Safari	Safari 26.0: known fingerprinting scripts blocked, OS version frozen in the user agent	2025-09-15	2025-09-15	0	Default change	yes
C64	Safari	Safari 26.2: partitioned cookies (CHIPS) shipped again	2025-12-12	2025-12-12	0	New capability	no
C65	Firefox	Firefox 145: fingerprinting protections and stateless bounce tracking protection in ETP Strict	2025-11-10	2025-11-11	1	Default change	yes
C66	Firefox	Firefox 151: fingerprinting protection strengthened in standard mode	2026-05-19	2026-05-19	0	Default change	yes
C67	Microsoft Advertising	Consent Mode or TCF required for UET with users from the EEA, UK and Switzerland	2025-03-31	2025-05-05	35	Policy change	yes
C68	Microsoft Advertising	Modelled conversions for UET Consent Mode	2025-08-05	2025-08-05	0	Default change	yes
C69	Microsoft Advertising	Advanced Consent Mode	2026-02-19	2026-02-19	0	New capability	no

[OBSERVED] Three changes carry an announcement date that does not precede the effective date even though the source is dated: Shopify documented the change of the subtotal value in Web Pixels on 30 April 2025 with effect from 24 April 2025 and the loading of pixels on customer accounts and the order status page on 21 July 2025 with effect from 15 July 2025. [29][30] Google describes the sunset of developer tokens on 9 September 2026 as completed in the documentation; the blog post followed on 10 September 2026. [15][16]

---

4. Notice periods

4.1 Overall picture

[CALCULATED] Across the 65 dated changes the median notice period is 6 days, the shortest value minus 6 days, the longest 867 days. The mean is not meaningful because of interface sunsets with more than two years of notice and is not reported.

The distribution has two peaks. 31 changes lie at 0 days or below. 9 changes lie at 180 days and more. In between lie 25 changes, 13 of them in the class 30 to 89 days.

Notice class	Changes	Of which default change	Of which sunset
none	31	18	2
under 30	7	3	0
30 to 89	13	4	4
90 to 179	5	4	1
180 and more	9	0	9
unknown	4	2	1

4.2 By change type

Type	Changes	Median notice in days	Shortest	Longest	No advance notice	180 days and more	Silent number change
Sunset	17	357	0	867	2	9	6
Migration required	5	27	0	31	1	0	2
Policy change	5	30	0	35	1	0	2
Default change	31	0	-6	139	18	0	28
New capability	11	0	0	73	9	0	0

[CALCULATED] All 9 changes with 180 days of notice or more are sunsets: three versions of the Google Ads API with 350, 364 and 371 days, five versions of the Meta Graph API with 722 to 867 days and the sunset of script tags in Shopify Plus stores with 660 days. [17][36][26]

[CALCULATED] Of 29 dated default changes, 18 took effect without advance notice. The longest advance notice of a default change is 139 days: the automatic migration of Search campaigns to AI Max, announced on 15 April 2026, effective from 1 September 2026. [13][14]

[INTERPRETATION] Platforms give long notice where a breach of contract with developers looms and short or no notice where only numbers shift. From the platform’s point of view that is consistent. From the operator’s point of view it is exactly the opposite of what they would need.

4.3 Announcements on the day of taking effect

[OBSERVED] 13 of the 31 changes without advance notice come from the Google Analytics what’s new page. That page documents releases on the day of release. It is a log, not an advance announcement. [19][20] A further 6 come from the Tag Manager release notes, which have the same character. [21]

[LIMITATION] A value of 0 days does not mean the platform hid the change. It means the official source contains no earlier announcement. Internal advance information to partners or beta releases are not part of the register.

4.4 Undated sources

[OBSERVED] Four changes carry no computable notice period because the official page names no date: the unified setting for enhanced conversions in Google Ads [9], Consent Mode as the single control for ads data from Google Analytics from 15 June 2026 [23], the sunset of script tags in Shopify stores without Plus on 26 August 2026 [27] and the end of new order status scripts in the ScriptTag API from 1 February 2025 [28].

For two of them a lower bound can be determined: the Consent Mode page was public by April 2026 at the latest, the Shopify migration page by May 2025 at the latest. The notice period was therefore at least two months and at least fifteen months respectively. In the register both remain recorded as unknown, because a lower bound is not a date.

[CRITICAL] Undated does not mean short notice. It means the platform does not make its own notice period verifiable. For the operator that is the same situation as a change without advance notice: they cannot prove when they could have known.

---

5. Platform profiles

Platform	Changes	Notice computable	Median notice in days	No advance notice	Automatic	No opt-out	Silent number change
Chrome	4	4	90	1	4	4	2
Firefox	2	2	0	1	2	2	2
Google Ads	3	2	96	0	3	1	2
Google Ads API	14	14	31	2	13	11	4
Google Analytics	14	13	0	13	8	8	8
Google Tag Manager	8	8	0	6	6	4	5
Meta	10	10	407	1	9	8	4
Microsoft Advertising	3	3	0	2	2	2	2
Safari	2	2	0	2	1	1	1
Shopify	9	7	30	3	9	8	8

For Google Ads the median rests on two dated values of 54 and 139 days. For Safari and Firefox it rests on two values each.

5.1 Google Analytics

[OBSERVED] Google Analytics contributes 14 changes, among them 8 silent number changes: attribution through aggregate identifiers from 24 April 2025, conversion completeness with several linked ad accounts from 6 August 2025, the removal of user-provided data from the reporting identity from 5 November 2025, the AI Assistant channel from 13 May 2026 and the retroactive reclassification of Source Platform from 11 June 2026. [19][20]

Five of the 14 changes are new capabilities that stay voluntary but can have permanent consequences: the data filters for excluding and for allowing hostnames of 11 June 2026 and 21 September 2026 act permanently on raw data once activated. [19]

[INTERPRETATION] Google Analytics is the platform with the most silent shifts in the register and at the same time the one with the best traceability, because every change is dated and permanently addressable. The two belong together: whoever reads the page can assign every shift to a date. Whoever does not read it sees trends.

5.2 Google Tag Manager

[OBSERVED] Tag Manager contributes 8 changes, 5 of them silent number changes. Two concern the server container: since 28 July 2025 Floodlight tags there send unconsented requests server-to-server to improve modelled conversions and since 1 May 2026 server-to-server conversions are joined with parallel browser signals, which attributes conversions that were previously undercounted. [21] Both change numbers in the ad account without anyone touching a tag.

The change with the largest announcement gap is the automatic loading of a Google tag before Google Ads and Floodlight tags, announced on 10 March 2025 and effective from 10 April 2025. [21]

5.3 Google Ads and Google Ads API

[OBSERVED] The Google Ads API contributes 14 changes, 13 of them addressed to developers or providers. The series of required migrations follows a pattern: on 2 February 2026 acceptance of new adopters ended for session attributes and IP address, on 1 April 2026 for Customer Match uploads, on 15 June 2026 for offline conversion imports including enhanced conversions for leads. The notice periods were 26, 28 and 31 days. The replacement path in each case is the Data Manager API, generally available since 9 December 2025. [5][6][7][11]

[OBSERVED] Legacy access applies only with proven usage in a window before the change: October 2025 to March 2026 for Customer Match, December 2025 to May 2026 for offline conversion imports. [7][11] The sunset of developer tokens on 9 September 2026 follows the same logic: access levels were transferred to Google Cloud projects based on the usage of the 90 days before. [15]

[INTERPRETATION] Usage becomes the condition for continued operation. A tool that uploads seasonally or quarterly can be without usage in such a window and loses access without its code having changed.

Since September 2025 Google publishes four major versions of the Ads API per year with a lifetime of about one year. [18] The three versions v19, v20 and v21 sunset within the window had 350, 371 and 364 days of notice. [17]

5.4 Shopify

[OBSERVED] Shopify contributes 9 changes, 8 of them silent number changes and 2 data losses. The sunset of script tags on the thank-you and order status pages happened for Plus stores on 28 August 2025 after 660 days of notice from the announcement of 7 November 2023 and for stores without Plus on 26 August 2026 on an undated help page. [25][26][27]

Two changes were documented after they took effect, each with a gap of six days. [29][30] Two changes remove cookies from which scripts read the consent state and the client and session identifiers, on 15 September 2025 and on 1 January 2026. [32][33] Since 10 December 2025 app pixels without approval for protected customer data receive empty personal fields, which lowers match quality at Meta and Google. [31]

5.5 Meta

[OBSERVED] Meta contributes 10 changes with the highest median notice of all platforms at 407 days. The value is carried by five version sunsets of the Graph API whose dates are known with the release of each version. [36] With the sunset of v16.0 on 14 May 2025 the Offline Conversions API ended; according to Meta, v16.0 was the last version with support for offline events. [37]

The remaining Meta changes are announced on shorter notice: the attribution windows 7d_view and 28d_view were announced on 16 October 2025 and removed on 12 January 2026. [39] The restriction of click attribution to link clicks was announced on 3 March 2026 and took effect “later this month”. [40] The AI-enhanced Meta Pixel is enabled 30 days after notification unless the operator declines. [41]

5.6 Chrome, Safari and Firefox

[OBSERVED] Browser changes have no actor. On 22 April 2025 Chrome confirmed keeping third-party cookies and not introducing a new standalone prompt. [42] On 17 October 2025 Google announced the retirement of the Privacy Sandbox ad APIs, with deprecation from Chrome 144 of 13 January 2026. [43][44] IP Protection in Incognito mode was rolled out with Chrome 140 and added to the same list of retiring features in October 2025. [42][43][44]

[OBSERVED] Safari 26.0 of 15 September 2025 blocks known fingerprinting scripts from accessing device APIs, long-lived storage, URL parameters and the referrer and no longer reports the current operating system version in the user agent on iOS. [46][47] Safari 27 of 14 September 2026 documents no further change to tracking protection or storage lifetime. [49] Firefox 145 of 11 November 2025 and Firefox 151 of 19 May 2026 strengthened fingerprinting protection first in strict and then in standard mode. [50][51]

[LIMITATION] Browser changes act only on the share of visitors who use the respective browser, mode and protection level. The register counts the change, not its reach.

5.7 Microsoft Advertising

[OBSERVED] Since 5 May 2025 Microsoft Advertising requires a consent signal through Consent Mode or TCF for users from the EEA, the United Kingdom and Switzerland; without the signal, conversion measurement and remarketing lists stop. The announcement came on 31 March 2025, 35 days earlier. [52] Since August 2025 reports of eligible accounts include modelled conversions. [53] Advanced Consent Mode of 19 February 2026 stays voluntary. [54]

---

6. Automation, opt-out and actor

[CALCULATED] 57 of the 69 changes apply automatically. 49 provide no opt-out, 6 a partial one, 14 a full one. 47 changes are automatic and without opt-out at the same time. That is 68 percent of the register.

Effect if nobody acts	Changes	Actor site owner	Actor developer	Actor nobody
Silent shift	32	5	8	19
Feature unavailable	15	1	14	0
Data loss	6	3	3	0
No effect	16	8	6	2

[CALCULATED] Of the 32 silent shifts, 19 address nobody, 8 developers and 5 site owners. Of the 6 data losses, 3 address developers and 3 site owners; none addresses nobody. In the register a data loss always has an actor, a silent shift usually does not.

[INTERPRETATION] That is the core of the finding. Data losses are visible, addressed and usually come with notice. Silent shifts are invisible, without an actor and usually without notice. An organisation that secures its measurement only against data loss is not secured against the more frequent effect.

---

7. Silent number changes

[CALCULATED] 38 changes alter reported numbers without involvement. By platform: 8 at Google Analytics, 8 at Shopify, 5 at Tag Manager, 4 at the Google Ads API, 4 at Meta, 2 at Google Ads, 2 at Chrome, 2 at Firefox, 2 at Microsoft Advertising, 1 at Safari.

[CALCULATED] By layer: 19 of the 38 affect identity and attribution, 6 event generation and semantics, 5 consent and governance, 5 platform and integration, 2 transport and endpoint, 1 operations and reconciliation.

Three examples of how to read this:

Attribution moves. Since 24 April 2025 Google Analytics uses aggregate identifiers for attribution; paid Google Ads channels gain share, other channels lose it. [20] Since March 2026 Meta counts only link clicks as click attribution; click-attributed conversions fall and move into the new engage-through category. [40] In both cases no event is lost. The report looks different.

Value moves. Since 24 April 2025 Shopify outputs the subtotal net of order-level discounts in Web Pixels. Pixels that report this value as revenue have reported less since then, with unchanged revenue in the shop. [29]

Counting moves. Since 15 July 2025 Shopify Web Pixels also load on customer accounts and the order status page. Page views rise without any visitors having been added. [30]

[RECOMMENDATION] Every time series that is compared before and after one of these dates needs a break marker. Without it the shift is read as the success or failure of a measure that never existed.

---

8. The cluster in August and September 2026

[CALCULATED] 9 of the 69 changes took effect between 1 August 2026 and 25 September 2026. That is the densest sequence in the window.

ID	Platform	Change	Effective	Notice in days
C13	Google Ads API	Passkey required for new OAuth authorisations	2026-08-05	9
C17	Google Ads API	Google Ads API v21 sunset	2026-08-05	364
C30	Google Analytics	Custom conversion windows	2026-08-11	0
C39	Google Tag Manager	Google tag and Tag Manager unified, visual tagging	2026-08-20	0
C41	Shopify	Non-Plus: thank-you and order status pages upgraded automatically, script tags end	2026-08-26
C03	Google Ads	AI Max: automatic upgrade of campaign-level broad match and automatically created assets	2026-09-01	139
C14	Google Ads API	Developer tokens sunset, access level bound to the Google Cloud project	2026-09-09	0
C31	Google Analytics	Hostname include data filters	2026-09-21	0
C53	Meta	Graph API v20.0 sunset	2026-09-24	856

[INTERPRETATION] Within eight weeks the script path in Shopify stores without Plus went silent, the Google Ads API changed a version and its access key, Google merged the Google tag and Tag Manager, Search campaigns are moving to AI Max and Google Analytics gained two permanently acting data tools and custom conversion windows. Whoever notices one of these changes in the numbers without knowing the date looks for the cause in the business first.

[CRITICAL] The cluster is a finding about the window, not a forecast. The report does not claim that September is a regular month for changes.

---

9. Exposure of the reference architectures

FDR-2026-08 defined six reference architectures from A0 to A5, which differ by their control families K01 to K10. This report lays the register over the same architectures.

9.1 Rule

Every architecture is assigned a set of components: browser tag, browser engine, platform account and shop runtime for A0 to A2, additionally the first-party gateway for A3 and additionally the backend upload for A4 and A5.

exposed(A, c) =
  change c has an effect other than "no effect"
  and touches at least one component of A

detectable(A, c) =
  exposed and A contains a control
  that can detect this effect

correctable(A, c) =
  exposed and A contains a control
  that can correct this effect

open(A, c) =
  exposed and not detectable

Can detect: K08, K09 and K10 a data loss; K08 and K10 a silent shift; K09 and K10 an unavailable feature. Can correct: K05 and K08 a data loss; K08 a silent shift. An unavailable feature is correctable by no control, only by migration.

9.2 Result

ID	Reference architecture	Controls	Exposed	Detectable	Correctable	Open
A0	Unmanaged browser-only	none	34	0	0	34
A1	Governed client-side	K01, K02, K07, K09, K10	34	34	0	0
A2	Consent-aware multi-domain client	K01, K02, K03, K07, K09, K10	34	34	0	0
A3	First-party transport	K01, K02, K03, K04, K07, K09, K10	37	37	0	0
A4	Hybrid browser + backend	K01, K02, K03, K04, K05, K07, K09, K10	53	53	6	0
A5	Auditable hybrid + reconciliation	K01, K02, K03, K04, K05, K06, K07, K08, K09, K10	53	53	38	0

[CALCULATED] Exposure rises with the architecture: 34 changes for A0 to A2, 37 for A3, 53 for A4 and A5. The 19 additional changes for hybrid architectures are changes to backend upload and first-party gateway that do not affect a pure browser architecture.

[CALCULATED] Already A1 with consent state, event contract, shared identifiers, tests and monitoring can detect all 34 exposed changes, but correct none. A4 with the persisted backend event can correct the 6 data losses. Only A5 with source-of-truth reconciliation can additionally correct the 32 silent shifts, 38 in total.

9.3 Reading and limit

[INTERPRETATION] A hybrid architecture trades reach for surface. It sees more business events and is exposed to more changes. That is not an argument against hybrid architectures. It is an argument for running them only with the controls that can detect and correct their exposure.

[CRITICAL] Detectable means: the architecture contains a control that can make the effect visible. It does not mean the organisation sees it. Correctable means: a reconciliation against the authoritative source can show and classify the shift. It does not mean the platform recalculates its numbers.

[LIMITATION] The exposure model is binary and unweighted. It counts changes, not reach, revenue impact or duration. A change that affects all Safari users counts as much as one that affects only accounts with two linked ad accounts.

---

10. Response protocol

Twelve protocol items translate the finding into operational requirements. Every item names the change types it applies to and the control family from FDR-2026-08 it belongs to.

ID	Stage	Requirement	Change types	Control from FDR-2026-08
R01	Operations	The official announcement pages of every platform in use are recorded with an owner and a review cadence.	Sunset, Default change, Migration required, Policy change, New capability	K10
R02	Operations	Every integration is recorded with platform, access path (tag, pixel, app, API, upload), project and owner.	Sunset, Migration required	K10
R03	Operations	Ad account, analytics property, container and cloud project are owned by the operator, not by an agency.	Sunset, Migration required	K10
R04	Lead time	For sunsets and required migrations an internal completion date before the effective date is defined.	Sunset, Migration required	K09
R05	Lead time	Every announced default change is consciously accepted or declined before the effective date.	Default change	K09
R06	Measurement	Before and after every effective date a synthetic transaction proves destination acceptance per path.	Sunset, Default change, Migration required	K09
R07	Measurement	Orders or leads are reconciled against every destination for two weeks before and after the date.	Sunset, Default change, Migration required, Policy change	K08
R08	Measurement	Every effective date is recorded as an annotation in analytics and the ad account.	Sunset, Default change, Migration required, Policy change, New capability	K10
R09	Measurement	When old and new run in parallel during a migration, the duplicate rate is measured per destination.	Migration required	K07
R10	Evidence	Every own response is documented with date, owner, version and rollback point.	Sunset, Default change, Migration required, Policy change, New capability	K10
R11	Evidence	Changes with a permanent effect on raw data are activated only after a test mode and documented approval.	New capability, Default change	K09
R12	Evidence	Time series carry a break marker from the effective date of a silent shift.	Default change, Policy change	K08

[RECOMMENDATION] The reconciliation window of two weeks before and after the effective date in R07 is a minimum. For attribution changes with long windows, say 90 days of click attribution, the effect spreads over weeks and the reconciliation has to run correspondingly longer.

[RECOMMENDATION] R11 applies in particular to the data filters in Google Analytics: an active filter acts permanently on raw data. The testing mode with the dimension “Test data filter name” is the only way to see before activation what would be lost. [19]

---

11. Announced, but effective after the cutoff

Four changes were announced within the window but only take effect after 25 September 2026. They are not in the register because their taking effect could not be observed.

Platform	Change	Announced	Effective	Notice in days
Google Ads	Dynamic Search Ads upgraded to AI Max, postponed from September 2026	2026-06-11	2027-02-01	235
Shopify	ScriptTag API: creating and updating script tags returns errors	2026-08-24	2026-10-01	38
Shopify	ScriptTag API: script tags stop running	2026-08-24	2027-03-01	189
Microsoft Advertising	SOAP interface: new features only through REST	2026-04-01	2026-10-01	183

Sources: [14][35][55]. Added to that is the planned removal of the Privacy Sandbox APIs from Chrome, for which Google names Chrome 152 in the release notes; the deprecation from Chrome 144 is in the register, the removal is not. [44]

[OBSERVED] On 11 June 2026 Google postponed the migration of Dynamic Search Ads from September 2026 to February 2027. [14] Postponements happen. The register contains no case in which a date was brought forward.

---

12. 30/60/90-day implementation

Days 0 to 30: inventory and ownership

• record all platforms in use and their official change pages with an owner;
• inventory every integration with access path, project and owner;
• check and transfer ownership of ad account, property, container and cloud project;
• check the 9 changes from August and September 2026 against the own setup;
• add annotations for all effective dates of the current year in analytics and the ad account.

Gate: For every integration it is known through which path it reports, who owns the access and which change page concerns it.

Days 31 to 60: lead-time budget and tests

• define the lead-time budget per change type;
• set up the test transaction as a repeatable procedure with a check of destination acceptance per path;
• set up source-of-truth reconciliation as a routine with a two-week window;
• consciously accept or decline open default changes, such as AI Max and the AI-enhanced Meta Pixel;
• check tools uploading to Google Ads for Data Manager API and cloud project.

Gate: Every change with an effective date in the next 90 days has a date, an owner and a test case.

Days 61 to 90: break markers and operations

• add break markers to time series for all silent shifts;
• activate duplicate checks for running migrations;
• keep a change log with rollback per own response;
• activate permanently acting features only after testing mode and approval;
• define and keep a review cadence for change feeds.

Gate: Every deviation in a time series can be assigned either to an effective date, to an own change or to the business.

Stop rules

• no activation of a permanently acting filter without testing mode;
• no migration without a test transaction before and after the cutover;
• no reading of a number shift as a business trend while an effective date lies in the window;
• no upload tool without a known cloud project and a known owner;
• stop on access that depends on usage in a window the own tool does not reliably meet.

---

13. Executive scorecard

Dimension	Core question	Reliable indicator
Visibility	Does the organisation know every relevant change page?	List of feeds with owner and last review date
Ownership	Do account, property, container and project belong to the operator?	Access evidence per system
Lead time	Is there an internal completion date per change type?	Lead-time budget and adherence
Decision	Was every default change consciously accepted or declined?	Decision log with date
Test	Does a test transaction prove destination acceptance before and after the date?	Test case with result per path
Reconciliation	Is the variance against the source measured around every date?	Reconciliation rows with business identifier
Break marker	Does every time series carry the relevant effective dates?	Annotations in analytics and ad account
Migration	Is every required migration completed before the date?	Remaining list with dates
Evidence	Is every own response documented with rollback?	Change log
Permanence	Was every permanently acting feature tested first?	Testing mode evidence before activation

No single dimension replaces the others. A complete inventory without break markers explains no shift. A reconciliation without ownership of the account cannot act.

---

14. Visualisation specification

Chart 1: notice period per change

• File: FDR-2026-09_platform_change_register.csv
• X axis: effective date, Y axis: notice in days, logarithmic from 1 with a separate zone for 0 and negative values;
• colour by change type, shape by platform;
• undated changes as markers without Y value at the bottom edge;
• table fallback with all 69 identifiers.

Chart 2: notice classes by type

• File: FDR-2026-09_change_summary.csv
• stacked bars per type, six classes;
• no percentage axis without absolute number;
• annotation: 0 days means announcement on the day of taking effect.

Chart 3: silent number changes by platform and layer

• File: FDR-2026-09_platform_change_register.csv
• matrix platform by layer, cell value number of silent number changes;
• tooltip with identifiers of the changes;
• filter by actor.

Chart 4: exposure of the reference architectures

• File: FDR-2026-09_architecture_exposure.csv
• four bars per architecture: exposed, detectable, correctable, open;
• Y axis 0 to 69;
• annotation: model count, not reach.

Chart 5: timeline August to September 2026

• File: FDR-2026-09_platform_change_register.csv, filtered to the window;
• 9 changes on one axis with platform and notice;
• no extrapolation beyond the cutoff.

Accessibility

• every chart with figcaption;
• complete text alternative;
• values in the DOM, not only canvas;
• keyboard access to filters;
• no meaning through colour alone;
• mobile tables horizontally scrollable;
• download link directly at the chart.

---

15. Reproducibility

Files

1. data/FDR-2026-09_platform_change_register.csv
2. data/FDR-2026-09_change_summary.csv
3. data/FDR-2026-09_architecture_exposure.csv
4. data/FDR-2026-09_change_response_protocol.csv

Checksums

• FDR-2026-09_platform_change_register.csv
  SHA-256 79dbbcda9e9a8fc091ceb83a6e399a16510df7a0b039459a97dd84889087e11d
• FDR-2026-09_change_summary.csv
  SHA-256 50463c77bc633f28856b8d605f655fe36e6bea3ae81d7f3deabf85cab9ed2765
• FDR-2026-09_architecture_exposure.csv
  SHA-256 728fc3be5337c157a457f837725d7ac9211a12e6f10aabcddfeb2658caa74c56
• FDR-2026-09_change_response_protocol.csv
  SHA-256 f61ab3ad59e285c589e85143e887ac677bc0f195a2435e0bfb88cd213e4ffcf6

Calculation rules

• Notice in days is effective date minus announcement date; only where both dates exist.
• Month values are set to the first day of the month, “later this month” to the last day; both are marked as precision in the register.
• The median is computed over whole days and rounded down for an even count.
• Notice classes: no advance notice at 0 days and less, under 30, 30 to 89, 90 to 179, 180 and more, unknown.
• Boolean fields are 0 or 1.
• Exposure, detectability and correctability per architecture are derived from components, effect and control families, not maintained by hand.
• No weighted total score, no imputation of missing data.

Versioning

Material changes to register, coding, class boundaries, exposure rule or conclusions produce at least version 1.1. Announcement dates found later for the 4 undated changes produce version 1.1 with recomputed key figures. Typos or broken links can be corrected as 1.0.1. CSV, charts, claim ledger and report version must be updated together.

---

16. Limitations

1. The register contains documented changes. Changes without an official page are missing. Platforms with better documentation are over-represented.
2. The selection of what is measurement-relevant is a coding decision. Other coders would include or omit individual changes.
3. The announcement date is the date of the official page. Earlier hints to partners, beta phases or conference announcements without a date are not captured.
4. For 4 changes the official page is undated. Their notice period is missing from all notice figures.
5. Month values were set to a day. For 4 changes the notice period is therefore imprecise to the day.
6. For version sunsets the release date of the version counts as the announcement. That measures the lifetime of the version, not the operator’s attention.
7. The coding “silent number change” describes whether numbers can change without action, not by how much.
8. Changes are unweighted. Reach, revenue impact, duration and regional scope are not included.
9. Browser changes act only on a share of visitors; that share is not part of the register.
10. The exposure model adopts the architectures and controls from FDR-2026-08 and inherits their limits, in particular the single-author coding.
11. The window ends on 25 September 2026. Changes with a later effective date are captured only in section 11.
12. The report is not legal advice. Consent and policy changes are classified technically.
13. Vendor pages can be changed after the fact. The checksums secure the supporting data, not the sources.
14. The cluster in August and September 2026 is a finding about the window, not a statement about future months.
15. LinkedIn, TikTok and Pinterest are not represented because the official pages do not meet the inclusion criteria; that is a gap of the register, not a statement about those platforms.

---

17. Permitted and prohibited statements

Permitted

“In the FW Delta register the median notice period across 65 dated platform changes is 6 days; 31 were made public on the day they took effect or afterwards.”

Prohibited

“Platforms announce changes only 6 days in advance on average.”

Permitted

“All 9 changes with 180 days of notice or more are sunsets; no default change in the register had 180 days of notice.”

Prohibited

“Default changes are never announced in advance.”

Permitted

“38 of the 69 changes can alter reported numbers without action by the operator.”

Prohibited

“38 changes altered the numbers of every ad account.”

Permitted

“In the exposure model a hybrid architecture is exposed to 53 changes, a browser architecture to 34.”

Prohibited

“Hybrid architectures are riskier than browser architectures.”

Permitted

“Google sunset the developer tokens on 9 September 2026; the blog post appeared on 10 September 2026.”

Prohibited

“Google did not announce the sunset of the developer tokens.”

Permitted

“9 changes took effect between 1 August 2026 and 25 September 2026.”

Prohibited

“Platform changes regularly cluster in September.”

---

18. Version history

• 1.0 · September 2026 · First edition with 69 changes, 10 platforms, 65 notice periods, exposure model across 6 reference architectures, 12 protocol items and 4 supporting datasets.
• Open · Add announcement dates for the 4 undated changes as soon as the platforms publish them; cutoff for version 1.1 after completion of the AI Max migration.

---

19. Sources

1. Google, “Update to Customer Match membership duration”, https://ads-developers.googleblog.com/2025/02/update-to-customer-match-membership.html, accessed 25 September 2026.
2. Google, “Upcoming removal of debug_enabled in UploadClickConversions”, https://ads-developers.googleblog.com/2025/06/upcoming-removal-of-debugenabled-in.html, accessed 25 September 2026.
3. Google, “Increased flexibility for Google Ads conversion uploads”, https://ads-developers.googleblog.com/2025/07/increased-flexibility-for-google-ads.html, accessed 25 September 2026.
4. Google, “Streamlined account-default conversion goals”, https://ads-developers.googleblog.com/2025/09/streamlined-account-default.html, accessed 25 September 2026.
5. Google, “The Data Manager API is now generally available”, https://ads-developers.googleblog.com/2025/12/the-data-manager-api-is-now-generally.html, accessed 25 September 2026.
6. Google, “Changes to IP address and session attributes in conversion imports”, https://ads-developers.googleblog.com/2026/01/changes-to-ip-address-and-session.html, accessed 25 September 2026.
7. Google, “Changes to Customer Match support in the Google Ads API”, https://ads-developers.googleblog.com/2026/03/changes-to-customer-match-support-in.html, accessed 25 September 2026.
8. Google, “Upcoming improvements to offline conversion imports”, https://ads-developers.googleblog.com/2026/03/upcoming-improvements-to-offline.html, accessed 25 September 2026.
9. Google, “Changes to enhanced conversions settings”, https://support.google.com/google-ads/answer/16884284, accessed 25 September 2026.
10. Google, “New data retention policy for Google Ads APIs”, https://ads-developers.googleblog.com/2026/05/new-data-retention-policy-for-google.html, accessed 25 September 2026.
11. Google, “Changes to offline click conversion imports”, https://ads-developers.googleblog.com/2026/05/changes-to-offline-click-conversion.html, accessed 25 September 2026.
12. Google, “Passkey authentication requirement for the Google Ads API”, https://ads-developers.googleblog.com/2026/07/passkey-authentication-requirement-for.html, accessed 25 September 2026.
13. Google, “Migrate campaign-level broad match and automatically created assets to AI Max”, https://ads-developers.googleblog.com/2026/08/migrate-campaign-level-broad-match-and.html, accessed 25 September 2026.
14. Google, “Dynamic Search Ads upgrade to AI Max”, https://blog.google/products/ads-commerce/dsa-upgrade-to-ai-max-2026/, accessed 25 September 2026.
15. Google, “Google Ads API: Developer token”, https://developers.google.com/google-ads/api/docs/api-policy/developer-token, accessed 25 September 2026.
16. Google, “New onboarding experience for the Google Ads API”, https://ads-developers.googleblog.com/2026/09/new-onboarding-experience-for-google-ads-api.html, accessed 25 September 2026.
17. Google, “Google Ads API: Sunset dates”, https://developers.google.com/google-ads/api/docs/sunset-dates, accessed 25 September 2026.
18. Google, “More frequent releases coming for the Google Ads API”, https://ads-developers.googleblog.com/2025/09/more-frequent-releases-coming-for.html, accessed 25 September 2026.
19. Google, “What’s new in Google Analytics”, https://support.google.com/analytics/answer/9164320, accessed 25 September 2026.
20. Google, “What’s new in Google Analytics: archive 2019 to 2025”, https://support.google.com/analytics/answer/13420269, accessed 25 September 2026.
21. Google, “Tag Manager release notes”, https://support.google.com/tagmanager/answer/4620708, accessed 25 September 2026.
22. Google, “Updates to Google tag and Google Tag Manager”, https://support.google.com/tagmanager/answer/17079602, accessed 25 September 2026.
23. Google, “Updates to Google Analytics Data Controls”, https://support.google.com/analytics/answer/17016975, accessed 25 September 2026.
24. Google, “Google tag gateway for advertisers”, https://support.google.com/google-ads/answer/16214371, accessed 25 September 2026.
25. Shopify, “checkout.liquid”, https://shopify.dev/docs/storefronts/themes/architecture/layouts/checkout-liquid, accessed 25 September 2026.
26. Shopify, “Extensibility is now available for Plus merchants on Thank you and Order status pages”, https://changelog.shopify.com/posts/extensibility-is-now-available-for-plus-merchants-on-thank-you-and-order-status-pages, accessed 25 September 2026.
27. Shopify, “Upgrading and replacing your Thank you and Order status pages”, https://help.shopify.com/en/manual/checkout-settings/customize-checkout-configurations/upgrade-thank-you-order-status, accessed 25 September 2026.
28. Shopify, “Blocking script tags”, https://shopify.dev/docs/apps/build/online-store/blocking-script-tags, accessed 25 September 2026.
29. Shopify, “Web Pixels API: checkout.subtotalPrice.amount value change”, https://shopify.dev/changelog/web-pixels-api-eventdatacheckoutsubtotalpriceamount-value-change-on-the-new-thank-you-page-and-checkout-events, accessed 25 September 2026.
30. Shopify, “Web pixels now run on Customer Accounts and Order status page”, https://shopify.dev/changelog/web-pixels-now-run-on-customer-accounts-and-order-status-page, accessed 25 September 2026.
31. Shopify, “Protected customer data scopes required for web pixels”, https://shopify.dev/changelog/protected-customer-data-scopes-required, accessed 25 September 2026.
32. Shopify, “_tracking_consent, _landing_page and _orig_referrer cookies will no longer be set”, https://shopify.dev/changelog/trackingconsent-landingpage-origreferrer-cookies-will-no-longer-be-set, accessed 25 September 2026.
33. Shopify, “_shopify_y and _shopify_s cookies will no longer be set”, https://shopify.dev/changelog/shopifyy-and-shopifys-cookies-will-no-longer-be-set, accessed 25 September 2026.
34. Shopify, “Migrating pixels”, https://help.shopify.com/en/manual/promoting-marketing/pixels/pixel-migration, accessed 25 September 2026.
35. Shopify, “Online Store script tags deprecation”, https://shopify.dev/changelog/online-store-script-tags-deprecation, accessed 25 September 2026.
36. Meta, “Graph API changelog”, https://developers.facebook.com/docs/graph-api/changelog, accessed 25 September 2026.
37. Meta, “Graph API v17.0 changelog”, https://developers.facebook.com/docs/graph-api/changelog/version17.0, accessed 25 September 2026.
38. Meta, “Marketing API: out-of-cycle changes 2025”, https://developers.facebook.com/docs/marketing-api/out-of-cycle-changes/occ-2025/, accessed 25 September 2026.
39. Meta, “Ads Insights API metric availability updates”, https://developers.facebook.com/blog/post/2025/10/16/ads-insights-api-metric-availability-updates/, accessed 25 September 2026.
40. Meta, “Updates to click attribution”, https://www.facebook.com/business/news/click-attribution, accessed 25 September 2026.
41. Meta, “Updates to Meta Pixel and Conversions API”, https://www.facebook.com/business/news/pixel-conversionsapi-updates, accessed 25 September 2026.
42. Google, “Next steps for Privacy Sandbox and tracking protections in Chrome”, https://privacysandbox.google.com/blog/privacy-sandbox-next-steps, accessed 25 September 2026.
43. Google, “Update on plans for Privacy Sandbox technologies”, https://privacysandbox.google.com/blog/update-on-plans-for-privacy-sandbox-technologies, accessed 25 September 2026.
44. Google, “Chrome Enterprise and Education release notes”, https://support.google.com/chrome/a/answer/10314655, accessed 25 September 2026.
45. Chromium, “Bounce tracking mitigations without storage access”, https://chromestatus.com/feature/6299570819301376, accessed 25 September 2026.
46. WebKit, “WebKit Features in Safari 26.0”, https://webkit.org/blog/17333/webkit-features-in-safari-26-0/, accessed 25 September 2026.
47. Apple, “Safari 26 Release Notes”, https://developer.apple.com/documentation/safari-release-notes/safari-26-release-notes, accessed 25 September 2026.
48. WebKit, “WebKit Features in Safari 26.2”, https://webkit.org/blog/17640/webkit-features-for-safari-26-2/, accessed 25 September 2026.
49. Apple, “Safari 27 Release Notes”, https://developer.apple.com/documentation/safari-release-notes/safari-27-release-notes, accessed 25 September 2026.
50. Mozilla, “Firefox 145.0 release notes”, https://www.firefox.com/en-US/firefox/145.0/releasenotes/, accessed 25 September 2026.
51. Mozilla, “Firefox 151.0 release notes”, https://www.firefox.com/en-US/firefox/151.0/releasenotes/, accessed 25 September 2026.
52. Microsoft, “Providing user consent signals on your Microsoft campaigns by May 5, 2025”, https://about.ads.microsoft.com/en/blog/post/march-2025/providing-user-consent-signals-on-your-microsoft-campaigns-by-may-5-2025, accessed 25 September 2026.
53. Microsoft, “Impression-based remarketing updates and other product news for August”, https://about.ads.microsoft.com/en/blog/post/august-2025/impression-based-remarketing-updates-and-other-product-news-for-august, accessed 25 September 2026.
54. Microsoft, “Advanced Consent Mode: preserving accurate measurement while respecting user privacy”, https://about.ads.microsoft.com/en/blog/post/february-2026/advanced-consent-mode-preserving-accurate-measurement-while-respecting-user-privacy, accessed 25 September 2026.
55. Microsoft, “Evolving the Microsoft Advertising API platform”, https://about.ads.microsoft.com/en/blog/post/april-2026/evolving-the-microsoft-advertising-api-platform, accessed 25 September 2026.

---

Disclosure and disclaimer

FW Delta provides web tracking, Shopify tracking, Consent Mode, server-side tagging, conversion interfaces and tracking monitoring as commercial services. The company can economically benefit when organisations have measurement architectures reviewed, migrated or monitored.

That position may influence question selection and interpretation. Therefore the report publishes:

• the full register with sources per change;
• coding rules and class boundaries;
• exposure rule and control assignment;
• calculation rules;
• checksums;
• limitations and prohibited statements.

The report does not rank platforms and does not claim a damage amount. A high number in the register is not a judgement about the quality of a platform; it can be an expression of good documentation.

The report does not replace legal, data protection or platform approval. Consent, data categories, contracts, responsibilities and local law must be assessed individually.

Supporting data

• FDR-2026-09_platform_change_register.csv
  69 rows · 21 columns · changes with dates, precision, notice, type, layer, automation, opt-out, actor, effect, components, sources and notes.
• FDR-2026-09_change_summary.csv
  21 rows · 12 columns · key figures per platform, change type and measurement layer.
• FDR-2026-09_architecture_exposure.csv
  414 rows · 12 columns · exposure, detectability and correctability per architecture and change.
• FDR-2026-09_change_response_protocol.csv
  12 rows · 8 columns · protocol items with stage, requirement, change types and control family.

License: All rights reserved. An open license for the supporting datasets has not yet been decided. Every reuse must identify: FW Delta Research, Measurement Platform Change Velocity Report 2026, FDR-2026-09, Version 1.0, data cutoff 25 September 2026.

Commercial offers by FW Delta

Commercial services from the publisher. They are not part of the research findings.

• Tracking check: Review every route by which an order or lead is reported, including access, ownership and affected changes.
• Tracking monitoring: Source-of-truth reconciliation, test transactions and break markers as a routine.
• Shopify tracking: Migration of script paths to customer events and server with a shared identifier.
• Server-side tracking: Backend events and Data Manager API with queue, consent and reconciliation.
• Technical tracking audit: Apply the 12 protocol items to the own architecture.