ESHOPMANESHOPMAN Logo
Our Blog

HubDB Filtering Secrets: Using __in for Dynamic Content

HubDB Filtering Secrets: Using __in for Dynamic Content

Ever wrestled with filtering data in HubSpot's HubDB to show the right content to the right people? It's a common challenge, especially when you want to personalize experiences based on user preferences. A recent HubSpot Community thread highlighted a hiccup someone ran into while trying to filter HubDB content based on a contact's meal preferences. Let's dive into the problem and the solution that emerged.

The Challenge: Dynamic Filtering with HubDB

The original poster was aiming to pull recipes from a HubDB table based on a contact's meal preferences. The goal was to display recipes matching the contact's dietary choices, which were stored as a comma-separated list in the contact's profile. The initial code looked something like this:

{% set diet_list = contact.meal_preference|split(',') %}
{% set diet_query = "limit=5&meal_tag=" + diet_list|join(',')|lower %}
{% set recipes = hubdb_table_rows('ID', diet_query) %}

The problem? The query wasn't working as expected, throwing an error indicating that the specific combination of preferences wasn't found in the `dietary_tag` column. When the query string was printed, it looked correct (e.g., `limit=5&meal_tag=vlees,vis`), but the HubDB wasn't interpreting it as a list of options.

The Solution: Understanding the __in Operator

The key to solving this puzzle lies in understanding how HubDB handles multiple values. While the initial approach seemed logical, it was missing a crucial piece: the `__in` operator. This operator allows you to specify that you're looking for rows where a column's value is *one of* the values in a list.

One respondent pointed out the missing `__in` operator. The corrected code should look like this:

{% set diet_query = "limit=5&meal_tag__in=" + diet_list|join(',')|lower %}

By adding `__in` to the query string, you're telling HubDB to search for rows where the `meal_tag` column contains any of the values in the comma-separated list. This is a subtle but significant change that unlocks the power of dynamic filtering.

Important Considerations

  • Data Types: Ensure that the data types in your HubDB column and your contact property match. In this case, both should be text-based.
  • Case Sensitivity: The `.lower` filter ensures that the values are all lowercase, which can prevent issues caused by inconsistent casing.
  • HubSpot Context: The contact variable needs to be properly defined within the HubSpot context (e.g., on a web page or in an email).

Practical Application: Building a Personalized Recipe Finder

Let's imagine you're building a recipe finder on your HubSpot-powered website. Here's how you can use this technique to show personalized recipes:

  1. Create a HubDB Table: Set up a HubDB table with columns for recipe name, ingredients, instructions, and a `meal_tag` column containing dietary tags (e.g., vegetarian, vegan, gluten-free).
  2. Capture User Preferences: Use a HubSpot form to capture the user's meal preferences and store them in a contact property.
  3. Implement the Filtering Logic: On your recipe finder page, use the code snippet above to dynamically filter the HubDB table based on the contact's meal preferences.
  4. Display the Results: Display the filtered recipes to the user, creating a personalized and engaging experience. This can be used to start up online shop with personalized product recommendations too.

ESHOPMAN Team Comment

This HubDB filtering issue highlights the importance of understanding the nuances of HubSpot's CMS. The `__in` operator is a powerful tool for creating dynamic and personalized experiences. We've seen similar issues when trying to filter products in an ESHOPMAN storefront based on customer attributes. Always double-check your query syntax and data types to avoid these common pitfalls.

By understanding and utilizing the `__in` operator, you can unlock the full potential of HubDB and create truly personalized experiences for your audience. It's all about connecting the dots between your data and your users' needs. You can even use this to free online shop maker and drive more sales.

Share: