On this page

Snowflake Marketplace sample

Reference

Forgewell Analytics Demo

A synthetic subscription wellness company that joins Pendo product usage, Stripe billing, and GA4 acquisition in one account-level model. Use it to test product-to-revenue analysis, semantic views, and Cortex questions without customer data.

Get the sample on Snowflake Marketplace Talk to sales

Free · Secure share · Cortex AI-ready · All regions

Brainforge Data Team

Snowflake Marketplace

Last updated: 2026-11-04
Sample version: v1.0
Data window: Nov 2025 to Oct 2026
Rows: 300 accounts / 1M events
Share: Secure share
Regions: All regions
Refresh: Static

The sample contains 300 accounts, 2,837 visitors, 999,846 Pendo events, and 1,591 Stripe invoices across 12 months. Every row is synthetic. No real people, customers, or Pendo customer data are included.

First run

The share exposes the SECURE schema only, using Snowflake Secure Data Sharing. Source schemas stay internal.

Get the listing.Open the listing on Snowflake Marketplace and use the Get dialog. Choose the role that should read the sample and keep the default database name unless you have a reason to rename it.
Create the database.The Get flow creates a database from the share. If your account requires it, grant imported privileges on that database to the role your team uses for analysis.
Run the first query.Replace FORGEWELL_DEMO if you renamed the database during creation.
First query
```
SELECT *
FROM FORGEWELL_DEMO.SECURE.ACCOUNT_360
LIMIT 10;
```

Verify the sample.The account view should return 300 rows. Check the build date and data window in the config view.

Verify the sample

SELECT COUNT(*) AS ACCOUNTS
FROM FORGEWELL_DEMO.SECURE.ACCOUNT_360;

SELECT COMPANY_NAME, IS_SYNTHETIC, START_DATE, END_DATE, GENERATED_AT
FROM FORGEWELL_DEMO.SECURE.DEMO_CONFIG;

If the first query fails

Database not found: confirm the name you chose in the Get dialog, then update the query.
Insufficient privileges: grant imported privileges on the database to the role you are using.
Region mismatch: confirm the listing is available in your region under Region Availability.

Query cookbook

Six recipes for common product-to-revenue questions. Outputs are illustrative, tied to sample version v1.0, and show the shape of the answer rather than exact production values.

1. Revenue per acquisition channel

Which channel brings in the most revenue per paying account?

SQL

SELECT ACQUISITION_CHANNEL,
       SIGNUPS,
       PAYING_ACCOUNTS,
       SIGNUP_TO_PAID_RATE,
       REVENUE_PER_PAYING_ACCOUNT_USD
FROM FORGEWELL_DEMO.SECURE.ACQUISITION_TO_REVENUE
ORDER BY REVENUE_PER_PAYING_ACCOUNT_USD DESC;

Illustrative output
Channel	Signups	Paying	Paid rate	Revenue / payer
Partner	520	300	57.7%	$2,180
Organic	770	420	54.5%	$1,840
Paid search	690	360	52.2%	$1,720
Social	430	210	48.8%	$1,540

What it proves: Partner traffic converts at the highest rate and produces the highest revenue per payer in this sample.

2. Feature lift for active versus canceled accounts

Which product behaviors are associated with retention?

SQL

SELECT FEATURE,
       AVG_ACTIVE_USES,
       AVG_CANCELED_USES,
       ACTIVE_TO_CANCELED_LIFT
FROM FORGEWELL_DEMO.SECURE.FEATURE_LIFT
ORDER BY ACTIVE_TO_CANCELED_LIFT DESC;

Illustrative output
Feature	Active uses	Canceled uses	Lift
Goals	8.6	2.1	4.1x
Reports	6.2	1.8	3.4x
Integrations	5.4	1.9	2.8x
Export	3.1	1.2	2.6x

What it proves: Goal setting has the widest usage gap between retained and canceled accounts.

3. Activation by channel

Where does the signup-to-paid funnel break?

SQL

SELECT CHANNEL,
       SIGNUPS,
       ACTIVATED,
       PAID,
       ACTIVATION_RATE,
       PAID_RATE
