We’re experimenting with Customer Segment Template Extensions. We wanted to release some templates that are only specific to a subset of our merchants. One’s that have adopted a certain feature, say “feature X”. The template won’t be relevant to our merchants that have not adopted that feature, it may even give them the wrong idea and create a bad perception for our app as there isn’t much of a way to communicate to them in that screen that this segment is valid only if they are using said “feature X”.
What is the blocker with unlisted approach? Possible I am overlooking an important point but I see this as flagging shops that are eligible within the app and prompting users to click a link to install unlisted app. A few extra steps yes.
Different approach is to install for all and use metafield to show or hide template content. For shops not eligible displaying “Upgrade to enable” as alternative.
Actually yeah, that metafield gating approach makes a lot of sense. We can use it to change the copy or even not render an extension…
Thanks that approach makes the most sense for me.
Side note: Why the unlisted app approach won’t work for us is, its too much friction for merchants to start using it and it is tough to scale if we have 3-4 different customer segments targeting different subsets of merchants.
