The Campaign Clock
The event already has a date. The campaign needs a clock.
A live event has a fixed date. Attention has a window. The Campaign Clock shows how a campaign usually changes as the date approaches, so the final week is not the first real campaign.
The stages
-
Before announcement
The event is confirmed but not public. The brief, the ticket path, the artwork, the accounts, and the budget get sorted before anyone sees anything.
- RichLife
- Reviews the market, the room, the date, the ticket path, and the accounts. Proposes the scope in writing.
- Client approves
- Confirms event facts, artwork rights, budget, and access.
- What is read
- Lead time, account and tracking status, current position.
- Depends on
- Announcement timing, on-sale timing, and how much lead time the event actually has.
-
Announcement
The event goes public with one clear message: who, where, when, and how to buy.
- RichLife
- Launches the announcement phase with approved creative, copy, links, and tracking.
- Client approves
- Approves the announcement creative and posts on owned accounts where scoped.
- What is read
- Delivery, early click-through, landing-page views.
- Depends on
- Whether the on-sale happens with the announcement or later, and whether the artwork is ready.
-
Initial audience build
The campaign reaches the local market and starts building engager, viewer, and visitor audiences for later phases.
- RichLife
- Runs the launch audiences, watches response, and adjusts within scope.
- Client approves
- Shares early ticket signals if available.
- What is read
- Reach, frequency, audience response by segment.
- Depends on
- Market size, audience availability, and the media budget.
-
Creative rotation
The audience has seen the announcement. New hooks, formats, and angles keep the event readable instead of repetitive.
- RichLife
- Rotates creative variants and captions. Retires what is not responding.
- Client approves
- Approves new variants.
- What is read
- Creative response, frequency, click-through by variant.
- Depends on
- How many variants exist and how the first ones performed.
-
Reminder phase
People who noticed but did not act get a reason to come back: date, lineup, price, or the ticket action itself.
- RichLife
- Runs reminder creative to warm audiences.
- Client approves
- Confirms accurate details for every reminder.
- What is read
- Return visits, landing-page views, engagement on reminders.
- Depends on
- Ticket pace and whether the event details have changed.
-
Retargeting
Where the accounts and tracking allow it, the campaign follows up with people who engaged or visited the ticket page and left.
- RichLife
- Builds and runs retargeting audiences that are actually available.
- Client approves
- Approves spend allocation to follow-up.
- What is read
- Retargeting audience size, response, attributed conversions where tracking exists.
- Depends on
- Pixel or tracking availability, privacy settings, audience size, and platform eligibility.
-
Final-week pressure
The window is closing. Urgency has to be accurate: real dates, real availability, real ticket action.
- RichLife
- Concentrates the approved final-push creative and budget on the audiences most likely to act.
- Client approves
- Approves the final-push message and any spend change. Confirms availability claims are true.
- What is read
- Response to final-push creative, frequency, remaining budget.
- Depends on
- Sales pace, remaining budget, and whether more spend is justified.
-
Event day
Day-of messaging covers doors, set times, directions, and last availability. Then the window closes.
- RichLife
- Runs day-of reminders where scoped and pauses spend at the agreed time.
- Client approves
- Confirms day-of details.
- What is read
- Day-of clicks and landing-page views.
- Depends on
- Whether day-of sales are possible on the ticketing platform.
-
Post-run review
The run is read before it is repeated: delivery, response, ticket-path performance, attribution limits, and what the next event should change.
- RichLife
- Delivers the read and practical next-event recommendations.
- Client approves
- Shares the actual outcome if they choose to. Decides the next plan.
- What is read
- Everything the platform and the tracking can show, with attribution limits stated.
- Depends on
- Reporting access and whether the operator shares ticket totals.
This clock shows how a campaign usually changes as the date approaches. It is not a schedule and not a formula. Timing depends on event type, market, venue, artist, existing demand, announcement timing, on-sale timing, ticket price, capacity, creative, budget, account history, tracking availability, and sales pace. There is no countdown here because no public event is attached to it.
Why there is no formula
The campaign should move before the clock runs out.
Two events with the same date can need completely different clocks. A weekly club night, a touring headliner, a comedy run, and a branded launch have different demand, different lead time, and different ticket paths. The clock is built per event after the brief.
Statements like launch exactly a set number of days out, spend a fixed share in the final week, or retarget every visitor are not how this works. Retargeting depends on tracking and platform eligibility. Spend follows sales pace and the approved budget. Launch follows the announcement and the on-sale.
Timing depends on
- Event type
- Market
- Venue
- Artist
- Existing demand
- Announcement timing
- On-sale timing
- Ticket price
- Capacity
- Creative
- Budget
- Account history
- Tracking availability
- Sales pace
Start a campaign
Build the clock around your event.
The brief asks for the date, the market, the room, the ticket path, the current position, and the budget picture. That is what the clock is built from.