How To Track Brand Mentions Using Brand24 Step-By-Step

Table of Contents

Some links on The Justifiable are affiliate links, meaning we may earn a small commission at no extra cost to you. Read full disclaimer.

Learning how to track brand mentions using Brand24 is less about collecting every reference to your name and more about turning online conversations into useful decisions. A good setup helps you spot praise, complaints, campaign reactions, competitor activity, and emerging issues without manually searching dozens of platforms.

In this guide, you’ll build a Brand24 monitoring project from the ground up, refine the keywords that control what gets collected, organize the Mentions feed, configure alerts, troubleshoot noisy data, and measure changes over time. By the end, you’ll have a repeatable workflow rather than another dashboard you rarely check.

Understand What Brand24 Is Actually Tracking

Before creating a project, it helps to separate a “mention” from a useful brand signal. Brand24 can collect public references from many online sources, but the quality of your monitoring still depends on the keywords, scope, and interpretation you apply.

Know What Counts as a Brand Mention

A brand mention is any monitored public piece of content that contains a keyword or phrase your project is configured to track. That could be your company name, product name, campaign hashtag, social handle, executive name, slogan, or another phrase strongly connected to your business.

The important detail is that a mention does not automatically equal customer feedback. A news article may reference your company without expressing an opinion. A forum user may compare your product with a competitor. A social post may use your campaign hashtag sarcastically.

Think in layers. Your core brand name tells you when the company is discussed. Product keywords reveal specific demand or complaints. Campaign terms help you measure launches. Executive names can expose reputation issues that do not include the company name.

If your brand is called “Northstar Analytics,” for example, tracking only “Northstar Analytics” may miss people who shorten it to “Northstar,” mention a flagship product, or tag a campaign. Your goal is to capture the language real people use while avoiding keywords so broad that the feed becomes noisy.

Understand Where Mentions Come From

Brand24 is designed for media monitoring and social listening across public online sources such as social media, news sites, blogs, forums, video content, reviews, podcasts, and other indexed web content. The exact source coverage and collection behavior can vary by platform, source availability, account configuration, and subscription.

That matters because no monitoring setup should be treated as a perfect copy of the internet. Private groups, closed communities, direct messages, restricted profiles, deleted posts, or content blocked by platform access rules may not be available. A useful monitoring process therefore measures what Brand24 can collect consistently rather than assuming every conversation is visible.

I recommend treating the tool as a high-signal listening layer. It is especially valuable when manual searching would become repetitive or inconsistent.

The practical takeaway is simple: judge the quality of your monitoring by whether it helps you make faster decisions. A smaller, cleaner collection of relevant mentions is usually more useful than a huge feed filled with unrelated references.

Decide What You Want Monitoring to Accomplish

Before adding keywords, write down the decisions you expect the data to support. This prevents the common mistake of collecting mentions first and trying to invent a purpose later.

A reputation-monitoring project might prioritize negative sentiment, high-reach mentions, sudden spikes, and recurring complaint themes. A campaign project might focus on mention volume, reach, sentiment, hashtag use, and the sources driving attention. A competitive project may emphasize share of voice, comparative sentiment, and changes in discussion volume.

Choose a primary objective and two or three supporting questions. For example: “Are negative mentions increasing?” “Which issue is causing the increase?” and “Which channels are spreading it?”

I recommend building each monitoring project around a decision, not around a dashboard. When you know what action a signal should trigger, Brand24 becomes much easier to use.

This also makes reporting more useful. Instead of presenting a large set of metrics, you can show whether awareness, reputation, campaign response, or competitor position is improving and explain what changed.

Plan the Right Keywords Before Creating Your Project

Keyword design determines what Brand24 collects. A few minutes spent planning brand variations, required terms, and exclusions can save hours of cleaning irrelevant mentions later.

Build a Core Keyword Set Around Real Brand Language

Start with the terms people are most likely to type when talking about you. Brand24 can monitor brand names, handles, products, services, slogans, hashtags, people, campaigns, and other phrases, so you should build the project around actual audience language rather than internal naming conventions.

Your first keyword should usually be the clearest version of the brand name. Then consider common abbreviations, branded hashtags, product names, campaign phrases, or executive names that genuinely deserve monitoring.

