This article provides guidance for when you are creating a visitor segment using the metadata fields "Account ID" or "Account IDs" and need clarification on the difference.
Environment: People > Segments (Web, Mobile)
Issue
Typically, you can create a segment to review analytics for an account. If you create a segment based on a certain account, it's possible for visitors associated with other accounts to display in the metrics.
For example, if you apply a segment with the rule "Account IDs contains Test Account 4" to a visitor report:
You might see results with Account IDs that differ from the Account ID you specified in the segment:
Diagnosis
Pendo has two different, yet very similarly named, metadata fields: Account IDs at the visitor level and Account ID at the account level. If you see results from multiple accounts but only want to see results from one, you might need to use Account ID in your segment instead of Account IDs.
Despite having similar names, each field yields different results. It's important to understand when to use each field in a segment and what to expect from the results.
Metadata field | Definition |
Account ID |
The Account ID value that a visitor was assigned at the time an event occurred. This is always a singular value. When selecting this field in the segment builder, it's always in the Account Data section and has a double-headed icon. |
Account IDs |
A list of all Account ID values a visitor has ever been associated with. This could be a singular value or a list of values. When selecting this field, it is always in the Visitor Data section and has a single head icon. |
Solution
To ensure you're seeing the expected results, make sure you're using the appropriate metadata field.
- If you use a segment with Account ID for a report, Pendo only displays the events for the visitor that were associated with that specific Account ID.
- If you use a segment with Account IDs for a report, Pendo displays the events for the visitor for every account they have ever been associated with, as long as they were associated with the Account ID in your segment at some point in time.
In the scenario mentioned in the Issue section above, Account IDs was used for the segment rule. The visitor, Creed.Bratton, generated events while associated with Test Account 4 at one point in time. You can confirm this by verifying the account is listed on the Visitor Details page:
This means this visitor is a match for the segment, and Pendo will return all events that Creed.Bratton has generated across any account, even if it’s not Test Account 4.
If you only wanted to see the events Creed.Bratton generated while associated with Test Account 4, you would need to switch the segment rule to “Account ID is equal to Test Account 4".
For more information about metadata and segments, see our articles on Visitor and account metadata and Segments.