Using 'NOT' and Brandwatch Lists to Filter Data

One question I recently had from a few work colleagues was about the use of the NOT operator in Brandwatch dashboards, and how that differs from using Brandwatch lists.

If you’re already a Brandwatch user then you may be familiar with their lists: site lists, author lists, location lists. These help you group sites, authors and locations so you can later filter your data based on the lists you’ve curated. (You can find more info about it here.)

However, if you have a dashboard and you exclude authors via an author list or if you exclude them right in the query (using the author: operator), you’ll get the same result: you won’t see mentions from those people anywhere in your dashboard. The same applies when using the site: operator vs. filtering out site lists, and using the 5 location operators (city:, county:, state:, country:, continent:) vs. filtering out location lists.

I’ve seen a few Brandwatch users filtering lists out instead of using the NOT operator to exclude mentions, mainly when it comes to long lists of parameters (authors, locations or sites). For instance, if you have a really long list of authors, you can add them to a list which you can use to quickly filter their mentions out, instead of dumping all of those names in the query, especially if you don’t have enough space left in the query builder.

So, what’s essentially the difference between the two? Are there any advantages in using the custom operators rather than filtering out by lists?

Excluding vs. Filtering out

Lists don’t really exclude mentions, they merely filter them out, and that makes a huge difference. The NOT operator makes sure that Brandwatch doesn’t pull those mentions at all if they’re from the authors/locations/sites you don’t want to see. On the other hand, the author list looks at those mentions you already have, finds the mentions that match those lists, and hides them from your dashboard. All your components will update accordingly: figures, charts, everything else. However, take off the author list exclusions and you’ll see those mentions again.

So, which one’s better?

Lists are a great way to filter your data, but you should really use them for more than just permanent exclusions. If you’re unsure of which option to go for, chances are you can use more effective ways to exclude mentions, like the following:

  • can you afford to have Brandwatch collect those mentions, even if you’re not going to need them later? If you already have a small data allowance, or you’re struggling to stay within your monthly allowance, then perhaps you should just exclude those mentions from those authors/locations/sites at a query level;
  • do you need those mentions from those authors/locations/sites at all? If not, then you can safely delete those mentions at a query level.
  • does anyone sharing the same project need to see those mentions? If you’re sharing a project with other people then you might not want to “tamper” with a shared query, and have your own lists to exclude mentions you don’t need instead. Other users sharing that query might need to see those mentions after all, and any changes you make to the query will affect everything that it powers (dashboards, alerts, Vizia screens etc.). Sure, you could duplicate the query so you can add your exclusions to it (thus leaving the main query intact), but bear in mind that Brandwatch will see the mentions from both queries as separate. So, if Query A has 1,000 mentions and the duplicate Query A1 (which is a copy of Query A + your exclusions) has 800 mentions, Brandwatch will take off 1,800 (Query A + Query A1) from your data allowance. You may not need to worry about data usage if you have unlimited data, but you may want to use your query allowance sparingly, in which case I suggest using rules and/or lists.
  • does the list of authors make you go over your query character limit? Brandwatch has a limit of 5,000 characters per query. While that covers most of your needs (especially with the advanced operators, which we’ll talk about in the next post), you may run out of characters if you have a really complex query (and I know a thing or two about those). If that’s the main reason why you’re considering using lists, the first thing I’d recommend is reviewing your query. You may be using a lot of space unnecessarily: try and condense your query if you can, by using the advanced Boolean operators. So, for example, say we want to exclude all Buzzfeed Twitter accounts from our query. There are at least two things we can do:
    • instead of listing all Buzzfeed accounts (there are quite a few of them), we can use the "*" operator, so by writing NOT author:buzzfeed*, Brandwatch will exclude all Twitter accounts that begin with Buzzfeed (and most of Buzzfeed Twitter accounts do). However, if you’ve ran out of characters in your query and you really need a few more, use rules to delete the mentions you don’t need. Rules are a clever way to use an extra 5,000 characters on top of your query. You can keep your query as it is, and then list your exclusions as a rule that deletes all mentions that match your rule query. Please note: the rule won’t stop the query from capturing the mentions you don’t need; the rule will simply delete the mentions you don’t need after Brandwatch has captured them.
    • another tip is grouping all the authors together. While most Buzzfeed Twitter accounts start with “Buzzfeed”, there’s also a number of “secondary accounts” that don’t follow that rule (e.g. @YrBFF, @CocoaButterBF). Instead of writing “NOT author:” every time you want to exclude an author...

      buzzfeed NOT author:buzzfeed* 
      NOT author:YrBFF NOT author:CocoaButterBF... can group them all by writing...

      NOT author:(buzzfeed* OR YrBFF OR CocoaButterBF)... 

      (cue: distributive property.) That’ll save you a few characters.

Proximity Operators (and Why You Need Them)

Brandwatch Unveils New "links:" Operator