Client Dashboards
Client link
Access
Setting a new password replaces the old one immediately — anyone using the old link+password combo is locked out until you share the new one. Staff signed in to the Hub always preview without a password.
Data sources
+ Register a source
Coupler lands each dataset in the client schema (e.g. securitize.meta_campaign_performance) with contract columns
(date, campaign_name, spend, impressions, clicks, conversions, conversion_value — remap via column_map in SQL if Coupler names differ).
Registered sources federate on the hourly sweep, or hit Sync now. Runbook: docs/client-dashboards.md.
Needs mapping
Campaigns whose name didn't parse to a tactic. Assign a tactic (+ audience) — takes effect immediately.
Campaign labels
Nickname replaces the raw campaign name on the client page. Objective is campaign-level and drives the conversion framing. Save appears on rows with unsaved changes.
Plan targets
Leave Tactic BLANK on the rows that should drive pacing — the client dash reads only blank-tactic rows; tactic rows are optional detail on top. Channel must exactly match the data feed's name (pick from the dropdown) or actual spend won't join. Switching month loads that month — Save all after editing.
Annotations
Shown on the client page against the matching dates (and channel tab, if set) — launches, pauses, tracking changes, anything that explains a bump or dip.