Skip to main content

Data Analytics

Feed a data warehouse, data lake, or business-intelligence platform with the operational data SECUTIX produces — contacts, orders, tickets, and product inventory — so you can build reporting, dashboards, and customer analytics on top of a consolidated view.

This pattern is push-based: you register your ingestion endpoints once and SECUTIX pushes each change to you in near real-time, via webhooks. Your platform receives the payloads, lands them in your warehouse, and models them for analysis. Each data domain is an independent feed, so you can start with the domains you need today and add the others as they become available.

Example use cases​

  • Land contacts, orders, tickets, and product inventory in a data warehouse or data lake as they change.
  • Analyse attendance and gate activity by joining ticket-control events with the orders that generated them.
  • Run deep historical or cross-domain analysis over the Datamart when the streaming feeds don't cover the dataset you need.

Architecture Overview​

Data Analytics Integration Architecture

Integration Steps​

The numbered steps below correspond to the flows shown in the architecture diagram. Each feed is configured by your SECUTIX administrator, who registers your ingestion endpoint URL and its authentication (NONE, Basic, or API key) — see How to Configure Webhook Feeds for Data Analytics? for the setup procedure, and Authentication & Authorization for obtaining API credentials.

  1. Contact Data Feed — SECUTIX pushes contact changes to your warehouse in near real time: whenever a contact is created, updated, or deleted (through the ticketshop, box office, or backoffice), the configured payload — individuals and structures, with the criteria, addresses, and opt-ins you selected — is delivered to your endpoint. Your platform implements the receiving endpoint. API reference: Contact Webhook.

  2. Order Data Feed (coming soon) — SECUTIX pushes finalized orders as they complete, carrying the order type, total amount, the individual operations (tickets, memberships, season passes), payment details, and the associated contact number — everything needed to analyse revenue, basket composition, and purchase behaviour. Your platform implements the receiving endpoint. API reference: Finalized Orders Webhook.

  3. Ticket Data Feed (coming soon) — SECUTIX pushes ticket-level data, so your warehouse can track ticket holdings and attendance alongside the orders that generated them. Two feeds are available: ticket details, and ticket-control (scan) events for access analytics. Your platform implements the receiving endpoints. API references: Push Tickets, Push Ticket Checks.

  4. Inventory Feed (coming soon) — for reporting that needs product reference data (which events, prices, and availabilities were on sale), SECUTIX pushes catalog changes the same way, across all product families. This is the same inventory webhook used by the distribution and CRM patterns; see Ticket Distribution and How to Sync Inventory with a CRM for details. Representative endpoints: Push On Sale Events, Push On Sale Event Availabilities, Push On Sale Event Prices.

  5. Analyse & Report — once the feeds land in your warehouse, you own the modelling. Join contacts, orders, and tickets into the schema your BI tooling expects, and build dashboards, segmentation, and reporting on a single consolidated dataset. Because the feeds are incremental, schedule a periodic reconciliation to detect and backfill any gaps from delivery failures or endpoint downtime.

Advanced Data Requirements: Datamart​

For advanced analytics that need a broader dataset than the streaming feeds provide, SECUTIX offers a Datamart — a managed, query-ready data store covering an extensive set of BI and reporting domains. It suits deep historical analysis and complex cross-domain queries that would be impractical to reconstruct from webhooks alone.

Two trade-offs distinguish it from the feeds above:

  • Latency — the Datamart is refreshed on a schedule rather than pushed in real time, so it is not suited to time-critical use cases.
  • Commercial — it is a paid add-on service, provisioned on request rather than enabled by default.

Accessing the Datamart​

The Datamart is an Oracle SQL database hosted on OCI, accessed over a VPN connection.

  1. Request provisioning — talk to your SECUTIX contact about your analytics requirements. They will confirm the reporting domains you need and provision access.
  2. Set up connectivity — a VPN connection is established between your infrastructure and the Datamart.
  3. Query with SQL — once connected, query the Datamart directly with standard SQL, across the provisioned reporting domains.

For the full catalogue of available reporting domains, see BI and Reporting Domains.

Beyond the standard feeds above, ad-hoc webhooks can be designed for specific use cases, with a delivery frequency tailored to each — from near real time to periodic batches. Talk to your SECUTIX contact about your analytics requirements.