Every event on the Stigg platform is audited, and visibility for these events is available via the Activity Log.
Using the Activity Log users can answer the following questions:
Thus, the Activity Log serves as an audit log for actions on the Stigg platform and can also be useful for troubleshooting.
The Activity Log is available on the Stigg Growth plan or higher, and provides accurate information for all events that took place on May 22nd, 2024 or later.
Every event includes the following properties:
Type | Description |
---|---|
Stigg application | An event that was triggered by a logged in user in the Stigg app |
Backend SDK | An event that was triggered by the backend SDK, for example: by a customer or migration script |
Frontend SDK | An event that was triggered by the frontend SDK, for example: by a customer |
Salesforce | An event that was triggered by the CRM integration with Salesforce |
Stripe | An event that was triggered by the billing integration with Stripe |
AWS Marketplace | An event that was triggered by the integration with the AWS Marketplace |
Import process | An event that was triggered by an import process into Stigg |
Subscription migration | An event that was triggered by a subscription migration |
System | An event that was triggered by an automation of the Stigg platform |
Stigg support | An event that was triggered by a Stigg support representative |
The general log provides visibility for all of the events that took place on the selected Stigg environment and is accessible via the “Activity” item on the left navigation pane.
An entity-specific activity log is accessible via the “Activity” tab of the customer, subscription plan and add-on entities.
The entity-specific log includes only events that are relevant for the specific entity; thus, making troubleshooting easier.
Users can copy links to specific events by clicking on the “Copy event link” button in the header of a specific event.
Event links can be shared with other users that have access to the Stigg app, which can also assist with troubleshooting.
Stigg allows you to easily navigate between different events by either selecting the relevant event from the Activity Log table, or via the arrows at the footer of a specific events.
Query
Variables
More details about the GraphQL API can be found here:
Usage events are accessible via a dedicated Usage Event Log:
Every event on the Stigg platform is audited, and visibility for these events is available via the Activity Log.
Using the Activity Log users can answer the following questions:
Thus, the Activity Log serves as an audit log for actions on the Stigg platform and can also be useful for troubleshooting.
The Activity Log is available on the Stigg Growth plan or higher, and provides accurate information for all events that took place on May 22nd, 2024 or later.
Every event includes the following properties:
Type | Description |
---|---|
Stigg application | An event that was triggered by a logged in user in the Stigg app |
Backend SDK | An event that was triggered by the backend SDK, for example: by a customer or migration script |
Frontend SDK | An event that was triggered by the frontend SDK, for example: by a customer |
Salesforce | An event that was triggered by the CRM integration with Salesforce |
Stripe | An event that was triggered by the billing integration with Stripe |
AWS Marketplace | An event that was triggered by the integration with the AWS Marketplace |
Import process | An event that was triggered by an import process into Stigg |
Subscription migration | An event that was triggered by a subscription migration |
System | An event that was triggered by an automation of the Stigg platform |
Stigg support | An event that was triggered by a Stigg support representative |
The general log provides visibility for all of the events that took place on the selected Stigg environment and is accessible via the “Activity” item on the left navigation pane.
An entity-specific activity log is accessible via the “Activity” tab of the customer, subscription plan and add-on entities.
The entity-specific log includes only events that are relevant for the specific entity; thus, making troubleshooting easier.
Users can copy links to specific events by clicking on the “Copy event link” button in the header of a specific event.
Event links can be shared with other users that have access to the Stigg app, which can also assist with troubleshooting.
Stigg allows you to easily navigate between different events by either selecting the relevant event from the Activity Log table, or via the arrows at the footer of a specific events.
Query
Variables
More details about the GraphQL API can be found here:
Usage events are accessible via a dedicated Usage Event Log: