Multi-location campaign management

Running marketing across many sites means balancing one brand against many local markets. Cohiva Campaign handles this with a clear HQ and location model. HQ creates a campaign and activates it to specific locations, and each activation creates one child instance per location, so a venue gets its own working copy rather than editing the shared original.

Control is set with field locks. A field-lock configuration decides which fields a location must not change, such as brand assets and the key message, while the fields HQ leaves open stay editable so a location can adapt to its own market. This keeps the brand consistent where it matters and flexible where it should be.

The locks are enforced, not advisory. A locked field edited at a location returns HTTP 403 FIELD_LOCKED, so a local change to something HQ has fixed is rejected rather than quietly accepted. Visibility follows the same logic: HQ sees everything across the network, and each location sees only its own campaigns.

Local marketing has its own planning surface. The Location Area Marketing hub adds per-location targets, directories, and plans, so a location is not only executing a head-office campaign but also managing its own area marketing within the boundaries HQ has set.

Each location instance still passes the same go-live gate, so local execution stays on brand and on record across the whole network.

The model scales because the control is set once and enforced everywhere. HQ decides which fields are fixed and which are open, activates the campaign to the locations that should run it, and the API holds that decision for every child instance. A franchisee adapts the venue, the dates, and the local call to action, while the brand assets, the key message, and the compliance requirements stay locked. That removes the need for HQ to review every local edit by hand, yet HQ keeps a single view of what ran where, with each location's go-live recorded in the same append-only audit. Start a free trial of Cohiva Campaign to put a non-bypassable go-live gate behind every launch.