Show the "[your section]" section only to logged-in [your customer tag — e.g., B2B] customers. Everyone else sees the regular featured collection.
Want more control? See the expanded prompt ›
On the homepage, show the 'Wholesale catalog' section only to logged-in customers with the `b2b` tag. For everyone else, show the regular Featured collection instead.
- Liquid
customer.tags contains 'b2b'check. - Fallback section for non-matching customers.
- Works for any block, not just homepage sections.
- Supports multi-tag rules (e.g.
b2bORvip).
What you're trying to do
Most stores serve a single experience to everyone. As you grow, you'll want to show different content to wholesale, VIP, or loyalty-tier customers. Customer-tag gating is the simplest way to start — same store, different views per tag.
Things to watch out for
- Logged-out state — Fudge gated content is invisible to non-logged-in shoppers.
- Tag hygiene — Fudge can audit your customer tag usage.
- Combinations — Fudge handles this: supports AND/OR/NOT logic across multiple tags.
- Caching — Fudge gated sections don't get edge-cached the same way.
How Fudge does it
Fudge duplicates your live theme into a draft, wires the integration to your real store data, and verifies it works end-to-end before anything goes live. Everything starts in draft — test on the preview, tweak settings, and publish when you're ready. Your live store stays untouched.
When customer-tag content gating makes sense
Some content should only show to specific customer segments — wholesale catalogs for B2B customers, VIP previews for top spenders, member-only sections. Tag-based visibility gating shows or hides content based on the logged-in customer’s tags.
When this is worth doing
Use customer-tag gating for legitimate segmentation needs — B2B vs. retail, member vs. non-member, paid tier vs. free tier. Don’t use for misleading personalization that erodes trust.
What makes a great implementation
- Tag-based logic — checks customer.tags for matching values.
- Logged-out fallback — non-logged-in shoppers see the public version.
- AND/OR/NOT logic — supports combinations across multiple tags.
- Caching-aware — gated content doesn’t get edge-cached the same way.
Common mistakes to avoid
The biggest mistake is gating critical commerce flows. Don’t gate the cart or checkout based on customer tags — that breaks the buying experience.
The second mistake is caching conflicts. Tag-gated content needs cache busting for the logged-in version. Fudge handles this.
Pair this with conditional Liquid hide by product handle and theme code investigation — three technical tools for fine-grained control.