And now you can access your analytics data in Shopify Flow with a "Get analytics data" action. It works with our scheduled time trigger, enabling reporting use cases and more. https://t.co/LBN3vwlhrs
@Jonezell_@Moore@Shopify Rollout being https://t.co/g4MjLp5FsF and Launchpad being https://t.co/FjZiRNw8XY ? Just want to make sure we're talking about the same things
@Moore@Jonezell_@Shopify ๐ฏ We know how powerful it will be to have manual + API-driven annotations.
Do you have any other meaningful events in mind that you would expect to see derived from activity that's already on Shopify?
@0x15f@Jonezell_@Shopify I appreciate the feedback. What events would you like to see? We want to make sure we're surfacing what's meaningful and timely that can be correlated to changes in your business performance.
Another great @Shopify update ๐
New annotations in Shopify Analytics showing what changed during the time periods to help show what caused the change in the metrics
New Shopify Release: you can now set an Analytics Target (goal) and see the progress tracked towards achieving it
This is great ๐
https://t.co/P5M1KbSfHK
Starting this week, millions of @Shopify merchants can sell in ChatGPT, into the US.
Their PDP, their checkout, their customizations, no extra setup.
AI is a new front door to commerce. Shopify is whatโs behind it everywhere.
Hey folks! Adding some context here:
We made this change because large metafield values negatively impact storefront performance. Splitting data into multiple metafields or using metaobjects provides more flexibility in how and when fields are accessed.
To minimize disruption, the 16KB limit only applies to writes in version 2026-04 and later. Calls to older API versions will respect previous limits. We've updated the changelog to clarify this.
We're also reaching out to all affected apps to understand use cases requiring >16KB that can't be solved with alternative approaches. We have options to provide greater limits in specific cases where needed.