> ## Documentation Index
> Fetch the complete documentation index at: https://docs.adriel.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Alternative channel names

> Override the default display name and icon on file and database data sources so a generic CSV or BigQuery table appears as the platform it really represents.

A CSV file holding **Meta Ads** data exported from a BI tool shows up by default with the **CSV File** icon and label. That makes it harder to read on dashboards alongside a native **Meta Ads** connection. The **Alternative channel name** feature overrides the display label and icon on file and database data sources, so the source is labeled as what it actually represents.

This is display-only. It does not change the data source type, the breakdown structure, or which fields are available — just the label and icon shown to viewers.

## Supported data sources

The alternative channel name and icon fields appear during creation on the following data sources. Both fields stay editable from data source settings after creation.

* **CSV File**
* **CSV with URL**
* **File from Email**
* **File from SFTP**
* **File from OneDrive**
* **File from SharePoint**
* **Amazon S3**
* **Google Sheets**
* **Custom URL Import**
* **BigQuery**
* **Redshift**
* **Snowflake**
* **MySQL**
* **PostgreSQL**
* **MongoDB**

Native ad-platform and analytics data sources do not expose this field — their default name already reflects the platform.

## Set the alternative name and icon

<Steps>
  <Step title="Open the source's settings">
    Navigate to **Data sources**, find the source, and click the settings icon. The **General** tab opens by default.
  </Step>

  <Step title="Fill in Alternative channel name">
    Enter the name that should appear on widgets, source labels, and the source picker. Any string is accepted. For example, set a CSV file holding Meta Ads exports to `Meta Ads`.
  </Step>

  <Step title="Upload an Alternative channel icon">
    The icon field accepts `.svg` files only. Upload an SVG and it replaces the default file or database icon everywhere the source appears.
  </Step>

  <Step title="Save">
    The new name and icon apply immediately. Dashboards rendering the source pick up the change on the next refresh.
  </Step>
</Steps>

## Where the alternative name appears

Once set, the alternative name shows up in:

* The source label next to widget data points.
* The source picker when adding the source to a widget.
* The Data sources page row label.
* Widget legends and tooltips.
* Source filters and breakdowns where the source name is referenced.

The underlying data source type doesn't change. A CSV file relabeled as `Meta Ads` is still a CSV source — its available fields, refresh schedule, and Data Integration tab behavior are determined by the **CSV File** data source, not by the alternative name.

## When to use it

| Use it when                                                                                                                                   | Skip it when                                                       |
| --------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------ |
| The source carries data from a specific platform that has its own native data source (for example a Meta Ads export landing in Google Sheets) | The source genuinely is generic — a sales CSV, a custom ETL output |
| Renaming the source for clarity on shared dashboards                                                                                          | The default name is already accurate                               |
| Distinguishing multiple file imports from each other on the same dashboard                                                                    | One-off uploads that won't be looked at often                      |

## Going further: Data conversion

An alternative channel name changes how the data source is **displayed**. [Data conversion](/data-sources/data-integration/data-conversion) goes further — it lets a non-ad data source actually **behave** like an ad channel inside Adriel, showing up in channel filters, contributing to channel-level totals, and accepting other sources blended onto it.

<Note>
  If the goal is just to relabel a CSV or database source so it reads as its underlying platform on dashboards, the alternative channel name is enough. If the goal is to also have that source participate in channel-level reporting (filters, totals, blending targets), set up **Data conversion** as well.
</Note>

## Troubleshooting

<AccordionGroup>
  <Accordion title="Set the name but the dashboard still shows the default">
    The change applies on the next dashboard render. Reload the dashboard. If the default still shows after a reload, confirm the field was saved (check the source's General tab) and that the dashboard is reading from the correct source.
  </Accordion>

  <Accordion title="Uploaded an SVG icon but it doesn't appear">
    Only `.svg` files are accepted. Other image formats (PNG, JPG) are rejected silently or fail validation. Re-export the icon as SVG and upload.
  </Accordion>

  <Accordion title="Want to remove the alternative name and revert to the default">
    Clear the **Alternative channel name** field in source settings and save. The default data source name returns. To remove a custom icon, the icon field needs to be cleared the same way.
  </Accordion>

  <Accordion title="Multiple CSV sources show the same label">
    The alternative channel name doesn't have to be unique across sources, but identical labels become confusing on dashboards. Suffix with the account name or campaign focus (for example `Meta Ads — Brand`, `Meta Ads — Performance`) to keep them distinguishable.
  </Accordion>

  <Accordion title="Why can't a custom channel logo be assigned to a generic Google Sheet or BigQuery column?">
    Custom per-value logos require Adriel to know what values are inside the mapped column. If channel is mapped to a generic column (for example, `Paid_Media_Channel` from Google Sheets or BigQuery), Adriel cannot enumerate the values and cannot resolve custom logos for that mapping.

    Custom logos only work for mappings where the possible values are known.
  </Accordion>
</AccordionGroup>

Related: [Naming conventions for data sources](/data-sources/managing/naming-conventions) · [Data conversion](/data-sources/data-integration/data-conversion) · [Connector catalog overview](/data-sources/overview)