Production KPI evolution, refreshed with weekly segmented trends
Window: 14 Aug - 27 Sep 2026 - Latest complete day: 27 Sep 2026
Chart trend segments: 17-23 Aug, 24-30 Aug, 31 Aug-06 Sep, 07-13 Sep, 14-20 Sep, 21-27 Sep
Report generated: 28 September 2026 - Source: PostHog live queries - Production (106150) - https://eu.posthog.com
The latest segment (13-27 Sep) is compared with the prior matched-length segment (29 Aug-12 Sep). Onboarding moved 153 -> 1,817 (+1087.6%), while posts created were 526 -> 822 (+56.3%) and group joins were 61 -> 129 (+111.5%).
Daily active users and onboarded users
Each metric is shown across the full 45 days. Dashed trend lines follow complete Monday-Sunday weeks through 14-20 Sep; the first Fri-Sun days remain visible but are not treated as a week.
For weekly reporting, onboarded users means users counted by the Onboarding v2 ordered funnel final step, onboarding_v2_welcome_continue, with the dashboard's real-onboarder filters. This keeps the report aligned with the Onboarding v2 dashboard instead of the looser raw event count.
Active users weekly totals
Onboarded users weekly totals
Reach is distributed across all five main components: Feed 2,166, Buddy Match 1,695, Workouts 1,678, Chat 1,619, and Map 1,602 users. The narrow spread supports the interpretation that people are not stopping at one destination after onboarding; they are sampling the wider product.
Reach shows component discovery. The annotations below distinguish opening a component from performing a deeper action inside it.
| Component | Users reached | What happened after opening |
|---|---|---|
| Feed | 2,166 | Largest reach; likes were the main engagement action. |
| Buddy Match | 1,695 | Highest interaction volume, driven primarily by swipe decisions. |
| Workouts | 1,678 | Strong tab reach, but substantially fewer people progressed to deeper actions such as creating a workout. |
| Chat | 1,619 | Frequent page reach; 357 users opened a conversation from the Chat tab. |
| Map | 1,602 | Strong post-open engagement; about 900 users interacted with markers, previews, or map movement. |
The top-to-bottom reach difference is only 564 users; even Map, the smallest component, reaches 74% as many users as Feed. Discovery is broad. The next product question is therefore not “are users finding the components?” but “which components convert that reach into a meaningful deeper action?”
Posts created moved 526 -> 822. Feed reached users moved 1,009 -> 3,641, while engaged users moved 876 -> 1,707.
The weekly action set counts likes, post opens, comments, shares, and reposts. It moved 3,064 -> 10,526 events in the latest week. The 45-day daily engagement chart below uses the daily fields available in this monthly extract: likes + comments.
Feed metrics
Feed reached users = distinct users with PageFeed, feed_visit, or any feed_* event on that day.
Feed reached users weekly totals
Feed engaged users weekly totals
Feed likes + comments weekly totals
Distinct users weekly totals
Posts created weekly totals
Distinct creators weekly totals
Feed likes weekly totals
Distinct users weekly totals
Feed comments weekly totals
Distinct users weekly totals
feed_post_create_post carries field_filled. Photo and video can overlap on the same post, so posts with photo/video is counted as total published posts minus text/no-media posts. Text/no-media means no photo and no video; it may still include location.
Post media metrics
Posts with photo/video weekly totals
Posts with photo weekly totals
Posts with video weekly totals
Text/no-media posts weekly totals
| Action | 14-20 Sep events | 07-13 Sep events | Event change | 14-20 Sep users | 07-13 Sep users | User change |
|---|---|---|---|---|---|---|
| Like | 8,133 | 2,607 | +212.0% | 678 | 256 | +164.8% |
| Open post | 1,674 | 251 | +566.9% | 714 | 123 | +480.5% |
| Comment | 612 | 186 | +229.0% | 313 | 99 | +216.2% |
| Share | 88 | 16 | +450.0% | 43 | 10 | +330.0% |
| Repost | 19 | 4 | +375.0% | 18 | 3 | +500.0% |
Red lines show daily event volume. Gray lines show distinct users on the right axis, so it is easier to see whether growth comes from more people or more actions per person.
Like events weekly totals
Distinct users weekly totals
Open post events weekly totals
Distinct users weekly totals
Comment events weekly totals
Distinct users weekly totals
Share events weekly totals
Distinct users weekly totals
Repost events weekly totals
Distinct users weekly totals
Buddy Match users = distinct users who opened Buddy Match via explorer_pageview; it does not mean chat users. Positive actions = explorer_swipe_right + explorer_follow + explorer_swipe_right_button. Negative actions = explorer_swipe_left + explorer_swipe_left_button. Suggested-group checks = taps on explorer_check_group to inspect a suggested group; the event does not include a group ID, so the specific group cannot be identified. Each action chart is followed by its distinct-user chart and its average actions per distinct user. Weekly averages use the true distinct-user count for the whole week. All interactions = every explorer_* event except explorer_pageview. The technical events still use the legacy explorer_* prefix.
Buddy Match activity begins materially on 21 Sep. Read 21-27 Sep as the first rollout baseline, not a mature week-over-week comparison.
Buddy Match users weekly totals
Positive actions weekly totals
Distinct users with positive actions weekly totals
Average positive actions per user weekly rate
Negative actions weekly totals
Distinct users with negative actions weekly totals
Average negative actions per user weekly rate
All Buddy Match interactions weekly totals
Distinct Buddy Match interaction users weekly totals
Average Buddy Match interactions per user weekly rate
Swipe decisions weekly totals
Superlikes weekly totals
Say hello taps weekly totals
Suggested-group checks weekly totals
Filter actions weekly totals
Gender, role, sport level, and preferred sport send a selected value. Radius and address currently record usage but not the chosen value. Most preferred-sport selections contain multiple sports; the table shows the total plus the most common exact single-option selections.
| Filter | Selected option | Actions | Distinct users |
|---|---|---|---|
| Filter panel opened | — | 1,423 | 553 |
| Filters saved | — | 1,357 | 537 |
| Radius | Value not captured | 408 | 238 |
| Gender | Women | 315 | 298 |
| Gender | Men | 51 | 49 |
| Gender | Any | 31 | 29 |
| Address | Value not captured | 195 | 114 |
| Preferred sport | All selections | 126 | 89 |
| Preferred sport | Empty selection | 24 | 23 |
| Preferred sport | Running only | 4 | 4 |
| Preferred sport | Fitness only | 2 | 2 |
| Preferred sport | Weightlifting only | 2 | 2 |
| Preferred sport | Tennis only | 2 | 2 |
| Role | Athlete | 79 | 75 |
| Role | Any | 18 | 18 |
| Role | Coach | 4 | 4 |
| Sport level | Any | 13 | 13 |
| Sport level | Recreational | 12 | 11 |
| Sport level | Intermediate | 11 | 10 |
| Sport level | Advanced | 9 | 9 |
| Sport level | Professional | 5 | 5 |
Workouts created now uses workout_create_success, which begins on 21 Sep; earlier zeros mean the current trigger was not yet available. Own profile viewers are distinct people opening their own profile via profile_owner_pageview. Workouts created moved 0 -> 158, services created moved 9 -> 41, and profile follows moved 247 -> 769.
Profiles and creation metrics
Own profile viewers weekly totals
Profile follows weekly totals
Workouts created weekly totals
Database definition: non-deleted type = individual workouts where createdAt > startAt. This is a subset of all personal workouts and is consistent with past-workout imports.
Likely personal uploads weekly totals
Distinct uploaders weekly totals
Services created weekly totals
1,459 unique direct chats is the authoritative total: one database chat ID counts once, regardless of users, opens, or message volume. Of these, 674 had no qualifying text, 495 were one-way, and 290 were two-way. The gender-direction counts are subsets of the 785 chats with at least one message, so 655 man → woman is fully consistent with the 1,459 total.
| Metric | 21-27 Sep | Unit and interpretation |
|---|---|---|
| All direct chats | 1,459 | Unique production database chat IDs; authoritative total. |
| Man → woman | 655 | Database chats whose first qualifying text was sent by a man to a woman; subset of 785 messaged chats. The earlier 739 used a moving seven-day window, not this fixed report week. |
| Buddy Match chat pairs | 423 | Unique unordered user pairs on the PostHog explorer_chat event; an origin proxy, not a database-chat total. |
| Profile message actions | 335 | PostHog profile_message events; action volume, not users or chats. |
Each database chat ID is counted once. Message volume does not affect the result.
Among 785 direct chats with at least one qualifying text message, classified by the first sender and the other active participant.
PostHog profile_message action events. This is action volume—not distinct users, messages, or database chats.
Profile message actions weekly totals
PostHog origin proxy: one unique unordered user pair from explorer_chat counts once. Repeat taps or messages between the pair do not increase it. It cannot be joined exactly to a database chat ID.
New unique Buddy Match chat pairs weekly totals
Filters generated 914 actions from 351 users, led by workouts and sports. Trending reached more people than search (209 vs 68 users). Search is concentrated among a smaller repeat-use group, and 39 of 68 search users (57%) clicked a result.
Actions and distinct users share one scale, making repeat intensity visible as the gap between each pair of bars.
All 914 filter clicks, split by filter category.
Maps users weekly totals
Maps searches weekly totals
Map entity opens weekly totals
Filter changes on Maps across workouts, sports, posts, facilities, and tracks.
Map filters weekly totals
The clearest view is a category-and-state table. Workouts was the most-used toggle. Sport records that a selection changed and the number selected, but not the sport names, so the exact sports cannot be shown yet.
| Map filter | State / captured meaning | Actions | Distinct users |
|---|---|---|---|
| Workouts | On | 231 | 174 |
| Workouts | Off | 71 | 58 |
| Sport | Selection changed; chosen sport not captured | 215 | 176 |
| Posts | On | 139 | 115 |
| Posts | Off | 14 | 12 |
| Facilities | On | 125 | 90 |
| Facilities | Off | 17 | 16 |
| Tracks | On | 96 | 74 |
| Tracks | Off | 13 | 10 |
Production database counts use non-deleted rows created during the fixed GMT week. Personal means type = individual; group means type = group. The upload proxy is the personal subset where createdAt > startAt.
The earlier live query included 28 Sep, while this report uses the completed 21-27 Sep week. Including 28 Sep produces the earlier 5,258 personal records from 139 users, 362 group records from 210 creators, and 40 users in both sets. For the fixed week, 4,736 is valid specifically as the likely-upload subset—not as all personal workouts.
Database records and distinct users for the completed 21-27 Sep week. The personal upload proxy is a subset of all personal records.
The live 21-28 Sep result is 43 starts from 31 distinct users and 41 finishes from 26 distinct users. The completed 21-27 Sep slice was 37 starts and 37 finishes; adding 28 Sep contributes six starts and four finishes. The two-event gap suggests possible abandonment, but starts and finishes have no shared workout_id or tracking_session_id, so it is not an exact abandoned-workout count.
workout_tab_start_tracking_confirm records Start tracker presses; workout_tab_start_tracking_finish records finishes. The live period includes 28 Sep and therefore matches the referenced analysis.
Period totals
| KPI | 14-28 Aug | 29 Aug-12 Sep | 13-27 Sep | Latest vs prior |
|---|---|---|---|---|
| Active users daily total | 3,113 | 2,118 | 4,245 | +100.4% |
| Onboarded users | 557 | 153 | 1,817 | +1087.6% |
| Feed visitors | 1,370 | 1,009 | 3,641 | +260.9% |
| Feed engaged users | 1,189 | 876 | 1,707 | +94.9% |
| Posts created | 704 | 526 | 822 | +56.3% |
| Post creators | 528 | 398 | 578 | +45.2% |
| Posts with photo/video | 646 | 487 | 739 | +51.7% |
| Posts with photo | 510 | 382 | 528 | +38.2% |
| Posts with video | 193 | 149 | 271 | +81.9% |
| Text/no-media posts | 58 | 39 | 83 | +112.8% |
| Feed likes + comments | 13,374 | 8,414 | 12,025 | +42.9% |
| Feed likes + comments users | 949 | 678 | 1,093 | +61.2% |
| Feed likes | 12,625 | 7,780 | 11,198 | +43.9% |
| Feed like users | 872 | 610 | 972 | +59.3% |
| Feed open post events | 1,218 | 846 | 1,966 | +132.4% |
| Feed open post users | 477 | 348 | 855 | +145.7% |
| Feed comments | 749 | 634 | 827 | +30.4% |
| Feed comment users | 352 | 254 | 428 | +68.5% |
| Feed share events | 40 | 23 | 105 | +356.5% |
| Feed share users | 30 | 19 | 54 | +184.2% |
| Feed repost events | 20 | 11 | 23 | +109.1% |
| Feed repost users | 18 | 11 | 21 | +90.9% |
| Group joins | 230 | 61 | 129 | +111.5% |
| Groups created | 9 | 1 | 10 | +900.0% |
| Own profile viewers | 1,070 | 725 | 1,723 | +137.7% |
| Profile follows | 227 | 247 | 769 | +211.3% |
| Workouts created | 0 | 0 | 158 | n/a |
| Workout joins | 1 | 0 | 37 | n/a |
| Services created | 17 | 9 | 41 | +355.6% |