Executive summary
- What: since November 20, 2026 the two server pixel update mutations require an offline token, or an online token for a staff member with app access.
- Why: it closes a gap where a staff member without app access could change where a server pixel sends customer event data, aligning the update mutations with the create and delete equivalents.
- Who: apps that call these mutations with online access tokens. Offline tokens, and online tokens for users who do have app access, are unaffected.
What changed
Both eventBridgeServerPixelUpdate and pubSubServerPixelUpdate now perform a user access check before applying a change. An offline access token satisfies it unconditionally. An online token satisfies it only when the staff member it represents has access to the app in the Shopify admin. Scope requirements are unchanged: write_pixels, read_customer_events, and write_server_pixels behave exactly as before.
When the check fails, the mutation returns an access denied error with no payload, and the server pixel endpoint is left as it was. One detail is worth planning around: the error message is identical to the one returned for a missing access scope, and it does not mention user access, so an app that treats access denied as a scope problem will mislead whoever debugs it. The create and delete mutations already enforced this check, so the update path is now consistent rather than newly restricted. As a security fix, it applies to all Admin API versions immediately, with no deprecation window.
Why it matters
Server pixels forward customer event data to an external destination, which makes endpoint configuration a data governance control, not a routine setting. If any staff member holding an online token could repoint that destination, the permission boundary around customer event data was wider than the app access model implied. Narrowing it to users who genuinely have app access is the correct posture.
The practical question is whether anything in your stack calls these mutations from a session context. Apps that configure pixels from a background job already use offline tokens and will notice nothing. Those configuring them from an embedded admin interface, the common pattern for analytics and data pipeline tooling, are the ones to check. Teams working through the governance side of event data may find our notes on analytics and GDPR for Shopify merchants a useful companion.
Role-specific impact
- Marketers: no change to data already flowing. If a pixel destination needs repointing and your tooling runs in a session context, the staff member performing it now needs access to the relevant app.
- Developers: audit which token type these calls use. Move pixel configuration to an offline token or a background job where practical, and handle the access denied error explicitly, including a message that distinguishes a user access failure from a missing scope.
- Store admins: confirm that staff responsible for analytics configuration have access to the apps that manage server pixels. App access, not scope, is now the gate on these operations.
Use-case example
Real-world scenario
A merchant operates a custom data pipeline app that publishes checkout events to a warehouse. Its pixel endpoint was reconfigured through an embedded admin screen using the online token of whichever analyst was signed in. After the change, an analyst without app access attempted a scheduled endpoint rotation and received an access denied error that the app surfaced as a scope failure. The team spent close to three hours reviewing scopes before finding the real cause. Moving the call to the offline token held by their background worker removed the dependency on individual access.
Implementation checklist
- Identify every call site for both mutations across your apps and internal tooling.
- Record which token type each call site uses, separating offline from session-issued online tokens.
- Move pixel configuration to an offline token or a background job wherever the operation does not genuinely require a user context.
- Where an online token must be used, confirm the staff member has access to the app in the Shopify admin.
- Handle the access denied error explicitly, and log enough context to tell a user access failure apart from a missing scope.
- Test an update from an online token belonging to a user without app access, and confirm your error handling reports the cause clearly.
FAQ
Q: Could this have silently broken our existing pixel configuration?
A: The configuration itself is untouched. A failed mutation returns an error with no payload and leaves the endpoint as it was, so data keeps flowing to the previous destination. The risk is a repoint that appears applied but was not, which is why explicit error handling matters.
Q: Why was there no deprecation period for a breaking change?
A: Shopify classified it as a security fix, which applies across all API versions immediately.
Resources
eventBridgeServerPixelUpdate mutation reference
Need guidance? Talk to Makro.