Skip to help content
RightMessage

Connect Stripe and see which segments buy

You'll connect Stripe with a read-only key, then see how much revenue each segment and answer brings in, right next to how many visitors it has.

Updated

View as Markdown

Connect Stripe and RightMessage puts revenue next to your segments. You'll see which segments and answers bring in money, how much each buyer is worth, and whether new customers come from different places than your renewals. Once it's connected, the same numbers show up on your dashboard, your segment groups, and your questions.

Visitor counts tell you who's on your site. They don't tell you who pays. WorkForge (opens in a new tab), for example, might find that agencies are a small share of its visitors but a big share of its revenue. That's the kind of thing that tells you where a dedicated offer or a sharper question is worth your time.

This is a one-time step. RightMessage reads your payments through a restricted key, which can't change anything in your Stripe account. It's separate from how you pay for RightMessage.

1. Open the Stripe connection

  1. Open Project settings (the gear at the bottom of the sidebar), then Integrations.
  2. Select the Connected apps tab.
  3. Beside Stripe, choose Connect.
Connected apps tab of Integrations listing Senja with Connect and Stripe as Connected with Manage connectionOriginal
Connected apps tab of Integrations listing Senja with Connect and Stripe as Connected with Manage connection

You can also start where you'll read revenue. The dashboard's Results section shows See which segments buy with a Connect Stripe button, and choosing Revenue on the Segment Groups or Questions page before Stripe is connected opens the same dialog.

2. Create a restricted key in Stripe

RightMessage needs a restricted key, not your secret key. The Connect Stripe dialog walks you through it.

  1. Choose Create a restricted key in Stripe. Stripe's page for a new restricted key opens in a new tab.
  2. Name it RightMessage.
  3. Set Charges to Read. This also covers refunds.
  4. Set Customers to Read.
  5. Set Subscriptions to Read.
  6. Leave everything else as None, then create the key and copy it.
Connect Stripe dialog explaining the read-only restricted key, with steps to create it in Stripe and an empty Restricted key fieldOriginal
Connect Stripe dialog explaining the read-only restricted key, with steps to create it in Stripe and an empty Restricted key field

3. Paste the key and connect

  1. Back in RightMessage, paste the key into Restricted key. It starts with rk_live_.
  2. Choose Connect.

RightMessage checks that the key can read all three before it saves anything. If something's missing, the dialog says what to fix. The last section of this page lists each message.

Once it's saved, the dialog closes and you'll see Stripe connected: "Importing the last 90 days of payments in the background. We'll let you know when they're in." You don't need to keep the page open.

4. Let the import finish

RightMessage brings in the last 90 days of payments first, so recent revenue is ready quickly. Then it works back through older history and adds new payments as they arrive. Once it's caught up, it checks Stripe again about every hour.

When the first 90 days are in, you'll get Stripe payments are in: "Revenue from the last 90 days is ready." Its View revenue button opens your segment groups with revenue showing. If Stripe stops accepting the key, a Stripe import stopped notice explains why and offers Reconnect.

While older history is still coming in, a few things wait for it:

  • Days before the imported range show no revenue yet. The revenue pages say so, as in "Stripe payments before Aug 1, 2026 are still importing, so earlier days show no revenue yet."
  • RightMessage can't tell a brand-new customer from a returning one until every past payment is in, so parts that depend on it show "Waiting for Stripe's full history."

See which segments buy

Revenue shows up in a few places, all counted the same way:

  • Dashboard. The Results section below the activity chart shows New customers and Existing customers for the dashboard's dates, then a By segment table with each segment's revenue, its share of visitors next to its share of revenue, and Worth. See the dashboard reference.
  • Segment groups. Switch the Visitors | Revenue toggle on the Segment Groups page or a group's Results tab to see revenue, buyers, and revenue per buyer for each segment. See the segment library reference.
  • Questions. Switch the Answers | Revenue toggle on the Questions page or a question's Results tab to split revenue by answer. See question results and activity.
  • Campaigns. A campaign with a holdback adds Revenue per visitor to its Results tab, comparing personalized and held-back visitors. It's descriptive and doesn't change the test result. See compare personalization with a holdback.
