We are writing to request the addition of the "last_active field" to the Stripe accounts table schema in our Fivetran connector. This field exists in the Stripe application but is currently not being synced to our data warehouse.

Background: We use Fivetran to sync Stripe Connect data for our platform, which manages multiple landlord accounts. The last_active field is available in Stripe's application and tracks the last time an account performed any activity (charges, payouts, disputes, transfers, etc.). This timestamp is crucial for understanding account engagement and lifecycle management and filtering out the account based on when we went live.

Current Issue: The last_active field is missing from the fivetran_stripe.account table schema. While we can see fields like id, created, charges_enabled, payouts_enabled, and business_type, the critical last_active timestamp is not available. This forces us to use created to filter out accounts but gives us inaccurate data.

Business Impact: Without the last_active field, we cannot accurately distinguish between test accounts and actual live accounts since our platform launch, creating data quality issues for all downstream analytics, limiting our sales and product teams' ability to prioritize efforts effectively.

Request: Could you please add the last_active field from the Stripe accounts API to the existing accounts table schema? This field should be available at the fivetran_stripe.accounts table and would be a timestamp data type.

Thank you for your consideration. Please let us know if you need any additional information or clarification about this request.