Using SQL like conditions, this tool allows you to mine for very specific numbers.
The best way to explain this tool is by example.
To begin with, you need to select an interface of interest.
Now, let’s say we select the interface ‘main.inputs.list’, which is the “gender” question we used in the example of the previous chapter, Trend Finder.
If we add no conditions, the tool will mine all unique answers, in the same way as the Trend Finder does, except it will not count ‘null’ answers, where the question was never shown.
Now what if we only wanted to count the answers that meet certain criteria.
Start by adding a condition, and let’s set that condition to only count the cases where the interface ‘main.carried_on.drop_down’ is equal to ‘Option 2’,
For demonstration purpose we will imagine it was a question like this:
Which fruit do you prefer:
- Option 1: Apples
- Option 2: Oranges
- Option 3: Kiwis
Now engine will only count the ‘main.inputs.lists’ unique answers in cases where the ‘main.carried_on.drop_down’ is equal to ‘Option 2’:
You could add as many conditions as you like, and they can track any interface.
All conditions except the first also require a conjunction key, either ‘AND’ or ‘OR’, which will determine how the engine joins the conditions to filter the eventual data.
For example, we may only be interested in cases where the gender was female, so we could add another condition to only include cases where ‘main.inputs.list’ is equal to “Female”:
Be careful when using the ‘OR’ conjunction - it will negate the other conditions.
For example, if we added another condition to our example above, and made it:
'OR' 'main.inputs.list' '=' 'Male'
You might expect the results to show all counts of both men and women who answered Option 2. You’d be wrong.
The final condition is joined with an ‘OR’ conjunction, which means that the engine will add all cases where the ‘main.inputs.list’ was ‘Male’, regardless of the first two conditions: