Data Thresholds

All about Data "thresholds" and what that means for you as a SALT subscriber

Updated over a week ago

What is a Data “threshold?”

Every billable add-on integration at SALT has been given an integration “threshold.” This threshold is an agency-level setting that allows you to set a limit on how many Data Credits or Big Data Vendor requests your agency can utilize, and therefore, be billed for each month.

For example, if you want to pay no more than $20/mo for Estated Data reports, you'd simply configure your Estated threshold to a number less than 20.

How do I manage Data thresholds?

You can manage your agency’s thresholds by navigating to your Integrations section and selecting the “Adjust Limit” option under the Estated or Fenris integrations. That link will load controls that allow you to set your desired monthly threshold for this integration.

What happens when my threshold is met?

When your Data request allowance is heading toward its maximum threshold, SALT will send 3 email notices:

  1. Approaching” - This indicates that you're approaching the threshold set for your agency

  2. Met” - This indicates that the threshold set for your agency has been reached.

  3. Exceeded” - This email is sent to both SALT and your team and indicates a bug that has allowed a Data request to happen despite your threshold having been met. [Note: This warning is extremely rare and in every sense, should never happen; however, we've created it to protect both you and SALT.]

What if I forget to set a threshold?

Thresholds are there to stop Data requests from happening endlessly. The threshold setting defaults to 100 requests monthly, but an admin/owner can adjust that number at any time.

Consider the hypothetical value of if an Agent with “100” set as their Data request threshold does a substantially targeted marketing campaign. If 10,000 people fill were to respond to your ad, your agency might not be prepared to pay for those 10,000+ Data requests. Thresholds are there to prevent that type of scenario from occurring.

Did this answer your question?