V4 Reporting Domain
What is a Reporting Domain?
TIXNGO is continuously computing several statistical data for reporting purposes based on operational events occurring in the system like ticket injection, download or transfer. These statistical data are stored in a dedicated database separated from the main operational database, and are regularly consolidated to optimize both performance and storage space. All this allows TIXNGO to be able to efficiently provide these statistical data, in almost-real-time or at any point in time in the past, without any impact on the core-business operations.
Sounds cool, how to access it?
In addition to some basic screens in Backoffice to access these statistical data, we decided to expose dedicated endpoints in the Organizer API to empower organizers to leverage these data in any way they see fit.
Reporting API Key must be used to access Reporting Domain
You can find it in the Profile screen (login to TIXNGO Backoffice with ADMIN role > top-right dropdown menu > My account)
Be careful with sharing this key as it gives access to ALL your TIXNGO data.
Great, I’m eager to query that API to feed my BI, Data lake or similar!
Go for it! Please find attached the YAML definition of those endpoints:
These endpoints are available under the following URL (adjust the first part to match your slot):
https://{slot}-api.tixngo.io/prod/v4.0/organizer/report/Please refer to the detailed documentation of every endpoint for more details:
Mmmh, API what? Can I use Excel or Power BI?
Yes, of course, as our APIs are compatible with these tools through Power Queries !
But be mindful of the volume of data involved!
If you have significant volume of data to analyze, Excel and Power BI desktop are NOT the right tools. In those contexts, direct API integration or Power BI services with incremental refresh activated MUST be used (see https://learn.microsoft.com/en-us/power-bi/connect-data/incremental-refresh-overview).
Here are some Excel and Power BI templates to illustrate how TIXNGO data could be leveraged for some common use cases, from high level (quick and efficient), to detailed (that can take significant time to load and refresh depending on the number of tickets):
Global events metrics:
Monthly injection report:
Global tickets & spectators analysis, with some fraud-oriented analysis:
Detailed tickets analysis, for instance to cross-check injection logic:
Mobile logs analysis, global trend & focus on errors:
These templates are provided as documentation and for illustration purposes only. They are NOT to be considered as part of the product and we will NOT provide support neither on their usage in production nor on their customization.
In Excel, please click Enable Content to allow this file to connect to our Reporting Domain.
In Excel, you will have to enter the required parameters in the first Setup sheet
Then go to the Ribbon bar > Data > Refresh All
When you create a Power BI report from the template, Power BI will ask you to provide the required parameters.
Make sure your parameters are correct (especially the Mobile App ID and Reporting API Key matching the environment) otherwise your will see no data or errors.
Generally, the last data refresh is stored in the report and displayed at the bottom of each page for clarity, and also avoid some “refresh craziness”.
The first time you will connect to an environment, Excel & Power BI will ask you to define the privacy level of this data source in a popup. Selecting Organizational should work in most contexts, but please refer to the corresponding Microsoft documentation for more details: Set privacy levels (Power Query) - Microsoft Support.
Do not share the file with the Reporting API Key filled in, unless you trust the recipient !