Guided Analysis Search: The Power of Custom SQL and AI

A guided analysis offers a more intuitive search experience that empowers you to explore your data with ease.

Create a data driven workflow for your users with the perfect combination of custom SQL and AI powered search queries. Defined pathways in a structured guided search are particularly beneficial for commonly run analyses because they standardize the process, ensuring consistency and reliability in the results. By guiding users through a predefined sequence of steps, the system minimizes the risk of errors or omissions, which can be common when navigating large, complex datasets. This structure is especially useful when the analysis is routine or critical, as it ensures that all necessary data points are considered and the proper methodology is followed.

Step 1: Add an example to your data source in console

• Log into https://console.getzingdata.com/
• Click on ‘Data Sources’
• Find the data source you want to add the guided analysis to and select ‘Settings’
• Click on ‘Examples’ and ‘+ Add New Example’
• In the modal window (see video above) change Example Type to Analysis question
• Complete the requested forms as seen in the UI and ‘Save’ when you are done

Step 2: Experience search with a guided analysis workflow

• In the Zing app, start your search from the home screen (see video above)
• Your guided analysis will be available once a trigger word [1] has been entered or select directly [2] in the UI
• Follow the guided workflow and complete requested forms. Click on X [3] to cancel guided analysis at any time and return to standard search

A few tips for adding custom SQL to a guided analysis

If you want a user to be able to select multiple items for an input field, your SQL will need to use the IN comparison operator instead of the = comparison operator E.G. brand IN [brand name] instead of brand = [brand name]

If a guided analysis has a lot of columns then it gets shown as a table. To ensure a field is graphed on the X-axis, add the “_x1” alias to your field in custom SQL. If you also specify “_x2" that _x2 field will be used as the ‘cut’ or ‘split’ for the x-axis field.

To ensure a field is graphed on the Y-axis, add the “_y1”, “_y2", “y3”, alias to your field name in custom SQL. The underscore and axis designation in your alias won’t show up in your graph titles, but are used to indicate which axis you want a field graphed on.

To learn more please visit our documentation:
Guided Analysis
Custom SQL

Get started for free! Sign In or create a new account.