Customer Owned App Metafield Defs Not Showing as Segment Query Filters

Custom Data
1

We’re working on generating customer segment queries based on our app metafields. In some shops, all expected metafields appear and can be used as segment query filters. However, in others, only a limited subset is visible. None of these shops have any other customer owned metafields defined.

All shops have the correct metafield definitions defined, and setting the metafields functions correctly. The issue is that not all of them are available as filters when building the segment queries.

Any ideas why this might be occurring?

1 Like
2

Hey @Joshua_Lucas :waving_hand: thanks for flagging this. The only reason that I can think of would be that the metafields may not meet the requirements for data types that are allowed to be used as segment filters.

There’s a bit more info here:

https://help.shopify.com/en/manual/customers/customer-segmentation/reference-guide/metafield-segments

But essentially, they can only be these data types: date and time, number, text, true or false (boolean).

If you’ve double checked that already, no worries, still happy to help. If you could share the shop ID/myshopify.com URL of an affected shop and the queries you’re using to determine that the metafields can’t be used as query filters I can see if we’re able to replicate the behaviour on our end and look into this further - just let me know. If needed I can set up a DM if you’d like to share the info that way. Hope this helps a little bit!

3

Thank you for following up, @Alan_G, this is a huge help!

I’ve reviewed the types, and they all meet the required criteria for filtering. Just one of them does not show up :confused:

If you don’t mind, a DM would be great, since the filter includes some app-specific data, that might be easier to share privately.

Thanks again! :folded_hands:

1 Like
4

Hey @Joshua_Lucas - no worries, sending you a DM :slight_smile:

5

Hey @Joshua_Lucas :waving_hand: - I was able to work with our product team on this and it does look like this was a database issue on our end. The metafield should be showing up now - can you let me know if you see this or a similar behaviour happen anywhere else?

If so, just ping me here, but I’ll close out our thread for now - let me know if I can help out further :slight_smile:

1 Like
6

@Alan_G Thank you for the quick response and resolution! I really appreciate the work from you and the product team to fix this. Everything is working great now!

1 Like
7

Glad to hear it’s working @Joshua_Lucas! We think this may have just been a single instance of this issue popping up (potentially related to a database deadlock/race condition), but if you do see it happen more frequently, just message me here and I’ll take a look for sure.