Once your Product Feed is successfully uploaded you will need to decide which columns from the file will be used to filter down the results. You can do this by mapping the relevant questions and responses to column headers and values from your product feed.
Setting Up Your Logic
Navigate to the Dynamic Product Feed mapping page. You can find this within the Screen Editor by clicking on "Product Feed Logic"
Make sure there is a feed associated to your campaign. You will be prompted to add a feed to the campaign automatically but you can also click on "Attach Feed" in the upper left corner to select a feed from your account.
Once a feed is associated with your campaign, you can start to map columns from the feed onto questions in your quiz. Click on a blue plus button to pull the columns from your feed so you can map one of them onto the most relevant question:
Not all questions and responses from your experience need to be mapped to your feed, only the ones that are relevant for displaying the relevant product at the end of the experience. You can map a question to numerous columns and multiple values from your feed to one response. It's quite flexible! You can learn more about the filtering logic rules here.
Once you have mapped your questions and responses to your product feed, you need to decide which products to show to the end consumer. Make sure you save all of the mapping that you've done and then select the "Next" button near the upper right to advance to the next screen.
On this screen, you will designate Fallback Logic, as well as determine how you want Jebbit to display appropriate matches in your quiz. For example, you may have specified within the Screen Editor that you want to display four products to the end consumer. However, after they go through the experience it may be that there are only two products from your feed which match perfectly. To plan for this case, you will have two options:
Only show exact matches
Fill all of your product slots even if there are not enough exact matches
In the case of an exact match, we will only display the perfect matches from the result set. So even if you want to display up to four products to the end consumer, in the case where they are perfectly matched with two, your experience will only serve two.
If there are no matches at all, then you can choose to set up Fallback Logic or to display a default message so consumers know there were not matches. If you choose to set up Fallback Logic, then in the case of no exact match, we will drop the filtering for the column with the lowest ranking. We will do this until we can find the best match to serve, even if it's not exact.
If you don't want to display any products if there are no exact matches, then you can choose to display a standard message instead:
If you would rather have Jebbit fill all of your product slots, even when there are not enough exact matches to select from your feed, then you will select 'Fill all of your product slots even if there are not enough exact matches.' This will allow you to set Fallback Logic so that we can removing filtering from the lowest ranked columns until we find the next best products to fill up all product slots available on your screen.
Mapping Guide
The following is a guide to help you understand how different mapping combinations will impact the filtering logic behind the scenes.
1) Map fields across questions
Mapping unique columns to unique screens is the most common way that the dynamic product feed is used. In this scenario, you never map the same column from your feed onto more than one question. The end result is that all mapped values across questions are ANDed.
In the example below, if a user selects Womens and Treadmills, Jebbit will look for items in your product feed that have both Female AND Road as associated descriptors.
2) Select multiple values tied to a button click
Tying multiple descriptors from your catalog to a button click will OR the product feed for that selection.
In the example below, we will filter by products that are classified as Green OR Greenish black if an end user selects Green as their response on that screen.
3) Map multiple fields to a question
If multiple fields are mapped to a question, the values will be ANDed.
In the example below, if a user selects All Types, Jebbit will filter your catalog by Terrain of Roads AND Gender of Female. The product(s) that we’ll match the user to do not need to contain both of these descriptions, only one of them.
4) If the product feed has multiple values in a cell
If a product from the product feed has numerous values (say comma separated) in one cell, that combination of values will appear as a unique value when mapping button clicks. In this case, we would filter by the exact combination of those items.
For example, if your product feed has a custom column for Color and you list one of your products as being Blue, Green, the descriptor Blue, Green will be available for you to map within the platform.
Keep in mind, mapping the descriptor Blue, Green to a button click is not the same as mapping Blue and Green to a button click. Products that are Blue only do not count as products with the Blue, Green combination.
If you want to select all products that have Blue in them, would you select the first two checkboxes below. By doing so, you will OR those products in the filtering process.
5) Select the same field/column across questions
If you map the same custom column across more than one question, your product feed will use 'OR" rules by default. Doing so will expand the amount of items from your catalog that become relevant to your end user.
For example, if on question #2 a user selects a response that’s mapped to Green items from your catalog, and then on question #5 the user clicks a response that’s mapped to Blue items from your catalog, Jebbit will display all blue products and all green products because Jebbit looks for items that contain Blue OR Green descriptors from your feed.
6) Select all the apply screens
If a user selects multiple options on a select all that apply screen, all the mapped values will be ORed with one another.
In the example below, if the end user selects Orange and Grey, Jebbit will filter by all products with Orange OR Grey tied to them.
Frequently Asked Questions
Q: What does Jebbit do if there are more than enough product matches but less product placeholders set up within the Screen Editor?
A:In the case where there are more results than the number of product slots, we will randomly choose which products to display to the consumer. Granted all the products will be exact matches.
Q: What is the difference between "AND" and "OR" logic?
A: By nature, “AND” rules will limit the amount of items from your catalog that are relevant to the end user because only items with “descriptor 1” AND “descriptor 2” will become relevant.
“OR” rules will expand the amount of relevant items from your catalog that a user can get matched to. This is because “OR” rules imply that an item with either “descriptor 1” OR “descriptor 2” would be relevant.
Q: I've used the 'Tags' field from Shopify and have mapped that across all of my screens. Will Jebbit use "AND" or "OR" logic in this scenario?
A: Shopify feeds are unique in this regard. Even though most manual feeds will have a unique column created for each question asked, it's common for Shopify users to map the same "Tags" column across more than one question. In this case, Jebbit will "AND" Tags by default.