Skip to main content
Data source names appear everywhere in Adriel: the widget data source picker, dashboard filters, teamspace settings, the connections list, and the Ads Table. A workspace with 5 connected sources can get away with default names — a workspace with 50 or 500 sources can’t. Consistent, descriptive naming pays off every time someone builds a widget, sets up a filter, or scopes a teamspace.

​
When it matters most

  • Agency workspaces managing many clients from one workspace.
  • Multi-brand accounts with separate ad accounts per brand or product line.
  • Multi-market accounts running the same channel across many countries or regions.
  • Any workspace where the same channel (Meta, Google, TikTok) has more than one connected account.
If a workspace only has one Meta account, one Google account, and one GA4 property, default names are usually fine.

​
Set the display name at connection time

When connecting a data source, most connectors let you set a custom display name at the last step of the connection flow. This is the name that appears everywhere in Adriel — not the underlying account name from the platform. Set it deliberately at connection time rather than accepting the default. For sources that don’t allow custom names (some search and analytics platforms), the display name is derived from the platform’s own account name. Rename at the platform end when possible. A three-part naming pattern that scales well:
Examples:
  • Meta – Client A – US
  • Meta – Client A – EU
  • Google Ads – Client A – Brand
  • Google Ads – Client A – Performance
  • TikTok – ClientCo – APAC
  • GA4 – Client A
Choose a separator that doesn’t appear inside any of the parts — em-dash (—), en-dash (–), or double-pipe (||) work well. Avoid single hyphens (-) if client or campaign names contain hyphens themselves.

​
Consistency is more valuable than perfection

The exact convention matters less than using the same one everywhere. Once the workspace has 20 data sources, the difference between:
  • Meta Ads – Client A
  • Meta Client A
  • Facebook Client A US
  • client_a_meta
…is enough friction to slow down every dashboard build. Pick a convention, document it internally, and hold to it.

​
Naming for teamspace settings

If the workspace uses Teamspace settings to scope which data sources are available in each teamspace, naming helps a lot:
  • Include the client or brand name in the data source name so admins picking data sources for a Client A teamspace can quickly identify every relevant source.
  • Sort matters: names are sorted alphabetically in the picker, so a client-first naming pattern (Client A – Meta, Client A – Google) groups a client’s sources together, while a platform-first pattern (Meta – Client A, Google – Client A) groups everything by platform.
  • Neither approach is objectively better — pick based on the more common access pattern in the workspace (usually client-first for agencies, platform-first for single-brand accounts with many regions).

​
Naming for shared dashboards

Shared dashboard links surface data source names in filters and widget headers to viewers. That means the naming convention isn’t just for internal use — clients and stakeholders viewing a shared dashboard see these names too.
  • Use client-friendly names on connected sources for accounts that ship shared reports.
  • Avoid internal codes or slugs (client_a_prod_02) — spell things out (Client A Prod – Google).

​
Renaming an existing data source

Data source display names can be edited any time from the connection’s settings. Renaming updates the name everywhere it appears (widget pickers, existing widgets, filters, teamspace settings), so a rename doesn’t break existing dashboards.

Performance optimization

Practical tips to make dashboards load faster.

Teamspace settings

Use data source naming to speed up teamspace configuration.