Signals

Coming Soon in Data Explorer!

[Available for the Enterprise Tier only]
Creating a Signal
Signals can be accessed any time you are in the Data Explorer. Follow the normal process to choose your data sources, dimensions and metrics. Once you've pulled some data into the explorer you will be able to click on the Signals tab to view the Signal-specific form input.
 Navigate to your Workspace and find Signals in your left-side bar
Click on Create Signal on the Signals Dashboard to open the Signal Explorer
Just as in Data Explorer, select your Data Source, apply relevant filters to make sure you're pacing the right data set
Select the date range, the summary metric you want to track, the Target value, and the threshold.
For example: A user might want to pace your overall spend for a data source, and receive a notification when you are "Above", "Below" or "Above or Below" a percentage of the threshold that has been set.
Add all the Subscribers that should receive notifications, name and save your Signal! Once a Signal has been created, you will be returned to the Signals dashboard, where the Signal is now displayed as a row in a table interface.
Anatomy of a Signal
In the Signals UI, the user will be able to create a new Signal in a large modal. When creating a new Signal, the following inputs will be required:
Attribute
Description
Date Range
Users will be required to input a start and end date and time that is at least 24 hours. The Signal stops monitoring the metric when the end date and time is reached. 
​
Users will be able to input time in the highest granularity available to the data source they selected. For example: because Hourly is available in Facebook Ads, Signals using Facebook Ads as their data source will be able to input a specific hour of the day for their start/end date.
Data Source
Users will be required to specify which data source to monitor for the Signal.
Data Source will be a required condition.
Users will be allowed to add filters to apply to the data source being monitored, such as Publisher, Campaign Name contains, Age Bucket, Gender, etc.
Workspace filters Must be applied before Signal filters, e.g. the actual husky query must apply workspace_filters + signal_filters
If Workspace Filters are edited while Signals are scheduled in the future OR some Signals are mid-flight, when the user saves their edited workspace filters, a prompt will be triggered, stating: “These updates will not apply to your current Signals. Would you like to proceed?”
Filters available will include both metrics and dimensions.
Target Metric
When creating a Signal, users will be required to select a summary metric they would like to track. The menu of selectable metrics will be a list of taxons where taxon_type=’metric’, and aggregation_type = ‘SUM’’, and metric_calculation=None.
Target Value
Users will be allowed to apply a target value to the target metric, which is a target value specifically for the Signal’s date range. 
Pacing Model
When a target metric is being measured against a target value, the user will have the ability to select a pacing model that the platform will monitor their Signal with. In V1, “Even” pacing will be available, and more to come in the future.
Pacing Threshold
When a Signal has a target value, users will be able to set a threshold (% value) for their pacing. 
The default value will be X%. 
A Collaboration message will only fire when the target metric is outside of the pacing threshold upon reaching a pacing checkpoint. More on this in the Pacing Checkpoints section.
Signal Name
As the user is filling out the Data Source and Metric fields, the name field will parse the inputs and auto-fill with the format {{Data Source}} {{Metric}} {{Create Date}} (example: Facebook Ads Spend 02/20/2020).
Subscribers
Users will have the ability to add Subscribers for their Signal.
By default, the Signal creator is a Subscriber to the Signal, but can be removed.
Workspace users can be added as Subscribers to a Signal.
Updates are posted as Collaboration conversation messages in the Signal Line Chart. See the Subscription section for more information on how and when these notifications are posted.
When Subscribers are added or removed to a Signal, they are added or removed as Followers of all conversation messages in the Signal Line Chart.

Data Monitoring & Insights - Previous

Boards

Automated Insights

Last updated 9 months ago

Attribute	Description
Date Range	Users will be required to input a start and end date and time that is at least 24 hours. The Signal stops monitoring the metric when the end date and time is reached. Users will be able to input time in the highest granularity available to the data source they selected. For example: because Hourly is available in Facebook Ads, Signals using Facebook Ads as their data source will be able to input a specific hour of the day for their start/end date.
Data Source	Users will be required to specify which data source to monitor for the Signal. Data Source will be a required condition. Users will be allowed to add filters to apply to the data source being monitored, such as Publisher, Campaign Name contains, Age Bucket, Gender, etc. Workspace filters Must be applied before Signal filters, e.g. the actual husky query must apply workspace_filters + signal_filters If Workspace Filters are edited while Signals are scheduled in the future OR some Signals are mid-flight, when the user saves their edited workspace filters, a prompt will be triggered, stating: “These updates will not apply to your current Signals. Would you like to proceed?” Filters available will include both metrics and dimensions.
Target Metric	When creating a Signal, users will be required to select a summary metric they would like to track. The menu of selectable metrics will be a list of taxons where taxon_type=’metric’, and aggregation_type = ‘SUM’’, and metric_calculation=None.
Target Value	Users will be allowed to apply a target value to the target metric, which is a target value specifically for the Signal’s date range.
Pacing Model	When a target metric is being measured against a target value, the user will have the ability to select a pacing model that the platform will monitor their Signal with. In V1, “Even” pacing will be available, and more to come in the future.
Pacing Threshold	When a Signal has a target value, users will be able to set a threshold (% value) for their pacing. The default value will be X%. A Collaboration message will only fire when the target metric is outside of the pacing threshold upon reaching a pacing checkpoint. More on this in the Pacing Checkpoints section.
Signal Name	As the user is filling out the Data Source and Metric fields, the name field will parse the inputs and auto-fill with the format {{Data Source}} {{Metric}} {{Create Date}} (example: Facebook Ads Spend 02/20/2020).
Subscribers	Users will have the ability to add Subscribers for their Signal. By default, the Signal creator is a Subscriber to the Signal, but can be removed. Workspace users can be added as Subscribers to a Signal. Updates are posted as Collaboration conversation messages in the Signal Line Chart. See the Subscription section for more information on how and when these notifications are posted. When Subscribers are added or removed to a Signal, they are added or removed as Followers of all conversation messages in the Signal Line Chart.