Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Dashboard Improvement: Introduce tags

Answered
Andrew Paterson User

For billing purposes we would like to be able to tag entities in Fivetran to allow us to allocate costs, and customers will likely have other potential use cases. Tags would be useful against Destinations and individual Connectors. The tags should ouput into the Fivetran Log connector tables for downstream usage. A key pair would be ideal e.g. Charge Code: 1234-56, Classification: Sensitive

Please sign in to leave a comment.

Comments

6 comments

Date Votes
  • Official comment
    Andrew Morse User

    Hi Andrew Paterson- Thank you so much for sharing this request. We're looking to add some additional functionality to allow users to better manage their Connectors next year and tags are one of the methods we're exploring. Good idea to get these tags included in the log connector for some more advance use-cases. 

    Can you share more about your request for Destination tags and how Connect-level tagging wouldn't meet your needs?

  • Andrew Paterson User

    Hi Andrew,

    We have a couple of Desinations that are multi-tenant, in that they are configured by one central team for multiple consumers. As such we distinguish the costs are the connector level for these two Destinations, so tagging Destinations would handle this scenario. Let me know any other questions!

     

    Thanks

  • Yohei Onishi User

    Hi, we want this feature. for example, we want to tag priority to each connector

  • Reuben Gerald User

    I wanted to follow up on the lack of connector-level tags. If tags can't be implemented, we should at least have a comment or description field. This would help manage connectors and provide necessary details or comments at the connector level itself which should flow to the platform log tables

  • Safoora Jalali User

    Please note below use-case for this feature.

    This is an important feature so that we can tag the data replications against different business units to charge back for the data replication.

    This information must also get captured in the fivetran_billing connector. Please see example below of key-value pairs used for this purpose:

    x_application: central data platform, x_vertical: pt, x_cost_center: pt_amr, x_purpose: ingestion, x_uptime: continuous

  • Florian VANDINI User

    Hi,
    We strongly support the request to add tags.

    Tags would allow us to quickly group and filter connectors, transformations, and destinations across different teams, projects, or environments. This is especially valuable when managing a large number of pipelines, where current filtering options can be limiting.

    The ability to assign multiple tags (e.g., environment:prod, team:finance, project:customer-analytics) would make monitoring, troubleshooting, and auditing far more efficient. It would also help in reporting and governance by giving us a structured way to organize resources without changing their core configurations.

    This enhancement could greatly improve both usability and scalability of the dashboard experience for all customers.

    Please consider prioritizing this—many users could benefit from the flexibility and clarity that tagging brings.

    Best Regards,

    Florian