Overview: Query Builder

With Query Builder, you can create Custom Metrics for select Data Sources by adding Dimensions, Segments, Filters, and more.

Some popular use cases for Query Builder include creating Campaign-specific Metrics for Google Ads and Facebook Ads data, reporting on HubSpot Smart Lists with more granularity, and more. Query Builder often allows you to access additional Metrics or Dimensions from a Data Source and enhance your Databox reports. 


How to access Query Builder 

Navigate to Metrics > Query Builder to access Query Builder. 

    Query Builder is available on the Professional and Performer plans. Request a trial of Query Builder by following these steps.  

Query Builder is currently available for the following Data Sources:

How to use Query Builder

The setup of Query Builder differs depending on the Data Source that is selected. Each Query Builder is designed to mirror the terminology and setup of the UI of the Data Source itself as much as possible.

Some key fields to understand in order to become an expert Query Builder user are outlined below.

  • Metric: A Metric is a quantitative measurement, meaning there is a value associated with it. Examples of Metrics are "Sessions," "Leads" and "Impressions."
  • Dimension: Dimensions allow you to re-categorize the returned Metric values based on a similar attribute. Examples of Dimensions are "Country," "Source" and "Campaign." 
    Pro Tip: Add the word "by" in between the Metric and Dimension in order to determine an appropriate Custom Metric Name. From the Metric and Dimension examples outlined above, we could create the Custom Metrics "Sessions by Country," "Leads by Source," and "Impressions by Campaign." 
  • Segment: A Segment is a subset of your data that is configured within the Data Source itself. For example, Google Analytics Users often create Segments to isolate and analyze subsets of data based on specific Metrics or Dimensions. 
  • Filter: Filters restrict the data that gets included in the Custom Metric. All data that is returned is tested against the Filter. If the data matches the filtered Metric and Dimension specifications, the data is retained and included in the resultant Custom Metric. If the data returned doesn't match the filtered Metric and Dimensions specifications, the data is not included in the resultant Custom Metric. 
Pro Tip: Filters are case-sensitive. You should set identical filter entries as is set in the Data Source UI in order to avoid potential Custom Metric setup problems due to unrecognized filter entries. Learn more about how to identify correct entry names here.

How to view Custom Metrics

Use the Created By, Tags, and Data Source drop-downs in the top right of the Query Builder page to view significant Custom Metrics.

From the Data Source drop-down, you can view the number of Custom Metrics that have been built for each Data Source.

How to add a Custom Metric to a Databoard

 Open the selected Databoard in the Designer, or create a new Databoard.
 Drag and drop a blank Datablock onto the Databoard from the Metric Library
 Click on the Datablock on the Databoard to open the corresponding  Datablock Editor on the right-hand side of the Designer
 In the  Metrics drop-down, click  Data Source to select the appropriate Data Source. This will filter out metrics from the specific Data Source.
 In the Metric Type drop-down, select Custom to filter out all Custom Metric from this specific Data Source.
 In the main  Metrics drop-down, select the metric you'd like to display on the Datablock, using the Search bar if needed. This will update the Datablock and it will populate with the corresponding data 

Additional Information

  • The Data Preview is limited to display a maximum of 20 Dimensions per Date Range for Attributed Metrics. Dimensions will be sorted by descending value, therefore the 20 Dimensions with the highest total values will be displayed in the Data Preview for each Date Range.
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.