Dashboard Results for a pricing-page goal showing people who reached it, new and existing customer revenue from Stripe, and a By segment table with Reached goal, Revenue, Visitors to revenue and WorthOriginal
Dashboard Results for a pricing-page goal showing people who reached it, new and existing customer revenue from Stripe, and a By segment table with Reached goal, Revenue, Visitors to revenue and Worth

The dashboard's goal columns need conversion goals, which require Scale or Pro. Revenue itself works without a goal.

RightMessage matches Stripe customers to visitors by email, so revenue only counts for buyers RightMessage has recognized on your site. Buyers matched shows how many that is. Payments without an email can't be matched, and the revenue pages say how many there were. To match more buyers, make sure RightMessage recognizes your visitors. For how buyers are credited to segments, the 5-buyer minimum, and what Worth means, see how revenue by segment is counted.

Try it with a test key

A test-mode key (rk_test_) works too. RightMessage imports your Stripe test payments and tags them Test data on the Connected apps tab, in the dashboard's Results section, and in the revenue views of your segment groups and questions, so you can't mistake them for real sales. When you're ready, replace it with an rk_live_ key.

Check the connection

The Connected apps tab shows Stripe's state with a tag and a status line underneath:

If you seeIt means
ImportingThe first 90 days of payments are still coming in. "Importing the last 90 days of payments… We'll let you know when they're in."
ConnectedPayments are up to date, with when it last synced, like "Synced 5m ago".
Sync delayedRightMessage hasn't synced successfully for 3 hours. It keeps retrying automatically.
Key rejectedStripe stopped accepting the key. It may have been deleted or rolled. Choose Reconnect, paste a new restricted key into Replace key, and choose Save key.

Choose Manage connection to open Stripe's dialog. It shows Last sync, a Data row with Test data for a test key, and what it Imports: "All payments and refunds: the last 90 days first, then older history and new payments as they arrive". The dashboard's Results section has a Manage link that opens the same dialog.

Replace your key or disconnect

  1. On the Connected apps tab, choose Manage connection beside Stripe.
  2. To use a new key, paste it into Replace key and choose Save key. How to create a restricted key shows the Stripe steps again.
  3. To stop using Stripe, choose Disconnect.

Replacing the key deletes the payments imported with the old key and imports your history again, starting with the last 90 days. That's how you switch from a test key to a live key, or to a different Stripe account.

Disconnecting deletes the imported payments and removes revenue from the dashboard, segment groups, questions, and campaigns. Nothing changes in your Stripe account. To bring revenue back, connect again and the import starts over.

If Stripe won't connect

The dialog checks the key before saving it and names the problem under Restricted key:

If the message saysDo this
"This is a secret key with full access to your Stripe account."You pasted an sk_ key. Create a restricted key instead. RightMessage only needs to read charges, customers and subscriptions.
"This is a publishable key."You pasted a pk_ key. Create a restricted key, which starts with rk_live_.
"Stripe restricted keys start with rk_live_ or rk_test_."Copy the whole restricted key from Stripe and paste it again.
"This key can't read Customers or Subscriptions." (or whichever permissions are missing)In Stripe, edit the key and set each named permission to Read, then choose Connect again.
"Stripe didn't accept this key. It may have been deleted or rolled; create a new restricted key."The key no longer works in Stripe. Create a new restricted key and paste it.

If the dashboard shows "Stripe stopped accepting your key", the key was deleted or rolled after you connected. Choose Reconnect and paste a new restricted key.

If the dashboard says "No Stripe payments in this period", try 30 days, or check that payments go to the Stripe account you connected.

Still need a hand?

Tell us what you’re trying to do and where you’re getting stuck.

support@rightmessage.com