Skip to content

How to use the data🔗

Analysts could work with data uploaded through Unified Logs using the following servises:

  • Hue for analysis data using SQL queries.
  • Jupyter Hub for analysis data using Python or R.
  • AeroStat for data visualizationcin custom dashboards.

How to access DWH data analysis services🔗

To work with DWH services, the following accesses are required:

  • If you have access to https://jira.astrum.team/, please create a task for access to DWH services in the GAMESTAT project.
  • MGVC studios could contact the curator for access.

How data is stored in DWH🔗

For studio analysts🔗

Studio analyst has access to the studio_<studio_name> database. In this database, analyst could use the following tables:

Available tables

  • studio_<studio_name>.mrgs_api_event_logs_vw — logs from a specific studio.
  • studio_<studio_name>.mrgs_game_profile_vw — profiles from a specific studio.
  • studio_<studio_name>.dict_<ID application>_<table_suffix> — dictionaries from a specific studio.

Please note that if a dictionary with the same name is already exists during its uploading, old dictionary will go to backups and be replaced by a new one.

For cross-studio analysts🔗

Cross-studio analysts can analyze data from all projects in the oda_mrgs database. In this database, analysts could use the following tables:

Available tables

  • oda_mrgs.mrgs_api_event_logs — logs for all studios
  • oda_mrgs.<profiles> — profiles for all studios

Dictionaries are located in the studio databases.

Important

If you need cross-studio analyst rights:

  • If you have access to https://jira.astrum.team/, please create a task for extended access to DWH services in the GAMESTAT project.
  • MGVC studios could contact the curator for access.

What other data is available in DWH🔗

In addition to Unified logs, analysts have access to data from the general MyGames systems. The studio_<studio_name> database will have views of this data, filtered by studio projects:

Available tables

  • 1Link
    • onelink_profiles_vw — Profiles.
    • onelink_payments_vw — Payments.
    • onelink_payments_adrevenue_vw — Ad monetization.
    • onelink_logins_vw (only for pc games) — Logins.
    • onelink_projects_vw — Projects dictionary.
    • onelink_traffic_dict_vw — Advertising campaigns dictionary.
  • MyTracker
    • mytracker_install_metrics_vw — Installs.
    • mytracker_launches_metrics_vw — Launches.
    • mytracker_payments_metrics_vw — Payments.
  • MRGS
    • mrgs_kafka_application_run_vw — Logins.
    • mrgs_kafka_payments_vw — Payments.
    • mrgs_usr_dev_vw — Mapping between user devices and accounts.
  • Terrabank
    • terrabank_payments_wo_dmr_vw — Payments.

Data usage tips🔗

  • In order to reduce the DWH storage load and recieve data faster, be sure to use a partition filter log_dt in your requests (WHERE log_dt = '2022-01-01')
Last update: 2025-01-21
Created: 2022-01-31