kapa.ai

No, Session Replay itself cannot be implemented server-side — it requires a client-side SDK running in the user's app or browser to capture the actual user experience (DOM changes on web, or screen pixels on mobile). However, there is a related server-side feature worth knowing about:

While you can't record replays server-side, Mixpanel's Server-Side Stitching allows server-side events (sent via API, backend code, or warehouse imports) to be linked to existing client-side replays. It works by matching the event's timestamp and Distinct ID to an active replay session. [Server-Side Stitching] For example, if a Purchase Completed event is fired from your server, Mixpanel can infer which replay it belongs to and let you view what the user was doing at that moment. [Server-Side Stitching] To ensure this works correctly, you should call identify() from the client-side SDK so that both client and server events share the same Distinct ID. [Replay ID docs] So in summary:

Tak, Twoje rozumienie jest w zasadzie poprawne.

Ważne zastrzeżenie: źródła nie precyzują wprost, czy do średniej wliczani są wszyscy użytkownicy z kohorty, czy tylko ci, którzy wykonali zdarzenie transakcji. Jeśli chcesz mieć pewność co do mianownika, sprawdź to na małej próbce w interfejsie. Przedział czasu: jeśli ustawisz zakres dat obejmujący kilka dni rejestracji, raport pokaże wiersze dla poszczególnych kohort (np. dziennych), a także zagregowany wynik. Ta część jest moim wnioskiem z działania raportu Retention. Źródła nie opisują jej szczegółowo.

Wystarczy, że z każdą transakcją prześlesz wartość tej transakcji. Nie musisz wysyłać skumulowanego LTV. Dokumentacja dla modeli transakcyjnych zaleca wysyłanie wartości zakupu jako właściwości zdarzenia przy każdym zakupie, np. {"event_name": "Purchase completed", "properties": {"item": "clothing", "price": 100}}. [Revenue FAQ] Sumowaniem w czasie zajmie się Mixpanel. Jeśli chcesz analizować profit, a nie przychód, prześlij profit jako liczbową właściwość zdarzenia. Dokumentacja opisuje przychód (amount), więc to moja interpretacja. Jak to przeanalizować (raport Retention):

Ten sam typ raportu pokazuje skumulowane wydatki nowych użytkowników według kohort, np. po 5, 30 i 60 dniach. [Revenue Use Cases] Ograniczenia:

Infelizmente, as fontes de documentação do Mixpanel não contêm informações suficientes para responder com precisão a esse cenário específico de "integrar dois Data Views existentes em um terceiro". O que a documentação confirma sobre Data Views é que:

Como cada Data View é uma configuração independente de filtros [Data Views & Classification], não existe nativamente um conceito de "herdar" ou "mesclar" dois Data Views em um terceiro. Cada Data View precisa ter seus filtros definidos de forma independente. Para o seu caso, a alternativa mais próxima seria:

Recomendo entrar em contato com o suporte do Mixpanel para verificar se existe alguma forma avançada de configurar esse cenário, pois as fontes disponíveis não cobrem esse caso de uso específico.

Tak, dla Flutter również jest to możliwe! Możesz przekazać wiele właściwości naraz w jednym wywołaniu getPeople().set(), używając mapy (obiektu):

mixpanel.identify('USER_ID');

mixpanel.getPeople().set({
    'name': 'Jane Doe',
    'email': 'jane.doe@example.com',
    'plan': 'Premium',
    'company': 'Mixpanel'
});

Jedno wywołanie wystarczy — nie musisz wywoływać .set() osobno dla każdej właściwości. [Storing User Profiles]

Ważne: Pamiętaj, aby przed wywołaniem getPeople().set() wywołać mixpanel.identify(), żeby aktualizacja profilu była powiązana z właściwym użytkownikiem. [Storing User Profiles]

A borrowed property’s value is replaced under the following conditions:

The provided knowledge sources do not explicitly state whether the virtual Session Start event can be referenced within the formula of a custom property. The documentation explains that custom properties allow you to combine existing properties (event properties and user profile properties) using formula functions, rather than referencing events themselves directly within the custom property formula [Custom Properties]. While you can create custom event properties derived from event properties, the sources do not mention if virtual events like Session Start or their associated properties can be used to construct a custom property definition. However, you can use the Session Start event directly in standard report formulas (such as dividing Page Views by Session Start in an Insights report) [Use Cases; Session Controls in Reports].

Yes, an Event-Based Session can help you determine a landing page, provided that the event you define as the starting event includes the page URL [Event-Based Sessions; Session Properties]. Here is how it works and what to keep in mind:

Unlike timeout-based sessions (which look through the session for the first event containing the property), an event-based session defines the session start by a specific event you choose (such as "Page View" or "Login") [Event-Based Sessions; Session Properties]. Mixpanel associates properties onto the virtual Session Start event directly from that starting event [Session Properties].

For the Session Start event to determine the landing page:

If you configure an event like "Login" as your starting event, but "Login" does not track the URL or happens after a user has already browsed pages, the Session Start event will only reflect the URL where the login action occurred rather than the true landing page.

Once your event-based session has a page-load event set as the starting event, you can build an Insights report, select the Session Start event, and break down by Current URL to see your most common landing pages [Use Cases].

Yes, page views are dedicated events and they do count toward your billing volume.

(Note: If your organization is on an MTU-based plan, a page view is a qualifying event that counts an anonymous or identified visitor as an MTU, and it counts toward the total event volume used in the MTU guardrail calculation [MTU billing].)

In Mixpanel, the recommended way to define and analyze landing pages with timeout-based sessions is to build an Insights report measuring the Session Start event broken down by the Current URL property [Use Cases].

docs.mixpanel.com/_next/image?w=3840&q=75&…