Suppose a company called “BrightPath CRM” is often shortened to “BrightPath.” The full name is precise, but the short name may collide with unrelated businesses, organizations, or everyday language. In that case, you could monitor the exact brand name confidently and test the shorter variation with additional filters or required terms.

Keep product and campaign tracking separate when their analysis needs differ. If a product launch generates thousands of mentions, combining it with normal brand discussion can distort your baseline. A cleaner setup lets you identify whether a spike comes from the company overall or from one temporary campaign.

Your initial keyword list should be broad enough to discover patterns but small enough that you can understand why each term is included.

Use Required and Excluded Keywords to Reduce Noise

Required and excluded keywords are among the most important tools for brands with ambiguous names. A required keyword narrows results by specifying another word that must appear. An excluded keyword removes mentions containing terms you know are irrelevant.

Imagine you monitor “Mercury,” but your company is a software brand rather than the planet, chemical element, automobile, or mythology reference. You could require words associated with your product category or exclude recurring irrelevant terms after reviewing the first batch of results.

ALSO READ: Marketing Tools to Maximize Your Digital Strategy

Set exclusions early when possible. Changes to excluded keywords may affect newly collected mentions rather than rewriting all previously collected data, so a clean initial setup makes trend comparisons easier later.

Be conservative with required terms. If you require too many words at once, genuine mentions may disappear simply because people do not use your preferred vocabulary. Start with your main keyword, inspect the results, and tighten only where the noise is obvious.

Boolean search can provide more precise combinations using operators such as AND, OR, and NOT. Use it when a simple keyword plus exclusions cannot express the monitoring logic clearly.

Decide When to Separate Projects

A Brand24 project should group keywords that make sense to analyze together. However, combining too many unrelated objectives can make your data difficult to interpret.

Create separate projects when you need clean comparisons between brands, products, campaigns, or markets. Competitor monitoring is a good example. You can place competitors together when your main goal is simply reading mentions, but separate competitor projects make comparative analytics much clearer because each brand retains its own data set.

The same principle applies to a major product launch. If you expect a temporary surge in discussion, isolating that campaign prevents the launch from overwhelming normal brand-performance trends. You can still compare the projects later, but the underlying data remains easier to explain.

Reputation staff can watch the core brand project, product marketers can monitor launch-specific discussion, and competitive-intelligence users can review competitor projects without everyone working from one overloaded feed.

Do not split projects unnecessarily, though. More projects and keywords may affect account limits, and fragmented monitoring can create duplicated work. A useful rule is to separate data only when you expect to analyze, alert on, or report it differently.

Set Up Your Brand24 Project Step by Step

Once your keyword plan is ready, project creation is straightforward. The key is to configure enough scope to collect useful data without applying so many restrictions that you accidentally suppress relevant mentions.

Create the Project and Enter Your Primary Keywords

Log in to Brand24 and create a new project. Name the project so its purpose is immediately clear, such as “Core Brand Reputation,” “Spring Product Launch,” or “Competitor – Brand A.” Clear naming becomes more valuable when your account contains several projects.

Enter the main keyword or keywords you prepared. Begin with the strongest identifiers: your exact brand name, handle, product, or campaign phrase. If the setup asks for language preferences, choose based on the markets you actually need to monitor. “All languages” may be appropriate for an international brand, but selecting a narrower language can reduce irrelevant volume when your business operates in one market.

Add required or excluded keywords only where you already know they are necessary. It is usually better to see an initial sample than to over-filter from the start. A project that returns too much data is easier to refine than a project that silently misses conversations.

After creation, give the project a clear internal owner. Someone should be responsible for checking whether the collected mentions match the original monitoring goal.

Review Sources and Add Relevant Integrations

Brand24 can monitor multiple source categories, and the default broad coverage is useful during setup. Review the project’s source settings before disabling anything. If you switch off a category that happens to contain most discussion about your brand, you may create an artificial decline in mention volume.

Some social sources may benefit from account integrations or additional-source configuration. Brand24 documentation currently supports connecting certain social accounts and adding selected sources or profiles where required.

Also consider how alerts will reach your team. If your workflow depends on Slack, Brand24 can integrate notifications into that environment, which can be more practical than expecting several people to check the dashboard continuously.

