# Stripe + HubSpot integration and analysis

Connect Stripe and HubSpot to Hendrik. Compare HubSpot deal progression with Stripe payment, refund, and dispute data while keeping booked and paid outcomes separate.

## The question this stack can answer

Are won HubSpot deals turning into Stripe payments?

## What Hendrik reads from each source

- **Stripe:** Payments, refunds, and disputes show whether money was collected after an order was placed.
- **HubSpot:** Contacts, deals, and pipeline stages show whether paid leads become qualified pipeline.

## What you need to connect

- Use one explicit 28-day comparison window, time zone, market, and legal-entity scope before comparing values.
- Connected Stripe account with payment, refund, and dispute data for the same legal entity.
- Connected HubSpot account with agreed lifecycle and deal-stage definitions.
- Keep provider-specific definitions visible and use an identity or product mapping only where it is established for this workspace.

## Important limits

- Payments must not be added to storefront or marketplace revenue; transaction reconciliation needs a proven payment relationship.
- Contacts and deals do not automatically map to an ad-platform lead, website session, store order, or Stripe payment.

## Illustrative example

### Stripe + HubSpot review

Previous: 1–28 January. Current: 29 January–25 February. Both periods contain 28 days. Monetary values use USD and all timestamps use UTC. Reported lead volume and CRM wins describe different cohorts. Stripe adds collected payment data. Compare those stages without treating them as a joined funnel.

*About this example: Synthetic data · illustrative analysis · Hendrik only acts with the permissions you give it.*

- successful payment amount (USD, 28 days) (Stripe): 102,000 USD → 94,000 USD
- Won deals · close date in period (count, 28 days) (HubSpot): 34 → 29

### What Hendrik checks

- **Payment and refund scope:** Check Stripe payment, refund, dispute, and balance-transaction dates. Establish an order-to-payment reference before reconciliation.
- **Pipeline definition:** Check HubSpot form routing, deal stage definition, stage-history timing, and identity coverage before using pipeline movement.
- **Explain the divergence:** Stripe: successful payment amount (USD, 28 days) changed from 102,000 USD to 94,000 USD. HubSpot: Won deals · close date in period (count, 28 days) changed from 34 to 29. Compare the timing and definitions before attributing one change to the other.

### What Hendrik sees

Stripe successful payment amount fell. HubSpot won deals fell.

### What to do next

Review payment data before treating pipeline movement as collected value; reassess when relationship coverage and date definitions are known.

**Limit:** A HubSpot deal is not a Stripe payment, and values must not be added.

## Provider documentation

- [Stripe documentation](https://docs.stripe.com/reports)
- [HubSpot documentation](https://knowledge.hubspot.com/reports)

## Start with this stack

[Create a workspace and connect Stripe + HubSpot](https://app.withhendrik.com/auth?mode=sign-up&acquisition_channel=marketing&return_to=%2Fonboarding%2Factivation&cta_location=integration_markdown&landing_page_id=combination-stripe-hubspot&combination=stripe-hubspot)