28 Aug 14:20 UTC
User 3601c8f04ba

Nexo Bank MX · ACTIVE

Churn risk91
AUMS UUID
1c8f04ba-2e77-4a90-b3c1-8d05f2a61e37
Plan
Partner bundle · monthly
State
ACTIVE since 18 Jul 2026
Activated
41 days ago
Country
MX
Platform
iOS · iPhone 13
OS
iOS 18.2
App
3.4.1
Edge
QRO
Lifetime
0 min
Sessions 30d
14

Timeline

Newest first. Every event names the system that produced it — no single console could draw the row above or below its own.

6 events

  1. Play attempt failed — La Frontera

    NPAW3h 34m ago

    MFT-401 entitlement handshake rejected · 14th consecutive failure

    error code
    MFT-401
    error source
    player
    attempt
    14 of 14 failed
    F-2294open alert

  2. Included in alert F-2294

    AWG7h 48m ago

    Matched cohort: Nexo Bank MX · status ACTIVE · error MFT-401

    F-2294open alert

  3. Session started

    FIREBASE1d 3h ago

    iOS 18.2 · iPhone 13 · app 3.4.1 · cellular · Monterrey

    plays attempted
    3
    plays started
    0
    minutes watched
    0

  4. Payment succeeded

    REDSHFT3d 0h ago

    MXN 149.00 · card · vendor AWG-MX — second month billed with zero minutes watched

    amount
    MXN 149.00
    minutes watched to date
    0

  5. First auth success

    FIREBASE40d 20h ago

    Partner SSO · Nexo Bank MX

  6. Subscription activated

    AWG41d 0h ago

    Entitlement granted via Nexo Bank MX bundle · state PENDING → ACTIVE

    channel
    B2B partner
    product_id
    prd_nexo_bundle_v2

Identity spine

§7.2
  • AUMS UUID
    1c8f04ba-2e77-4a90-b3c1-8d05f2a61e37
  • AWG subscription
    sub_2Lp91xB7wF
  • Firebase user id
    1c8f04ba-2e77-4a90-b3c1-8d05f2a61e37
  • NPAW user id
    1c8f04ba-2e77-4a90-b3c1-8d05f2a61e37
  • Zendesk requester
    — no ticket raised
  • Datadog RUM id
    —

2 of 6 identifiers do not resolve for this user. Anything those systems know about them is absent from the timeline.

What is missing

  • DatadogNo APM or RUM for this user — the connector is not live, so client-side latency is absent from every event above.
  • CloudWatchEdge logs join at request level, so CDN behaviour appears only as the cohort signal on their alerts, never as a row here.