- Head over to the Publish tab on the left bar of the editor.
- Click on
Analyticsinside the deployment section on the top right of the deployment card.
Once you are on the analytics page, you shall find various sections on the page, that will show you a detailed analysis of your deployment.
You can configure live viewer state information to be forwarded to an external API.
- To do so, head over to the
Settingspage by clicking on your avatar on the top right of the page.
Settingspage, scroll down to the
Advancedsection and expand it.
- Clicking on the
ENABLE VIEWER STATE FORWARDINGwill reveal the following.
- An API secret will be created for your organization. This can be used to validate source identity by you.
- Enter an API endpoint for us to send requests to.
Every time there is an update to any viewer state (variables) in the organization (for all projects), the updated viewer state will be sent to the external endpoint. One possible use of this is to keep a database at your end updated with the progress of viewers across your experiences.
- Type of request:
authorization: JWT token created using shared API secret and
|organization_slug||The slug of your organization|
|deployment_slug||The slug of the deployment that the viewer visited|
|...||There might be more variables depending on viewer information.|
- deployment_slug is the link of the deployment specified in the publish page.
- organization_slug is the last part of the URL you see on your portal page (abcxyz in https://portal.gmetri.com/abcxyz) when you login to the portal.