Skip to main content
Lobyco provides the data packages for analytical, reporting and financial use across the loyalty ecosystem. They reach you through Delta Sharing as structured, versioned tables. This page says what they are for, how often they refresh, and where the line runs between reporting on what happened and acting on it.
The packages are not an operational feed. Delta Sharing is batch-oriented and can carry processing delays, so a package is never the place for marketing activation or real-time eligibility decisions. Activation belongs in Nexus, the orchestration product.

​
Purpose

The data packages let a retailer:
  • Measure campaign, communication and loyalty performance.
  • Analyse customer engagement and behavioural trends.
  • Reconcile bonus and discount usage.
  • Allocate and split costs across funding entities, such as store owners.
  • Support accounting, settlement and financial reporting.
They are built for reporting and insight, not for operational activation.

​
Tiers

Each package comes in two tiers. More frequent refreshes mean more processing, compute and storage, so the Premium tier raises the Azure costs of the environment. Pick the tier that matches how fresh your reporting must be, and no fresher. Return of retailers is a Premium service in both tiers. The retailer is the source of truth for that data, and providing it carries a cost. Contact Lobyco Customer Success for the details.

​
Do

  • Use the packages for reporting, analytics and performance measurement.
  • Combine packages to analyse how loyalty, communication, app usage and transactions relate.
  • Build dashboards and financial reports for internal stakeholders.
  • Reconcile bonus balances, coupon redemptions and promotion funding.
  • Allocate costs and liabilities across participating business units.

​
Don’t

  • Do not use the packages as an operational feed for marketing activation.
  • Do not trigger communications or campaigns from Delta Shared tables.
  • Do not use the datasets for real-time eligibility decisions.
  • Do not replicate orchestration logic with analytical exports.
  • Do not use the datasets to check or validate activity configuration.

​
Why the separation exists

Delta Sharing is optimised for analytical workloads and financial reconciliation. It provides stable, auditable datasets that can include processing delays and batch behaviour. That suits reporting and settlement, not real-time activation. Operational marketing requires strict enforcement of consent, frequency controls, eligibility logic and delivery guarantees. Nexus, the orchestration product, is built for exactly that.
Last modified on October 12, 2026