Do not connect a source simply because the option exists. Match each integration to a decision. A customer-support team may need fast notification of complaints. A PR team may care more about influential news and social mentions. A campaign team may need launch-specific updates.

The goal is coverage with purpose, not maximum configuration.

Validate the First Mentions Before Automating Anything

Open the Mentions tab and inspect the first set of results manually. This is where you confirm whether the project reflects real brand conversation or whether your keyword logic needs adjustment.

Look at approximately the first several dozen mentions across different sources and ask three questions: Is this actually about us? Would I want this type of result in a report? Would I want to be alerted if this became negative or unusually visible?

Check the date range, source labels, sentiment classification, reach or influence indicators, and the original context of the mention. If one unrelated meaning appears repeatedly, add an excluded keyword. If important conversations use a variation you did not monitor, consider adding it. If results are unexpectedly sparse, temporarily remove restrictive conditions before assuming the platform cannot find the conversation.

Avoid configuring aggressive alerts during this validation stage. A noisy project can flood inboxes and team channels, which teaches people to ignore notifications.

Once you can scan the feed and recognize that most results are genuinely relevant, you are ready to turn the project from a collection mechanism into a daily monitoring workflow.

Use the Mentions Feed to Find What Needs Attention

The Mentions feed is where monitoring becomes operational. Instead of reading every result equally, use filters, context, sentiment, and tags to separate routine references from conversations that need action.

Filter Mentions by Source, Sentiment, Importance, and Context

As mention volume grows, filtering becomes essential. Brand24’s advanced filters can narrow results by criteria such as source, sentiment, author, domain, date, location, and importance, depending on the data available for the mention.

Start by filtering around your monitoring goal. For reputation management, look at negative mentions and important or high-impact sources. For campaign analysis, isolate campaign dates and the channels where promotion took place. For customer research, filter discussions to the product or topic you are studying.

Use the Importance filter to surface higher-impact references, but do not let it replace human review.

Save recurring filter combinations when the interface allows it. A “High-Impact Negative” view, for example, can become part of a daily reputation check. A “Campaign – Social Only” view can support a marketing review.

The objective is to create repeatable lenses on the same data. Once your team knows which filter corresponds to which decision, monitoring becomes faster and less subjective.

Read Sentiment as a Signal, Not a Verdict

Brand24 classifies sentiment to help you separate positive, neutral, and negative discussion. This is useful for spotting direction and changes over time, but automated sentiment should still be treated as a starting point rather than unquestionable truth.

Sarcasm, mixed opinions, technical language, jokes, and quoted text can be difficult for any automated classification system. A post saying, “Great, the app crashed again,” contains a positive word but expresses frustration. A news headline may appear negative because it describes a problem even when the brand is not being criticized.

When a mention matters, open the original context. Brand24 allows sentiment to be reviewed and, in supported workflows, manually corrected.

Use sentiment trends rather than obsessing over isolated labels. If negative volume rises across several days while total mention volume stays stable, investigate what changed. If negativity rises only because total awareness exploded during a controversial campaign, interpret it alongside reach, topics, and source distribution.

ALSO READ: Apollo IO Worth It For Startups: Real ROI Breakdown

The strongest insight comes from combining sentiment with context.

Tag Mentions Based on the Action They Require

Tags turn a stream of mentions into a working system. Instead of tagging by vague topic alone, I suggest using categories that reflect what your team should do next.

A simple taxonomy might include “Respond,” “Customer Issue,” “Sales Opportunity,” “Press,” “Creator,” “Product Feedback,” “Competitor,” and “Ignore.” You can add campaign-specific tags where useful, but keep the core set stable enough that reports remain comparable.

Suppose a negative forum post describes a recurring product problem. Tagging it “Customer Issue” and “Product Feedback” allows support and product teams to review it later without rereading the entire feed. A positive review from a high-reach creator could receive “Creator” and “Advocacy.”

Assign ownership outside the tag itself. A tag is only useful if someone knows what happens next. For example, mentions tagged “Respond” should have a response-time expectation, while “Product Feedback” could be summarized weekly for product managers.

This is where brand monitoring becomes more than observation. You are creating a lightweight routing layer that moves public conversation to the people who can act on it.

Configure Alerts and Reports Without Creating Notification Fatigue

Alerts are valuable when they shorten reaction time, but too many notifications quickly become background noise. Build separate alert rules for urgent events, routine monitoring, and reporting.

