---
title: How to see which signups become paying customers with Stripe
description: To see which signups become paying customers in Stripe, match each signup to its Stripe customer by your own user ID or email address, count the ones with a real paid invoice or charge, and compare signup groups at the same age, which is the matching and counting an AI marketer can do for you.
slug: /how-to/see-which-signups-become-paying-customers-with-stripe
page_type: playbook
lead_prompt: How do I see which signups become paying customers in Stripe?
target_prompts:
  - How can I use an AI marketing agent to see which signups become paying customers with Stripe?
entity: Kite
category: AI marketing agent
author: Devon Wells and Kite
date_published: '2026-10-21'
date_modified: '2026-10-21'
related_use_cases:
  - /use-cases/improve-website-conversion.md
integrations:
  - name: Stripe
    page: /integrations/stripe.md
---

# Playbook

# How to see which signups become paying customers with Stripe

## Key Takeaways

- You see which signups become paying customers by matching each signup to a Stripe customer and checking whether that customer has a paid invoice or a successful charge. Stripe holds the payments, but it only knows about the signups your app sent to it.
- If your app creates a Stripe customer or starts a Stripe trial at signup, Stripe already holds the whole answer. If Stripe only meets people at checkout, the signups who never paid live somewhere else, and you need that list too.
- The match is most reliable on your own user ID saved in Stripe, through customer metadata or the checkout session's client reference ID. Email works too, but billing emails often differ from signup emails.
- Kite reads your Stripe customers, subscriptions, invoices, charges, and checkout sessions, matches them to your signups, and counts only real payments. It compares each week's or month's signups at the same age, so older groups don't look better simply because they've had longer to pay.
- You get your signup-to-paid rate for each signup group, how long people take to pay, which plans they choose, and a list of the signups Kite couldn't match, with the reason for each.

## How do I see which signups become paying customers in Stripe?

You see which signups become paying customers by putting two lists side by side: everyone who signed up, and everyone who paid. Stripe keeps the second list well. Each Stripe customer has an email, a creation date, and any metadata your app saved, and each one's subscriptions, invoices, and charges show whether they're in a trial, paying, behind on payment, or gone. The first list is the tricky part, because Stripe only knows about the people your app told it about.

Where your signups live depends on how your app uses Stripe:

- **Your app creates a Stripe customer at signup.** Every signup is already a Stripe customer, so the people who never paid are in Stripe too, with no payments attached. Stripe alone can answer the question.
- **Your app starts a Stripe trial at signup.** Each trial is a subscription with a trialing status, and the ones that convert become active. Stripe's own Billing analytics show subscription measures such as recurring revenue and churn, and it can show how many trials convert.
- **Stripe only meets people at checkout.** This is the most common setup for a free plan or a trial without a card. Stripe sees only the people who started paying, so the signups who never paid live in your product database, your analytics, or your CRM, and you have to match the two lists yourself.

Inside Stripe, the dashboard lets you filter customers by creation date and look at each one's payments, and Stripe Sigma, a paid add-on, lets you write SQL queries against your Stripe data. Neither one knows about the signups outside Stripe. So for most teams, the job comes down to matching. You save something at signup that both systems share, ideally your own user ID on the Stripe customer or checkout session, then you join the two lists and count.

A good result is a signup-to-paid rate you can trust. It counts only real payments, not trials or free invoices. It compares signup groups fairly, so a group from three months ago isn't judged against one from last week. And it tells you how many signups it couldn't match, so you know how much of the picture it covers.

Kite does this work for you. It works out where your signups live, matches them to Stripe, decides who really paid, and reports your conversion by signup group.

## How to get started

Start by asking Kite which of your signups turned into paying customers:

> "How many of the people who signed up since July have become paying customers in Stripe?"

Kite is an AI marketer. It researches your business, builds a growth strategy, and ships the work that brings you new customers. By the time you ask, it already knows your plans, your pricing, and whether you offer a free plan or a trial from its research on your business. That lets it propose the date range, how to group signups, and what counts as a paying customer without a long brief. Confirm the plan or adjust it, and Kite starts.

You'll need to connect your Stripe account through OAuth so Kite can read your customers and their payments. If Stripe doesn't hold all your signups, Kite also needs the signup list. You can connect the tool that records it, such as PostHog, your CRM, or a Google Sheet, or share a CSV export from your product database in Slack.

This job only reads from Stripe, so Kite runs the analysis and posts what it found. It doesn't change any of your billing records.

## How Kite matches signups to Stripe customers

### Where do your signups live?

Kite starts by working out whether Stripe already knows about every signup, because that decides how much matching the job needs. It lists the Stripe customers created in your date range and compares the count with the signups in your product records. When the two counts are close and most of those customers have no payments, your app creates a Stripe customer at signup, and Kite can work from Stripe alone. When Stripe holds far fewer customers than you have signups, Stripe only meets people at checkout, and Kite reads the full signup list from the source you connected or shared.

Kite also checks what your app saves in Stripe. It reads the metadata on recent customers and checkout sessions, and the client reference ID on each checkout session, to see whether your own user ID is stored there. It reads trial dates on subscriptions to learn your trial length. That tells Kite when a signup has had a fair chance to pay.

### How is each signup matched to a Stripe customer?

Kite matches each signup to a Stripe customer using the most reliable identifier you have. When your user ID is stored in Stripe customer metadata or a checkout session's client reference ID, Kite matches on it directly, because it can't be mistyped or changed by the customer. When there's no shared ID, Kite matches on email address. It searches Stripe customers by email and treats addresses that differ only in capital letters as the same person.

