CONTENT
  thinking about it, please hold on..

Attributes and Account Hierarchy

Where Should You Bring in Contract Value (and other useful attributes)?

Usage data in Totango comes in at the lowest account level. For multiproduct versions, usage data comes in at the product account level. For most cases, we insist that the account attributes (i.e. contract value, create date, contract renewal date, etc.) come in at the lowest account branch as well. In this case, when you look at a parent account, you will be able to see not only the health composition, but also how much revenue is potentially at risk. For use cases where the parent is in charge of the contract value, you will only see the health composition at the parent level and not the revenue composition. In either case, we require that all attributes come in at the same level the contract value comes in.

Account Hierarchy (simple)

Mac International oversees three departments: Support, Sales and Marketing. Each department is its own account with its own incoming customer usage data. In this example, contract data comes in at the child level.

The Support Department receives customer usage data that places it in good health. It has a contract value of $8.0K.

If you take a look at the parent account, you can see the aggregated data from the Marketing, Support and Sales departments. In this case, the account profile displays the health of its children - as well as how much money is at risk.

If the contract value was passed at this level, you would not see the amount of money with its corresponding health. You would just see how many accounts are in good, average or poor health.

Multiproduct (simple)

X Solutions is a company that licenses two products: “Billing and Invoice” and “Digital Marketing”. X solutions is the parent account of two product accounts; each with their own incoming customer usage data. In this example, contract data comes in at the product account level.

The product account “X Solutions 1_Billing and Invoice” receives customer usage data that places it in good health. It has a contract value of $10.0K.

If you take a look at the parent account, you can see the aggregated data from the two product accounts. In this case, the account profile displays the health of its children - as well as how much money is at risk.

Multiproduct in Account Hierarchy (complex):

Cloudrumba is a giant conglomerate that oversees 65 departments in different countries and licenses 9 different products among its departments.

The Sales Department owns 7 products, of which you can see the product account here for Sales Cloud. Contract value comes in at the product account, as well as other attributes (like Renewal date, Status and Success Manager).

When you look at this account’s parent, you can see the aggregate data for its product accounts, which includes the contract value composition in the health score. If the contract value came in at this level, you would only see the health composition, and not how much money is potentially at risk. Since contract value comes in at the product account level, you will have to go into the product account to see account attributes.

The Cloudrumba account profile shows a snapshot of its children’s aggregated data. You can see the composition of each account’s health, as well as how much money is potentially at risk.

Have more questions? Submit a request

Comments

Follow
Powered by Zendesk