Limitations

Limitations include functional limitations and technical limitations.

Functional Limitations

  • Real-time ingestion is not yet available; the current release supports scheduled batch (T+1) pipelines only.
  • Event-level and journey-level interactions are not included and will be introduced as part of the expanded interaction layer.
  • Dashboards, monitoring, and operational visibility are not provided in this version; an observability layer is planned.
  • External API access is not exposed; data consumption currently happens via database views.
  • Formal reconciliation and audit frameworks are deferred to the next release cycles.
  • Unica application metadata is not captured, including report catalogs or report-definition registries.
  • Offer-level analytics is not yet supported:
    • No metrics are available at the campaign + offer level.
    • No ability to compute “offers served / offers given” counts.
  • Offer funnel stages (consider, commit, explore, fulfill, usage) are not modeled, preventing funnel-style behavioral analysis.
  • Campaign-level financial metrics are not available, including:
    • Gross revenue
    • Contact cost and cost per contact
    • Average revenue per response, net revenue, net profit
  • ROI and incremental ROI calculations cannot be generated due to absence of structured revenue/cost attribution and control-vs-target splits.
  • Operational timing indicators remain incomplete, including:
    • No explicit last run date per campaign
    • No measurement of responses received after campaign expiration
  • Cell- and segment-level performance is not yet modeled, meaning:
    • No metrics at campaign + cell level (responses, lift, ROI, etc.)
    • No metrics at campaign + segment level
  • Non-contacted responder classification is not implemented:
    • Cannot identify responders who were not contacted
    • No support for cell-level or offer-level non-contacted responder counts
  • Control group detail is limited; distinct responders at campaign/cell/offer level are not stored explicitly.
  • Offer master data is incomplete; there is no clean offer-dimension structure with standardized attributes.
  • Offer-level revenue and ROI cannot be computed, as revenue is not allocated to offers or offer–campaign combinations.
  • Initiative-level financial analytics are not supported due to missing foundational financial metrics.
  • Several metrics that can be derived today (for example, responder rate, lift over control) are not materialized as explicit fields, increasing reliance on semantic/BI logic.
  • UA_DtlContactHist stores tracking of personalized offer versions delivered to individual audience members is for Interact/campaign, and this will be done in the coming release.
  • The accuracy and completeness of 360-degree out-of-box features are wholly dependent on the quality and volume of source data provided by campaign and customer systems. Any gaps, inconsistencies, or deficiencies in upstream data will directly affect the fidelity of the calculated features and downstream insights.

Technical Limitations

  • Event-streaming integration (Kafka/Flink, etc.) is not included in this version.
  • Lineage visualization is not available; lineage exists in metadata but has no UI exposure
  • Retention and archival policies are not implemented in the pipelines and will be formalized in future releases.
  • Self-service DAG deployment and automation are not yet part of the orchestration framework.
  • Late-arrival and suspense data processing mechanisms will be implemented in the coming release.