The GraphQL Customer object has a CustomerStatistics object which includes the RFM group field and the spending tier field. Our application needs to be able to track changes for these fields but we found that when a customers/update webhook fires after an order is placed those fields are not yet upd…

[image] Mathieu_Nunez: I suspect the lag in stats calculation must be more than a few seconds. It would be useful to know what to expect even if it’s a rough estimate like 1 minute after the update. We don’t have guarantees on the latency, but you could expect between 15 minutes to 24 hours d…

Hey @Mathieu_Nunez , I’m looking in to this for you and will follow up once I know more. I’m assuming the delay is due to those fields being calculated asynchronously after the customer is updated.

Hey @KyleG-Shopify , Are there maybe any updates about this topic? We are also interested in this..

Hey @Mathieu_Nunez and @khaledAtKeaz , thanks for your patience! I’ve confirmed that this behavior you are seeing is expected. Customer Statistics fields like rfmGroup and predictedSpendTier are calculated asynchronously after order placement because they require complex calculations including store-…

Hey @KyleG-Shopify , Thanks for your reply! So just to confirm, whenever the rfmGroup or predictedSpendTierof a customer is changed, then the customers/update webhook/event is fired?

@KyleG-Shopify thank you for the reply. We are already polling the customer query after receiving the webhook but it does not seem to have thew updated information then. I suspect the lag in stats calculation must be more than a few seconds. It would be useful to know what to expect even if it’s a …

[image] khaledAtKeaz: So just to confirm, whenever the rfmGroup or predictedSpendTierof a customer is changed, then the customers/update webhook/event is fired? No, the webhook wouldn’t fire in that case, but the events that lead up to the change will.

Thank you @KyleG-Shopify . I will use the existing thread you pointed to to discuss the webhooks. It is not yet an ideal solution though as you need to have one subscription per existing segment id for each shop.

Yes, that’s exactly the nuance I was thinking of. That and it can’t be subscribed in the app configuration file.

Tracking Customer Statistics in GraphQL API

GraphQL Admin API Troubleshooting

KyleG-Shopify September 3, 2025, 3:05pm 9

We don’t have guarantees on the latency, but you could expect between 15 minutes to 24 hours due to some of the calculations requiring more time to establish the tiers. The segment webhooks could be more reliable here. There is some nuance with those webhooks. This thread has some great context on that:

Topic		Replies	Views
Customers/update webhook including customerStatistics? Webhooks and Events configuring	7	329	August 28, 2025
Customer segment search does not contain customer with recently added tag GraphQL Admin API Troubleshooting general-gql-troubles	2	130	October 2, 2025
Could not find the webhook topic customer.tags_added Webhooks and Events configuring	5	236	September 5, 2025
Cannot create customer.tags_added webhook Webhooks and Events troubleshooting	3	205	November 5, 2025
BulkOperation customer metafield updates and webhook delivery rate limits GraphQL Admin API Troubleshooting general-gql-troubles	6	247	August 6, 2025

Tracking Customer Statistics in GraphQL API

Related topics