Use Notifications for Specific Monitoring Jobs

Brand24 supports different notification options depending on account configuration, including email, mobile, Slack, reports, and spike-oriented alerts. Rather than enabling everything, map each notification to a response.

A reputation manager might need immediate visibility into important negative mentions. A marketing manager may only need a daily summary of campaign discussion. An executive may prefer a weekly report showing trend direction rather than individual posts.

If you send every mention to a team channel, high-volume days can make the channel unusable. Filter first. For example, send only negative or high-importance mentions to the rapid-response workflow and leave routine positive or neutral references for a scheduled review.

Test notifications for several days before expanding them to the wider team. Confirm that links open correctly, filters capture the intended mentions, and the recipients understand what action is expected.

The best alert is not the one that arrives fastest. It is the one that reaches the right person with enough context to make a decision without creating unnecessary interruption.

Set Storm Alerts for Sudden Conversation Spikes

Storm Alerts are designed to notify you when discussion changes sharply, which makes them useful for emerging crises, viral moments, campaign surges, or unexpected competitor events.

Treat a spike as a prompt to investigate rather than evidence that something is wrong. A burst of mentions could come from a favorable news story, a creator recommendation, a giveaway, a service outage, criticism, or a competitor comparison. When an alert fires, open the mentions around the spike and identify the sources, sentiment mix, repeated phrases, and highest-impact authors.

Create an escalation rule before you need it. For instance, a sharp increase in negative mentions may go to communications and customer support, while a high-reach positive spike may go to social and partnerships so they can amplify it. This keeps teams from improvising responsibilities during a fast-moving event.

A well-configured spike alert gives you earlier context. It should reduce reaction time without turning ordinary fluctuation into an emergency.

Build a Reporting Cadence Around Decisions

Daily monitoring and formal reporting serve different purposes. The daily workflow catches individual conversations and sudden changes. Reporting explains trends, patterns, and outcomes over a longer period.

Choose a cadence based on how quickly the business can act. A campaign team may review data every day during launch week. A reputation team may inspect alerts continuously but summarize performance weekly. Leadership may need a monthly comparison of mention volume, reach, sentiment, and competitive position.

Keep reports focused. Include the few metrics that answer the original monitoring questions, then add interpretation: what changed, why it changed, and what action follows. A chart showing increased mentions is incomplete if you do not explain whether the growth came from a campaign, a news event, a complaint, or unrelated noise.

Use tags and saved filters to make recurring reports consistent. If “Product Feedback” means the same thing every week, changes in that tag become interpretable. If filters change constantly, trend comparisons become less reliable.

Reporting is successful when a stakeholder can make a decision from it.

Troubleshoot Missing, Irrelevant, or Misleading Mentions

Even a well-designed project needs maintenance. Most monitoring problems come from keyword ambiguity, restrictive filters, disabled sources, short date ranges, or assumptions about what the platform can access.

Fix a Feed Filled With Irrelevant Mentions

When irrelevant results dominate, identify the pattern before adding exclusions. Open a sample of unwanted mentions and look for words, domains, authors, or contexts they share.

If one alternate meaning creates most of the noise, add specific excluded keywords. If the problem comes from a handful of websites or authors, source- or domain-level filters may be more precise. If your main keyword is inherently broad, consider adding a required term that connects it to your industry.

Avoid the temptation to keep stacking exclusions until the feed looks perfect. Over-filtering can hide unusual but important conversations. A brand may suddenly be discussed in a new context that your old assumptions would have excluded.

Boolean search is helpful for complex cases because you can express combinations more clearly than with a long list of individual filters. Save the logic and test it against recent data before relying on it in reports.

A clean feed does not mean every mention is positive or useful. It means most mentions are genuinely about the subject you intended to monitor.

Diagnose a Project That Shows Too Few Results

If a project is empty or unexpectedly quiet, simplify it. Start with the main keyword and broaden the date range. Then check language settings, enabled sources, required terms, excluded terms, and any active advanced filters.

One common problem is requiring too many words in the same mention. Another is accidentally using a term as both required and excluded. Disabled sources can also remove the only places where a niche brand is being discussed. A very short date window may make a low-volume project appear broken even when collection is working correctly.

