Building the Loyalty Analytics Platform That Powers Targeted Campaigns Across AirAsia's Global Network

AirAsia needed a productizable loyalty management platform that could crunch years of traveler data, enforce user-based access controls, and let campaign managers pull ad-hoc reports without waiting on engineering. Ideas2IT built the data warehouse, the rules engine, and the reporting layer that made it possible.

Client

AirAsia

Industry

Aviation

Service

BI & Analytics

Engagement

Active · Ongoing

Team

10 engineers · FDE model

01 Challenge

AirAsia's loyalty program had accumulated years of traveler data with no platform capable of turning it into campaign intelligence. Campaign managers could not pull reports without engineering involvement, and a single data access misconfiguration could expose sensitive customer records across the wrong teams.

02 Solution

The architectural decision that shaped everything else was the data warehouse layer: Snowflake with security modules embedded across every component, so data access was enforced structurally rather than by policy. On that foundation, a metadata-driven ETL layer in Talend turned the reporting problem from a custom engineering task into a configuration one, and Drools powered the rules engine governing point allocation.

03 Outcome

Campaign report turnaround dropped 70%, query throughput quadrupled, and every campaign manager gained self-serve access to ad-hoc and drill-down reporting. The platform is role-secured, productized, and absorbs new campaign logic without rebuilding the reporting layer.

Phase 01

Data Warehouse & Reporting Foundation

Data warehouse and ETL foundation: structured, secured, and built to run without engineering in the loop

The first architectural decision was the data layer: Snowflake as the warehouse, with security modules built across every component for storage of sensitive customer data, so user-based access was structural rather than a setting that could be misconfigured.

that foundation,
  1. Talend handled ETL using SNL and configurable data-driven jobs, turning the pipeline from a custom engineering exercise into a replicable configuration.
  2. The metadata models Ideas2IT developed were the key to the reporting layer: instead of handcrafted queries per report, campaign managers could compose ad-hoc reports against a model that already understood the loyalty data structure.
  3. Initial reports ran through Jasper. Drill-down capability came via Tableau, giving campaign managers the depth to investigate anomalies in loyalty data without raising a ticket.
DELIVERABLES
  • Snowflake data warehouse
  • Talend ETL pipeline (SNL, configurable data-driven jobs)
  • Metadata models for ad-hoc reporting
  • Jasper canned report layer
  • Tableau drill-down reports
  • Role-based data access controls

Phase 02

Rules Engine & Campaign Intelligence

Loyalty Point Calculation Engine: rules-based allocation, workflow approvals, and campaign feedback loop

The second layer was the rules engine governing how loyalty points were calculated, allocated, and approved. Ideas2IT built the Loyalty Point Calculation Engine on Drools, a production-grade rules engine that separated campaign logic from application code.

  1. This meant campaign rules, tier thresholds, and point allocation logic could be updated by configuring rules rather than releasing code.
  2. The workflow layer handled approvals and notifications at each step of the loyalty lifecycle, giving campaign operations teams visibility and control without touching engineering.
  3. The final component was the feedback loop: campaign performance results fed back into the analytics engine, so each campaign cycle produced data that tuned the next one. Redis handled session and cache management to keep response times consistent across the platform under concurrent campaign load.
DELIVERABLES
  • Drools Loyalty Point Calculation Engine
  • Workflow approval and notification layer
  • Campaign performance feedback pipeline
  • Redis cache layer
  • ReactJS + Redux campaign management UI
  • Role-based campaign allocation and override rules

The Outcome

A loyalty platform built to run campaigns

Category Metric Description
Reduction in campaign report turnaround time 70% Metadata-driven ad-hoc reporting replaced manual engineering extraction. Campaign managers could compose, filter, and run their own reports without raising a ticket, collapsing the cycle from days to minutes.
Increase in loyalty data query throughput Snowflake's columnar warehouse replaced prior OLTP-style queries against transactional data. Query performance scaled with data volume rather than degrading under it.
Campaign managers enabled with self-serve reporting 100% Role-based access controls enforced in Snowflake, combined with Jasper's filterable report layer, made every campaign manager independent of engineering for standard and ad-hoc reporting needs.
Campaign logic updates Zero code
releases required
The Drools rules engine separated campaign configuration from application code. Tier thresholds, point allocation rules, and role-based overrides became configuration changes, not deployments.
Concurrent platform load No degradation
at peak
Redis cache layer maintained response consistency under multi-market concurrent sessions, absorbing traffic spikes without engineering intervention.
Cross-market data exposure incidents 0 Structural security modules in Snowflake prevented misconfiguration-based data leakage across market boundaries, meeting compliance requirements by design rather than by policy enforcement.
The platform's results were a consequence of two architectural decisions made early: Snowflake with security embedded by design rather than bolted on, and metadata-driven reporting that separated data structure from query composition. Both decisions made campaign managers independent of the engineering team. The Drools rules engine extended that independence to campaign logic itself. AirAsia's loyalty program could now act on its own data at the speed of a campaign cycle, not an engineering sprint.