Campaign Hierarchy is on by default in every Salesforce org that has Campaigns enabled. The setup work is in planning levels, exposing the right rollup fields, and getting Customizable Campaign Influence turned on if you want fair attribution.
- Expose the hierarchy fields
Object Manager, Campaign, Page Layouts. Add Total Members in Hierarchy, Total Opportunities in Hierarchy, Total Value Won Opportunities in Hierarchy, and Total Actual Cost in Hierarchy to the Campaign Statistics section. Hide the non-hierarchy versions on parent campaigns to avoid confusion.
- Plan the level structure
Pick the meaning of each level before building. A common pattern is Program at level one, Channel at level two, Campaign at level three, leaving room to add Wave and Segment later. Document the structure in the campaign description field so future admins do not invent their own scheme.
- Parent the campaigns
On each child campaign record, set Parent Campaign to point at the right ancestor. The hierarchy rollup recalculates within minutes. Bulk via Data Loader: prepare a CSV with Id and ParentId, run Update, verify counts on the parent campaigns.
- Enable Customizable Campaign Influence
Setup, Feature Settings, Marketing, Campaign Influence Settings. Turn on Customizable Campaign Influence to capture multi-touch attribution. Without it, every Opportunity attributes 100% to the single Primary Campaign Source, which understates multi-channel programs.
- Add the View Hierarchy link
On the Campaign Lightning record page, drop the Campaign Hierarchy related list onto the Related tab. This lets marketing users navigate up and down the tree without leaving the record. The right rail also shows hierarchy metrics as a Quick Glance card.
The lookup field that creates the hierarchy. Self-referencing on the Campaign object. Up to five levels deep; deeper assignments are rejected.
Org-wide setting that switches Opportunity attribution from single-source to multi-touch. Once on, you define influence models (First Touch, Last Touch, Even, custom) and Influence records replace Primary Source as the primary credit.
Standard fields that aggregate counts and amounts across descendants. Cannot be customized; you cannot add a custom hierarchy rollup field without flow or scheduled Apex.
Org-wide default for Campaigns: Private, Public Read Only, or Public Read/Write. Hierarchy does not propagate access; share each level explicitly if you go Private.
- Five-level cap is a hard limit. Plan the level meaning before building or you run out of room as the program structure evolves.
- Total Members in Hierarchy deduplicates by member, so the same Contact across two child campaigns counts once. Reports that sum individual campaign member counts will exceed this number.
- Parent Campaign reassignment is fast and irreversible without backup. Export ParentId values before bulk restructures.
- Cost rollup double-counts if you populate Actual Cost on both parent and child for the same spend. Park cost on one level only.
- Access to a parent campaign does not grant access to children. Each level shares independently under the org-wide Campaign sharing model.