Add Company Revenue Data to Canny
Associate users with companies and supply company monthlySpend, or map a supported CRM revenue field. Establish one billing period and account ID convention before sending data.
Before you start: Have the Canny Identify SDK installed and the trusted user/company information available. Review visibility before passing sensitive revenue into a browser-side integration.
Worked example: Northwind pays 2,000 per month and has three users. Each user should reference the same Northwind company ID; three contacts should not become three revenue-bearing companies.
Step-by-step guide
Normalize the source value
Choose recurring monthly spend in one documented currency convention. Do not pass annual contract value into monthlySpend without converting the period.
Use stable company identity
Use your persistent account ID for company id. Keep the company name as a display value rather than the identity key.
Pass company data
After loading the Identify SDK, identify the current signed-in user with a companies array. The example uses illustrative values and no secret API key.
Canny('identify', {
appID: 'YOUR_APP_ID',
user: {
id: 'user-42',
name: 'Example Reviewer',
email: 'reviewer@example.com',
companies: [{
id: 'account-northwind',
name: 'Northwind',
monthlySpend: 2000
}]
}
});Inspect the account association
Open the user in Canny and verify the company and revenue. Repeat with a second person at the same company to check identity consistency.
Check the planning interpretation
Review the revenue context on actual feedback. Keep recurring spend separate from potential new opportunity revenue and from a forecast of feature impact.
Common mistakes
Multiplying one account by its contacts
All contacts from one account should use the same company identity. Duplicate companies can distort the revenue context.
Sources and verification
Based on product documentation checked on 2026-11-04. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.