Marketing Analytics Jumpstart (MAJ) is a terraform automated, quick-to-deploy, customizable end-to-end marketing solution on Google Cloud Platform (GCP). This solution aims at helping customer better understand and better use their digital advertising budget.
Customers are looking to drive revenue and increase media efficiency be identifying, predicting and targeting valuable users through the use of machine learning. However, marketers first have to solve the challenge of having a number of disparate data sources that prevent them from having a holistic view of customers. Marketers also often don't have the expertise and/or resources in their marketing departments to train, run, and activate ML models on paid channels. Without this solution that enables innovation through predictive analytics, marketers are missing opportunities to advance their marketing program and accelerate key goals and objectives (e.g. acquire new customers, improve customer retention, etc).
Version Name | Branch | Purpose |
---|---|---|
Multi Stream Activation | multi-stream-activation | Activate to multiple Google Analytics 4 data streams (websites and application). |
Multi Property | multi-property | Deployment of multiple MAJ resources per each Google Analytics 4 property in the same Google Cloud project. |
Want to quickly install and use it? Run this installation notebook π on Google Colaboratory and leverage Marketing Analytics Jumpstart in under 30 minutes.
If that was just too fast, continue reading this document to learn more in details.
After installing the solution users will get:
This solution is intended for Marketing Technologist teams using GA4 and GAds products. It facilitates efforts to store, transform, analyze marketing data, and programmatically creates audiences segments in Google Ads to support conversion optimization and remarketing campaigns.
Role | User Journeys | Skillset | Can Deploy? |
---|---|---|---|
Marketing Scientist | Using an isolated and secure sandbox infrastructure to perform and monitor explorations with sensitive data. Using automated machine learning to accelerate time-to-value on building use cases solutions. Faster learning curve to quickly and easily access and analyze data from the marketing data store. Ability to collaborate with other teams by reusing similar components. | Vertex AI, Python, SQL, Data Science | No |
Marketing Analyst | Simplifying the operation of the marketing data store (data assertions), machine learning pipelines (model training, prediction, explanation) and the activation application. Monitoring Ads Campaigns Performance, Web Traffic and Predictive Insights Reports. Interpreting the insights provided to plan and activate Ads campaigns. Defining audience segments using predictive metrics. | BigQuery, Looker Studio, Google Analytics 4, Google Ads | Yes |
Digital Marketing Manager | Gaining insights into customer behavior to improve marketing campaigns. Identifying and targeting new customers. Measuring the effectiveness of marketing campaigns. | Looker Studio, Google Analytics 4, Google Ads | No |
IT/Data Engineer | Building and maintaining marketing data store transformation jobs. Developing and deploying custom marketing use cases reusing a consistent infrastructure. Integrating 1st party data and Google 3rd party data by extending the marketing data store. | Python, SQL, Google Cloud Platform, Data Engineering | Yes |
This solution enables customer to plan and take action on their marketing campaigns by interpreting the insights provided by these common predictive use cases and reports that informs Campaigns performance, Traffic, User Behavior and Models Predictions insights, using the best of Google Cloud Data and AI products.
These insights are used to serve as a basis to optimize paid media efforts and investments by:
Use Case | Data Sources | Model | Looker Report Name | Google Ads Campaign Optimization |
---|---|---|---|---|
Audience Segmentation | Google Analytics 4 | BQML Kmeans | Demographic based Audience Segmentation | Custom Data Segments |
Auto Audience Segmentation | Google Analytics 4 | BQML Kmeans | Interest based Audience Segmentation | Custom Data Segments |
Customer Lifetime Value | Google Analytics 4 | Vertex AI Tabular Wokflows AutoML | Customer Lifetime Value | Custom Data Segments Bid Adjustment (maximize conversions) 1 2 |
Purchase Propensity | Google Analytics 4 | Vertex AI Tabular Wokflows AutoML | Propensity to Purchase | Custom Data Segments Bid Adjustment (maximize conversions) 1 2 |
Churn Propensity | Google Analytics 4 | Vertex AI Tabular Wokflows AutoML | Propensity to Churn | Custom Data Segments |
Aggregated Value Based Bidding | Google Analytics 4 | Vertex AI Tabular Wokflows AutoML | High Value Action | Static Conversion Values |
The solution's source code is written in Terraform, Python, SQL, YAML and JSON; and it is organized into five main folders:
config/
: This folder contains the configuration file for the solution. This file define the parameters and settings used by the various components of the solution.docs/
: This folder contains the detailed architecture, design principles, deployment, basic operation and troubleshooting guides for all the solution componentsinfrastructure/terraform/
: This folder contains the Terraform modules, variables and the installation guide to deploy the solution's infrastructure on GCP.
infrastructure/terraform/modules/
: This folder contains the Terraform modules and their corresponding Terraform resources. These modules corresponds to the architectural components broken down in the next section.notebooks/
: Contains python notebooks to be used in Workshop sessions.python/
: This folder contains most of the Python code. This code implements the activation application, which sends model predictions to Google Analytics 4; and the custom Vertex AI pipelines, its components and the base component docker image used for feature engineering, training, prediction, and explanation pipelines. It also implements the cloud function that triggers the activation application, and the Google Analytics Admin SDK code that creates the custom dimensions on the GA4 property.scripts/
: Miscelaneous scripts to support installation and operation of the solution.sql/
: This folder contains the SQL code and table schemas specified in JSON files. This code implements the stored procedures used to transform and enrich the marketing data, as well as the queries used to invoke the stored procedures and retrieve the data for analysis.templates/
: This folder contains the templates for generating the Google Analytics 4 Measurement Protocol API payloads used to send model predictions to Google Analytics 4.In addition to that, there is a tasks.py
file which implements python invoke tests who hydrate values to the JINJA template files with the .sqlx
extension located in the sql/
folder that defines the DDL and DML statements for the BigQuery datasets, tables, procedures and queries.
The provided architecture diagram depicts the high-level architecture of the Marketing Analytics Jumpstart solution. Let's break down the components:
Data Sources:
Marketing Data Store:
Feature Store:
Machine Learning Pipelines:
Activation Application:
Dashboards:
Monitoring:
This high-level architecture demonstrates how Marketing Analytics Jumpstart integrates various Google Cloud services to provide a comprehensive solution for analyzing and activating your marketing data.
Note: Google Ads Customer Matching currently only works with Google Analytics 4 Property and Subproperty linked to Google Ads Accounts, it won't work for Rollup properties.
Note: Project Owner for a Google Cloud Project is only required to speed up the deployment process. Consult this [guide]() for a more fine-grained permission list, not including the Owner role, to adhere to your company policies.
This solution is compatible in all the regions as listed in these listings:
Compute Regions | |
---|---|
https://cloud.google.com/compute/docs/regions-zones#available https://cloud.google.com/vertex-ai/docs/general/locations https://cloud.google.com/dataflow/docs/resources/locations |
"asia-east1", "asia-east2", "asia-northeast1", "asia-northeast3", "asia-south1", "asia-southeast1", "asia-southeast2", "australia-southeast1", "europe-west1", "europe-west2", "europe-west3", "europe-west4", "europe-west6", "europe-west12", "me-central1", "me-central2", "northamerica-northeast1", "southamerica-east1", "us-central1", "us-east1", "us-east4", "us-east5", "us-south1", "us-west1", "us-west2", "us-west4" |
Data Locations | |
---|---|
https://cloud.google.com/bigquery/docs/locations | "US", "EU", "asia-east1", "asia-east2", "asia-northeast1", "asia-northeast2", "asia-northeast3", "asia-south1", "asia-south2", "asia-southeast1", "asia-southeast2", "australia-southeast1", "australia-southeast2", "europe-central2", "europe-north1", "europe-west1", "europe-west2", "europe-west3", "europe-west4", "europe-west6", "europe-west8", "europe-west9", "northamerica-northeast1", "northamerica-northeast2", "southamerica-east1", "southamerica-west1", "us-central1", "us-central2", "us-east1", "us-east4", "us-west1", "us-west2", "us-west3", "us-west4" |
To facilitate the step by step installation process, we offer you two routes:
To understand better which route is more appropriate for your needs, read this documentation.
To follow the manual installation guide, open the Youtube video below on another tab and read the instructions on the documentation above.
We welcome all feedback and contributions! Please read CONTRIBUTING.md for more information on how to publish your contributions.
This project is licensed under the Apache License, Version 2.0.
This a list of public websites you can use to learn more about the Google Analytics 4, Google Ads, Google Cloud Products we used to build this solution.
This is not an officially supported Google product. This solution in a work in progress and currently in the preview stage.