---
title: >-
  eventBridgeServerPixelUpdate and pubSubServerPixelUpdate now require user
  access to the app - Shopify developer changelog
description: >-
  Shopify’s developer changelog documents all changes to Shopify’s platform.
  Find the latest news and learn about new platform opportunities.
source_url:
  html: >-
    https://shopify.dev/changelog/posts/eventbridgeserverpixelupdate-and-pubsubserverpixelupdate-now-require-user-access-to-the-app
  md: >-
    https://shopify.dev/changelog/posts/eventbridgeserverpixelupdate-and-pubsubserverpixelupdate-now-require-user-access-to-the-app.md
metadata:
  effectiveApiVersion: ''
  affectedApi:
    - displayName: GraphQL Admin API
      handle: admin-graphql
  primaryTag:
    displayName: API
    handle: api
  secondaryTag:
    displayName: Breaking API Change
    handle: breaking-api-change
  indicatesActionRequired: true
  createdAt: '2026-11-16T10:04:43-05:00'
  postedAt: '2026-11-20T12:00:00-05:00'
  updatedAt: '2026-11-19T14:11:07-05:00'
  effectiveAt: '2026-11-16T12:00:00-05:00'
---

November 20, 2026

# `eventBridgeServerPixelUpdate` and `pubSubServerPixelUpdate` now require user access to the app

DateNovember 20, 2026

Flags[Breaking API Change](https://shopify.dev/changelog?filter=breaking-api-change)[Action required](https://shopify.dev/changelog?action_required=true)

Tags[Security](https://shopify.dev/changelog?filter=security)[GraphQL Admin API](https://shopify.dev/changelog?api_type=admin-graphql)

Starting November 20, 2026, the [`eventBridgeServerPixelUpdate`](https://shopify.dev/docs/api/admin-graphql/latest/mutations/eventBridgeServerPixelUpdate) and [`pubSubServerPixelUpdate`](https://shopify.dev/docs/api/admin-graphql/latest/mutations/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.

## What changed

Both mutations now require an [offline access token](https://shopify.dev/docs/apps/build/authentication-authorization/access-tokens#offline-access-tokens), or an [online access token](https://shopify.dev/docs/apps/build/authentication-authorization/access-tokens#online-access-tokens) for a user who has access to the app. The `write_pixels`, `read_customer_events`, and `write_server_pixels` access scope requirements don't change.

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.

## Who's affected

This affects apps that call these mutations with an online access token for a staff member who doesn't have access to the app. Offline access tokens, and online access tokens for users who have access to the app, work as before.

If your app calls these mutations with online access tokens, then make sure the staff member has access to your app in the Shopify admin, or call the mutations with an offline access token, for example from a background job. Handle the access denied error either way.

## Why this matters

The update mutations now make the same user access check that [`serverPixelCreate`](https://shopify.dev/docs/api/admin-graphql/latest/mutations/serverPixelCreate) and [`serverPixelDelete`](https://shopify.dev/docs/api/admin-graphql/latest/mutations/serverPixelDelete) already make, so only a user who has access to an app can change where its server pixel sends events. This is a security fix, so it applies to all API versions without a deprecation period.