Test your assumptions outside the most restrictive view. If you know a public mention exists, search for its exact wording or source and inspect whether it falls within the project scope. If it cannot be collected, the issue may be source availability rather than keyword logic.

For a small brand, low mention volume may also be accurate. In that case, widen monitoring strategically by adding product names, founder names, campaign phrases, or category-specific terms only when those additions support a clear objective.

Validate Sentiment and Reach Before Acting on Them

Metrics can mislead when they are removed from context. Sentiment may misread sarcasm, while reach represents potential exposure rather than guaranteed attention from every person in the estimated audience.

When a high-stakes decision depends on a small number of mentions, review those mentions manually. Check whether the sentiment matches the actual message, whether the source is credible, and whether one large account is distorting the overall reach picture.

The same caution applies to spikes. A single widely followed profile can create a dramatic reach increase even if broader discussion remains limited. Conversely, hundreds of low-reach customer complaints may deserve more operational attention than one neutral mention from a large publisher.

Use multiple indicators together: mention volume shows how much discussion exists; reach estimates visibility; sentiment suggests emotional direction; engagement indicates interaction; source and author data help explain who is driving the conversation.

ALSO READ: Brand24 Real Brand Monitoring Case Study: Growth Story

The goal is not to eliminate imperfect measurement. It is to understand what each metric can and cannot tell you before you attach business meaning to it.

Measure Whether Brand Conversation Is Actually Improving

Once your data is clean enough to trust, move from monitoring individual mentions to measuring patterns. Consistent baselines and comparisons help you distinguish real change from normal daily variation.

Track Mention Volume, Reach, Sentiment, and Engagement Together

No single metric defines brand health. Mention volume tells you how often the monitored subject appears. Reach estimates how widely those mentions could be seen. Sentiment helps describe the balance of positive, neutral, and negative discussion. Engagement adds evidence about how strongly audiences are interacting with the conversation.

Read them as a system. If mentions rise but reach stays flat, discussion may be growing among smaller accounts or niche communities. If reach jumps while mention volume barely changes, one or two influential sources may be responsible. If volume and negative sentiment rise together, review the topics behind the increase before labeling it a crisis.

Create a baseline period that reflects normal activity. For an established brand, that could be several weeks or months outside major campaigns. Then compare future periods against that baseline rather than judging every daily fluctuation independently.

Measurement becomes useful when it identifies where change occurred and gives you enough context to decide what to investigate next.

Compare Periods and Separate Competitor Projects

Brand24’s Comparison functionality can evaluate different projects or different time periods, which is especially useful for competitor monitoring and before-and-after analysis.

For period comparison, choose comparable windows. Comparing launch week with an ordinary week may be intentional, but explain that campaign activity is the reason for the difference. For recurring reports, week-over-week or month-over-month comparisons are easier to interpret when seasonality and campaign timing are considered.

For competitors, separate projects give you cleaner data for comparing mention volume, reach, sentiment, source distribution, and share of voice. Share of voice helps show how much of the tracked conversation belongs to each brand, but it should not be interpreted as market share or revenue. It measures visibility within the monitored conversation.

A hypothetical example: your brand might have fewer mentions than a competitor but a higher proportion of positive discussion and stronger growth during a product launch. That tells a more useful story than simply saying the competitor “won” because it had more mentions.

The analysis should always move from “what changed?” to “what caused it?” and finally to “what should we do differently?”

Use AI Features to Investigate Patterns Faster

Brand24 includes AI-assisted capabilities that can help summarize data, detect unusual activity, group conversations into topics, and answer questions about project data. Availability depends on the plan and feature configuration, so work with the options enabled in your account.

AI Anomaly Detection can help flag unusual spikes in mentions or reach and provide context around what may have caused them. AI Topic Analysis groups mentions into discussion themes so you can see which subjects dominate, how their sentiment differs, and how attention changes. AI Insights can help summarize trends and surface recommendations, while AI Brand Assistant can answer natural-language questions about monitored data.

AI cannot rescue a poorly scoped keyword set filled with irrelevant references. If the input data contains noise, automated summaries may confidently describe the wrong conversation.

Use AI to accelerate investigation, not to remove judgment. When a generated insight says negative sentiment increased because of a particular issue, open the underlying mentions and verify that explanation.

