Reading the Events tab
Last updated: May 5, 2026
The Events tab shows a complete chronological record of everything that has happened on an account or subscription. Always check it before escalating on a complex issue.
What each event record includes
Timestamp — time the event occurred, in UTC
Event type — what happened (e.g. subscription.activated, payment.failed)
Source — what triggered the event: subscriber, partner, or system
Status / outcome — succeeded or failed
Metadata — error codes, plan IDs, carrier response codes
Common event types
Event type | What it means |
subscription.created | Subscription record created — does not mean service is active yet |
subscription.activated | Service is live and billing has started |
subscription.canceled | Cancellation confirmed |
subscription.resumed | Canceled subscription reactivated — cancellation removed, auto-renewal restored |
payment.succeeded | Payment processed successfully |
payment.failed | Payment attempt failed — check metadata for decline reason |
sim.profile_downloaded | eSIM profile downloaded to a device |
sim.profile_deleted | eSIM profile removed from a device |
porting.requested | Port-in request submitted to losing carrier |
porting.completed | Port-in fully complete — number is live |
porting.failed | Port-in rejected — check metadata for rejection reason |
Tips for using Events effectively
Read oldest to newest — sequence matters. A failed event later in the log often has its cause in an earlier one.
Check the source field — critical for disputes: was this triggered by the subscriber, partner, or system?
Look for gaps — a missing subscription.activated after subscription.created means the subscription never fully activated.
Check metadata on failed events — often points directly to the cause. Include these when escalating to Gigs support.
This article doesn't cover:
Getting started →Getting started with the Gigs Dashboard
Manage subscriptions →How to manage subscriptions in the Dashboard