GoHighLevel Announcement Banners: Sub-Account Targeting Guide

If you have looked for a way to push a message into specific client sub-accounts inside GoHighLevel – a plan upgrade nudge, a compliance notice, an onboarding reminder – and come away confused by outdated screenshots, that is because you were probably looking at three different features that all share the word “banner.” As of August 28, 2026, the newest of the three can target a banner to a specific sub-account, country, or user role using AND/OR rule logic, and almost nothing written about it exists yet, including HighLevel’s own help documentation.

This guide separates the three generations of the feature, walks through building a targeted banner today, and flags the two or three things the current docs genuinely do not answer.

Three features, one confusing name

Search “GoHighLevel banner” and you will land on content describing any one of these, often without saying which:

The distinction matters because the toggle-based Banner Management article is the only one HighLevel’s help center currently publishes on this whole area. If you are trying to build a custom banner and only find that article, you are reading about the wrong feature.

What the Builder itself does

The Announcements Builder walks you through four steps, with a live preview as you go:

• Content – the banner’s message, headline, and any call-to-action text
• Style – brand colors and visual treatment for the banner
• Audience – who sees it (this is where the new targeting rules live)
• Schedule – start and end timing, plus a frequency setting: Always, Weekly, or Monthly

Banners created in the Builder carry a priority level – Critical, Warning, or General – which decides which one wins if a sub-account qualifies for more than one banner at once. They also sit in Draft or Active status, so you can build and review a banner before it goes live, the same as a workflow draft.

What actually shipped on August 28

Before this update, the Audience step let you choose Agency level, Sub-account level, or both – a blunt broadcast switch. The update replaced that with a rule builder. For each rule you pick a field, an operator, and a value. HighLevel’s own changelog names three example fields: Sub-account, Country, and User Role.

The grouping logic, quoted directly from HighLevel’s changelog: conditions in the same group must all match (AND); you add a new group for an alternate match path (OR). In practice that means you can build something like “(Sub-account is on the Growth plan AND Country is United States) OR (User Role is Agency Admin)” – a single banner that serves two unrelated audiences with two different match conditions.

The same update also let call-to-action buttons open links in a new browser tab, which HighLevel frames as letting agencies safely point a banner at an external promotion or landing page without pulling the user out of the app they were working in.

Building a targeted banner, step by step

Real use cases this unlocks for agencies

• Plan-gated feature promos – target sub-accounts on a specific plan tier with an upsell banner for an add-on they don’t yet have, without emailing every client and annoying the ones who already have it
• Country-specific compliance notices – surface a messaging-compliance or tax notice only to sub-accounts operating in a country where it applies, rather than a blanket agency-wide banner that confuses everyone else
• Role-gated onboarding nudges – show a "finish setting up your workflow" reminder only to Standard Users who are still mid-onboarding, not to the admins who already configured everything
• Time-boxed external campaigns – link out to a landing page or webinar registration with a new-tab CTA so clients don’t lose their place in the CRM

Why in-app targeting beats another email

Agencies already have email and SMS for client communication, and most of what a banner says could technically go in either channel. The reason to use the Builder instead is reach inside the moment that matters: a banner shows up while someone is actively working in the CRM, not sitting unread in an inbox next to fifty other agency-tool notifications. For a plan-upgrade nudge or a "your automation needs attention" style message, that in-the-moment placement converts differently than an email a Standard User will read three days later, if at all. The tradeoff is that a banner is easy to dismiss and, per HighLevel’s own help documentation, dismissal persistence is described only as "typically user-based but may vary by device/session" – so treat it as a supplement to email and SMS for anything time-sensitive, not a replacement.

This also matters for agencies running white-label or SaaS-mode sub-accounts, where every touchpoint a client sees is supposed to look like it comes from the agency’s own brand, not HighLevel’s. Because the Builder’s Style step applies your own brand colors and the banner appears inside a rebranded interface, a targeted banner reads as a message from the agency itself. Getting the targeting rule wrong, on the other hand, is exactly how a client on a reseller plan ends up seeing an internal-sounding message meant for a different segment – one more reason to test a new rule group against a single known sub-account before setting a banner to Active agency-wide.

What is not yet confirmed

Two details are genuinely unclear from HighLevel’s own materials as of this writing, and this article is not going to guess at them:

• Whether the Country and Timezone rule fields key off the sub-account’s own registered settings or the individual viewing user’s profile settings. The changelog does not say, and no help article defines it yet. Test it against a known sub-account before relying on it for anything compliance-sensitive.
• The current, complete list of selectable User Role values under the new rule engine. The only documented role list – Agency Admin, Sub-account Admin, Standard User – comes from the older, pre-Builder toggle feature, so treat it as a starting point to verify in your own account rather than the confirmed current list.

Gotchas carried over from the older system

A few behaviors documented for the legacy Banner Management toggle are worth checking against the new Builder too, since HighLevel has not stated they changed:

• Priority only affects display order, not analytics or tracking – do not assume a higher-priority banner gets separately reported engagement
• A banner scoped to "Agency only" will not show inside sub-accounts even if it is otherwise enabled – a common source of "why isn’t anyone seeing this" tickets
• Some system banners are locked or mandatory regardless of your settings; that rule applied to the original toggle feature and there is no indication it applies to Builder-created banners, but it is worth confirming rather than assuming either way
• Only Agency Admins can manage banners by default; a custom role needs the Banner Management permission explicitly granted

The Announcements Builder’s targeting update is new enough that most of what exists online, including HighLevel’s own help center, is describing an older, simpler version of the feature. If you manage more than a handful of sub-accounts, the rule-group targeting is worth testing now, before every tutorial you find online has quietly gone stale again.

Frequently Asked Questions

What is the difference between GoHighLevel's Banner Management and the Announcements Builder?

Banner Management, under Agency Settings, only lets you toggle HighLevel's own built-in system banners on or off and set their priority and frequency. The Announcements Builder is a separate, newer tool that lets you create your own custom banners from scratch through a Content, Style, Audience, and Schedule flow, and now includes rule-based targeting.

Can I target a GoHighLevel announcement banner to only some sub-accounts?

Yes, as of the August 2026 update to the Announcements Builder. The Audience step now supports a rule builder where you choose a field such as Sub-account, Country, or User Role, an operator, and a value, and combine multiple rules with AND-within-a-group or OR-across-groups logic.

Does GoHighLevel say whether the new banner targeting is available on every plan?

HighLevel's changelog entry for the targeting update states it is available to all agencies, with no plan-tier restriction mentioned. It does not specify pricing or tier gating beyond that statement.

Why can't I find the Announcements Builder in GoHighLevel's help documentation?

HighLevel's current official help article on this topic (In-App Banner Management) only documents the older toggle-based system banner feature, not the custom Announcements Builder or its rule-based targeting. The documentation has not yet caught up to the changelog, so the Builder and its targeting rules are currently only described in HighLevel's own changelog entries.

We build your GoHighLevel account for you

CRM, pipelines, funnels, SMS and automation — configured for your business, not left for you to figure out.

• Setup (one-time)$850
• Ongoing (per month)$38.80

Get my free setup quote

No obligation quote · reply within 1 business day

This site is independently operated and is not officially affiliated with, endorsed by, or sponsored by HighLevel LLC. We do not receive referral commissions — this is our own flat-fee implementation service.