The strongest workflow is human-defined monitoring, machine-assisted pattern detection, and human-reviewed action.

Scale Brand Monitoring Into a Repeatable Business Process

Tracking mentions becomes more valuable when the insights move beyond the marketing dashboard. With clear ownership and consistent project design, the same data can support competitor research, customer feedback, campaign analysis, and opportunity discovery.

Extend Monitoring to Competitors and Campaigns

After your core brand project is stable, create dedicated monitoring for the areas where comparison will improve decisions. Competitors and major campaigns are usually the most useful next projects.

For competitors, track the same types of signals you track for yourself: brand name, flagship products, campaign phrases, and relevant executives where appropriate. Then use project comparisons to examine visibility, sentiment, reach, and share of voice.

Campaign projects should have a defined start date, objective, and naming convention. Monitor campaign hashtags, slogans, product names, and other unique identifiers. During the campaign, review which sources create the most attention and whether sentiment changes as the message spreads.

Avoid treating competitor monitoring as imitation research. The value is identifying gaps. If customers repeatedly criticize a competitor for a specific service problem, that may reveal an opportunity for your positioning or product experience.

Likewise, campaign monitoring should influence decisions while the campaign is active. If a message is misunderstood, faster detection is more valuable than a polished report several weeks later.

Turn Mentions Into Customer and Growth Insights

Brand mentions often contain unsolicited language that surveys and internal reports do not capture. Customers describe problems in their own words, compare alternatives, reveal expectations, and sometimes ask for recommendations publicly.

Use tags or saved filters to collect recurring product feedback. Over time, separate one-off complaints from patterns. If several unrelated customers describe the same obstacle, summarize the language and examples for the product or support team. Do not reduce everything to sentiment; neutral questions can reveal serious usability gaps, while positive posts may contain suggestions for improvement.

Monitoring can also surface opportunities. People discussing a problem your product solves, asking for alternatives to a competitor, or praising your brand without an existing relationship may deserve follow-up. Context matters: helpful engagement is more effective than jumping into every mention with a sales pitch.

Influencer and author data can help you identify recurring voices that already discuss your category. Look for relevance and credibility, not only large follower counts.

Use them to improve messaging, FAQs, support material, campaign creative, positioning, and product priorities where the pattern is strong enough.

Create Governance Before Mention Volume Grows

Scaling monitoring requires rules. Decide who owns project settings, who can add keywords, who reviews alerts, who responds publicly, and how important findings are escalated. Without governance, different teams may change filters and tags until historical comparisons become unreliable.

Document a simple monitoring playbook. It should define each project’s purpose, monitored keywords, key exclusions, saved filters, tags, alert recipients, reporting cadence, and escalation criteria. Record major configuration changes with dates so unusual data shifts can be distinguished from real market changes.

Set review intervals. Monthly or quarterly, inspect whether keywords still match audience language, exclusions are still appropriate, source settings remain enabled, and alerts still produce useful signals. High-volume campaigns may need much more frequent review.

Not every negative mention needs a public response. Sometimes the best action is routing feedback internally, correcting a factual error, or watching whether a small conversation grows.

As volume increases, consistency becomes more important than complexity. A monitoring system that your team understands and follows will outperform an elaborate setup that depends on one person remembering how everything works.

Choose Your Next Step With Brand24

The best way to learn how to track brand mentions using Brand24 is to start with one well-defined monitoring objective, build a clean keyword set, and validate the Mentions feed before adding automation. From there, filters, sentiment, tags, alerts, comparisons, and AI analysis can help you move from individual references to patterns you can act on.

Keep the system disciplined. Review noisy results, protect your baseline when changing filters, verify high-stakes sentiment or reach data, and connect every alert or report to a real owner. As your process matures, expand into competitor monitoring, campaigns, customer insight, and trend analysis only when each new project supports a clear decision.

If your current challenge is scattered brand conversation, create a focused project in Brand24, monitor the first results manually, and refine from evidence rather than assumptions. That gives you the cleanest foundation for useful long-term brand intelligence.

Juxhin

I’m Juxhin, the voice behind The Justifiable.
I’ve spent 6+ years building blogs, managing affiliate campaigns, and testing the messy world of online business. Here, I cut the fluff and share the strategies that actually move the needle — so you can build income that’s sustainable, not speculative.