What problem are you trying to solve?
The Gainsight Community Salesforce integration currently maps community members to Salesforce accounts, but only at the parent account level. For organizations that use parent-child account hierarchies in Salesforce (which is extremely common in enterprise environments), this means the majority of community members are not being accurately mapped to their correct account. Any user associated with a child account is either mapped to the wrong account or not mapped at all.
For companies with complex account structures, child accounts often represent the bulk of their customer base. The integration working for parent-only accounts effectively means the integration is not working for most users.
How are you currently working around it?
Currently there is no clean workaround. Options being explored include configuring SSO field mapping through a third-party identity provider (Auth0) to manually surface Salesforce IDs, or building a custom connector to call the Salesforce API at login to retrieve account data by email. Both require significant custom development and introduce complexity and security considerations that would not be necessary if the integration worked as expected out of the box.
What would the ideal solution look like?
The Salesforce integration should be updated to traverse the full account hierarchy when mapping community members. Specifically:
When a community member's email or contact record is matched in Salesforce, the integration should identify and store the associated child account ID (not just the parent account ID) so that the member is mapped to the correct account at every level of the hierarchy.
Ideally, administrators would have the option to configure how the hierarchy is handled, for example mapping to the child account by default, or selecting whether to surface child account ID, parent account ID, or both.
Why does this matter?
Accurate account mapping in the community is foundational to almost everything else: reporting, segmentation, personalization, success tracking, and integrations with tools like Pendo, Gainsight CS, and other platforms that rely on account-level identification. When community members are mapped to the wrong account or not mapped at all, every downstream system that depends on that data is affected.
This is not just a reporting inconvenience. For teams using the community as part of a broader digital customer success strategy, incorrect account mapping means you cannot reliably attribute community engagement to the right customer, cannot personalize experiences at the account level, and cannot connect community activity to product usage or health scores.
Who else is impacted?
Any Gainsight Community customer whose Salesforce instance uses parent-child account relationships, which represents a significant portion of enterprise customers. This is likely a silent pain point for many organizations who may not have investigated why their member-to-account mapping appears incomplete.