Setting Up Segmentation in a Continu Extend Account

Segmentation in Extend lives inside the Extend account itself, in the Segmentation area. The segmentation you build there controls what content the account’s users can see, what shows up on their Explore page, and what can be assigned to them. Every user in the account inherits the same segmentation. This guide covers how the model works and how to configure it.


The Extend segmentation model

In your internal Continu instance, Smart Segmentation is applied to content — each piece of content carries its own audience rules and users see only what their attributes match.

In Extend, segmentation moves up one level. It lives inside the Extend account, in the Segmentation area. The single segmentation you build there controls three things for every user in that account:

  • Content visibility — what the account’s users can access at all
  • Explore — what shows up on their Explore page
  • Assignment — what can be assigned to them, manually or via Automation

Every user inside the Extend account inherits this same segmentation. Users don’t carry their own segmentation rules — they get the account’s.

The implication: an Extend account is one audience scope. If you need different scopes (different content, different Explore experience, different assignable pool), you build separate Extend accounts.


When to use one Extend account vs. multiple

The rule of thumb: one Extend account per audience scope.

Scenario How to set it up
One partner program, all partners see the same content One Extend account
Partner program with Gold / Silver / Bronze tiers, each tier sees different content Three Extend accounts
Customer education for a single product, all customers see the same content One Extend account
Customer education across two product lines, customers see only their product’s content Two Extend accounts
Multi-brand parent company, each brand needs its own audience One Extend account per brand
Mixed audiences (partners + customers + vendors) Separate Extend account per audience type

If you find yourself wanting to give different users in the same Extend account different content or Explore experiences, that’s the signal to build a second Extend account, not to try to layer rules inside the existing one.


Configuring the segmentation

Inside the Extend account, open the Segmentation area. The segmentation is configured with the standard Continu user attribute fields:

  • Location — top-level region, country, or office (e.g., Los Angeles)
  • Department — the department this Extend account corresponds to (e.g., Sales)
  • Grade — leave blank if not applicable
  • Level — leave blank if not applicable
  • Teams — search and select Team values
  • Groups — search and select Group values

Populate the fields that define the audience scope. Leave any field blank that doesn’t apply — every populated field narrows the segmentation. Save when done.

Single criterion

If the segmentation is defined by one attribute, populate just that field. Example: an Extend account for California sales partners might have Location set to Los Angeles and Department set to Sales — everything else blank.

Multiple criteria

When you combine criteria, all of them must match for a user to be included — Location AND Department AND Teams. Use this when the cohort needs a tighter definition. Watch out for over-narrowing; a segmentation no one matches is the most common cause of “users can’t see anything” tickets.

Saving and verifying

Save the segmentation. Add a test user to the Extend account, sign in as that user, and confirm:

  • The content you expect to be visible is visible
  • Explore shows the right items for that audience
  • Assignments fire for the right audience

If anything is off, adjust the segmentation on the Extend account — not on individual content pieces or users.


What the segmentation controls

The segmentation on an Extend account controls three things, all in the same direction (the segmentation = the audience for the entire account):

Content visibility. Users in the Extend account only see content scoped to the segmentation. Content outside the segmentation isn’t accessible to them, even via direct link.

Explore. The Explore page for users in the account is filtered by the segmentation. Users browse only what their account’s segmentation allows.

Assignment. When you assign content (manually or through an Automation) inside an Extend account, the segmentation is what determines who’s eligible. Automations targeting the account fire for the users the segmentation matches.

Reporting also follows the same boundary — see the next section.


How users inherit the segmentation

The lifecycle of a user in an Extend account:

  1. Admin creates the Extend account
  2. Admin configures the segmentation on the account
  3. Admin adds users to the account (manual invite or bulk CSV upload)
  4. Each user automatically inherits the account’s segmentation
  5. If the segmentation changes later, the change applies to every user in the account
  6. If a user is moved to a different Extend account, they inherit the new account’s segmentation

Users don’t carry segmentation memberships explicitly. The Extend account is the source of truth for what each of its users sees and gets.


Reporting on an Extend account

Reporting on Extend works at two scopes:

Report by Extend account. The default when you’re inside an Extend account. Shows every learner, completion, engagement metric, and assignment outcome for the account’s users — the natural roll-up for “how is this customer/partner doing overall.”

Report scoped to the segmentation. Same data, but viewed through the lens of the segmentation. Useful when the question is about the segmented cohort itself rather than the raw user list.

Both views live in the Reports area inside the Extend account.

For cross-Extend-account roll-ups (executive views like “completion across all our Extend accounts”), use the Continu admin’s cross-portal reporting.


Common pitfalls

Pitfall Symptom Fix
Trying to split a single Extend account into multiple audience scopes Different users in the same account see the same content even though they shouldn’t Build separate Extend accounts for separate scopes. One Extend account = one audience scope.
Editing user-level attributes to “fix” what a user sees The change has no effect because content visibility is account-level Adjust the segmentation on the Extend account, not on the user
Over-narrow segmentation Users get added to the account but see nothing in Explore Audit the segmentation criteria — every populated field narrows the scope. Loosen any field that’s too tight.
Co-mingling unrelated populations in one Extend account Reports leak across populations; users see each other’s progress in shared views Use separate Extend accounts when populations should be isolated
Forgetting to save the segmentation New Extend account behaves unpredictably until segmentation is saved After configuring, save explicitly. Verify with a test user before adding the full cohort.
Confusing internal-Continu Smart Segmentation with Extend segmentation Documentation describes per-content audience tabs — which doesn’t apply to Extend Internal segmentation is per-content. Extend segmentation is per-account and controls content visibility, Explore, and assignment for everyone in the account.

Quick reference

Task Where to do it
Configure segmentation for an Extend account Inside the Extend account → Segmentation area
Change the audience scope for all users in the account Edit the Extend account’s segmentation; every user updates automatically
Need a different scope for some users Create a new Extend account with the different segmentation
Add users who should inherit the segmentation Inside the Extend account → Users → invite or bulk upload
Assign content to the account’s audience Assignment flow → target the Extend account
Run a report at account level Inside the Extend account → Reports
Run a report scoped to the segmentation Inside the Extend account → Reports → scope to segmentation
Cross-account roll-up Continu admin → cross-portal reporting

See Also

Was this article helpful?
0 out of 0 found this helpful