Customer events / New feature

The app pixel's
activity log has arrived

For stores that share customer data with apps, you can now review the history of "when and how data access changed" directly from each app pixel's detail page. All changes from June 3, 2026 onward are recorded.

On this page
  1. What was added (understand it in 30 seconds)
  2. How it works: the flow of how access changes get recorded
  3. Facts stated in the article / Items not mentioned
  4. Before vs. after comparison
  5. How to check (3 steps)
  6. 5 points developers should know
  7. 3 use cases you can apply to your work
  8. A one-line summary for your pitch

1What was added

In the Shopify admin's "Customer events" section,an activity log for app pixelshas been added.
Stores that share customer data with apps can now track "when and how data access changed" as a history from each app pixel's detail page.

Where does it appear?

In the admin's "Customer events," on each app pixel's detail page.

Recorded from when?

On or after June 3, 2026, all data access changes are recorded. From that point on, a complete history is retained.

Who can use it?

All merchants using app pixelsalready have access.

2How it works: the flow of how access changes get recorded

App Shares customer data Connected app Access change App pixel Customer events Running within Shopify admin Record Activity log Appended chronologically Reviewed by the merchant
What an app pixel is : An integration point through which an app receives event data, such as store purchase behavior, via the "Customer events" mechanism.
This log appends, in chronological order, a history of how that app pixel's data access has changed, with a new entry added each time there's a change.

3Facts stated in the article / items not covered

Stated in the article
  • Released an activity log for app pixels within "Customer events"
  • You can view the history from each app pixel's detail page
  • Recording begins June 3, 2026 onward
  • A complete history is kept from then on (going forward)
  • Already available to all merchants using app pixels
  • Category: Feature / Admin
Not stated in the article
  • The specific items and data granularity recorded in the log
  • Whether API / Webhook / export support is available
  • How history prior to June 3, 2026 is handled
  • Permissions / roles required to view it
  • Supported plan and region constraints
  • Log retention period
For items marked "not stated" in the table above, the original Changelog provides no information, so speculation is avoided. For details, check the Shopify Help Center and the actual display in your own store's admin.

4Before vs. after comparison

ItemBeforeAfter the activity log
Visibility of data access changes No history You can only see the current state History available Review the sequence of changes chronologically
Where to check — Self-contained within each app pixel's detail page
Scope of recording — All changes from June 3, 2026 onward
Target — All merchants using App Pixels

5How to check (3 steps)

1

Open "Customer events"

Go to the Customer events section in the admin.

2

Open the target App Pixel

Enter the detail page of the relevant App Pixel.

3

Check the activity log

The history of data access changes is shown in chronological order.

No setup required.Already enabled for all merchantsso you can view the log simply by opening the detail page.

65 points developers should know

1. Scope is per App Pixel

The log is not store-wide, butper App Pixel detail page. You can trace access changes separately for each app the data is shared with.

2. Starts on June 3, 2026

The recording start date is clearly stated.Changes before that date are not included— design your audits and reviews on that assumption.

API ?

3. No mention of API/export

The article only covers viewing in the admin.No support is mentioned for Admin API, Webhook, or CSV export. If you want automated integration, you'll need to verify it separately.

4. It serves as an audit trail for data governance

The change history of "who was granted what access, and when" can be used asa primary record for privacy audits and incident investigations.

5. Zero extra setup, enabled for all merchants

There's no mention of opt-in or plan restrictions,and it's automatically available if you're using App Pixels. Just add "review the log regularly" to your workflow and you're done.

73 use cases you can apply to your operations

USE CASE 1

Creating an audit trail for privacy audits and data-sharing reviews

Challenge
You share customer data with multiple apps, but have no way to trace after the fact when and which app's access changed, so you can't explain it during an audit.
Solution
During quarterly or annual audits, check each App Pixel's activity log and keep a review record of how access changed.
Impact
Makes it easier to meet data-governance accountability requirements and reduces the effort of external audits and internal checks.
Technical notes
Records start from June 3, 2026. Set up your operations assuming earlier states are supplemented by separately archived materials.
USE CASE 2

Early detection of "unintended access changes"

Challenge
Even if the scope of data access silently expands due to an app update or a settings change, it goes unnoticed and the risk is left unaddressed.
Approach
Add "regularly review the activity logs of key app pixels" to your operational checklist, and review any unexpected changes.
Effect
Detect unnecessary or excessive data sharing early, and when needed, follow up by revisiting the integration or contacting the app vendor.
Technical notes
Since there is no mention of API notifications, the practical approach for now is to make manual visual checks in the admin a routine.
USE CASE 3

Backing up incident investigations and inquiry responses

Challenge
When a data-related inquiry or incident occurs, you can't reconstruct "which app had what access at that point in time."
Approach
During investigation, cross-reference the activity log timeline to verify the timing and content of changes on a factual basis.
Effect
Explain from primary evidence rather than guesswork, improving response speed and reliability.
Technical notes
The log retention period and the granularity of recorded items are not specified. For important cases, it's safer to keep records such as screenshots at the relevant point in time.

8A one-line summary you can use in a proposal

"A log has arrived that lets you trace theaccess change historyof customer data shared with apps, right from each app pixel's detail page.
Everything from June 3, 2026 is recorded, with zero extra setup and enabled for all merchants.
For privacy audits and early detection of suspicious changes, start by making "regular reviews" part of your operations."