Science Score: 44.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
✓CITATION.cff file
Found CITATION.cff file -
✓codemeta.json file
Found codemeta.json file -
✓.zenodo.json file
Found .zenodo.json file -
○DOI references
-
○Academic publication links
-
○Academic email domains
-
○Institutional organization owner
-
○JOSS paper metadata
-
○Scientific vocabulary similarity
Low similarity (12.4%) to scientific vocabulary
Repository
Basic Info
- Host: GitHub
- Owner: linglistack
- License: apache-2.0
- Language: Python
- Default Branch: main
- Homepage: https://merd-beta.vercel.app
- Size: 8.33 MB
Statistics
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 0
- Releases: 0
Metadata Files
README.md
cursor 如何跑程序
进入后端目录
cd backend python3 -m venv venv source venv/bin/activate pip install -r requirements.txt
启动后端服务
uvicorn main:app --reload --host 0.0.0.0 --port 8000
关闭后端服务
kill $(lsof -t -i:8000)
进入前端目录
cd frontend npm install npm start
关闭前端服务
kill $(lsof -t -i:3000)
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. 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 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 to make sure that correct versions of all the dependencies are installed, as defined in 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.
The Meridian model uses a holistic MCMC sampling approach called No U Turn Sampler (NUTS) 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 | Main landing page for Meridian documentation. | | Meridian basics | Learn about Meridian features, methodologies, and the model math. | | Getting started colab | Install and quickly learn how to use Meridian with this colab tutorial using sample data. | | User guide | A detailed walk-through of how to use Meridian and generating visualizations using your own data. | | Pre-modeling | Prepare and analyze your data before modeling. | | Modeling | Modeling guidance for model refinement and edge cases. | | Post-modeling | Post-modeling guidance for model fit, visualizations, optimizations, refreshing the model, and debugging. | | Migrate from LMMM | Learn about the differences between Meridian and LightweightMMM as you consider migrating. | | API Reference | API reference documentation for the Meridian package. | | Reference list | White papers and other referenced material. |
Support
Questions about methodology: Please see the Modeling tab in the technical documentation.
Issues installing or using Meridian: Feel free to post questions in the Discussions or 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 tab of the Meridian GitHub repository. We also encourage the community to share tips and advice with each other on the 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 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:
BibTeX
@software{meridian_github,
author = {Google Meridian Marketing Mix Modeling Team},
title = {Meridian: Marketing Mix Modeling},
url = {https://github.com/google/meridian},
version = {1.1.1},
year = {2025},
}
cd frontend npm start
cd backend source venv/bin/activate # If not already activated uvicorn main:app --reload
Owner
- Login: linglistack
- Kind: user
- Repositories: 1
- Profile: https://github.com/linglistack
Citation (CITATION.cff)
cff-version: 1.2.0 message: "If you use this software, please cite it as below." title: "Meridian: Marketing Mix Modeling" authors: - name: "Google Meridian Marketing Mix Modeling Team" year: 2025 url: "https://github.com/google/meridian"
GitHub Events
Total
- Member event: 1
- Push event: 13
- Create event: 2
Last Year
- Member event: 1
- Push event: 13
- Create event: 2
Dependencies
- actions/checkout v4 composite
- actions/setup-python v5 composite
- actions/upload-artifact v4 composite
- actions/checkout v4 composite
- actions/github-script v6 composite
- actions/setup-python v5 composite
- ./.github/actions/install-meridian * composite
- actions/checkout v4 composite
- ./.github/actions/build * composite
- ./.github/actions/install-meridian * composite
- ./.github/actions/version-check * composite
- actions/checkout v4 composite
- ./.github/actions/build * composite
- ./.github/actions/create-version-tag * composite
- ./.github/actions/version-check * composite
- actions/checkout v4 composite
- actions/download-artifact v4 composite
- pypa/gh-action-pypi-publish release/v1 composite
- 1589 dependencies
- autoprefixer ^10.4.21 development
- postcss ^8.5.5 development
- tailwindcss ^4.1.10 development
- @emotion/react ^11.14.0
- @emotion/styled ^11.14.0
- @mui/icons-material ^7.1.1
- @mui/material ^7.1.1
- @mui/x-data-grid ^8.5.1
- @testing-library/dom ^10.4.0
- @testing-library/jest-dom ^6.6.3
- @testing-library/react ^16.3.0
- @testing-library/user-event ^13.5.0
- axios ^1.9.0
- plotly.js ^3.0.1
- plotly.js-dist ^3.0.1
- react ^19.1.0
- react-dom ^19.1.0
- react-plotly.js ^2.6.0
- react-scripts 5.0.1
- recharts ^2.15.3
- victory ^37.3.6
- web-vitals ^2.1.4
- arviz >=0.14.0
- h5py >=3.8.0
- numpy >=1.23.5
- pandas >=1.5.3
- scipy >=1.9.3
- tensorflow-cpu >=2.10.1
- tensorflow-probability >=0.18.0
- xarray >=2023.1.0
- arviz ==0.14.0
- fastapi ==0.95.2
- h5py ==3.8.0
- numpy ==1.23.5
- openpyxl ==3.1.2
- pandas ==1.5.3
- pydantic ==1.10.7
- python-dateutil ==2.8.2
- python-multipart ==0.0.6
- scipy ==1.9.3
- setuptools ==65.5.1
- starlette ==0.26.1
- tensorflow-cpu ==2.10.1
- tensorflow-probability ==0.18.0
- typing-extensions ==4.5.0
- uvicorn ==0.22.0
- werkzeug ==2.0.3
- wheel ==0.40.0
- xarray ==2023.1.0
- altair >= 5
- arviz *
- immutabledict *
- joblib *
- natsort >= 7.1.1, < 8
- numpy >= 2.0.2, < 3
- pandas >= 2.2.2, < 3
- scipy >= 1.13.1, < 2
- tensorflow >= 2.18, < 2.19
- tensorflow-probability >= 0.25, < 0.26
- tf-keras >= 2.18, < 2.19
- xarray *
- python 3.12-slim build
- arviz >=0.15.0
- fastapi >=0.95.2
- h5py >=3.9.0
- immutabledict >=2.2.3
- numpy >=1.24.0
- openpyxl >=3.1.2
- pandas >=2.1.1
- pydantic >=1.10.7,<3.0.0
- python-dateutil >=2.8.2
- python-multipart >=0.0.6
- scipy >=1.11.0
- starlette >=0.26.1
- tensorflow-cpu >=2.13.0
- tensorflow-probability >=0.21.0
- typing-extensions >=4.5.0
- uvicorn >=0.22.0
- werkzeug >=2.0.3
- xarray >=2023.1.0
- absl-py >=1.0.0
- altair >=5.0.0
- arviz >=0.15.0
- fastapi >=0.95.2
- h5py >=3.9.0
- immutabledict >=2.2.3
- jinja2 >=3.0.0
- joblib >=1.3.0
- natsort >=8.0.0
- numpy >=1.24.0
- openpyxl >=3.1.2
- pandas >=2.1.1
- protobuf >=4.21.0
- pydantic >=1.10.7,<3.0.0
- python-dateutil >=2.8.2
- python-multipart >=0.0.6
- scipy >=1.11.0
- setuptools >=65.5.1
- starlette >=0.26.1
- tensorflow-macos >=2.13.0
- tensorflow-metal >=1.0.0
- tensorflow-probability >=0.21.0
- typing-extensions >=4.5.0
- uvicorn >=0.22.0
- werkzeug >=2.0.3
- wheel >=0.40.0
- xarray >=2023.1.0
- fastapi >=0.95.2
- jinja2 >=3.0.0
- numpy >=1.24.0
- openpyxl >=3.1.2
- pandas >=2.1.1
- pydantic >=1.10.7,<3.0.0
- python-dateutil >=2.8.2
- python-multipart >=0.0.6
- uvicorn >=0.22.0