Overview

The Partner Data Warehouse is a strategic tool offered by Monta, aimed at facilitating seamless access to raw, operational data for its partners. This system serves as a bridge, enabling partners to delve into the extensive data ecosystem of Monta, which encompasses a wide range of operational domains such as charging services, charge points, team activities, user activity, and financial transactions.

Purpose and Utility

Data Access and Integration: Partners can effortlessly integrate the Partner Data Warehouse with most SQL-based interface or dashboarding tools. This flexibility ensures that partners can choose their preferred tools and environments to interact with Monta's data, enhancing usability and accessibility.

Insight Generation: The primary objective of the warehouse is to empower partners with the capability to extract valuable insights into user behaviors and operational efficiencies. It provides a comprehensive view of how users engage with Monta's services, including usage patterns of charging stations, team activities, and transactional behaviors.

Key Features

Comprehensive Data Coverage: The warehouse encompasses critical data related to Monta's core services. This includes detailed information on charges, charge points, teams, users, and transactions. Such a broad data spectrum allows for a holistic analysis of operational performance and user engagement.

Operational Insights: Partners can leverage this data to generate detailed insights into several key operational aspects. For instance, analyzing charging patterns can reveal user preferences and peak usage times, while data on charge points can shed light on their placement, utilization rates, and operational uptime.

Financial Analysis: By tying transactional data to users or charge points, partners can undertake financial analyses to understand the revenue streams and profitability associated with each user or service point. This can aid in identifying high-value segments or areas for operational improvement.

Data Quality: Monta ensures that the data shared through the warehouse is not only comprehensive but also cleaned and curated. This guarantees that partners can rely on the quality of the data for creating accurate and insightful dashboards or for conducting advanced analytical studies by joining multiple data sets

Change Log

Recent changes to transactions

(2025-05-28) We recently made 2 changes to the transactions table. This links to deeper re-engineering work at Monta, but also to efforts to make data in the Partner Data Warehouse align more cleanly with the raw data one can query from the API or see in the Hub.

• column transaction_idis now id
• columns to_currency_rate_eurand from_currency_rate_eur were removed.

Please contact us, if these changes are causing issues in your setup.

Coming changes to charges table -- June to August 2025

Overview of changes and motivation

(2025-05-28) We are redesigning the way our charges table is created. This links to deeper re-engineering work at Monta, but also to efforts to make data in the Partner Data Warehouse align more cleanly with the raw data one can query from the API or see in the Hub.

With these changes, we will replace the charges table and add two new tables charge_pricings and charges_config. Some columns currently in charges will in the future exist in the new tables. The three tables can be joined using charge_id.

COMING IN WEEK 23: Schema pages for the coming tables

Timing of the changes

• before 2025-06-15: New charges, charge_pricings, and charges_configtable will appear with the FUTURE__ preposition. No changes will be made to the existing table.
• 2025-07-15: Existing charges table will be renamed with DEPRECATED__ preposition. New tables will be available both with and without the FUTURE__ preposition allowing preparing your codebase for the future stable state.
• 2025-08-15: Tables with the DEPRECATED__ and FUTURE__ prepositions are dropped

Some highlighted changes in the charges table

• is_deleted_charge column is removed.
  • This column is always 0 in the current table, so no data is lost
• avg_renewable column is removed
• start_source, payment_method , payment_method_type and state columns have same universe of values but the values have different format
  • values are in upper case
  • values use _ separator instead of -

Roadmap 2025

This roadmap shows what new columns and tables we aim to add as the year moves along. This is non-committal and liable for change. If certain columns or tables are crucial for your operations, please reach out to your CSM.

---

April

New Tables

• plans

Columns to Existing Tables

transactions

• note
• to_operator_name
• from_operator_name
• to_wallet_vat_number
• from_wallet_vat_number
• exchange_rate (can be calculated from current to_eur and from_eur conversion rates)

teams

• partnerExternalId
• type

charge_keys

• team_id
• user_id

charge_pricing_breakdown

• operator_id

subscriptions

• serviceConfig

charge_points

• partnerExternalId
• maxKw
• isActive (Depends on whether state in DWH behaves like the API — a disabled CP might still show an "available" state)
• costGroupId
• sponsorPriceGroupId
• sponsorChargePointId reference

charge_point_sites

• partnerExternalId

---

May

• Expand charge_price_breakdown table to include specification of the price
• Add Sponsored Charge Points table

Columns to Existing Tables

transactions

• metadata

---

June

• Expand team_price_groups table to include:
  • List of price specifications
  • Add Tariffs