Revenue Related Tables
Answered
Connector name: RevenueCat
Table name: subscription
API documentation link: https://www.revenuecat.com/docs/api-v2/customer/resources
Additional details:
We need per-customer subscription and purchase history from RevenueCat API v2 to compute subscribers, MRR, churn and revenue across App Store and Google Play. The connector currently syncs only product configuration and metric_overview.
Requested tables (in priority order):
1. subscription: GET /v2/projects/{project_id}/customers/{customer_id}/subscriptions (permission customer_information:subscriptions:read). Key fields: id, customer_id, product_id, store, status, gives_access, auto_renewal_status, starts_at, current_period_starts_at, current_period_ends_at, ends_at, environment, store_subscription_identifier, total_revenue_in_usd (gross, commission, tax, proceeds).
2. customer: GET /v2/projects/{project_id}/customers (parent table to iterate customers), including first_seen_at, last_seen_at and aliases.
3. purchase (one-time / n
Table name: subscription
API documentation link: https://www.revenuecat.com/docs/api-v2/customer/resources
Additional details:
We need per-customer subscription and purchase history from RevenueCat API v2 to compute subscribers, MRR, churn and revenue across App Store and Google Play. The connector currently syncs only product configuration and metric_overview.
Requested tables (in priority order):
1. subscription: GET /v2/projects/{project_id}/customers/{customer_id}/subscriptions (permission customer_information:subscriptions:read). Key fields: id, customer_id, product_id, store, status, gives_access, auto_renewal_status, starts_at, current_period_starts_at, current_period_ends_at, ends_at, environment, store_subscription_identifier, total_revenue_in_usd (gross, commission, tax, proceeds).
2. customer: GET /v2/projects/{project_id}/customers (parent table to iterate customers), including first_seen_at, last_seen_at and aliases.
3. purchase (one-time / n
-
Official comment
Hi Matt,
Thank you for submitting your feature request for the RevenueCat connector.
We are currently assessing customer demand and will begin a detailed feasibility analysis to determine the viability of building and maintaining a high-quality Fivetran connector for RevenueCat. The request has been added to our backlog, and as we progress through our evaluation, we may reach out for additional details to ensure the solution aligns closely with your requirements and expectations.
We appreciate your feedback and continued support - it plays an important role in shaping our product roadmap.
Best regards,
Sahu
Please sign in to leave a comment.
Comments
1 comment