Email matching has two common gaps, and Kite handles both. First, one person can end up as several Stripe customers, for example after starting checkout twice. Kite groups those customers under the one signup, so a person isn't counted twice. Second, some people pay with a different email than the one they signed up with, such as a company billing address. When a Stripe customer's email shares a company domain with an unmatched signup from the same period, Kite lists it as a possible match for you to check, and it doesn't count that pair until you confirm it.

Kite also removes accounts that would distort the numbers. It leaves out test-mode customers, signups from your own company's email domain, and staff accounts you name.

### Who counts as a paying customer?

Kite counts a signup as a paying customer only when Stripe shows real money changing hands. For a subscription business, that means an invoice with a paid status and a total above zero. For one-time purchases, it means a successful charge or a completed checkout session that wasn't fully refunded. Kite reads each matched customer's subscriptions, invoices, and charges to find the first payment that qualifies.

Several things look like a conversion in Stripe without being one, and Kite keeps them out of the count:

- A subscription that is still in its trial
- An invoice paid entirely by a 100 percent discount coupon
- A charge that was fully refunded
- A payment that failed, even if a later attempt is still pending

Kite records the date of each person's first real payment, the plan and price they chose, and the amount. It reports amounts in each currency separately, instead of adding dollars to euros.

### How do you compare signup groups fairly?

Kite compares each week's or month's signups at the same age, because a group that signed up long ago has simply had more time to pay. It groups signups by the week or month they joined, then measures the share that paid within the same window for every group, such as 30 days after signup. A group that hasn't reached that age yet is marked as still converting rather than counted as a failure.

Kite picks the window from your trial length and from how long your paying customers actually took. If most of them paid within two weeks of signing up, a 30-day window catches nearly everyone. If many paid months later, Kite uses a longer window and shows the rate at more than one point, such as 30, 60, and 90 days.

For each signup group, Kite works out these measures:

- Signups, and how many it matched to Stripe
- Paying customers within the window, and the signup-to-paid rate
- How many are still in a trial
- The typical number of days from signup to first payment
- The plans paying customers chose
- How many paid and then canceled or were refunded within their first billing period

### What Kite reports back and what happens next

When the analysis is done, Kite posts a summary in the conversation where you asked, in the Kite web app or in Slack. It gives your signup-to-paid rate for each signup group, says whether the rate is rising or falling, and points out the groups that stand out. It also says how many signups it couldn't match and why. The full table comes with the summary. When the results need more room than a message, Kite can publish them as a report with charts that you can share by link.

When matching on email leaves a large share of signups unmatched, Kite tells you how to close the gap. Usually the fix is to save your user ID in Stripe customer metadata when you create the customer, or in the client reference ID when you open a checkout session. Your developers make that change in your app, and the next run matches those customers exactly.

From there, the numbers point to the next piece of work. A falling paid rate in recent groups is a reason to look at onboarding or the upgrade prompt, and Kite can propose changes to the pages and emails new users see. If you want this tracked, ask Kite to run it every month. It will post each new report where you choose, in the same Slack thread, by email, or as its own conversation in the Kite web app.

## What the finished work contains

When Kite finishes, you have a signup-to-paid rate you can trust for each signup group, the list of who paid, and a clear statement of what the analysis covers.

- **The conversion table.** Each week or month of signups shows its signup count, matched count, paying customers within the window, signup-to-paid rate, and how many are still in a trial. Groups too young to judge are marked as still converting.
- **The paying customer list.** Each signup who paid shows their signup date, first payment date, days between the two, the plan and price they chose, and the amount of their first payment in its currency.
- **Early cancellations and refunds.** The paying customers who canceled or were refunded in their first billing period, so you can see whether conversions are holding.
- **The unmatched list.** The signups Kite couldn't match to Stripe and the Stripe customers it couldn't match to a signup, with possible matches marked for you to confirm.
- **The method.** The date range, the window, how Kite matched people, what it counted as a payment, and which accounts it left out.

## Common questions

### How do I connect a signup in my app to a Stripe customer?

The most reliable way is to save your own user ID on the Stripe record when it's created. If your app creates the Stripe customer, put the user ID in the customer's metadata. If people pay through Stripe Checkout, put the user ID in the checkout session's client reference ID, which stays attached to the completed session. Payment Links accept a client reference ID as a parameter in the link's address. Either way, every payment can be traced back to the exact signup without relying on email.

### Should I create a Stripe customer for every signup?

Creating a Stripe customer for every signup makes this job much easier, because Stripe then holds both the people who paid and the people who didn't. The cost is a Stripe account full of customers with no payments, which some teams find cluttered for billing work. If you'd rather not, saving your user ID at checkout gives you an exact match without adding every signup to Stripe.

### Can I see trial conversion in the Stripe dashboard?

You can see trial conversion in Stripe when your trials start inside Stripe, because each trial is a subscription that either becomes active or ends. Stripe's Billing analytics cover subscription measures like these. When people sign up for a free plan or a trial without a card, Stripe never sees most of them, so its numbers describe only the people who reached checkout, not everyone who signed up.

## Related pages

- **Use case:** Turn free users into paying customers (coming soon)
- **Use case:** [Improve website conversion](/use-cases/improve-website-conversion.md)
- **Use case:** Work out what a lead or customer is worth (coming soon)
- **Use case:** Work out your customer acquisition cost and payback (coming soon)
- **Integration:** [Stripe + Kite](/integrations/stripe.md)