Skip to main content

Tags vs Collections: When to Use Each

Tags vs Collections: When to Use Each Why: Choose the right organizer so members can filter attributes with tags and browse curated themes with col...

Written by Ken Truesdale

Platform 2 Guide — This article applies to the new platform. Looking for classic platform docs? Browse the Platform 1 collection.

Why: Choose the right organizer so members can filter attributes with tags and browse curated themes with collections.

Navigate: App Station > Settings > Branding & Design > Tags & Collections

Overview

Tags and Collections both help members find content but serve different purposes. Here’s a quick comparison:

Tags

Collections

Job

Label content with attributes so members can filter and search

Curate themed groups members can browse as destinations

Think of them as

Filters / facets

Mini landing pages / themed shelves

Examples

Gluten Free, Italian, Breakfast, Easy, Slow Cooker

Weeknight Winners, Meal Prep Sunday, Summer Entertaining

What members see

Chips on cards and in filter panels

Cards/nav with cover images; dedicated collection pages

Extras

Optional short name (e.g. GF); type (Dietary, Cuisine, etc.)

Description, cover image/gallery, color, sort order, default sort

Where admins manage them

App Station → Settings → Tags & Collections → Tags

App Station → Settings → Tags & Collections → Collections

How many to create

Many is fine if names stay clear

Fewer, intentional groupings

When to Use Tags

Use tags when the label is an attribute of the content that members might filter by. Examples include:

  • Dietary needs: Gluten Free, Dairy Free, Vegan

  • Cuisine: Italian, Mexican, Thai

  • Meal type: Breakfast, Lunch, Dinner, Snack

  • Effort / method: Easy, Slow Cooker, Air Fryer

  • Topics (for resources/blog): Nutrition, Meal Prep, Beginners

Rule of thumb: If a member would say "show me everything that is ___," use a tag.

Tags power filter panels, quick-filter chips, saved filter presets, and search refinement. They appear as chips on content cards when card templates are configured to show them.

When to Use Collections

Use collections when you are curating a story or theme — a set you want members to discover as a group. Examples include:

  • Seasonal: Summer Grilling, Holiday Favorites

  • Lifestyle: Busy Weeknights, Family Favorites, Meal Prep

  • Programs or journeys: 7-Day Reset, Beginner's Kitchen

  • Cross-type themes: "Quick Dinners" with recipes and meal plans

Collections support cover images, rich text descriptions, and their own pages. You can feature them with category navigation and showcase blocks on home and library pages.

Rule of thumb: If you would put it on a homepage shelf or give it its own page with a story, use a collection.

Using Both Together

Most kitchens should use both tags and collections.

For example, a recipe in Weeknight Winners (collection) might also be tagged Dinner, Easy, and Gluten Free.

  • Collection = where it lives in your curated experience

  • Tags = how members filter and refine

Avoid putting the same idea in both places unless you mean it. For instance, do not create a "Gluten Free" collection and a "Gluten Free" tag if members only need to filter — use the tag. Save collections for themes you will feature and explain.

Quick Decision Guide

  1. Will members mainly filter by this? → Tag

  2. Do you want a browsable page with image + description? → Collection

  3. Is it a fact about the recipe (diet, cuisine, meal type)? → Tag

  4. Is it a curated theme or program? → Collection

  5. Unsure? Start with a tag. Promote it to a collection later if you want to feature it.

Where This Lives in App Station

  • Tags: Settings → Tags & Collections → Tags

  • Collections: Settings → Tags & Collections → Collections

  • Apply either from the content editor (General tab: Collections and Tags are separate sections)

  • Bulk-assign tags and collections from Content Library multi-select actions

Did this answer your question?