Priori Signal

Home/Platform/Data model

All solutions

Data model

Give every chart, prediction, app, and AI answer the same description of your business.

Connect your customer, acquisition, and payment records. Define how they relate and how your metrics are calculated. Apps, dashboards, and AI use those same definitions, while predictions stay linked to the customers or sources they describe.

Data model

Everything you already have

Databases and APIs, but also the portals and spreadsheets that were never built to hand data over. It all lands in one place, joined and kept current.

App databaseAffiliate networksCRMTrackersPayment processorSpreadsheets

Your business as real objects

Affiliates, users, payments, chargebacks. Each one a real thing on one map, not a row in a table.

Joined the way they connect in reality: this user came from that campaign, paid, earned the payout, then charged back six weeks later. The map holds the whole chain.

A context the AI understands. This is the context layer: models and agents reason over things they actually know, the objects and how they relate.

AI context layer
AffiliateCampaignUserConversionPurchaseOfferChargebackMID

Everything downstream reads the context layer

Analytics, machine learning, agents, and anomaly detection share the same definitions, so every answer agrees.

Connect the customer history, define shared metrics, then use the same foundation across Signal.

Describe the business records

Raw data records what happened, but table and column names rarely explain the business on their own. The data model adds that meaning. Objects represent things such as a customer, acquisition source, payment, or chargeback. Attributes describe them, such as a customer's country or a payment's date and amount.

Relationships connect the objects. A source acquired a customer. The customer made a payment. A later dispute belongs to that payment. Priori also calls this connected model an ontology: one map of the objects and relationships the business uses.

Human in the loop

Your team

nothing acts without your sign-off

Interfaces & agents

Priori Lens

BI & dashboards

Priori Sentry

Anomaly detection

Priori Lab

ML models in production

real-time inference

Priori Runner

Proactive agents

your sign-off

Tools

via MCP

One shared context

The context layer

one live model of your operation, in a form AI can reason over

Semantics & ontology

Knowledge graph

Wiki

Agent skills & workflows

Business systems

Systems of record

app databasepaymentsCRM

Systems of data

warehousespreadsheetstrackers

Systems of knowledge

docs & wikisrepositoriesNotion

Systems of engagement

Slackemailsupport

outcomes feed back into the context layer, so it keeps learning

Define how records connect

A plausible join can still produce the wrong answer. Join one customer to several payments at the wrong level and the customer row is duplicated. Sum revenue after another one-to-many join and the same payment can be counted more than once. An inner join can also remove customers who never paid.

The shared model records which fields connect, the direction of the relationship, and the level of detail in each object. Queries can then follow an approved path and preserve the population being measured instead of rebuilding the join from nearby column names.

Compare and forecast from one metric definition

A metric is more than a label and a formula. Revenue may mean billed revenue or net revenue, use a payment date or booking date, and include or exclude refunds, tests, or particular payment states. Those choices belong in the shared definition.

VAMP ratio is one example of a calculation with several rules about which records count. Once you define it and connect the relevant records, you can compare it across traffic sources, countries, or customer cohorts. Investigate which groups account for a change, using the same calculation for each comparison.

Use that history to train a machine learning model to forecast the metric, with uncertainty shown alongside the estimate. Compare where sources stand today with where they are expected to go. Your team can use those comparisons in an app, monitor them in a dashboard, or ask the AI to investigate them. The same approach applies to conversion rate, revenue per paying customer, and other business metrics.

Data models and machine learning models

The data model describes what the business records mean and how they connect. A machine learning model learns from selected history to estimate an outcome. For example, it may estimate a customer's lifetime value from information available at a defined point in time.

After evaluation, the prediction returns to the shared data model as an output linked to that customer. Recorded revenue and predicted lifetime value remain distinct, but applications can use both without creating a separate customer definition.

Customer view showing recorded net revenue beside predicted lifetime value and customer actions
One customer object with recorded value, machine learning outputs, and the actions that can use them.

Build several tools on one foundation

The path is simple: raw records become a shared data model; machine learning adds predictions; apps, dashboards, BI, APIs, and AI work from both. A new interface does not need to redefine the customer, the source, or net revenue.

This context gives AI analytics approved fields, relationships, and calculations, reducing the information it needs to guess. Important results remain available for review. The same foundation also supports forecasting and flexible custom apps and dashboards.

  • Connect the history. Follow a customer from acquisition through activity, payments, and later outcomes.
  • Keep definitions shared. Relationships and metrics stay consistent across different interfaces.
  • Place predictions in context. Machine learning outputs remain linked to the records and objects they describe.