google-meridian 1.3.0__tar.gz → 1.3.2__tar.gz

google_meridian-1.3.2/MANIFEST.in

@@ -0,0 +1,2 @@
+global-exclude *_test.py
+include meridian/templates/*

google_meridian-1.3.2/PKG-INFO

@@ -0,0 +1,209 @@
+Metadata-Version: 2.4
+Name: google-meridian
+Version: 1.3.2
+Summary: Google's open source mixed marketing model library, helps you understand your return on investment and direct your ad spend with confidence. 
+Author-email: The Meridian Authors <no-reply@google.com>
+Project-URL: homepage, https://github.com/google/meridian
+Project-URL: repository, https://github.com/google/meridian
+Project-URL: changelog, https://github.com/google/meridian/blob/main/CHANGELOG.md
+Project-URL: documentation, https://developers.google.com/meridian
+Keywords: mmm
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Topic :: Other/Nonlisted Topic
+Classifier: Topic :: Scientific/Engineering :: Information Analysis
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: arviz
+Requires-Dist: altair>=5
+Requires-Dist: immutabledict
+Requires-Dist: joblib
+Requires-Dist: natsort<8,>=7.1.1
+Requires-Dist: numpy<3,>=2.0.2
+Requires-Dist: pandas<3,>=2.2.2
+Requires-Dist: patsy<1,>=0.5.3
+Requires-Dist: scipy<2,>=1.13.1
+Requires-Dist: statsmodels>=0.14.5
+Requires-Dist: tensorflow<2.21,>=2.18
+Requires-Dist: tensorflow-probability<0.26,>=0.25
+Requires-Dist: tf-keras<2.21,>=2.18
+Requires-Dist: xarray
+Provides-Extra: dev
+Requires-Dist: pytest>=8.0.0; extra == "dev"
+Requires-Dist: pytest-xdist; extra == "dev"
+Requires-Dist: pylint>=2.6.0; extra == "dev"
+Requires-Dist: pyink; extra == "dev"
+Provides-Extra: colab
+Requires-Dist: psutil; extra == "colab"
+Requires-Dist: python-calamine; extra == "colab"
+Provides-Extra: and-cuda
+Requires-Dist: tensorflow[and-cuda]<2.21,>=2.18; extra == "and-cuda"
+Provides-Extra: mlflow
+Requires-Dist: mlflow; extra == "mlflow"
+Provides-Extra: jax
+Requires-Dist: jax==0.5.3; extra == "jax"
+Requires-Dist: jaxlib==0.5.3; extra == "jax"
+Requires-Dist: tensorflow-probability[substrates-jax]==0.25.0; extra == "jax"
+Provides-Extra: schema
+Requires-Dist: mmm-proto-schema; extra == "schema"
+Requires-Dist: semver; extra == "schema"
+Dynamic: license-file
+
+# About Meridian
+
+Marketing mix modeling (MMM) is a statistical analysis technique that measures
+the impact of marketing campaigns and activities to guide budget planning
+decisions and improve overall media effectiveness. MMM uses aggregated data to
+measure impact across marketing channels and account for non-marketing factors
+that impact sales and other key performance indicators (KPIs). MMM is
+privacy-safe and does not use any cookie or user-level information.
+
+Meridian is an MMM framework that enables advertisers to set up and run their
+own in-house models. Meridian helps you answer key questions such as:
+
+*   How did the marketing channels drive my revenue or other KPI?
+*   What was my marketing return on investment (ROI)?
+*   How do I optimize my marketing budget allocation for the future?
+
+Meridian is a highly customizable modeling framework that is based on
+[Bayesian causal inference](https://developers.google.com/meridian/docs/causal-inference/bayesian-inference).
+It is capable of handling large scale geo-level data, which is encouraged if
+available, but it can also be used for national-level modeling. Meridian
+provides clear insights and visualizations to inform business decisions around
+marketing budget and planning. Additionally, Meridian provides methodologies to
+support calibration of MMM with experiments and other prior information, and to
+optimize target ad frequency by utilizing reach and frequency data.
+
+If you are using LightweightMMM, see the
+[migration guide](https://developers.google.com/meridian/docs/migrate) to help
+you understand the differences between these MMM projects.
+
+## Install Meridian
+
+Python 3.11 or 3.12 is required to use Meridian. We also recommend using a
+minimum of 1 GPU.
+
+Note: This project has been tested on T4 GPU using 16 GB of RAM.
+
+To install Meridian, run the following command to automatically install the
+latest release from PyPI.
+
+*   For Linux-GPU users:
+
+    Note: CUDA toolchain and a compatible GPU device is necessary for
+    `[and-cuda]` extra to activate.
+
+    ```sh
+    $ pip install --upgrade google-meridian[and-cuda]
+    ```
+
+*   For macOS and general CPU users:
+
+    Note: There is no official GPU support for macOS.
+
+    ```sh
+    $ pip install --upgrade google-meridian
+    ```
+
+Alternatively, run the following command to install the most recent, unreleased
+version from GitHub.
+
+*   For GPU users:
+
+    ```sh
+    $ pip install --upgrade "google-meridian[and-cuda] @ git+https://github.com/google/meridian.git"
+    ```
+
+*   For CPU users:
+
+    ```sh
+    $ pip install --upgrade git+https://github.com/google/meridian.git
+    ```
+
+We recommend to install Meridian in a fresh
+[virtual environment](https://virtualenv.pypa.io/en/latest/user_guide.html#quick-start)
+to make sure that correct versions of all the dependencies are installed, as
+defined in [pyproject.toml](https://github.com/google/meridian/blob/main/pyproject.toml).
+
+## How to use the Meridian library
+
+To get started with Meridian, you can run the code programmatically using sample
+data with the [Getting Started Colab][3].
+
+The Meridian model uses a holistic MCMC sampling approach called
+[No U Turn Sampler (NUTS)](https://www.tensorflow.org/probability/api_docs/python/tfp/experimental/mcmc/NoUTurnSampler)
+which can be compute intensive. To help with this, GPU support has been
+developed across the library (out-of-the-box) using tensors. We recommend
+running your Meridian model on GPUs to get real time optimization results and
+significantly reduce training time.
+
+## Meridian Documentation & Tutorials
+
+The following documentation, colab, and video resources will help you get
+started quickly with using Meridian:
+
+| Resource                    | Description                                    |
+| --------------------------- | ---------------------------------------------- |
+| [Meridian documentation][1] | Main landing page for Meridian documentation.  |
+| [Meridian basics][2]        | Learn about Meridian features, methodologies, and the model math. |
+| [Getting started colab][3]  | Install and quickly learn how to use Meridian with this colab tutorial using sample data. |
+| [User guide][4]             | A detailed walk-through of how to use Meridian and generating visualizations using your own data. |
+| [Pre-modeling][5]           | Prepare and analyze your data before modeling. |
+| [Modeling][6]               | Modeling guidance for model refinement and edge cases. |
+| [Post-modeling][7]          | Post-modeling guidance for model fit, visualizations, optimizations, refreshing the model, and debugging. |
+| [Migrate from LMMM][8]      | Learn about the differences between Meridian and LightweightMMM as you consider migrating. |
+| [API Reference][9]          | API reference documentation for the Meridian package. |
+| [Reference list][10]        | White papers and other referenced material.    |
+
+[1]: https://developers.google.com/meridian
+[2]: https://developers.google.com/meridian/docs/basics/meridian-introduction
+[3]: https://developers.google.com/meridian/notebook/meridian-getting-started
+[4]: https://developers.google.com/meridian/docs/user-guide/installing
+[5]: https://developers.google.com/meridian/docs/pre-modeling/collect-data
+[6]: https://developers.google.com/meridian/docs/advanced-modeling/control-variables
+[7]: https://developers.google.com/meridian/docs/post-modeling/model-fit
+[8]: https://developers.google.com/meridian/docs/migrate
+[9]: https://developers.google.com/meridian/reference/api/meridian
+[10]: https://developers.google.com/meridian/docs/reference-list
+
+## Support
+
+**Questions about methodology**: Please see the [Modeling](https://developers.google.com/meridian/docs/basics/meridian-introduction) tab in the technical documentation.
+
+**Issues installing or using Meridian**: Feel free to post questions in the
+[Discussions](https://github.com/google/meridian/discussions) or [Issues](https://github.com/google/meridian/issues) tabs of the Meridian GitHub repository. The Meridian team responds to
+these questions weekly in batches, so please be patient and don't reach out
+directly to your Google Account teams.
+
+**Bug reports**: Please post bug reports to the [Issues](https://github.com/google/meridian/issues)
+tab of the Meridian GitHub repository. We also encourage the community to share
+tips and advice with each other on the [Issues](https://github.com/google/meridian/issues)
+tab. When our team addresses or resolves a new bug, we will notify you through
+the comments on the issue.
+
+**Feature requests**: Please post these to the [Discussions](https://github.com/google/meridian/discussions)
+tab of the Meridian GitHub repository. We have an internal roadmap for Meridian
+development, but would love your inputs for new feature requests so that we can
+prioritize them based on the roadmap.
+
+**Pull requests**: These are appreciated but are very difficult for us to merge
+because the code in this repository is linked to Google internal systems and has
+to pass internal review. If you submit a pull request and we believe that we can
+incorporate a change in the base code, we will reach out to you directly about
+this.
+
+## Citing Meridian
+
+To cite this repository:
+
+<!-- mdlint off(SNIPPET_INVALID_LANGUAGE) -->
+```BibTeX
+@software{meridian_github,
+  author = {Google Meridian Marketing Mix Modeling Team},
+  title = {Meridian: Marketing Mix Modeling},
+  url = {https://github.com/google/meridian},
+  version = {1.3.2},
+  year = {2025},
+}
+```

{google_meridian-1.3.0 → google_meridian-1.3.2}/README.md

@@ -151,7 +151,7 @@ To cite this repository:
   author = {Google Meridian Marketing Mix Modeling Team},
   title = {Meridian: Marketing Mix Modeling},
   url = {https://github.com/google/meridian},
-  version = {1.3.0},
+  version = {1.3.2},
   year = {2025},
 }
 ```

google_meridian-1.3.2/google_meridian.egg-info/PKG-INFO

@@ -0,0 +1,209 @@
+Metadata-Version: 2.4
+Name: google-meridian
+Version: 1.3.2
+Summary: Google's open source mixed marketing model library, helps you understand your return on investment and direct your ad spend with confidence. 
+Author-email: The Meridian Authors <no-reply@google.com>
+Project-URL: homepage, https://github.com/google/meridian
+Project-URL: repository, https://github.com/google/meridian
+Project-URL: changelog, https://github.com/google/meridian/blob/main/CHANGELOG.md
+Project-URL: documentation, https://developers.google.com/meridian
+Keywords: mmm
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Topic :: Other/Nonlisted Topic
+Classifier: Topic :: Scientific/Engineering :: Information Analysis
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: arviz
+Requires-Dist: altair>=5
+Requires-Dist: immutabledict
+Requires-Dist: joblib
+Requires-Dist: natsort<8,>=7.1.1
+Requires-Dist: numpy<3,>=2.0.2
+Requires-Dist: pandas<3,>=2.2.2
+Requires-Dist: patsy<1,>=0.5.3
+Requires-Dist: scipy<2,>=1.13.1
+Requires-Dist: statsmodels>=0.14.5
+Requires-Dist: tensorflow<2.21,>=2.18
+Requires-Dist: tensorflow-probability<0.26,>=0.25
+Requires-Dist: tf-keras<2.21,>=2.18
+Requires-Dist: xarray
+Provides-Extra: dev
+Requires-Dist: pytest>=8.0.0; extra == "dev"
+Requires-Dist: pytest-xdist; extra == "dev"
+Requires-Dist: pylint>=2.6.0; extra == "dev"
+Requires-Dist: pyink; extra == "dev"
+Provides-Extra: colab
+Requires-Dist: psutil; extra == "colab"
+Requires-Dist: python-calamine; extra == "colab"
+Provides-Extra: and-cuda
+Requires-Dist: tensorflow[and-cuda]<2.21,>=2.18; extra == "and-cuda"
+Provides-Extra: mlflow
+Requires-Dist: mlflow; extra == "mlflow"
+Provides-Extra: jax
+Requires-Dist: jax==0.5.3; extra == "jax"
+Requires-Dist: jaxlib==0.5.3; extra == "jax"
+Requires-Dist: tensorflow-probability[substrates-jax]==0.25.0; extra == "jax"
+Provides-Extra: schema
+Requires-Dist: mmm-proto-schema; extra == "schema"
+Requires-Dist: semver; extra == "schema"
+Dynamic: license-file
+
+# About Meridian
+
+Marketing mix modeling (MMM) is a statistical analysis technique that measures
+the impact of marketing campaigns and activities to guide budget planning
+decisions and improve overall media effectiveness. MMM uses aggregated data to
+measure impact across marketing channels and account for non-marketing factors
+that impact sales and other key performance indicators (KPIs). MMM is
+privacy-safe and does not use any cookie or user-level information.
+
+Meridian is an MMM framework that enables advertisers to set up and run their
+own in-house models. Meridian helps you answer key questions such as:
+
+*   How did the marketing channels drive my revenue or other KPI?
+*   What was my marketing return on investment (ROI)?
+*   How do I optimize my marketing budget allocation for the future?
+
+Meridian is a highly customizable modeling framework that is based on
+[Bayesian causal inference](https://developers.google.com/meridian/docs/causal-inference/bayesian-inference).
+It is capable of handling large scale geo-level data, which is encouraged if
+available, but it can also be used for national-level modeling. Meridian
+provides clear insights and visualizations to inform business decisions around
+marketing budget and planning. Additionally, Meridian provides methodologies to
+support calibration of MMM with experiments and other prior information, and to
+optimize target ad frequency by utilizing reach and frequency data.
+
+If you are using LightweightMMM, see the
+[migration guide](https://developers.google.com/meridian/docs/migrate) to help
+you understand the differences between these MMM projects.
+
+## Install Meridian
+
+Python 3.11 or 3.12 is required to use Meridian. We also recommend using a
+minimum of 1 GPU.
+
+Note: This project has been tested on T4 GPU using 16 GB of RAM.
+
+To install Meridian, run the following command to automatically install the
+latest release from PyPI.
+
+*   For Linux-GPU users:
+
+    Note: CUDA toolchain and a compatible GPU device is necessary for
+    `[and-cuda]` extra to activate.
+
+    ```sh
+    $ pip install --upgrade google-meridian[and-cuda]
+    ```
+
+*   For macOS and general CPU users:
+
+    Note: There is no official GPU support for macOS.
+
+    ```sh
+    $ pip install --upgrade google-meridian
+    ```
+
+Alternatively, run the following command to install the most recent, unreleased
+version from GitHub.
+
+*   For GPU users:
+
+    ```sh
+    $ pip install --upgrade "google-meridian[and-cuda] @ git+https://github.com/google/meridian.git"
+    ```
+
+*   For CPU users:
+
+    ```sh
+    $ pip install --upgrade git+https://github.com/google/meridian.git
+    ```
+
+We recommend to install Meridian in a fresh
+[virtual environment](https://virtualenv.pypa.io/en/latest/user_guide.html#quick-start)
+to make sure that correct versions of all the dependencies are installed, as
+defined in [pyproject.toml](https://github.com/google/meridian/blob/main/pyproject.toml).
+
+## How to use the Meridian library
+
+To get started with Meridian, you can run the code programmatically using sample
+data with the [Getting Started Colab][3].
+
+The Meridian model uses a holistic MCMC sampling approach called
+[No U Turn Sampler (NUTS)](https://www.tensorflow.org/probability/api_docs/python/tfp/experimental/mcmc/NoUTurnSampler)
+which can be compute intensive. To help with this, GPU support has been
+developed across the library (out-of-the-box) using tensors. We recommend
+running your Meridian model on GPUs to get real time optimization results and
+significantly reduce training time.
+
+## Meridian Documentation & Tutorials
+
+The following documentation, colab, and video resources will help you get
+started quickly with using Meridian:
+
+| Resource                    | Description                                    |
+| --------------------------- | ---------------------------------------------- |
+| [Meridian documentation][1] | Main landing page for Meridian documentation.  |
+| [Meridian basics][2]        | Learn about Meridian features, methodologies, and the model math. |
+| [Getting started colab][3]  | Install and quickly learn how to use Meridian with this colab tutorial using sample data. |
+| [User guide][4]             | A detailed walk-through of how to use Meridian and generating visualizations using your own data. |
+| [Pre-modeling][5]           | Prepare and analyze your data before modeling. |
+| [Modeling][6]               | Modeling guidance for model refinement and edge cases. |
+| [Post-modeling][7]          | Post-modeling guidance for model fit, visualizations, optimizations, refreshing the model, and debugging. |
+| [Migrate from LMMM][8]      | Learn about the differences between Meridian and LightweightMMM as you consider migrating. |
+| [API Reference][9]          | API reference documentation for the Meridian package. |
+| [Reference list][10]        | White papers and other referenced material.    |
+
+[1]: https://developers.google.com/meridian
+[2]: https://developers.google.com/meridian/docs/basics/meridian-introduction
+[3]: https://developers.google.com/meridian/notebook/meridian-getting-started
+[4]: https://developers.google.com/meridian/docs/user-guide/installing
+[5]: https://developers.google.com/meridian/docs/pre-modeling/collect-data
+[6]: https://developers.google.com/meridian/docs/advanced-modeling/control-variables
+[7]: https://developers.google.com/meridian/docs/post-modeling/model-fit
+[8]: https://developers.google.com/meridian/docs/migrate
+[9]: https://developers.google.com/meridian/reference/api/meridian
+[10]: https://developers.google.com/meridian/docs/reference-list
+
+## Support
+
+**Questions about methodology**: Please see the [Modeling](https://developers.google.com/meridian/docs/basics/meridian-introduction) tab in the technical documentation.
+
+**Issues installing or using Meridian**: Feel free to post questions in the
+[Discussions](https://github.com/google/meridian/discussions) or [Issues](https://github.com/google/meridian/issues) tabs of the Meridian GitHub repository. The Meridian team responds to
+these questions weekly in batches, so please be patient and don't reach out
+directly to your Google Account teams.
+
+**Bug reports**: Please post bug reports to the [Issues](https://github.com/google/meridian/issues)
+tab of the Meridian GitHub repository. We also encourage the community to share
+tips and advice with each other on the [Issues](https://github.com/google/meridian/issues)
+tab. When our team addresses or resolves a new bug, we will notify you through
+the comments on the issue.
+
+**Feature requests**: Please post these to the [Discussions](https://github.com/google/meridian/discussions)
+tab of the Meridian GitHub repository. We have an internal roadmap for Meridian
+development, but would love your inputs for new feature requests so that we can
+prioritize them based on the roadmap.
+
+**Pull requests**: These are appreciated but are very difficult for us to merge
+because the code in this repository is linked to Google internal systems and has
+to pass internal review. If you submit a pull request and we believe that we can
+incorporate a change in the base code, we will reach out to you directly about
+this.
+
+## Citing Meridian
+
+To cite this repository:
+
+<!-- mdlint off(SNIPPET_INVALID_LANGUAGE) -->
+```BibTeX
+@software{meridian_github,
+  author = {Google Meridian Marketing Mix Modeling Team},
+  title = {Meridian: Marketing Mix Modeling},
+  url = {https://github.com/google/meridian},
+  version = {1.3.2},
+  year = {2025},
+}
+```

{google_meridian-1.3.0 → google_meridian-1.3.2}/google_meridian.egg-info/SOURCES.txt

@@ -13,7 +13,6 @@ meridian/constants.py
 meridian/version.py
 meridian/analysis/__init__.py
 meridian/analysis/analyzer.py
-meridian/analysis/formatter.py
 meridian/analysis/optimizer.py
 meridian/analysis/summarizer.py
 meridian/analysis/summary_text.py
@@ -25,14 +24,6 @@ meridian/analysis/review/configs.py
 meridian/analysis/review/constants.py
 meridian/analysis/review/results.py
 meridian/analysis/review/reviewer.py
-meridian/analysis/templates/card.html.jinja
-meridian/analysis/templates/chart.html.jinja
-meridian/analysis/templates/chips.html.jinja
-meridian/analysis/templates/insights.html.jinja
-meridian/analysis/templates/stats.html.jinja
-meridian/analysis/templates/style.scss
-meridian/analysis/templates/summary.html.jinja
-meridian/analysis/templates/table.html.jinja
 meridian/backend/__init__.py
 meridian/backend/config.py
 meridian/backend/test_utils.py
@@ -63,4 +54,27 @@ meridian/model/eda/constants.py
 meridian/model/eda/eda_engine.py
 meridian/model/eda/eda_outcome.py
 meridian/model/eda/eda_spec.py
-meridian/model/eda/meridian_eda.py
+meridian/templates/card.html.jinja
+meridian/templates/chart.html.jinja
+meridian/templates/chips.html.jinja
+meridian/templates/formatter.py
+meridian/templates/formatter_test.py
+meridian/templates/insights.html.jinja
+meridian/templates/stats.html.jinja
+meridian/templates/style.scss
+meridian/templates/summary.html.jinja
+meridian/templates/table.html.jinja
+schema/__init__.py
+schema/serde/__init__.py
+schema/serde/constants.py
+schema/serde/distribution.py
+schema/serde/eda_spec.py
+schema/serde/function_registry.py
+schema/serde/hyperparameters.py
+schema/serde/inference_data.py
+schema/serde/marketing_data.py
+schema/serde/meridian_serde.py
+schema/serde/serde.py
+schema/serde/test_data.py
+schema/utils/__init__.py
+schema/utils/time_record.py

{google_meridian-1.3.0 → google_meridian-1.3.2}/google_meridian.egg-info/requires.txt

@@ -8,13 +8,13 @@ pandas<3,>=2.2.2
 patsy<1,>=0.5.3
 scipy<2,>=1.13.1
 statsmodels>=0.14.5
-tensorflow<2.19,>=2.18
+tensorflow<2.21,>=2.18
 tensorflow-probability<0.26,>=0.25
-tf-keras<2.19,>=2.18
+tf-keras<2.21,>=2.18
 xarray
 
 [and-cuda]
-tensorflow[and-cuda]<2.19,>=2.18
+tensorflow[and-cuda]<2.21,>=2.18
 
 [colab]
 psutil
@@ -27,9 +27,13 @@ pylint>=2.6.0
 pyink
 
 [jax]
-jax==0.4.26
-jaxlib==0.4.26
+jax==0.5.3
+jaxlib==0.5.3
 tensorflow-probability[substrates-jax]==0.25.0
 
 [mlflow]
 mlflow
+
+[schema]
+mmm-proto-schema
+semver

{google_meridian-1.3.0 → google_meridian-1.3.2}/google_meridian.egg-info/top_level.txt

@@ -1 +1,2 @@
 meridian
+schema

{google_meridian-1.3.0 → google_meridian-1.3.2}/meridian/analysis/__init__.py

@@ -15,9 +15,8 @@
 """Meridian analysis API for trained models."""
 
 from meridian.analysis import analyzer
-from meridian.analysis import formatter
 from meridian.analysis import optimizer
 from meridian.analysis import review
 from meridian.analysis import summarizer
 from meridian.analysis import visualizer
-
+from meridian.templates import formatter

{google_meridian-1.3.0 → google_meridian-1.3.2}/meridian/analysis/analyzer.py

@@ -53,7 +53,6 @@ def _validate_non_media_baseline_values_numbers(
       )
 
 
-# TODO: Refactor the related unit tests to be under DataTensors.
 @dataclasses.dataclass
 class DataTensors(backend.ExtensionType):
   """Container for data variable arguments of Analyzer methods.

{google_meridian-1.3.0 → google_meridian-1.3.2}/meridian/analysis/optimizer.py

@@ -27,10 +27,10 @@ import jinja2
 from meridian import backend
 from meridian import constants as c
 from meridian.analysis import analyzer as analyzer_module
-from meridian.analysis import formatter
 from meridian.analysis import summary_text
 from meridian.data import time_coordinates as tc
 from meridian.model import model
+from meridian.templates import formatter
 import numpy as np
 import pandas as pd
 import xarray as xr
@@ -1174,10 +1174,12 @@ class OptimizationResults:
       diff = self.optimized_data.total_cpik - self.nonoptimized_data.total_cpik
       non_optimized_performance_title = summary_text.NON_OPTIMIZED_CPIK_LABEL
       non_optimized_performance_stat = (
-          f'${self.nonoptimized_data.total_cpik:.2f}'
+          f'{currency}{self.nonoptimized_data.total_cpik:.2f}'
       )
       optimized_performance_title = summary_text.OPTIMIZED_CPIK_LABEL
-      optimized_performance_stat = f'${self.optimized_data.total_cpik:.2f}'
+      optimized_performance_stat = (
+          f'{currency}{self.optimized_data.total_cpik:.2f}'
+      )
       optimized_performance_diff = formatter.compact_number(diff, 2, currency)
     non_optimized_performance = formatter.StatsSpec(
         title=non_optimized_performance_title,