UNLEASH 2026
Campaigns live for 5 weeks · Google, Meta, LinkedIn, Microsoft · Data refreshed daily
Spend to date
£ ——
vs plan: ——
Registrations
——
this week: ——
Cost per registration
£ ——
trend: ——
Weeks remaining
——
event date: ——
1
These numbers come straight from the ad platforms every day, through the same data connection that already exists. There is no Data Studio in the middle, so the portal can show exactly what matters for events: spend against plan, registrations, and time to the event date.
Weekly registrations & cost per registration
Placeholder chart. Bars are weekly registrations, the line is cost per registration.
Spend by platform
Placeholder chart. All four platforms in one view, one source of truth.
This week at a glance
Weekly Report
Pick a week and the numbers and commentary for that week load together.
2
Commentary is written per week and stored against that week. Selecting a week shows the right words next to the right numbers, with nothing to match up by hand.
Week 5 numbers
| Platform | Spend | Impressions | Clicks | Registrations | Cost per reg |
|---|---|---|---|---|---|
| Meta | £ —— | —— | —— | —— | £ —— |
| £ —— | —— | —— | —— | £ —— | |
| £ —— | —— | —— | —— | £ —— | |
| Microsoft | £ —— | —— | —— | —— | £ —— |
Performance Comments · Week 5
Sample text. The real commentary is drafted by AI from the week's platform data and the team's own notes, then reviewed by the team before the client sees it.
Registrations picked up again this week after the audience changes made last week.
- The campaigns have been live 5 weeks and overall cost per registration continues to trend down.
- Meta remains the biggest driver of volume; LinkedIn is the most efficient on cost.
- Spend is tracking slightly ahead of plan, which is deliberate ahead of the early-bird deadline.
Saved. The client sees the updated wording immediately.
3
Anyone on the team can edit a commentary block right where the client will read it: click Edit, change the wording, save. Client logins never see the Edit buttons.
Completed Optimisations · Week 5
- Narrowed the LinkedIn audience to the two best-performing job functions.
- Refreshed the Meta creative with the three top ads from last week.
- Added the new speaker announcement to Google responsive search ads.
Saved. The client sees the updated wording immediately.
Action Points · Week 5
- Shift a small amount of budget from Microsoft to LinkedIn while efficiency holds.
- Brief new creative for the final-fortnight push.
- Confirm the early-bird deadline messaging with the client this week.
Saved. The client sees the updated wording immediately.
4
Past weeks stay exactly as they were written, so the report is also an archive. Anyone can look back at Week 2 and see the numbers and the commentary as they stood at the time.
Top Ads
The five best-performing ads for the selected week, pulled automatically from the platforms.
5
The actual creative comes straight from Meta and Google each week, with its numbers underneath, so the client sees the real ads running for their event. This works for image, video and search ads, and for the more visual Google formats (Demand Gen, Performance Max, YouTube).
ad creative
Meta
Ad name ——
Impressions——
Clicks——
Registrations——
video still
Meta
Ad name ——
Impressions——
Clicks——
Registrations——
ad creative
Google · Demand Gen
Ad name ——
Impressions——
Clicks——
Registrations——
ad creative
LinkedIn
Ad name ——
Impressions——
Clicks——
Registrations——
search ad text
Google · Search
Ad name ——
Impressions——
Clicks——
Registrations——
Pacing & Budget
Where spend sits against plan, and what is left to run before the event.
6
The portal knows the event date and the planned budget, so it can always show whether the campaigns are ahead of or behind plan in the run-up to the event.
Cumulative spend vs plan
Placeholder chart. Solid line is actual spend, dashed line is the plan, ending at the event date.
Budget by platform
| Platform | Planned | Spent | Remaining | Pace |
|---|---|---|---|---|
| Meta | £ —— | £ —— | £ —— | —— |
| £ —— | £ —— | £ —— | —— | |
| £ —— | £ —— | £ —— | —— | |
| Microsoft | £ —— | £ —— | £ —— | —— |
Optimisation Log internal only
Everything the team has changed, in one place, feeding the client-facing commentary.
7
This page exists only in the team view. It is the raw feed (the team's working notes) that the AI draws on when drafting the weekly commentary. The client-facing version of these entries is what appears, reviewed and edited, on the Weekly Report page.
| Date | Platform | Change | Logged by |
|---|---|---|---|
| —— | Audience narrowed to two job functions —— | —— | |
| —— | Meta | Creative refresh, three new ads live —— | —— |
| —— | Added speaker announcement to RSAs —— | —— | |
| —— | Microsoft | Budget trimmed, moved to LinkedIn —— | —— |
Internal Notes internal only
A scratchpad the client never sees, kept next to the report it relates to.
8
Anything the team wants to keep beside the report but away from the client lives here: context on the client relationship, things to watch, draft wording. Because visibility is decided by login, there is no risk of it leaking into the client view.
Type here. This block is editable in the wireframe, the same in-place editing as the commentary blocks.
A short plain-English summary of the week sits here, written for the client. It is the same commentary the team writes and approves on the Weekly Report page, so the overview always matches the detail.