FROM FORGEWELL_DEMO.SECURE.ACTIVATION_FUNNEL
ORDER BY ACTIVATION_RATE DESC;

Illustrative output
Channel	Signups	Activated	Paid	Activation	Paid rate
Organic	770	620	420	80.5%	54.5%
Paid search	690	540	360	78.3%	52.2%
Partner	520	410	300	78.8%	57.7%
Social	430	300	210	69.8%	48.8%

What it proves: Social loses the most accounts before activation, while Partner converts the best after activation.

4. At-risk accounts

Which accounts need attention this week?

SQL

SELECT ACCOUNT_NAME,
       SUBSCRIPTION_STATUS,
       EVENTS_30D,
       OPEN_INVOICES,
       OPEN_AMOUNT_USD,
       RISK_SIGNALS
FROM FORGEWELL_DEMO.SECURE.CHURN_RISK
WHERE RISK_SIGNALS > 0
ORDER BY RISK_SIGNALS DESC, EVENTS_30D ASC;

Illustrative output
Account	Status	Events 30d	Open invoices	Open amount	Signals
Northstar Labs	past_due	12	2	$840	2
Harbor Fitness	active	8	1	$320	2
Cedar Studio	trialing	5	1	$0	1

What it proves: The highest-risk accounts combine low usage with unpaid invoices.

5. Revenue by usage quartile

Do the heaviest product users generate more revenue and churn less?

SQL

WITH usage AS (
  SELECT u.ACCOUNT_ID,
         u.LIFETIME_REVENUE_USD,
         u.EVENTS_90D,
         a.SUBSCRIPTION_STATUS,
         NTILE(4) OVER (ORDER BY u.EVENTS_90D) AS QUARTILE
  FROM FORGEWELL_DEMO.SECURE.REVENUE_BY_USAGE u
  JOIN FORGEWELL_DEMO.SECURE.ACCOUNT_360 a
    ON a.ACCOUNT_ID = u.ACCOUNT_ID
)
SELECT QUARTILE,
       COUNT(*) AS ACCOUNTS,
       ROUND(AVG(LIFETIME_REVENUE_USD), 0) AS AVG_REVENUE_USD,
       ROUND(
         AVG(CASE WHEN SUBSCRIPTION_STATUS = 'canceled' THEN 1 ELSE 0 END),
         3
       ) AS CHURN_RATE
FROM usage
GROUP BY 1
ORDER BY 1;

Illustrative output
Quartile	Accounts	Avg revenue	Churn rate
Q1 lowest usage	75	$640	31%
Q2	75	$1,120	22%
Q3	75	$1,760	14%
Q4 highest usage	75	$2,380	7%

What it proves: Revenue rises and churn falls as 90-day product usage increases.

6. Cortex Analyst question

Which channel has the highest revenue per paying account?

Cortex prompt

Which acquisition channel has the highest revenue per paying account, and how many paying accounts does it have?

Illustrative output
Expected answer	Value
Channel	Partner
Revenue per paying account	About $2,180
Paying accounts	300

What it proves: Cortex can answer the core channel question from FORGEWELL_SEMANTIC without writing SQL.

Schema reference

Every object in the share, with its grain and key columns. The six featured objects appear first. Search by object, description, or column name.

Filter objects

Showing 29 of 29 objects.

ACCOUNT_360Featured

One row per account

Plan, channel, region, industry, subscription status, lifetime revenue, and 90-day product usage.

Keys: ACCOUNT_ID

From	To	Note
`PENDO.ACCOUNTS.ID`	`STRIPE.CUSTOMER.METADATA:account_id`	Primary account key across product and billing.
`PENDO.VISITORS.ID`	`GA4.EVENT.USER_ID`	Visitor-level product and web behavior.
`PENDO.VISITORS.ACCOUNTID`	`PENDO.ACCOUNTS.ID`	Roll users up to accounts.
`PENDO.MATCHEDPAGEEVENTS.MATCHABLEID`	`PENDO.PAGES.PAGEID`	Page-matched events to page definitions.
`GA4.EVENT.USER_PROPERTY_ACCOUNT_ID`	`PENDO.ACCOUNTS.ID`	Values starting with `acct_` are accounts. `lead_` values are modeled leads.