Data Subject Request API Version 1 and 2
Data Subject Request API Version 3
Platform API Overview
Accounts
Apps
Audiences
Calculated Attributes
Data Points
Feeds
Field Transformations
Services
Users
Workspaces
Warehouse Sync API Overview
Warehouse Sync API Tutorial
Warehouse Sync API Reference
Data Mapping
Warehouse Sync SQL Reference
Warehouse Sync Troubleshooting Guide
ComposeID
Warehouse Sync API v2 Migration
Bulk Profile Deletion API Reference
Custom Access Roles API
Data Planning API
Group Identity API Reference
Calculated Attributes Seeding API
Pixel Service
Profile API
Events API
mParticle JSON Schema Reference
IDSync
AMP SDK
Initialization
Configuration
Network Security Configuration
Event Tracking
User Attributes
IDSync
Screen Events
Commerce Events
Location Tracking
Media
Kits
Application State and Session Management
Data Privacy Controls
Error Tracking
Opt Out
Push Notifications
WebView Integration
Logger
Preventing Blocked HTTP Traffic with CNAME
Linting Data Plans
Troubleshooting the Android SDK
API Reference
Upgrade to Version 5
Direct URL Routing FAQ
Web
Android
iOS
Initialization
Configuration
Event Tracking
User Attributes
IDSync
Screen Tracking
Commerce Events
Location Tracking
Media
Kits
Application State and Session Management
Data Privacy Controls
Error Tracking
Opt Out
Push Notifications
Webview Integration
Upload Frequency
App Extensions
Preventing Blocked HTTP Traffic with CNAME
Linting Data Plans
Troubleshooting iOS SDK
Social Networks
iOS 14 Guide
iOS 15 FAQ
iOS 16 FAQ
iOS 17 FAQ
iOS 18 FAQ
API Reference
Upgrade to Version 7
Getting Started
Identity
Upload Frequency
Getting Started
Opt Out
Initialize the SDK
Event Tracking
Commerce Tracking
Error Tracking
Screen Tracking
Identity
Location Tracking
Session Management
Initialization
Configuration
Content Security Policy
Event Tracking
User Attributes
IDSync
Page View Tracking
Commerce Events
Location Tracking
Media
Kits
Application State and Session Management
Data Privacy Controls
Error Tracking
Opt Out
Custom Logger
Persistence
Native Web Views
Self-Hosting
Multiple Instances
Web SDK via Google Tag Manager
Preventing Blocked HTTP Traffic with CNAME
Facebook Instant Articles
Troubleshooting the Web SDK
Browser Compatibility
Linting Data Plans
API Reference
Upgrade to Version 2 of the SDK
Getting Started
Identity
Cordova Plugin
Identity
Web
Alexa
Overview
Step 1. Create an input
Step 2. Verify your input
Step 3. Set up your output
Step 4. Create a connection
Step 5. Verify your connection
Step 6. Track events
Step 7. Track user data
Step 8. Create a data plan
Step 9. Test your local app
Overview
Step 1. Create an input
Step 2. Verify your input
Step 3. Set up your output
Step 4. Create a connection
Step 5. Verify your connection
Step 6. Track events
Step 7. Track user data
Step 8. Create a data plan
Overview
Step 1. Create an input
Step 2. Verify your input
Step 3. Set up your output
Step 4. Create a connection
Step 5. Verify your connection
Step 6. Track events
Step 7. Track user data
Step 8. Create a data plan
Step 1. Create an input
Step 2. Create an output
Step 3. Verify output
Node SDK
Go SDK
Python SDK
Ruby SDK
Java SDK
Introduction
Outbound Integrations
Firehose Java SDK
Inbound Integrations
Compose ID
Data Hosting Locations
Glossary
Rules Developer Guide
API Credential Management
The Developer's Guided Journey to mParticle
Create an Input
Start capturing data
Connect an Event Output
Create an Audience
Connect an Audience Output
Transform and Enhance Your Data
The new mParticle Experience
The Overview Map
Introduction
Data Retention
Connections
Activity
Live Stream
Data Filter
Rules
Tiered Events
mParticle Users and Roles
Analytics Free Trial
Troubleshooting mParticle
Usage metering for value-based pricing (VBP)
Introduction
Sync and Activate Analytics User Segments in mParticle
User Segment Activation
Welcome Page Announcements
Project Settings
Roles and Teammates
Organization Settings
Global Project Filters
Portfolio Analytics
Analytics Data Manager Overview
Events
Event Properties
User Properties
Revenue Mapping
Export Data
UTM Guide
Data Dictionary
Query Builder Overview
Modify Filters With And/Or Clauses
Query-time Sampling
Query Notes
Filter Where Clauses
Event vs. User Properties
Group By Clauses
Annotations
Cross-tool Compatibility
Apply All for Filter Where Clauses
Date Range and Time Settings Overview
Understanding the Screen View Event
Analyses Introduction
Getting Started
Visualization Options
For Clauses
Date Range and Time Settings
Calculator
Numerical Settings
Assisted Analysis
Properties Explorer
Frequency in Segmentation
Trends in Segmentation
Did [not] Perform Clauses
Cumulative vs. Non-Cumulative Analysis in Segmentation
Total Count of vs. Users Who Performed
Save Your Segmentation Analysis
Export Results in Segmentation
Explore Users from Segmentation
Getting Started with Funnels
Group By Settings
Conversion Window
Tracking Properties
Date Range and Time Settings
Visualization Options
Interpreting a Funnel Analysis
Group By
Filters
Conversion over Time
Conversion Order
Trends
Funnel Direction
Multi-path Funnels
Analyze as Cohort from Funnel
Save a Funnel Analysis
Export Results from a Funnel
Explore Users from a Funnel
Saved Analyses
Manage Analyses in Dashboards
Dashboards––Getting Started
Manage Dashboards
Organize Dashboards
Dashboard Filters
Scheduled Reports
Favorites
Time and Interval Settings in Dashboards
Query Notes in Dashboards
User Aliasing
The Demo Environment
Keyboard Shortcuts
Analytics for Marketers
Analytics for Product Managers
Compare Conversion Across Acquisition Sources
Analyze Product Feature Usage
Identify Points of User Friction
Time-based Subscription Analysis
Dashboard Tips and Tricks
Understand Product Stickiness
Optimize User Flow with A/B Testing
User Segments
IDSync Overview
Use Cases for IDSync
Components of IDSync
Store and Organize User Data
Identify Users
Default IDSync Configuration
Profile Conversion Strategy
Profile Link Strategy
Profile Isolation Strategy
Best Match Strategy
Aliasing
Overview
Create and Manage Group Definitions
Introduction
Catalog
Live Stream
Data Plans
Blocked Data Backfill Guide
Predictive Attributes Overview
Create Predictive Attributes
Assess and Troubleshoot Predictions
Use Predictive Attributes in Campaigns
Predictive Audiences Overview
Using Predictive Audiences
Introduction
Profiles
Warehouse Sync
Data Privacy Controls
Data Subject Requests
Default Service Limits
Feeds
Cross-Account Audience Sharing
Approved Sub-Processors
Import Data with CSV Files
CSV File Reference
Glossary
Video Index
Single Sign-On (SSO)
Setup Examples
Introduction
Introduction
Introduction
Rudderstack
Google Tag Manager
Segment
Advanced Data Warehouse Settings
AWS Kinesis (Snowplow)
AWS Redshift (Define Your Own Schema)
AWS S3 Integration (Define Your Own Schema)
AWS S3 (Snowplow Schema)
BigQuery (Snowplow Schema)
BigQuery Firebase Schema
BigQuery (Define Your Own Schema)
GCP BigQuery Export
Snowflake (Snowplow Schema)
Snowplow Schema Overview
Snowflake (Define Your Own Schema)
Aliasing
Event
Audience
Event
Audience
Feed
Event
Audience
Cookie Sync
Event
Audience
Audience
Audience
Feed
Event
Event
Event
Audience
Event
Data Warehouse
Event
Event
Event
Event
Audience
Event
Event
Event
Feed
Event
Event
Event
Audience
Event
Event
Feed
Event
Event
Feed
Audience
Event
Event
Custom Feed
Event
Event
Event
Audience
Audience
Audience
Event
Audience
Event
Event
Event
Event
Event
Audience
Audience
Event
Event
Audience
Data Warehouse
Event
Audience
Cookie Sync
Event
Event
Event
Event
Event
Feed
Feed
Event
Event
Audience
Event
Event
Event
Audience
Event
Event
Event
Feed
Audience
Event
Audience
Event
Event
Audience
Audience
Audience
Audience
Event
Audience
Event
Event
Event
Event
Feed
Event
Event
Event
Event
Event
Feed
Audience
Event
Event
Event
Event
Event
Event
Feed
Audience
Event
Event
Custom Pixel
Feed
Event
Event
Event
Event
Event
Audience
Event
Event
Data Warehouse
Event
Event
Audience
Audience
Audience
Event
Audience
Event
Audience
Cookie Sync
Audience
Feed
Event
Audience
Audience
Event
Audience
Event
Event
Event
Cookie Sync
Audience
Audience
Cookie Sync
Feed
Audience
Event
Event
Event
The mParticle integration with Google Marketing Platform allows you to forward event data to the following Google marketing and advertising tools:
mParticle utilizes Google Floodlight to forward and map your event data to Google Marketing Platform. Google Floodlight is a conversion tracking system that allows you to generate and manage tags. These tags track activities (also referred to as “conversions”) that can represent any action your users take, including interacting with an advertisement, installing an app, completing a purchase, or signing up for a newsletter.
Because all products in the Google Marketing Platform (including Display & Video 360, Campaign Manager 360, and Search Ads 360) can use Floodlight, the mParticle integration works by mapping mParticle events to Floodlight activity tags.
Make sure you have access to the following:
Before starting the integration setup, complete the following:
If you are forwarding event data collected from mParticle’s Web SDK, you must specify the counting method for each event that you want to forward to Google. To specify the counting method for an event in the Web SDK, create a custom flag with the attribute DoubleClick.Counter
set to one of the following possible counting methods:
standard
unique
per_session
transactions
items_sold
You can then pass this custom flag along with the event when calling the tracking method in your website’s code. For example:
var customFlags = {'DoubleClick.Counter': 'standard'};
mParticle.logEvent('Video Watched', customFlags);
There are two stages to setting up the mParticle event integration with Google Marketing Platform.
Search for “Google Marketing Platform”, hover your cursor over the Google Marketing Platform tile, and click Setup.
Check the box labeled Event, and click Configure.
Click Save & Open in Connections.
Select a configured inputs to connect to Google Marketing Platform.
Click Connect Output, and click Google Marketing Platform from the list of outputs. Select the configuration you just created from the Configuration Name dropdown menu, and click Next.
Add an install
event mapping.
install
events or one for a custom event. To map an install
event from mParticle to a Google Floodlight activity, enter the group tag and activity tag (joined with a semicolon ;
) that you have configured in Floodlight to track “install” events. For example: conversion_group;install
.
Add a Custom Event mapping.
;
for the floodlight event.
Add a Custom Variable mapping.
Under Consent Data Mapping, map the consent purposes you have defined in mParticle to Google’s consent purpose definitions.
Set the default consent status for Ad User Data Consent.
Set the default value for Ad Personalization Consent.
Set the default value for Ad Storage Consent.
Set the default value for Analytics storage Consent.
Google Marketing Platform, which uses Google’s gtag
, has added the following specific Consent Mode parameters that must be sent via a gtag
implementation:
ad_user_data
ad_personalization
ad_storage
analytics_storage
For Google Marketing Platform, the ad_personalization
consent type is mapped to Google Marketing Platform’s non-personalized ads (or NPA) consent type such that if ad_personalization
consent is set as GRANTED
, NPA will be set to 0 (which indicates the user consented to ad personalization) and vice versa.
To configure user-specified consent forwarding, you must map any consent purposes you have defined in mParticle to Google’s consent mode parameters. To learn more about defining and managing consent purposes within mParticle’s platform, see Data Privacy Controls.
Once you have defined one or more consent purposes in mParticle’s Data Privacy Controls, you can use those purposes to record your users’ preferences in events they trigger. These user-provided consents are what must be mapped to Google’s consent mode parameters in step 2.7 when creating a connection with Google Marketing Platform.
In the absence of user-defined consent values for the ad_user_data
, ad_personalization
, ad_storage
, and analytics_storage
fields, an optional, default value can be configured for each consent type. When no user consent is provided, the default status is used, if specified. If omitted, the Unspecified
status will be sent.
mParticle follows Google’s recommendations when forwarding consent state defaults and consent state updates. However, the Web kit behaves differently depending on how your default consent states are configured:
If your consent state default is set to Denied
or Granted
:
custom event
or page view
event is triggered.If your consent state default is set to Unspecified
:
application initialized
, with isFirstRun
set to true
.qty
and cost
variables. However, individual attributes of products cannot be forwarded.For every event forwarded to the Google Marketing Platform, the following event attributes must be included:
Device Advertising ID
Data is forwarded to the Google Marketing Platform events integration in real time, as it is ingested into mParticle.
Before activating your new connection, or when troubleshooting issues, please check the following:
Have you entered each required ID, token, and event mapping correctly?
While mParticle forwards data to integrations in real-time, there may be a 24-48 hour delay before forwarded data is viewable in your Google Marketing Platform tools.
You can read more about data latency in Google’s documentation.
Setting Name | Data Type | Default Value | Description |
---|---|---|---|
Advertiser ID | string |
Advertiser ID associated with your Floodlight activity | |
Authorization Token | string |
An advertiser-specific alphanumeric string in your DDM account |
Setting Name | Data Type | Default Value | Platform | Description |
---|---|---|---|---|
Install Event Mapping | string |
All | The corresponding group tag and activity tag strings set up in Floodlight for install event, separated by ’;’, e.g., ‘install;conversion_group’ | |
Custom Event Mapping | Custom Field |
All | Pick events and enter the corresponding group tag and activity tag strings set up in Floodlight, separated by ’;’, e.g., you may pick event name ‘Login’, and enter ‘login;conversion_group’ | |
Custom Variable Mapping | Custom Field |
All | The Group Tag String is also found as the value of ‘type=’ and the Activity Tag String found as the value of ‘cat=’ in a generated Floodlight tag snippet. | |
Custom Variable Mapping | Custom Field |
All | Allows you to map your mParticle event attributes and user attributes to the corresponding custom variable setup in Floodlight. On web, given the kit component of the integration, any mParticle events not mapped to GMP variables will cause Floodlight to populate an alert in the console: Event not mapped. Event not sent. | |
Apply EU Regulation | bool |
false | All | If enabled, the integration will be considered as European regulations do apply to these users and conversions. |
Enrich with IP Address | bool |
false | iOS, Android | If enabled, a batch will be enriched with the most-recently seen IP address value when missing from the batch. |
Consent Data Mapping | mapping |
null | All | A mapping of mParticle consents to Google Ads consents. |
Ad User Data Default Consent Value | string |
Unspecified |
All | The default consent value to forward for the Ad User Data field. |
Ad Personalization Default Consent Value | string |
Unspecified |
All | The default consent value to forward for the Ad Personalization field. |
Ad Storage Default Consent Value | string |
Unspecified |
Web | The default consent value to forward for the Ad Storage Field |
Analytics Storage Default Consent Value | string |
Unspecified |
Web | The default consent value to forward for the Analytics Storage Field |