Marketing · Source connector
Stripe ELT Connector
Extract brings Stripe marketing data into data warehouses and databases for analysis with the rest of your business data. Teams use it to compare channel performance, audience engagement, and campaign trends. Flexible scheduling keeps reporting current for routine analysis and time-sensitive decisions.
View setup guide
Use cases
What teams use this connector for
Marketing performance analysis
Compare Stripe channel, campaign, and engagement trends to identify opportunities for improvement.
Audience and content analysis
Use Stripe data to understand which audiences, content, and activities contribute to engagement.
Cross-channel reporting
Combine Stripe metrics with other marketing and business data for consistent performance reporting.
Flexible reporting cadence
Refresh Stripe reporting every 15 minutes, hourly, daily, or on a custom schedule as business needs change.
Warehouse and database analysis
Use Extract to make Stripe marketing data available in data warehouses and databases such as Snowflake, BigQuery, Redshift, and PostgreSQL for governed analysis.
Connector data
Available streams
| Stream | Description | Sync mode |
|---|---|---|
payouts | Fields include amount, application_fee, application_fee_amount, arrival_date. | Full refresh |
disputes | Fields include amount, balance_transaction, created, currency. | Full refresh |
checkout_sessions | Fields include id, adaptive_pricing.enabled, after_expiration.recovery.allow_promotion_codes, after_expiration.recovery.enabled. | Full refresh |
tax_rates | Fields include id, active, country, created. | Full refresh |
promotion_codes | Fields include id, active, code, coupon.id. | Full refresh |
accounts | Fields include id, business_profile.annual_revenue.amount, business_profile.annual_revenue.currency, business_profile.annual_revenue.fiscal_year_end. | Full refresh |
persons | Fields include id, account, address.city, address.country. | Full refresh |
prices | Fields include active, billing_scheme, created, currency. | Full refresh |
subscriptions | Fields include id, application_fee_percent, billing_cycle_anchor, billing_thresholds.amount_gte. | Full refresh |
setup_intents | Fields include id, application, cancellation_reason, created. | Full refresh |
cards | Fields include brand, cancellation_reason, cardholder.id, created. | Full refresh |
early_fraud_warnings | Fields include actionable, charge, created, fraud_type. | Full refresh |
payment_methods | Fields include id, au_becs_debit.bsb_number, au_becs_debit.fingerprint, au_becs_debit.last4. | Full refresh |
upcoming_invoices | Fields include customer, id. | Full refresh |
payment_intents | Fields include amount, amount_capturable, amount_details.tip.amount, amount_received. | Full refresh |
subscription_schedules | Fields include id, application, canceled_at, completed_at. | Full refresh |
reviews | Fields include billing_zip, charge, closed_reason, created. | Full refresh |
tax_ids | Fields include country, created, customer, id. | Full refresh |
invoice_line_items | Fields include amount, amount_excluding_tax, currency, description. | Full refresh |
application_fees | Fields include account, amount, amount_refunded, application. | Full refresh |
transaction_entries | Fields include balance_impact.cash, balance_impact.inbound_pending, balance_impact.outbound_pending, created. | Full refresh |
application_fee_refunds | Fields include amount, balance_transaction, created, currency. | Full refresh |
customers | Fields include id, address.city, address.country, address.line1. | Full refresh |
refunds | Fields include amount, balance_transaction, created, currency. | Full refresh |
invoice_items | Fields include amount, currency, customer, date. | Full refresh |
quotes | Fields include id, amount_subtotal, amount_total, application. | Full refresh |
authorizations | Fields include amount, amount_details.atm_fee, amount_details.cashback_amount, approved. | Full refresh |
balance_transactions | Fields include amount, created, credit_note, currency. | Full refresh |
subscription_items | Fields include id, application_fee_percent, billing_cycle_anchor, billing_thresholds.amount_gte. | Full refresh |
transfers | Fields include amount, amount_reversed, balance_transaction, created. | Full refresh |
plans | Fields include id, active, aggregate_usage, amount. | Full refresh |
card_holders | Fields include billing.address.city, billing.address.country, billing.address.line1, billing.address.line2. | Full refresh |
coupons | Fields include amount_off, applies_to.products, created, currency. | Full refresh |
charges | Fields include id, amount, amount_captured, amount_refunded. | Incremental |
products | Fields include active, created, default_price, description. | Full refresh |
bank_accounts | Fields include account, account_holder_name, account_holder_type, account_type. | Full refresh |
invoices | Fields include id, account_country, account_name, account_tax_ids. | Incremental |
credit_notes | Fields include id, amount, amount_shipping, created. | Full refresh |
transfer_reversals | Fields include amount, balance_transaction, created, currency. | Full refresh |
topups | Fields include amount, balance_transaction, created, currency. | Full refresh |
Schema
Data model at a glance
payouts
amountintegerapplication_feestringapplication_fee_amountintegerarrival_datestringautomaticbooleanbalance_transactionstringcreatedstringcurrencystring
disputes
amountintegerbalance_transactionstringcreatedstringcurrencystringevidence.canceled.additional_documentationstringevidence.canceled.canceled_atstringevidence.canceled.cancellation_policy_providedbooleanevidence.canceled.cancellation_reasonstring
checkout_sessions
idstringadaptive_pricing.enabledbooleanafter_expiration.recovery.allow_promotion_codesbooleanafter_expiration.recovery.enabledbooleanafter_expiration.recovery.expires_atstringafter_expiration.recovery.urlstringallow_promotion_codesbooleanamount_subtotalinteger
tax_rates
idstringactivebooleancountrystringcreatedstringdescriptionstringdisplay_namestringeffective_percentagenumberflat_amount.amountinteger
promotion_codes
idstringactivebooleancodestringcoupon.idstringcreatedstringcustomerstringexpires_atstringlivemodeboolean
accounts
idstringbusiness_profile.annual_revenue.amountintegerbusiness_profile.annual_revenue.currencystringbusiness_profile.annual_revenue.fiscal_year_endstringbusiness_profile.estimated_worker_countintegerbusiness_profile.mccstringbusiness_profile.monthly_estimated_revenue.amountintegerbusiness_profile.monthly_estimated_revenue.currencystring
No verified relationships are available in this schema preview.
Connector pairings
Popular destinations
Commonly paired with Stripe in Extract workflows.
Why Extract
Why Extract for Stripe
- Rust-native performanceUse Rust-native data movement to refresh Stripe reporting every 15 minutes, hourly, daily, or on a custom schedule as volume grows.
- Full run transparencyInspect Stripe API activity, execution steps, and timing in Extract's run-level logs when data needs review.
- ELT + Reverse ETL in oneCombine Stripe data with customer and finance models, then send approved outputs through a separately configured Reverse ETL destination.
FAQ
Frequently asked questions
How does Extract handle incremental and full Stripe syncs?
An incremental sync processes only new or changed data since a stored checkpoint or new date partition, while a full sync processes the complete selected dataset or date range again. By avoiding repeated processing and writes for the full dataset, incremental syncs can reduce destination database updates and warehouse compute costs. Stream schemas define full refresh, partition-based extraction. Behavior varies by stream and configuration. Extract records run details so teams can verify each sync.
Can I backfill historical Stripe data with Extract?
Historical coverage for Stripe: Backfill (Days) (backfill): The backfill setting revisits and updates data from the past X days, ensuring the most current and accurate information replaces any previously pulled data. Use the setup guide and run details to confirm the available source records and selected settings.
How can teams monitor Stripe data quality and freshness?
Compare expected reporting periods and record totals in your models, then use Extract's run-level logs to inspect Stripe API activity, execution steps, and timing. This helps teams distinguish a source-data delay from a failed or incomplete run.
How often can Extract sync data from Stripe?
Extract supports schedules every 15 minutes, hourly, daily, or on a custom cadence. Teams can choose a frequency that matches routine reporting, time-sensitive monitoring, or operational activation needs.
What does the Stripe data model look like in the destination?
The Available streams table describes the datasets Extract can read from Stripe. The inline schema previews entities and fields. Only relationships verified from the exported schema are shown. Use the full schema link for more details.