Introduction to the Stormly platform

Platform overview

For a big picture overview of the Stormly platform, there a three main elements:

  1. Projects — contains end-user's data.

  2. Templates — can be openen on top of end-user's project, basically like files that can be opened. Templates consist of plugins, questions and analytics based components such as reports, virtual user properties and user segments. Finally Insights are components that act as glue that brings all components together — using a simple to use JS/JSX API — and results in insights for end-users.

    Can be customized in any way, so each one can specialize in AB-testing, campaign marketing analytics, webshop user clustering, deployable predictions, etc. Due to it's customizability, they can go deep and focus on specific niches such as gaming companies, social apps or webshops.

  3. Results For End-Users — this can be in the form of Insights, plugin outputs, notifications, deployments and more.

Platform Overview details - Click for large version

Deciding what to build

The first step before you start building, is to decide what you'd like to build. There are roughly three options:

  1. Insight — glue that ties all template components such as plugins, questions, reports, intelligence models, virtual user properties and segments together using an easy to use JS API and JSX visualization layer. By using Insights you can fully automate any analytics process according to business needs and industry.

    An example would be an Insight that detects high-converting user segments and their properties. These properties and their conversion will be used to determine how much of an advertising budget should go to which user profiles. The Insight would ask two questions — one about the conversion event you want to optimize the campaign for and another for the monthly campaign budget.

    If this is what you need, go directly to the Insights documentation.

    Here is an Insight that provides campaign acquisiting details:

  2. Report plugin — uses a report as data source. Can be a timeseries (e.g. for forecasting), list of all users (e.g. for a/b testing) or a list of all events (e.g. for anomaly detection). Can be run by end-user from the Plugins drop-down menu on any report results page, or used in the Insight API to glue them together with other components.

    If this is what you need, go directly to the Report plugin documentation.

  3. Intelligence plugin — uses an intelligence model as data source. An intelligence model can have a binary goal (true or false), or no goal for unsupervised models like clustering. A few examples of available intelligence goals are:

  • User did event X.
  • Sum of some event property for user is at least X.
  • User came back after X days.
  • User had X sessions.
  • User complete step X of a funnel.
  • Any custom goal defined by SQL.

    If this is what you need, go directly to the Intelligence plugin documentation.