Understanding Queries (Collection)
Updated
Queries are a powerful way to control which assets appear in a Collection section. While Filters determine what a viewer can search or sort through dynamically on the front end, Queries determine what content is included in the section from the start. In other words, Queries define what content is shown, while Filters define how that content can be refined by users.
How Queries Work
Each “Query” field — such as Categories Query, Series Query, Speakers Query, or Albums Query — tells the Collection which assets to pull from your Media Library. When you select one or more options in a Query field, the system will automatically include only assets that match those parameters.
For example:
-
Categories Query: Choosing 'Creativity' and 'Nature' will show assets that have either category assigned.
-
Speakers Query: Selecting “Carlos Ramirez” will show only assets where that speaker is tagged.
-
Series Query: Adding “Faith Foundations” will limit the grid to assets within that series.
-
Albums Query: Selecting an album like “2024 Worship Highlights” will only display items contained in that album.
How Queries Match Assets
Queries can be used individually or combined, and they follow two simple rules:
-
Multiple values in one query = any match. If you select more than one value in the same query, assets only need to match one of them. For example, a Categories Query of “Creativity, Inspiration” shows assets tagged with Creativity, Inspiration, or both.
-
Multiple queries together = all must match. If you use more than one type of query (for example, Categories and Speakers), assets must match every query to appear.
For instance, you could combine a Categories Query of “Nature” with a Speakers Query of “Carlos Ramirez” to display only “Nature” assets from that specific speaker.
Custom Query
The Custom Query field lets you type a query directly instead of picking values from a list. Use this format:
db.categories=Value One,Value Two
Example:
db.categories=Sunday Morning,Plano Campus
This shows assets tagged with either Sunday Morning or Plano Campus.
Like other queries, multiple values in a Custom Query return assets that match any of them.
Example Setup
Imagine you are building a section on your site called “Creative Insights”.
You might configure your Vertical Assets Grid like this:
-
Section Type: Vertical Assets Grid
-
Categories Query: Creativity, Inspiration
-
Speakers Query: Monica Harris
-
Series Query: The Creative Life
The result: your Collection layout will only show assets that are tagged with either Creativity or Inspiration, and feature Monica Harris, and are in The Creative Life series.
This ensures that each section of your Collection layout can be tightly curated to display only relevant, high-quality content.
Queries vs Filters
| Feature | Purpose | Who Controls It | Example |
|---|---|---|---|
| Query | Determines which assets are included in a section. | Configured by the site editor (you). | Showing only assets in the “Nature” category. |
| Filter | Allows viewers to narrow down content within a section. | Controlled by the end user on the front end. | A user filtering videos by “Speaker: Monica Harris” while browsing. |
Think of Queries as the content pipeline—they define the data set you start with.
Filters are interactive tools layered on top of that data set, letting viewers personalize what they see.
Best Practices for Using Queries
-
Use Queries to create focused sections, like “Recent Sermons,” “Kids Content,” or “Music Albums.”
-
Combine multiple queries for precise targeting (e.g., narrow by both Speaker and Series).
-
Avoid leaving all Query fields blank unless you want all available assets to appear.
-
Use Filters sparingly in the same layout to give users control without cluttering the browsing experience.