Standalone campaigns are not tier pages

This article covers GiveCampus campaign administration. Available controls can vary between the classic and redesigned campaign interfaces.

A tier landing page is created under a parent campaign and uses its fundraising context. The normal tier creation/clone workflow does not convert a standalone campaign into a tier and back. For a seasonal parent, create a suitable tier page and reuse content; keep the original standalone campaign for evergreen use. Linking the original campaign does not automatically roll its gifts into the seasonal parent. Route new gifts through the correct checkout and avoid duplicating historical gifts.

Standalone campaign cannot simply become a tier

The tier editor creates a new TieredCampaign child under its parent Project; it does not convert an existing standalone campaign with its gift history. Plan the parent/child structure from the start if it is required later, or keep the independent campaign and link it from a broader page. Existing gift/total/URL migration requires separate review; moving a display card does not migrate the campaign.

Independent campaigns are not existing tier children

Tier 2 and Tier 3 pages belong to one parent campaign project. The tier editor creates a child within that project or clones another tier page from the same project. It does not offer a temporary adoption of an independent campaign and its existing history as a Tier 3 page. For a Giving Tuesday Athletics hierarchy, create the sport child pages under the intended parent campaign. This does not automatically move historical gifts from separate sport campaigns.