Client Dashboard

⚙ What it needs

For each ad platform it tries the direct connection first, then Marketing Milk, then the platform in a browser. It never fills a gap with zeros or an old snapshot.

▶ How to run it

First setup for a client

1. Open a Codex chat, ideally inside the client's Codex project folder so everything for that client stays together, then type $client-dashboard and name the client.
2. Pick the cadence. It asks how often the client should get an update: every 2 weeks (14-day view), every 30 days, or Other with a number of days and a first send date. This is saved for the client, so it won't ask again.
3. Confirm the client's Slack channel. It searches Slack for the client's channel and asks "Is this the correct dedicated client channel?" It never guesses. If Slack isn't connected or no channel turns up, fix it and choose Retry, or choose Ignore Slack to move on.
4. Pick your check-in reminder. "How would you like to be reminded two days before the client dashboard is updated and sent?" Setup Slack Only, Setup Email Only, Both or No reminders. A Slack reminder lets you reply with work items and a personal note before the update goes out. An email reminder goes to you, not the client. It stays off until the recurring schedule is approved.
5. Your contact card, first time only. Your name, email and phone are saved on your computer and shown on every dashboard you publish.
6. Who gets the email. "What primary client email address should receive the dashboard update?" Give one address, or choose Do not email client if you only want the web page updated. Then add anyone else who should get it, or leave that blank. You're copied by default.
7. "What we're working on." Tell it the current projects in your own words, like a video shoot, a new offer or an audience refresh. It turns them into at least three short cards. No current projects? It uses standard cards instead, such as "Continuing to monitor Meta campaign and ad performance for ongoing efficiency and account health." You can also give it a personal note for the top of the page.
8. It pulls the data, builds a local draft, and asks you to check accuracy and presentation. Nothing is published or emailed until you approve.
   Finish your edits before you publish. Each push to Netlify uses deploy credits and API calls, so make every change to the local draft first. Once it's final, tell Codex to publish it via Netlify.
9. Approve and choose what happens. It shows the link, the exact To and Cc addresses and the next delivery date, then asks: Publish, send now, and schedule · Publish and send now only · Publish and schedule only · Keep as draft. If you scheduled it, the check-in reminder is scheduled with it and you'll see both under Scheduled in Codex.
10. Slack test message. With a Slack reminder, it posts one setup message in the channel so you can see it works:

The check-in, two days before a refresh

For 30-day and custom cadences you get a check-in before every refresh. For 2-week clients it's every other refresh (every 28 days). It posts once and doesn't chase you:

• Reply with 1–3 short items in the thread. They replace the "What we're working on" cards, dated that day.
• Add a note with %...%. It shows on the dashboard as "NOTE from [your first name]" for this report only (up to 600 characters). You can send a note alone, items alone, or both.
• No reply? Last cycle's cards and their date stay, and the note goes back to the default: "Hope you've been well, let me know if you have any questions."
• Only replies from you (or the client's saved Account Strategist) count. Anything unclear, it asks you before changing the page.

Every refresh after that

The scheduled run reads your check-in reply, pulls fresh numbers, rebuilds, publishes, confirms the page is live, checks you haven't already sent this report, and emails the client. The email opens with the dashboard link, lists the reporting period and a few source-backed highlights, includes "What we're working on" only when you updated it, and ends with a short note that the update is automated. If any step fails, it doesn't send, and it tells you which step failed so you can fix it.

i Good to know

• Client-facing tone. Wins come first, and fixes get short, constructive wording. Measurement limits are stated plainly, for example when a client has no CRM.
• Account went down? If an ad account is verified down with no replacement, the page shows a clear notice with your contact details. If a new account is already live, it shows a quiet note instead.
• Periods are exact: 30 days means 30 complete days, not a calendar month.
• Private stays private. Recipient lists, account IDs, Slack channel IDs and send history are kept outside the published page.
• Your note stays on the page. The personal note shows on the dashboard, not in the client email, unless you ask for it there.
• Not indexed. Each dashboard carries noindex tags, so search engines skip it. Anyone with the link can open it; Netlify password protection is available if a client needs it.