Skip to main content
Three things have names that show up in the dashboard:
  1. The data source itself — the workspace-side label for a connected account, set when the source is connected. For example, the connection name shown in the Data sources list and the source picker.
  2. The data source’s channel name — the platform name shown next to widgets and in source labels. For file and database sources, this can be customized — see Alternative channel names.
  3. Campaign / ad set / ad names from the source platform — pulled on each refresh, used in widgets, breakdowns, and custom breakdowns.
This page covers what those names control and where to edit them. For the deeper mechanics of how naming feeds into custom breakdown extraction, see Custom breakdowns.

​
Where names come from

Renaming a campaign in the source platform is the only way to update its label in the dashboard. The data source pulls the current name on each refresh and overwrites the cached value.

​
Why naming matters for custom breakdowns

Custom breakdowns extract structured labels (such as objective, audience, region) out of campaign and ad names by splitting on a chosen separator and reading specific positions. For that to work, names need to follow a consistent structure across the campaigns the breakdown applies to. A recommended starting structure for campaign names: Example campaign name: 2025_01_Conversions_2040_all_0801_0830. For the full configuration mechanics (separators, segment positions, multi-source breakdowns), see Custom breakdowns. For prescriptive naming templates covering campaigns, ad sets, and ads, see Best practices: Naming conventions.

​
Propagating renames

Renaming a campaign in the source platform applies in the dashboard on the next refresh of that source. For platforms on a daily refresh cycle, expect the new name to appear within a day. To see it sooner, trigger a source refresh — see Refreshing data. If the new name doesn’t appear after a refresh, check whether the data source caches campaign metadata separately from performance data. Combined-cache data sources (such as CallRail) refresh reference data on a shorter cycle than performance rows; both have to refresh before the new name is fully reflected.

​
Troubleshooting

Trigger a source refresh. If the name still doesn’t update after refresh completes, the source may have a separate metadata cache — wait for the next scheduled cycle, or confirm the rename was saved on the source platform.
Inconsistent name structure is the most common cause. Audit recent campaigns for: missing segments, wrong separator, different segment order. See Custom breakdowns for how the extraction works.
Editing the data source name on the Data sources page changes only the display label. It does not affect historical data, cached metrics, or widget references. Saved widgets that select the source by ID continue to work.
Names are stored and rendered as-is. Custom breakdowns work on any character set as long as the separator is consistent.
Related: Best practices: Naming conventions · Custom breakdowns · Alternative channel names