​

Configuring Stripe as a Source

​

1. Add account access

• Client Secret: Your Stripe secret API key. You can find it in your Stripe Dashboard under Developers > API keys.
• Account ID: (Optional) Your Stripe account ID. Required when authenticating on behalf of a connected account.
• Start Date: The earliest date from which records will be synced.
• Stripe Connect: (Default: false) Enable this if your Stripe account is a platform account that uses Stripe Connect features. When enabled, the following additional streams become available: Connect Accounts, Connect Application Fees, Connect Transfers, and Connect Subaccount Transfers.
• Credit Balance: (Default: false) Enable this to retrieve Credit Balance data. When enabled, the Credit Balance Summary and Credit Balance Transaction streams become available.

​

2. Select streams

Tip: The stream can be found more easily by typing its name.

​

3. Configure data streams

• Layer: choose between the existing layers on your catalog. This is where you will find your new extracted tables as the extraction runs successfully.
• Folder: a folder can be created inside the selected layer to group all tables being created from this new data source.
• Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix to all tables at once and make this process faster!
• Sync Type: you can choose between INCREMENTAL and FULL_TABLE.
  • Incremental: every time the extraction happens, we’ll get only the new data - which is good if, for example, you want to keep every record ever fetched.
  • Full table: every time the extraction happens, we’ll get the current state of the data - which is good if, for example, you don’t want to have deleted data in your catalog.

​

4. Configure data source

• Configure Delta Log Retention and determine for how long we should store old states of this table as it gets updated. Read more about this resource here.
• Determine when to execute an Additional Full Sync. This will complement the incremental data extractions, ensuring that your data is completely synchronized with your source every once in a while.

​

5. Check your new source

​

Streams and Fields

​

Data Model

​

Use Cases for Data Analysis

​

1. Monthly Revenue Overview

• Monitor revenue trends over time
• Identify periods of growth or decline
• Compare paid vs. outstanding invoices

WITH monthly_revenue AS (
   SELECT
      DATE_FORMAT(DATE(i.created), '%Y-%m') AS month,
      SUM(CASE WHEN i.status = 'paid' THEN i.amount_paid ELSE 0 END) / 100.0 AS paid_revenue,
      SUM(CASE WHEN i.status = 'open' THEN i.amount_due ELSE 0 END) / 100.0 AS outstanding_revenue,
      SUM(CASE WHEN i.billing_reason = 'subscription_cycle' THEN i.amount_paid ELSE 0 END) / 100.0 AS recurring_revenue,
      SUM(CASE WHEN i.billing_reason != 'subscription_cycle' THEN i.amount_paid ELSE 0 END) / 100.0 AS one_time_revenue,
      COUNT(DISTINCT CASE WHEN i.status = 'paid' THEN i.id END) AS paid_invoices,
      COUNT(DISTINCT i.id) AS total_invoices,
      COUNT(DISTINCT i.customer) AS paying_customers
   FROM
      nekt_raw.stripe_invoices i
   WHERE
      i.created >= CURRENT_DATE - INTERVAL '12' MONTH
   GROUP BY
      DATE_FORMAT(DATE(i.created), '%Y-%m')
)
SELECT
   month,
   ROUND(paid_revenue, 2) AS paid_revenue,
   ROUND(outstanding_revenue, 2) AS outstanding_revenue,
   ROUND(recurring_revenue, 2) AS recurring_revenue,
   ROUND(one_time_revenue, 2) AS one_time_revenue,
   paid_invoices,
   total_invoices,
   paying_customers,
   ROUND(paid_revenue / NULLIF(paying_customers, 0), 2) AS avg_revenue_per_customer
FROM
   monthly_revenue
ORDER BY
   month DESC

WITH
   monthly_revenue AS (
      SELECT
         FORMAT_DATE('%Y-%m', DATE(i.created)) AS month,
         SUM(CASE WHEN i.status = 'paid' THEN i.amount_paid ELSE 0 END) / 100.0 AS paid_revenue,
         SUM(CASE WHEN i.status = 'open' THEN i.amount_due ELSE 0 END) / 100.0 AS outstanding_revenue,
         SUM(CASE WHEN i.billing_reason = 'subscription_cycle' THEN i.amount_paid ELSE 0 END) / 100.0 AS recurring_revenue,
         SUM(CASE WHEN i.billing_reason != 'subscription_cycle' THEN i.amount_paid ELSE 0 END) / 100.0 AS one_time_revenue,
         COUNT(DISTINCT CASE WHEN i.status = 'paid' THEN i.id END) AS paid_invoices,
         COUNT(DISTINCT i.id) AS total_invoices,
         COUNT(DISTINCT i.customer) AS paying_customers
      FROM
         `nekt_raw.stripe_invoices` i
      WHERE
         DATE(i.created) >= DATE_SUB(CURRENT_DATE(), INTERVAL 12 MONTH)
      GROUP BY
         1
   )
SELECT
   month,
   ROUND(paid_revenue, 2) AS paid_revenue,
   ROUND(outstanding_revenue, 2) AS outstanding_revenue,
   ROUND(recurring_revenue, 2) AS recurring_revenue,
   ROUND(one_time_revenue, 2) AS one_time_revenue,
   paid_invoices,
   total_invoices,
   paying_customers,
   ROUND(SAFE_DIVIDE(paid_revenue, paying_customers), 2) AS avg_revenue_per_customer
FROM
   monthly_revenue
ORDER BY
   month DESC

​

2. Subscription Churn Analysis

• Track monthly churn rates
• Identify high-churn periods
• Understand cancellation reasons to improve retention
• Monitor trial conversion rates

