Customer tags can be used as conditions in Skio features like Cancel Flow, Surprise & Delight, and Journeys but they aren't always reliable as a real-time data source. Before building flows that depend on them, it's worth understanding where that can create gaps.
If you're not familiar with how Skio applies customer tags in Shopify, start with Customer & Order subscription tags in Shopify.
Why customer tags aren't always reliable in real time
Skio automatically manages a set of subscription status tags on customer records in Shopify like ActiveSubscriber and CancelledSubscriber keeping them in sync as subscriptions change. For any custom tags applied by external tools or Shopify Flows, Skio reads those tags but does not create, modify, or remove them.
This means if a flow evaluates a tag condition at the wrong moment (ie. before Shopify has finished syncing), the condition may return an incorrect result, and the wrong offer, reward, or branch may trigger.
Where you can use customer tags as conditions
Customer tags are supported as conditions in the following features:
Cancel Flow: Show or hide specific offers based on whether a customer has a certain tag
Surprise & Delight: Target rewards to customers with specific tags
Journeys: Use a customer tag as a filter or branching condition
When to be cautious when using customer tags
Avoid building flows where the entire outcome depends on a tag being present at a precise moment. Situations to watch out for:
Checking for a tag immediately after a subscription event: If an external tool is meant to apply the tag when a subscription event fires, it may not have synced to Shopify yet by the time Skio evaluates the condition.
Using a tag as the only condition: If the tag is missing or delayed, there's no fallback, and the wrong path triggers
Relying on tags from third-party apps or Shopify Flow: When an external tool applies a tag, there are two delays stacked: first, the tool needs to write the tag to Shopify, then Shopify's API needs to sync that update before Skio can read it. This makes tag-dependent conditions particularly prone to timing issues when the tag is being set by something outside of Shopify itself.
Recommended approach
Pair the tag condition with at least one other condition so there's a fallback if the tag hasn't synced yet.
Test your flow in a low-stakes context first to confirm the tag is being read correctly and at the right time.
If you need precise, real-time segmentation, consider using Skio's native segmentation tools or subscription based conditions instead.