Introducing our Brand Safe feature

Published on February 04, 2019

Introducing our newest API feature: Brand Safe

The last thing you want is for your brand to be associated with something negative or offensive.

Upsetting your customers is never a good idea. While it’s impossible to avoid it from happening 100% of the time, you do what you can to prevent it from happening in the first place.

So how does PredictHQ help our customers protect their brand’s reputation when it comes to displaying events to their customers? Simple. Through our Brand Safe filter.

PredictHQ’s focus is always on data quality. From programmatically identifying and removing duplicates within and across providers, to detecting and eliminating spam events and handling geolocation issues, we do the heavy lifting so our API is as easy-to-use as possible. Adding a Brand Safe filter was a logical extension to our API.

Everyone’s definition of what’s offensive and inappropriate differs, so it’s difficult to arrive at universal agreement on what should be censored when it comes to real-world events. However, most companies want to avoid events that contains swear words in its title or adult-type content showing up in your family-friendly website or application. That’s where our Brand Safe filter comes in.

What is it?

Brand Safe is a filtering option in PredictHQ’s API that lets you exclude events that are potentially unsafe for your brand to be associated with.

Some examples of non-brand safe events include content that promotes hate, violence or discrimination, coarse language or content that is sexually-suggestive or explicit. Brand Safe includes the title and description of events when determining whether an event is brand-safe or not.

Who can use it?

The Brand Safe filter is available through the PredictHQ API for all users.

How do I use it?

You can choose to exclude potentially brand-unsafe events from your search results. Potentially brand-unsafe events are included in search results by default. Brand Safe is easy to turn on and you can see more details about this feature in our Developer Docs to learn how.