Pendo segment contains no visitors error: feature adoption drop for at-risk accounts not visible

TL;DR

An empty Pendo segment is a definition or identity problem until proven otherwise. Segments match visitors on metadata and activity, and one rule with the wrong operator, a renamed metadata field, or visitor IDs that stopped merging will empty a segment that looks correct on screen. Rebuild the segment logic piece by piece against known at-risk visitors, fix the rule or the identity feed that broke it, and only then trust the adoption numbers the segment feeds.

Pendo segment contains no visitors error: feature adoption drop for at-risk accounts not visible

Use this when

• A Pendo segment reports it contains no visitors while the underlying accounts are active
• The segment worked before a product release, metadata change, or Pendo configuration cleanup
• Feature adoption reports built on the segment show zero for at-risk accounts

Not for this skill when

• The feature genuinely launched to nobody yet because the rollout flag is off for those accounts
• Pendo data itself is delayed platform-wide, which the Pendo status and raw event views will show

Steps

1. Pick three specific visitors from at-risk accounts whom you know used the feature, using product or warehouse records, and find them in Pendo by visitor ID. Confirm Pendo recorded their feature activity at all, because if the events are missing this is a tagging or installation problem and no segment edit will fix it. Verify: the three known visitors and their feature activity are either found in Pendo or proven absent
2. Open the segment definition and list every rule, including account level and visitor level rules, the operators used, and any exclusion rules. Segments fail most often on an AND where an OR was intended, an exclusion that swallows the whole set, or a rule on a metadata field whose values changed format, such as a plan name gaining a prefix. Verify: every rule is listed and the suspect rule is identified
3. Test the rules one at a time. Clone the segment, strip it to a single broad rule that should match the known visitors, confirm they appear, then re-add rules one by one and watch the visitor count until the rule that empties the set reveals itself. Let the count guide you instead of re-reading the same definition repeatedly. Verify: the exact rule that empties the segment is proven by the count dropping to zero when it is added
4. Fix that rule at the right level. Correct a wrong operator or value in the segment, or, if the underlying metadata feed changed, fix the integration or visitor metadata update that populates the field, because editing the segment to match bad metadata spreads the error to every other segment using that field. Verify: the fixed segment returns the known visitors and a plausible total count
5. Check visitor identity merging. If your product moved to a new visitor ID scheme or the identify call changed, Pendo may hold the same people as two visitors, with history on one and metadata on the other, and segments match neither completely. Align the identify implementation with how accounts are keyed in the CRM before trusting any segment. Verify: visitor records for sampled people are consolidated or the ID scheme is confirmed consistent
6. Refresh the downstream adoption reporting for at-risk accounts, note the dates the segment was empty in the report itself, and add a simple watchdog that alerts when a production segment that normally holds hundreds of visitors reports zero, since an empty segment is a valid result Pendo will never flag for you. Verify: the watchdog alert exists and fires on a test segment set to an impossible rule

Why it happens

Pendo segments are live queries over visitor metadata and recorded activity. Any drift in what the product sends, a renamed plan value, a changed identify call, a new exclusion added during a cleanup, changes the matched set without changing the segment name or the report built on it. An empty result is a legitimate answer in Pendo, so the break announces itself only as a suspicious zero in a churn report downstream.

Compatibility: Pendo segments, visitor and account metadata, tagging, and identity calls, in current Pendo versions, with warehouse product data as ground truth.

Variants and edge cases

Pendo segment contains no visitors fix

['The direct phrasing. Known-visitor testing is the method, because a segment definition read in the abstract can look right while matching nobody.']

Pendo segment empty after metadata change

['The metadata variant. When a field source changes, audit every segment and guide target using that field, not only the one that emptied first.']

feature adoption zero Pendo segment at-risk accounts

['The reporting variant. Prove the feature events exist in Pendo before blaming the segment, or you will fix the wrong layer and still report zero.']

Edge cases to work through before you close the incident:

• Time based rules surprise people. A rule requiring activity in the last thirty days will empty a segment built for a quarterly feature on day thirty one, correctly.
• Account level segments and visitor level segments behave differently with shared rules. Confirm which level the report expects before rebuilding.
• If you clone and edit segments for testing, delete or clearly label the clones. Production segment lists fill with near duplicates and the next cleanup recreates this incident.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_mFSIWWHUFT9PtHu32gPGxg