WITH subscription_cohort AS (
   SELECT
      DATE_FORMAT(DATE(s.created), '%Y-%m') AS cohort_month,
      DATE_FORMAT(DATE(s.canceled_at), '%Y-%m') AS churn_month,
      s.id AS subscription_id,
      s.customer,
      s.status,
      s.cancel_at_period_end,
      s.cancellation_details.reason AS cancellation_reason,
      s.trial_start IS NOT NULL AS had_trial
   FROM
      nekt_raw.stripe_subscriptions s
),
monthly_churn AS (
   SELECT
      churn_month,
      COUNT(DISTINCT subscription_id) AS churned_subscriptions,
      COUNT(DISTINCT CASE WHEN cancellation_reason = 'cancellation_requested' THEN subscription_id END) AS voluntary_churn,
      COUNT(DISTINCT CASE WHEN cancellation_reason IN ('payment_failed', 'payment_disputed') THEN subscription_id END) AS involuntary_churn,
      COUNT(DISTINCT CASE WHEN had_trial THEN subscription_id END) AS churned_trials
   FROM
      subscription_cohort
   WHERE
      churn_month IS NOT NULL
      AND churn_month >= DATE_FORMAT(CURRENT_DATE - INTERVAL '12' MONTH, '%Y-%m')
   GROUP BY
      churn_month
),
monthly_active AS (
   SELECT
      DATE_FORMAT(DATE(created), '%Y-%m') AS month,
      COUNT(DISTINCT id) AS new_subscriptions
   FROM
      nekt_raw.stripe_subscriptions
   WHERE
      created >= CURRENT_DATE - INTERVAL '12' MONTH
   GROUP BY
      DATE_FORMAT(DATE(created), '%Y-%m')
)
SELECT
   mc.churn_month AS month,
   mc.churned_subscriptions,
   mc.voluntary_churn,
   mc.involuntary_churn,
   mc.churned_trials,
   COALESCE(ma.new_subscriptions, 0) AS new_subscriptions,
   ROUND(mc.churned_subscriptions * 100.0 / NULLIF(COALESCE(ma.new_subscriptions, 0) + mc.churned_subscriptions, 0), 2) AS churn_rate_pct
FROM
   monthly_churn mc
   LEFT JOIN monthly_active ma ON mc.churn_month = ma.month
ORDER BY
   month DESC

WITH
   subscription_cohort AS (
      SELECT
         FORMAT_DATE('%Y-%m', DATE(s.created)) AS cohort_month,
         FORMAT_DATE('%Y-%m', DATE(s.canceled_at)) AS churn_month,
         s.id AS subscription_id,
         s.customer,
         s.status,
         s.cancel_at_period_end,
         s.cancellation_details.reason AS cancellation_reason,
         s.trial_start IS NOT NULL AS had_trial
      FROM
         `nekt_raw.stripe_subscriptions` s
   ),
   monthly_churn AS (
      SELECT
         churn_month,
         COUNT(DISTINCT subscription_id) AS churned_subscriptions,
         COUNT(DISTINCT CASE WHEN cancellation_reason = 'cancellation_requested' THEN subscription_id END) AS voluntary_churn,
         COUNT(DISTINCT CASE WHEN cancellation_reason IN ('payment_failed', 'payment_disputed') THEN subscription_id END) AS involuntary_churn,
         COUNT(DISTINCT CASE WHEN had_trial THEN subscription_id END) AS churned_trials
      FROM
         subscription_cohort
      WHERE
         churn_month IS NOT NULL
         AND churn_month >= FORMAT_DATE('%Y-%m', DATE_SUB(CURRENT_DATE(), INTERVAL 12 MONTH))
      GROUP BY
         churn_month
   ),
   monthly_active AS (
      SELECT
         FORMAT_DATE('%Y-%m', DATE(created)) AS month,
         COUNT(DISTINCT id) AS new_subscriptions
      FROM
         `nekt_raw.stripe_subscriptions`
      WHERE
         DATE(created) >= DATE_SUB(CURRENT_DATE(), INTERVAL 12 MONTH)
      GROUP BY
         1
   )
SELECT
   mc.churn_month AS month,
   mc.churned_subscriptions,
   mc.voluntary_churn,
   mc.involuntary_churn,
   mc.churned_trials,
   COALESCE(ma.new_subscriptions, 0) AS new_subscriptions,
   ROUND(
      mc.churned_subscriptions * 100.0 / NULLIF(COALESCE(ma.new_subscriptions, 0) + mc.churned_subscriptions, 0),
      2
   ) AS churn_rate_pct
FROM
   monthly_churn mc
   LEFT JOIN monthly_active ma ON mc.churn_month = ma.month
ORDER BY
   month DESC

​

Implementation Notes

​

Data Quality Considerations

• All monetary amounts are provided in the smallest currency unit (e.g., cents for USD). Divide by 100 to get the standard value in queries.
• Incremental sync uses the updated_at field for most streams. Use created for Balance Transactions.
• Some streams (Subscription Items, Invoice Line Items) are children of parent streams and require the parent stream to be enabled.

​

Optional Features

• The Connect streams are only available when Stripe Connect is enabled in the source configuration. Enable this if you manage a marketplace or platform using Stripe Connect.
• The Credit Balance streams are only available when Credit Balance is enabled in the source configuration.

​

API Limits & Performance

• Selecting all streams can increase extraction times significantly.
• For faster extractions, select only the streams necessary for your analysis.
• Parent-child stream pairs (e.g., Invoices + Invoice Line Items) require both to be selected if you need the child data.

​

Skills for agents