Skip to content

Shopify Dude Release Breakdown

Shopify Customer Segment Query Broke on 2026-10? Use MATCHES for Functions

Shopify segment function syntax changed to MATCHES and NOT MATCHES in API 2026-10. Update stored expressions, relative dates, and membership tests safely.

Quick answer: Shopify Admin API 2026-10 uses MATCHES and NOT MATCHES for customer segment functions, replacing old function = true/false expressions. Function parameter comparisons also move inside the parentheses. Audit stored queries before upgrading integrations.
On this page

Why this happens

Segment query syntax changed in API 2026-10. Apps that store query strings or generate segment functions may continue sending the old syntax even if the Shopify admin segment builder has changed.

How to fix it

  1. Read existing segments and preserve their IDs, names, and query strings before making changes.
  2. Find function expressions ending in = true or = false and translate them to MATCHES or NOT MATCHES.
  3. Move parameter comparisons inside the function, preserving operators and intended audience criteria.
  4. Replace deprecated named relative dates such as 90_days_ago with the supported relative offset syntax, such as -90d.
  5. Update one segment at a time; read back its saved query and compare membership against known customer fixtures.

Production example

Old: products_purchased(quantity: 5) = true. New: products_purchased MATCHES (quantity = 5). Old: shopify_email.opened() = true. New: shopify_email.opened MATCHES (). These are segment function examples, not replacements for every ordinary equality condition.

Common misunderstanding: Every equals sign in a segment query is obsolete. Ordinary scalar comparisons remain valid; this migration specifically changes segment function expressions and their parameters.

How to test this

  1. Export the original query text and record the expected business rule.
  2. Translate a positive and a negative function condition.
  3. Validate both expressions against API 2026-10, checking GraphQL and mutation errors.
  4. Compare known customer membership and counts, including date boundaries.
  5. Verify scheduled integrations use the revised expression before activating campaigns or discounts.