TL;DR
Until this summer, an app pixel's data access could change on your store and leave no record anywhere. An app update could widen what a pixel reads, Shopify's Optimized data-sharing mode could quietly pause it, and the only evidence was a gap in your platform numbers weeks later. The activity log closes that hole: since June 29, 2026, every app pixel's detail page carries a per-pixel history of data access changes, recorded from June 3, 2026 onward [1]. Each entry states whether access was granted or paused and whether the change was automated or manual [2]. Reading it takes two minutes. Knowing which entries demand action is the part this guide covers.
Key Takeaways
- The activity log lives on each app pixel's detail page: Settings, then Customer events, then the three-dot menu next to the pixel, then View details [2].
- It records data access changes from June 3, 2026 onward. Anything earlier is gone; no tool recovers pre-June history [2].
- Every entry is one of two statuses, granted or paused, with one of two reasons, automated or manual [2].
- An automated pause is almost always Shopify's Optimized data-sharing default at work. That setting has been pausing low-signal pixels since January 13, 2026 [3], and until this log shipped a pause left no merchant-facing record.
- A granted entry on a pixel you don't recognize is your audit trigger: some app on your store started reading customer data, and now you have the date it happened.
- Pauses only affect the browser pixel layer. Conversions delivered server-side, from the order webhook, never pass through the web-pixel system and keep flowing during a pause.
What the activity log records (and what it leaves out)
Each log entry captures a data access status and the reason for the change [2]. Status is binary: access granted or access paused. Reason is also binary: automated, meaning Shopify's own optimization detection made the change, or manual, meaning a person on your store did [2]. Shopify released the feature on June 29, 2026 and backfilled history to June 3, 2026, so every store using app pixels has records dating back to June 3, 2026 and a complete history going forward [1].
Just as useful is knowing what the log does not show. It does not list which events a pixel subscribes to, does not show event payloads, and does not tell you whether the pixel is firing correctly right now. It is a change history for data access, not a debugger. If the question is "is my tracking wired right," that is a different exercise, and we wrote the pixel audit walkthrough for it. The log answers a question nothing else on Shopify answered before: "did something change, and when?"
How do you open a pixel's activity log?
From your Shopify admin:
- Go to Settings → Customer events.
- Find the app pixel you want to inspect and click the three-dot menu next to it.
- Click View details. The activity log is on the pixel's detail page.
- To narrow the window, click Date, pick a specific date or range, and click Save [2].
Two things to notice while you are there. First, the log is per pixel. If you run several tracking apps, each one keeps its own history, so a store-wide review means opening each detail page. Second, only app pixels have this page. Custom pixels, the ones you paste in yourself under Customer events, run exactly as written and carry neither a data-sharing Mode [3] nor an activity log [1].
What does an automated change mean?
This is where the log earns its place in your routine. Since January 13, 2026, app pixels ship in "Optimized" data-sharing mode by default. In that mode, Shopify watches whether a pixel appears to drive results and can pause some or all of its data sharing when it sees little useful signal, resuming later if new signals appear [3]. We covered the mechanism and the fix in detail in our guide to the Optimized data-sharing default; the one-line version is that the opt-out is setting each pixel you depend on to "Always on."
When that article published, the sharpest problem with Optimized mode was invisibility: a pause surfaced no alert and appeared in no log. That fact is now out of date, and the correction is good news. An activity log entry reading "data access paused" with an automated reason is exactly that mechanism leaving a record [2]. If your Meta or GA4 purchase counts started sagging on a particular date with no deploy to explain it, the log either shows a pause entry near that date or it rules the whole theory out. Diagnosis that used to take a spreadsheet reconciliation now takes one page view.
If you find an automated pause on a pixel you actively rely on, treat it as the setting talking, not the app breaking. Check the pixel's Mode and set it to Always on, then confirm in the log that access was granted again.
How to act on each entry type
Four combinations cover every line you will see. Here is the operator's read on each:
| Entry | What it means | What to do |
|---|---|---|
| Paused, automated | Shopify's Optimized mode judged the pixel low-signal and throttled it [3] | If you rely on this pixel, set its Mode to Always on and verify a granted entry follows |
| Paused, manual | Someone on your team (or an agency login) turned it off | Confirm it was intentional; the entry gives you the date to ask about |
| Granted, automated | Optimized mode resumed sharing after seeing new signals [3] | Fine on its own, but it means the pixel spent time paused; check what window you lost |
| Granted, manual | A person enabled data access, typically a new app install or a re-enable | If you recognize the app, nothing. If you don't, audit it: something started reading customer data on a date you now know |
The last row deserves the emphasis. Merchants think of tracking failures as data going missing, but the reverse case, an app quietly gaining access to customer data, is the one with compliance weight. The activity log is the first place Shopify has given store owners a dated record of access being granted. Read it whenever you inherit a store, part ways with an agency, or clean up after app trials.
Where the log fits in a tracking audit
The log is one instrument, and it slots into a sequence you may already run. A full health check on a store's tracking looks like this: verify what is actually installed and firing, which is the pixel audit; verify the wiring end to end after any install, which is the post-install checklist; and now, review each app pixel's activity log for changes you did not expect. The first two tell you the current state. The log tells you the history, and history is what you lack precisely when numbers look wrong and nobody remembers touching anything.
It also matters more each quarter, because more surfaces run through pixels now. Web pixels load on checkout, and since July 21, 2025 on customer accounts and the order status page as well [4], and the legacy script surfaces shut down for the last stores on August 26, 2026 [5]. If pixels are new territory for you, our plain-English guide to the Web Pixels API explains the sandbox model, and the thank-you page deadline guide covers the migration. The direction of travel is clear: pixels become the only browser tracking surface, which makes a per-pixel change log the closest thing Shopify tracking has to an audit trail.
Does a paused pixel stop server-side tracking?
No, and the distinction decides how much a silent pause can cost you. The activity log and the Optimized mode behind its automated entries both govern app pixels, the browser layer that runs in Shopify's web-pixel sandbox. Any tracking app's browser events live under that regime, ours included; there is no exemption for anyone.
Conversions delivered server-side take a different road. A purchase sent from the Shopify order webhook never enters the web-pixel system, so no data-sharing pause touches it. That is the architectural reason we deliver purchases server-side to every connected platform, with the browser event's ID carried along so platforms deduplicate cleanly. If a pause hits the browser layer, funnel events like page views thin out and the activity log records why, but the purchase, the event your ad platforms optimize on, keeps arriving.
That split also changes how you experience an incident. With a browser-only setup, an automated pause means conversions vanish until someone notices the revenue gap. With a server-led setup, purchases keep flowing while you read the log entry, flip the Mode to Always on, and move on.
FAQ
Can I see data access changes from before June 3, 2026?
No. The activity log records changes from June 3, 2026 onward, and Shopify states changes before that date are excluded [2]. For anything earlier, the only evidence is indirect: platform event counts, app install dates, and team memory.
Does the activity log tell me why Shopify paused my pixel?
It tells you the reason category: automated, from Shopify's optimization detection, or manual [2]. For automated pauses, the underlying trigger is the Optimized data-sharing mode, which pauses pixels showing little useful signal over days or weeks [3]. The log will not name the specific signals; the fix is the pixel's Mode setting either way.
Do custom pixels appear in the activity log?
No. The activity log is a feature of app pixels [1]. Custom pixels pasted into Customer events run as written, with no data-sharing Mode [3] and no activity log [1], so neither Optimized pauses nor log entries apply to them.
Should I check the activity log on a schedule?
Tie it to events rather than a calendar: after installing or removing a tracking app, when platform numbers diverge from Shopify orders with no deploy to explain it, and whenever a store changes hands between teams or agencies. A monthly glance costs a minute per pixel if you prefer a routine.
Keep purchases out of the blast radius
WeltPixel Conversion Tracking fires its browser events through an app pixel like every other tracking app, and it shows up in the activity log like every other tracking app. The difference is what happens during a pause: purchases are delivered server-side from the order webhook to GA4, Meta, TikTok, Google Ads, and the rest of your connected platforms, deduplicated against any browser event, so the number your bidding runs on does not depend on the browser layer's mood. The recent-events stream shows server events arriving in real time for GA4, Meta, TikTok, and most other connected platforms, which turns a data-sharing pause from a silent revenue mystery into a log entry you read and fix. Install WeltPixel Conversion Tracking and set every pixel you rely on to Always on while you are in Customer events anyway.
Sources
- Shopify Changelog, View data access changes with the new app pixel activity log (June 29, 2026): https://changelog.shopify.com/posts/view-data-access-changes-with-the-new-app-pixel-activity-log
- Shopify Help Center, App pixels (View activity log): https://help.shopify.com/en/manual/promoting-marketing/pixels/app-pixels
- Shopify Changelog, New default setting for pixel data sharing (January 13, 2026): https://changelog.shopify.com/posts/new-default-setting-for-pixel-data-sharing
- Shopify Changelog, Web pixels load on customer accounts and the order status page (July 21, 2025): https://changelog.shopify.com/posts/web-pixels-load-on-customer-accounts-and-order-status-page
- Shopify Help Center, Upgrade Thank you and Order status pages: https://help.shopify.com/en/manual/checkout-settings/customize-checkout-configurations/upgrade-thank-you-order-status