DeskLeap
ProductFeaturesPricingShopifyBlog
← Back to Blog

Shopify's Server-Pixel Update Check Returns the Wrong Error: Why 'Missing Access Scope' May Mean 'This Staff Member Can't Use Your App'

November 20, 2026·5 min read
Shopify's Server-Pixel Update Check Returns the Wrong Error: Why 'Missing Access Scope' May Mean 'This Staff Member Can't Use Your App'

Shopify's developer changelog entry of 20 November 2026 is flagged Breaking API Change and Action required, and it is already in force. It changes who may call two GraphQL Admin API mutations: eventBridgeServerPixelUpdate and pubSubServerPixelUpdate. In Shopify's words: "Starting November 20, 2026, the eventBridgeServerPixelUpdate and pubSubServerPixelUpdate mutations reject online access tokens for users who don't have access to the app. The change applies to all GraphQL Admin API versions."

The change itself is small. The way it fails is not, because the error points somewhere else.

The error names the wrong cause

This is the sentence from the entry to remember: "When the check fails, the mutation returns an access denied error and no payload, and the server pixel's endpoint stays the same. The error message is the same one you get for a missing access scope, so it doesn't mention user access."

So a developer who hits it sees what looks like a scope problem. The natural next step is to check the app's scopes: write_pixels, read_customer_events and write_server_pixels. Those will look fine, because they are fine. Shopify says so directly: "The write_pixels, read_customer_events, and write_server_pixels access scope requirements don't change."

The real cause is not what the app is allowed to do. It is who made the call. An online access token belongs to a particular staff member, and from 20 November these two mutations check whether that staff member has access to the app.

What changed, exactly

Shopify's entry: "Both mutations now require an offline access token, or an online access token for a user who has access to the app."

  • Offline access tokens: work as before.
  • Online access tokens for a staff member who has access to the app: work as before.
  • Online access tokens for a staff member who doesn't have access to the app: now rejected with an access denied error and no payload.

Nothing is moved when the call is refused. The server pixel's endpoint stays the same. The update simply doesn't happen.

Why Shopify did it: "The update mutations now make the same user access check that serverPixelCreate and serverPixelDelete already make, so only a user who has access to an app can change where its server pixel sends events." The create and delete mutations already had this check; the update mutations now match them.

No deprecation period, no version to pin

Many Shopify changes come with a date months ahead and an API version you can stay on for a while. This one doesn't. Shopify: "This is a security fix, so it applies to all API versions without a deprecation period." It started on 20 November 2026 and it applies to every GraphQL Admin API version.

That also makes it a separate item from the other Shopify app deadlines this month. Each has its own scope and date, so check each entry on its own.

Who is affected

Shopify: "This affects apps that call these mutations with an online access token for a staff member who doesn't have access to the app."

One way it can show up is an app screen that lets a staff member change the server pixel's EventBridge or Pub/Sub destination, using that staff member's online token. If the staff member has app access, it works. If not, the save fails, and the error looks like a scope problem.

The two real fixes

Shopify gives two, and one instruction that applies to both:

  1. Make sure the staff member has access to the app in the Shopify admin, if the call should run as that person.
  2. Call the mutations with an offline access token instead, "for example from a background job".
  3. Either way, handle the access denied error. Because the message reads like a missing scope, it's worth having the app say what is more likely: that this user may not have access to the app.

What isn't a fix: requesting the three scopes again. They didn't change, so re-checking them only uses up time.

What support teams should watch for

If you support a Shopify app, or a store that runs one, this can arrive as "your app is broken" or "it says a permission is missing", from one person while a colleague on the same store has no trouble. The difference between them may be whether each person has access to the app, not the app's scopes.

Two questions get to the answer quickly:

  • Does the staff member who saw the error have access to the app in the Shopify admin?
  • Does the app make this call with that person's online token, or with an offline token?

Write that answer down once in your knowledge base, with the date and the source. Then whoever picks up the next ticket starts from the right question instead of the scope list.

If you're setting that up, DeskLeap brings tickets, live chat and a knowledge base into one place. The platform is 100% free with unlimited human agents; an optional AI Agent add-on is $29/mo each.

Source: Shopify developer changelog, "eventBridgeServerPixelUpdate and pubSubServerPixelUpdate now require user access to the app", dated 20 November 2026, read 21 November 2026: shopify.dev.

Related posts

  • Shopify Network Access Declarations: What Changes on 1 December, What Changes on 1 January, and Which Apps Aren't Affected
  • Shopify's abandoned checkout URL now needs all four protected customer data approvals
  • Shopify B2B Customer Account API Change: Blank Is Not Deleted
Older post: Shopify's abandoned checkout URL now needs all four protected customer data approvals← All Posts
DeskLeap

Customer support that scales with your team — not against it.

Product
  • Inbox
  • Live chat
  • Knowledge base
  • Leap AI
  • Analytics
  • All features
  • Integrations
  • Shopify app
  • WordPress plugin
  • React SDK
  • Blog
Compare
  • vs Zendesk
  • vs Intercom
  • vs Freshdesk
  • vs Help Scout
  • vs Gorgias
  • vs Tidio
  • vs tawk.to
  • vs Crisp
  • Pricing
Resources
  • Blog
  • Developer docs
  • API reference
Company
  • Contact
  • Privacy
  • Terms
© 2026 Sidtechno.com LLC
PrivacyTerms