Skip to main content

Company Profile

Written by Niclas Aunin
Updated today

What the Company Profile shows

The Company Profile is the detail view for a single brand inside a report. It shows you, every prompt where it was mentioned, and gives you control over how the brand is matched in AI responses through aliases and custom variations.

You reach it by clicking any company name from the Brand Mentions table, the Visibility report, or the AI Presence matrix.

How ALLMO matches brands with system aliases and custom variations

The profile has three main parts:

  1. Company card. Shows the brand name, primary domain, category, and an icon.

  2. Aliases and variations. ALLMO uses two layers of matching:

    1. System aliases are global, maintained by ALLMO across all customers, and built with false-positive protection so they don't accidentally match unrelated mentions.

    2. Custom variations are scoped to your report only, and use a simple deterministic text based logic. You add and manage them yourself for terms specific to your tracking needs, internal product names, regional spellings, abbreviations your team cares about.

  3. Prompts table. Every prompt in the report that mentioned this company, ranked by mention count. Click a row to drill into the full prompt analytics.

Important: Custom variations only apply to new responses generated after you add them. Past data won't be retroactively rescored.

Read more about company entity matching here.
​

How to use profile insights to improve report accuracy

  • Audit your own brand first. Make sure every product name, abbreviation, and common misspelling of your company is captured. Missed variations = undercounted visibility.

  • Audit key competitors. The same logic applies, if you're under-tracking competitors, your benchmarks are wrong.

  • Investigate surprising prompts. The prompts table often reveals use cases or buyer questions you didn't realize the brand was associated with. That's content and positioning intelligence.

  • Watch new variations forward. Because changes only apply to future responses, add variations early in a tracking cycle, not right before you pull a report.

  • Flag system-level issues. If a system alias is causing false positives or a major variation is missing globally, send a suggestion β€” improvements benefit your future reports too.

Did this answer your question?