Features and subscribers, side by side.

Union measures each feature as a funnel and compares the people who used it in their first week with those who did not: how many came back on day 7, with the size of both groups. Subscriptions sit beside the same people, on their profiles and on the Overview.

Start for free Read the docs

The problem. Sound familiar?

A list of event counts where the most-tapped screen is always Home.
A dashboard that says a feature “drives” subscriptions from a correlation in a small sample.

Where Union answers it.

01
Declare the feature once
`Union.feature("checkout")` in the SDK marks discovery, adoption and success; production and TestFlight builds create it.
02
Use against return
Day-7 return for people who used the feature in week one against those who did not, with the size of both groups.
03
Revenue beside it
Subscriptions from RevenueCat or Apple next to the same people, on their profiles and on the Overview.

In the docs: Declaring features

Questions.

Why not show the lift as a percentage that “drives” revenue?

Because people who choose a feature differ from those who do not. Union shows both groups and their sizes, and marks the comparison as correlation.

See who is using your app right now. Your first 100,000 events a month are free.