Why This Approach Is Needed
The Looker Studio dashboard uses the Query API to access Scrunch data. The Scrunch-Looker Studio data connector is currently not mapped to support all filters you see in Scrunch such as:
Branded, non-branded
Prompt Topic
Stage
Prompt ID
The solution is to use tags to recreate the branded vs non-branded logic.
Step-by-Step Process
Follow these steps to set up branded or non-branded filtering in Looker Studio.
Filter prompts in Scrunch
Go to your Prompts view in Scrunch and apply the filter you want to replicate. For example, filter by non-branded prompts.
Tag all filtered prompts
Select all prompts that match your filter and apply a tag. For example, create and apply a tag called "non-branded" to all non-branded prompts.
You can do the same for branded prompts by filtering for branded and tagging them as "branded".
Use the tag filter in Looker Studio
In your Looker Studio dashboard, use the tag filter to display only prompts with your chosen tag. For example, filter by the "non-branded" tag to show only non-branded prompts.
Important Notes
This approach maintains the same logic used in Scrunch to determine branded vs non-branded status. By filtering first in Scrunch and then tagging, you ensure the list matches exactly.
This solution requires manual updates. When you add or remove prompts, you will need to update your tags in Scrunch to keep the filter current.
Why Not Use Regex Filters in Looker Studio
You could create custom regex filters in Looker Studio to match brand names. However, this approach is less scalable and harder to maintain. Each time you add a new brand name variation, you would need to update the regex filter manually. The tagging approach is simpler and more reliable.
Need Help
If you have questions about setting up this filter or need assistance with your Looker Studio dashboard, contact the Scrunch support team.
