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
Google Marketing Platform Offline Conversions helps marketers plan, buy, measure and optimize digital media and customer experiences in one place.
This integration utilizes Google’s Campaign Manager 360 API.
mParticle’s Google Marketing Platform Offline Conversions integration maps mParticle events to Floodlight activities. Event and user attributes can also be mapped to Floodlight Custom Variables.
In order to enable mParticle’s integration with Google Marketing Platform, you will need to have the following in Google:
See Google’s docs here for more information.
Events will be forwarded to Google Marketing Platform Offline Conversions if all the following are true:
These fields are set for events of all supported types.
| Google Field | mParticle Field | Description |
|---|---|---|
| Mobile Device ID | IDFA or Google Advertising ID (GAID) | Set to GAID if provided. Else, set to IDFA if provided. |
| Google Click ID | Google.ClickId Custom Flag |
See more information on custom flags here. |
| Treat for Underage | Variable Mapping setting |
This can be set to a user attribute or event attribute based on the Variable Mapping setting. See variable mapping for more information. |
| Child Directed Treatment | Variable Mapping setting |
This can be set to a user attribute or event attribute based on the Variable Mapping setting. See variable mapping for more information. |
| Limit Ad Tracking | Variable Mapping setting |
This can be set to a user attribute or event attribute based on the Variable Mapping setting. See variable mapping for more information. |
| Non-Personalized Ad | Variable Mapping setting |
This can be set to a user attribute or event attribute based on the Variable Mapping setting. See variable mapping for more information. |
Commerce events contain all the user data fields described in user data mapping as well as the fields below. Note, commerce fields can be set via variable mapping for events of all type.
| Google Field | mParticle Field | Description |
|---|---|---|
| Value | Variable Mapping setting or the total_amount field |
This can be set to a user attribute or event attribute based on the Variable Mapping setting. See variable mapping for more information. If no mapping is configured, this will be set to the total_amount field. See here for more information. |
| Quantity | Variable Mapping setting or the quantity field |
This can be set to a user attribute or event attribute based on the Variable Mapping setting. See variable mapping for more information. If no mapping is configured, this will be set to the sum of the quantity fields for all products on the event. See here for more information about the field. If none of the above are set, this will be set to 1. |
Many fields can be set via the Variable Mapping setting. This setting allows you to map a user attribute or event attribute to a variety of fields. See user data mapping and commerce data mapping for info about specific fields that can be set in Google.
mParticle will also map attributes to Floodlight custom variables.
Some important notes:
mParticle events are mapped to Floodlight activities via the Event Mapping setting. This setting allows you to specify an event and provide a Floodlight activity ID for that event.
Some important notes:
Note: To adhere to the EU user consent policy, starting March 2024, Google is enforcing the consent field to be populated for EU users. You can read the announcement from Google here.
Google Ads has several notions of user-provided consent, only one of which applies to Google Marketing Platform: ad_user_data. This represents consent for ad user data.
To configure user consent forwarding under this value, a mapping should be set-up leveraging mParticle’s notion of ConsentPurposes. To learn more about handling user consent within mParticle’s platform, see the following docs: Data Privacy Controls.
Once a ConsentPurpose is set up, user consent information can be associated with it in subsequent EventBatches. The ConsentPurpose data mapping can then be configured for downstream forwarding via the User Consent Data Mapping connection setting.
In the absence of a user-defined consent value for the ad_user_data field via the ConsentPurpose mapping, a default value can be optionally configured via a separate drop-down setting.When no user consent is provided, the default status is used as specified by the default dropdown setting.
| Setting Name | Data Type | Default Value | Description |
|---|---|---|---|
| Profile ID | Integer |
The ID associated with the user profile for this account. |
| Setting Name | Data Type | Default Value | Platform | Description |
|---|---|---|---|---|
| Floodlight Configuration ID | Integer |
All | The Floodlight Configuration’s ID. | |
| Variable Mapping | Custom Field |
All | Allows you to map your mParticle event attributes and user attributes to the corresponding variables setup in Floodlight. See variable mapping. | |
| Event Mapping | Custom Field |
All | Allows you to map your mParticle events to the corresponding activity ids in Floodlight. See event mapping. | |
| User Data Consent Mapping | mapping |
null | All | A mapping of mParticle consents to Google ads_user_data consent. |
| Default Ad User Data Consent | string |
Unspecified | All | The default consent value to forward for the Ad User Data field. |