Feature Request: Expose Connection-Level Billed Cost Data via Fivetran Platform Connector

Summary

Provide a supported method (via the Fivetran Platform Connector or REST API) to retrieve accurate, per-connection billed cost data that reconciles exactly with the Billing & Usage page, under the current (post-March 2025) tiered pricing model.

Problem Statement

Under the current pricing model, connection-level costs are calculated using tiered/blended pricing logic where the per-row cost decreases as usage increases, and tiering is applied at the connection level. This means:

• The legacy query method (documented at Monthly Costs Accrued for Each Connector) only works for pre-March 2025 pricing and allocates total account cost proportionally by MAR share — it does not reflect actual per-connection billed amounts under current pricing.
• The FIVETRAN_LOG.USAGE_COST table only records cost at the account/month level, not per connection.
• The FIVETRAN_LOG.INCREMENTAL_MAR table exposes connection-level MAR/usage, but not the internal tiered pricing calculations used to translate that usage into billed dollars.
• As a result, there is currently no supported way to programmatically derive exact per-connection spend — only the Billing & Usage UI shows the true, correct number, and it is not exportable/queryable at scale.

Why This Matters

Many customers need to allocate or report on cost by connector/data source for internal budgeting, chargeback, or cost tracking purposes. Without programmatic access to accurate per-connection costs, this has to be done manually by cross-referencing the Billing & Usage UI, which does not scale well for accounts with many connections and cannot be integrated into automated reporting or dashboarding workflows.

Requested Solution

Please consider one or more of the following:

1. Add a new field/table to the Fivetran Platform Connector (e.g., USAGE_COST_BY_CONNECTION) that records the actual billed cost per connection per month, reflecting the tiered pricing calculation already used internally for the Billing & Usage page.
2. Expose this same data via the REST API (e.g., a /usage/connections or similar endpoint) so it can be pulled programmatically.
3. At minimum, document the exact tiering/pricing formula so customers can accurately replicate the calculation using existing MAR data.

Acceptance Criteria

• Per-connection cost data (via Platform Connector table or REST API) reconciles exactly with the amounts shown on the Billing & Usage page.
• Data is available at monthly granularity, per connection/schema/destination.
• Solution works under the current (post-March 2025) tiered pricing model.

Additional Context

The legacy documented query (https://fivetran.com/docs/connectors/troubleshooting/monthly-costs-accrued) is explicitly limited to pre-March 2025 pricing. Fivetran Support has confirmed there is currently no supported way to derive exact per-connection billed costs from Platform Connector data under the current pricing model.