How does Hive9 calculate roll-up across the hierarchy?

Short Description Hive9 rolls values up the Plan → Campaign → Program → Tactic → Line Item hierarchy automatically. This article explains how roll-up applies to costs, performance, and custom attributes.

What this article answers

What rolls up and what doesn't.
The role of each hierarchy level in a roll-up.
How to interpret roll-up values you see on grids.

The hierarchy

Hive9's planning hierarchy has five levels:

Plan (highest)
Campaign
Program
Tactic
Line Item (attached to Tactic)

Values entered at lower levels roll up to higher levels. Most numeric values — Planned Cost, Actual Cost, Performance metrics — roll up automatically without action from the user.

What rolls up

Numeric values that roll up:

Planned Cost
Actual Cost (where applicable)
Performance metrics (Responses, MQLs, SQLs, Closed Deals, Pipeline, etc., depending on your instance)
Budget allocations and consumption

Custom attributes that roll up:

Many custom attributes are configured to roll up from lower levels to higher levels — you'll see them populated automatically on parent records based on child entries.

What doesn't roll up

Free-text attributes (descriptions, notes) — these stay at the level they're entered.
Approval status — each level has its own approval state.
Status (Active, Draft, In Approval) — set per object, not aggregated.
Percentage-based custom goals — these are not totaled or averaged across children (percentages aren't additive).

How roll-up looks in the UI

On the Plan Grid, you'll see roll-up columns showing aggregated values for parent rows. A Plan row's Planned Cost equals the sum of its Campaigns' Planned Costs, which equals the sum of their Programs' costs, and so on.

[SCREENSHOT NEEDED — Plan Grid with roll-up columns visible at each level]

If a Plan's Planned Cost doesn't match the sum of its children, that usually indicates one of:

A child object is in Draft status and excluded from a filtered roll-up.
A custom attribute roll-up rule is configured to exclude certain values.
A roll-up cache hasn't refreshed yet (refresh the page).

Multi-select attribute roll-up

When you use a multi-select custom attribute on a Tactic, you can assign proportions of Cost and Performance (CVR) per selected value:

Default: equally divided across selected values.
You can manually adjust the proportions; totals must equal 100% per dimension.
Cost and CVR proportions can be assigned independently — for example, US gets 50% of Cost but 75% of CVR.

This proportional split flows into roll-ups, so a multi-region Tactic's costs and performance appear correctly when aggregating by region.

Common questions

Can I edit a roll-up value directly on a parent? No — parent values are computed from children. Edit the child values; the parent recalculates.

Why is my Plan's Planned Cost showing as zero? Most often because the children haven't been populated with Planned Costs yet, or because they're in a status excluded from your current filter.

Does roll-up include Line Items or just Tactics? Line Item totals roll up to their parent Tactic via the Line Item's allocation. The Tactic's total (planned vs. line items) is governed by your instance's Prevent negative Sys_Gen_Balance setting.