Marketing for multi-site leisure operators
A leisure group rarely runs one campaign. It runs dozens at once: a learn-to-swim intake at one centre, a membership drive at another, a school-holiday program across the region. Keeping all of that on brand and on time is the daily job, and a static spreadsheet does not cut it.
Cohiva Campaign gives HQ one view across calendar, kanban, and gantt, then a multi-location model to push a campaign out. HQ activates a parent campaign to specific venues, creating one child instance per location, and locks the fields a venue must not change, such as brand assets and the key message.
The trigger engine connects marketing to operations. A threshold trigger can launch or escalate a campaign in response to a live metric, a date trigger can fire on a fixed schedule, and a test mode logs what would happen as a safe dry-run before anything goes live.
The compliance gate still applies. Go-live is enforced at the API for every location, and every decision lands in an append-only audit across the network, so a group can see exactly what ran where and how it was approved.
The combination of multi-location control and live-data triggers fits how a leisure group actually operates. HQ pushes a learn-to-swim intake or a membership drive to the venues that should run it, locks the brand assets and key message, and lets each centre adapt the local detail. A threshold trigger can then escalate a campaign when a venue's numbers fall below a target, and a date trigger can fire a school-holiday program on schedule, with a test mode to confirm the rule first. Each venue still clears the same gate, so reacting quickly to local conditions does not mean letting an unchecked campaign slip out.
Start a free trial of Cohiva Campaign to put a non-bypassable go-live gate behind every launch.
Frequently asked questions
- How does a leisure group keep venues on brand?
- HQ activates a campaign to each venue and locks the fields a venue must not change, such as brand assets and the key message. A locked field edit returns HTTP 403 FIELD_LOCKED.
- Can a campaign react to operational data?
- Yes. The live-data trigger engine can launch or escalate a campaign on a threshold, a date, an application event, or a webhook, with a non-executing test mode for a safe dry-run.
- Does Campaign work with the rest of the Cohiva suite?
- Yes. Campaign runs on the Cohiva suite with single sign-on through Cohiva Central and integrations with sibling products.
- Can HQ see activity across every venue?
- Yes. HQ sees everything across locations, while each venue sees only its own campaigns, all under one append-only audit.
- Is each operator's data isolated?
- Yes. Campaign runs database-per-tenant, so each operator's data sits in its own database.
Related
Put a non-bypassable gate behind every launch
Cohiva Campaign rejects an unchecked go-live at the API and keeps an append-only audit. Try it free.
Start free trial