One Company Has Several Product Workspaces: Reconcile Usage Before Outreach
Product usage from several workspaces should not become one company-level outreach trigger until the team can explain which commercial account owns each workspace, which users and events overlap, and which measures are comparable. Preserve the original workspace identifiers and lifecycle states. Aggregate only the evidence that belongs to the same decision, and hold unresolved relationships out of personalized claims.
The result is a defensible account scope: a record of whose activity supports the outreach and what remains unknown. It is not proof that a company intends to buy, and it does not establish that every user belongs to the same purchasing team.
Start with the workspace, not the company total
A company label can conceal several product environments. Before interpreting usage, inventory the workspaces that contributed to the account view. Keep the product workspace ID, the source system, the account reference supplied by that system, and the time of the extract. A display name is useful for reading; a stable identifier is necessary for joining and checking records.
Unify’s product usage integration documentation describes connecting identifiable users and product interactions to the data layer. That makes usage available for workflows. It does not establish that distinct product workspaces have already been reconciled to the correct commercial account. Treat that association as an explicit part of your implementation.
Distinguish the product’s workspace from your sales platform’s workspace. The first is an environment where customers or users interact with your product. The second is where your team manages prospecting and outreach. Mixing those meanings in a data dictionary can make an otherwise valid join look more authoritative than it is.
Retain the source record before creating a consolidated view. A growth operator should be able to move from the company-level conclusion back to the contributing workspace and user records without reconstructing the original export.
Establish the commercial account boundary
Ask which organization, contract, or independently managed business unit the proposed outreach concerns. The boundary should reflect your actual account model, not merely a shared email domain. A domain is evidence to evaluate alongside account IDs, billing relationships, verified CRM associations, and the team’s knowledge of the customer.
Keep the association evidence separate from the association decision. An imported reference says what the source supplied. A reviewed account mapping says what your team accepted. An unresolved mapping says neither. This distinction is especially useful when source systems disagree or one workspace has several plausible owners.
Unify’s object relationship documentation explains reference attributes and one-to-many or many-to-many relationships. Use those modeling concepts to represent genuine relationships rather than flattening every workspace into an undifferentiated company field. A relationship model can preserve complexity; it cannot determine the correct business relationship without evidence.
When supplying records programmatically, consult the Data API overview and record upsert reference. Review how stable source identifiers and references will be retained before changing an existing model. Do not use a successful write as proof that the account association is commercially correct.
Separate independent teams from duplicate and historical environments
Classify each workspace only to the extent supported by the source. Useful distinctions include currently active environments, retained historical environments, duplicate representations of the same environment, and environments that serve separate teams. Leave the classification unresolved when evidence is insufficient.
Historical activity can explain a relationship without supporting current outreach. A duplicate can inflate a total without representing additional usage. Separate teams can share a commercial parent while requiring different owners, timing, and messaging. These distinctions affect the meaning of the activity before any lead score is calculated.
Record why a workspace was included or excluded. Do not silently delete it from the analysis. The decision should be reversible when account ownership or source evidence changes, and the original record should remain traceable in your approved internal system.
For a broader introduction to the motion, use product usage data for outbound. The narrower task here is establishing the scope of the evidence that motion will consume.
Combine only compatible usage measures
Before adding activity across workspaces, define the event or measure, the observation window, the timezone, the source snapshot, and the deduplication key. Confirm that the same label has the same meaning in each environment. Counts produced under different definitions should remain separate until a compatible transformation is documented.
User counts deserve particular attention. Summing workspace-level users can count the same person more than once. A company-level distinct-user measure requires an identity rule that works across the included workspaces. If that rule is missing, describe the result as workspace-level counts rather than a distinct company audience.
Event counts need their own treatment. A replicated or replayed event should not automatically become another independent interaction. Preserve event identifiers where available, and document the handling of records without a reliable deduplication key. Do not imply that every event is a person, or that every person represents a separate buying opportunity.
For any reported proportion, define the population as the approved workspaces or users in the saved snapshot. State the numerator’s condition and the denominator’s eligible records. Keep unresolved associations visible as a separate count rather than silently treating them as inactive or excluding them without explanation. If the denominator is zero, report the measure as not applicable; do not display a conversion rate.
This is a measurement specification, not a benchmark. Set no performance expectation until your own reviewed data supports one.
Keep lifecycle and outreach decisions separate
An account-level usage view should preserve the lifecycle state of each contributing workspace. An active customer environment and an unresolved environment should not produce the same follow-up merely because they share a parent account. The person responsible for the commercial relationship should review whether the proposed action fits the account’s current situation.
Use the account view to explain the evidence, then decide whether outreach is appropriate. That decision should include account ownership, existing conversations, eligibility, and whether the message can accurately describe the relevant product activity. Product activity alone does not establish who holds purchasing responsibility.
The separate guide to finding the buying role behind product usage addresses that next problem. Keep role selection downstream of account reconciliation so that a well-researched contact is not approached with evidence from an unrelated team.
Unify’s engagement policies and sequence exclusions provide additional controls to review before activation. Correct usage scope does not override those controls or an account owner’s instructions.
Use a workspace-to-account reconciliation sheet
Create one row per source workspace and candidate commercial association. Repeat a workspace only when documenting distinct candidate relationships, and make that ambiguity explicit. The blank worksheet below is a review asset, not a set of observed results.
| Review field | What to record | Observed value or evidence |
|---|---|---|
| Source and workspace ID | Source system and stable product workspace identifier | |
| Commercial account | Stable account ID and the boundary being evaluated | |
| Association evidence | Reference, approved source, reviewer, and evidence location | |
| User identity scope | User identifiers and cross-workspace deduplication rule | |
| Usage scope | Event definition, window, timezone, and saved snapshot | |
| Workspace classification | Supported active, historical, duplicate, separate-team, or unresolved classification | |
| Lifecycle state | Source-backed state relevant to the outreach decision | |
| Aggregation decision | Included measures, exclusions, and reasons | |
| Unresolved relationships | Missing evidence, accountable owner, and next review | |
| Outreach decision | Approved account scope, conversation owner, and permitted next action |
Use references to evidence rather than copying unnecessary user activity into the sheet. Store the completed worksheet where the people responsible for the account can review it. A blank observation is an unfinished check, not an implicit approval.
When the same company appears in several systems, review the CRM synchronization conflict guide before deciding which system can update the commercial association. Reconciliation should not be undone by the next routine sync.
Make the workflow consume the reviewed scope
Once the scope is accepted, check which automation uses it. Inspect play triggers, the relevant actions, and play settings. Confirm that filters and downstream personalization reference the reviewed account or workspace attributes rather than an older aggregate.
Run a bounded, approved check before enabling broader outreach. Review the selected records, the reason each qualified, the owner, and the proposed message. Keep unresolved associations outside automatic claims about company-wide usage. If the workflow requires a total that cannot yet be supported, change the workflow or complete the reconciliation first.
The prioritize today’s accounts motion is useful once the inputs are trustworthy. Prioritization should preserve the distinction between an account worth reviewing and an account cleared for a specific message.
The Perplexity customer story describes a product-led outbound context that combines usage, firmographic information, and targeted engagement. It illustrates why account context matters. It does not demonstrate automatic resolution of multiple product workspaces, and its outcomes should not be transferred to this reconciliation method.
Review the mapping when the underlying relationship changes
Reconciliation is a maintained decision. Define which source changes require another review: a revised account reference, an ownership correction, a workspace consolidation, or a lifecycle change that affects the planned outreach. Record who can approve the updated boundary and how dependent workflows will be checked.
Preserve the prior decision and the new evidence internally. If an earlier message relied on an association that is no longer supported, review pending work before allowing it to continue. Correcting the data model without reviewing queued outreach leaves the operational problem unresolved.
The release criterion is practical: an account owner can identify the contributing workspaces, explain why their activity belongs together, reproduce the measure, and defend the next action. If one of those explanations is missing, the account scope still needs work.
Preserve the distinction between evidence and message
The final account view should explain what the evidence supports without automatically dictating a sales claim. Keep the reconciliation sheet available to whoever reviews the draft. If the message describes company-wide adoption, the reviewer needs company-wide evidence under the accepted boundary. If the evidence concerns only a particular workspace, the message should preserve that narrower scope. This review also gives the account owner a chance to identify an existing conversation or commercial arrangement that the usage data alone cannot explain.
Frequently asked questions
Should all workspaces with the same email domain be combined?
No. A shared domain is association evidence, but it does not establish a single commercial account or purchasing team. Preserve workspace IDs and review account references, lifecycle states, and unresolved relationships before aggregating usage.
Can workspace user counts be added to get company users?
Only when the measure and identity rules support that calculation. A person may appear in several workspaces. A distinct company-user count requires a cross-workspace deduplication rule, a defined observation window, and explicit treatment of unresolved identities.
Does connecting product usage to Unify reconcile every workspace automatically?
The documentation describes connecting product interactions and identities to Unify’s data layer. It does not establish automatic commercial reconciliation of every workspace. Define and verify the account relationships that your workflow will use.
What should happen when a workspace association is unresolved?
Keep the source record and uncertainty visible, assign a reviewer, and avoid using that workspace to support account-wide personalization. Resume the dependent decision only when the evidence supports the association or the workflow has been changed to exclude it explicitly.

