Unique/distinct count of clients with multiple responses | Experience Community
Skip to main content
Question

Unique/distinct count of clients with multiple responses

  • May 13, 2026
  • 2 replies
  • 31 views

Forum|alt.badge.img+1

I’m facing an issue with getting a distinct count of clients in my dashboard and wanted to check if there’s a workaround.

In my setup, “Client” is an embedded data field (e.g., ABC, DEF, GHI). Each client has multiple contacts/respondents. For example:

  • ABC → 12 contacts, 6 responses
  • DEF → 10 contacts, 5 responses
  • GHI → 6 contacts, 2 responses

Currently, the dashboard shows the total number of responses (6 + 5 + 2 = 13), which is expected. However, what I need is a way to show the number of distinct clients that have at least one response (in this case, 3 clients: ABC, DEF, GHI).

The data is managed through XM Directory, and the survey is already live with responses coming in.

Is there any workaround to achieve this—perhaps using a custom metric, table, or by counting distinct embedded data values where responses exist?

Any guidance would be really helpful. Thanks in advance!

2 replies

Forum|alt.badge.img+1
  • Level 1 ●
  • May 13, 2026

You can do this by using Quotas - Create a simple quota for every client that you have.

For ex. lets create quota for client ABC - condition in quota will be if Client ED is equal to ABC.

next for DEF - condition in quota will be if Client ED is equal to DEF….create this for every unique client

Now in survey flow you can program this condition as a branch logic to store unique client name
ex. create a branch logic as if quota for ABC is equal to 1 - then store ABC in Client_Store embedded data. Similarly create next branch logic for DEF - if quota for DEF is equal to 1 - then store DEF in Client_Store embedded data. create this for every unique client in survey flow.

Result will be Client_Store will only store client name only once if that client has hit one response.

This ED you can use in the dashboard.


Forum|alt.badge.img+1
  • Author
  • Level 1 ●
  • May 13, 2026

You can do this by using Quotas - Create a simple quota for every client that you have.

For ex. lets create quota for client ABC - condition in quota will be if Client ED is equal to ABC.

next for DEF - condition in quota will be if Client ED is equal to DEF….create this for every unique client

Now in survey flow you can program this condition as a branch logic to store unique client name
ex. create a branch logic as if quota for ABC is equal to 1 - then store ABC in Client_Store embedded data. Similarly create next branch logic for DEF - if quota for DEF is equal to 1 - then store DEF in Client_Store embedded data. create this for every unique client in survey flow.

Result will be Client_Store will only store client name only once if that client has hit one response.

This ED you can use in the dashboard.

Hey Thanks for this, I would really require a step by step guidance if you could provide me I would be very grateful next what I did was staging the survey data into imported data set with same set of dimensions with lowest granularity being Customer and store the aggregated count. Included this as one of the source. When I add it as source, using data modeller where I did left outer join with my survey. Then I should I would be able to get the count in the dashboard but instead it treated as “new response” so the dashboard increased the actual response and also the count of response is there any way to fix it ?