Skip to main content
All CollectionsGetting StartedAudience Setup
Layering Targeting & Filtering Audiences
Layering Targeting & Filtering Audiences

How to use different Audience capabilities to maximize your reporting analysis

Landon Anspach avatar
Written by Landon Anspach
Updated over 6 months ago

Our Audiences help doc lays out all the basics for creating audiences within KnoCommerce, and the Targeting Audiences & Filtering Audiences help docs showcase the main two use cases within the Kno platform.

One way to maximize both of those features is by layering a Filtering Audience over top of data received using a specific Targeting Audience. By utilizing this method, you can combine two audiences so that you can analyze the data for the combined segments.

Here are several examples of various combinations to start the creative juices flowing:

  1. New Customer Targeting Audience on a New Customer survey

    1. Discovery = TikTok Filtering Audience

    2. Discovery = Instagram Filtering Audience

    3. Discovery = Facebook Filtering Audience

    4. Other Filtering Audiences for your brand

    5. Helps to identify patterns by looking at all the survey questions on the survey through the lens of New Customers discovering on a particular marketing channel

  2. Product ID Targeting Audience on a survey only displaying to specific product purchasers

    1. New Customer Filtering Audience

    2. Returning Customer Filtering Audience

    3. High-Volume Purchaser Filtering Audience

    4. Helps you to identify patterns for specific products across different levels of customers

This is just a starting point. There are lots of options whenever you are intentional about the Targeting Audiences you use on surveys and combining them with all kinds of Filtering Audiences. Make sure you use your Audience superpowers for good! πŸ˜„

If you have questions about what is possible or how to best achieve a particular level of research, please reach out to hello@knocommerce.com and we'll give you some recommendations!

Did this answer your question?