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
Calculated Attributes Seeding API
Custom Access Roles API
Data Planning API
Group Identity API Reference
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
Cordova Plugin
Identity
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
Web
Alexa
Node SDK
Go SDK
Python SDK
Ruby SDK
Java SDK
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
Step 1. Create an input
Step 2. Create an output
Step 3. Verify output
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
Explore Users from a Funnel
Export Results from a Funnel
Saved Analyses
Manage Analyses in Dashboards
Dashboards––Getting Started
Manage Dashboards
Dashboard Filters
Organize Dashboards
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 (Snowplow Schema)
AWS S3 Integration (Define Your Own 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
Event
Audience
Audience
Feed
Event
Audience
Event
Cookie Sync
Audience
Audience
Feed
Audience
Event
Event
Event
Event
Audience
Event
Data Warehouse
Event
Event
Event
Audience
Event
Feed
Event
Event
Event
Event
Event
Audience
Event
Event
Feed
Event
Event
Feed
Audience
Event
Event
Event
Custom Feed
Event
Event
Audience
Audience
Audience
Event
Audience
Event
Event
Event
Event
Event
Audience
Audience
Event
Event
Audience
Data Warehouse
Event
Event
Event
Audience
Cookie Sync
Event
Event
Event
Feed
Feed
Event
Event
Event
Audience
Event
Event
Audience
Event
Event
Event
Audience
Feed
Event
Audience
Event
Audience
Event
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
Event
Event
Custom Pixel
Feed
Event
Event
Event
Audience
Event
Event
Event
Event
Data Warehouse
Event
Audience
Audience
Event
Audience
Audience
Audience
Audience
Cookie Sync
Event
Feed
Audience
Event
Event
Audience
Audience
Event
Event
Event
Audience
Cookie Sync
Event
Audience
Cookie Sync
Event
Feed
Audience
The mParticle integration with Google Marketing Platform allows you to forward audience data to the following Google marketing and advertising tools:
You must create a separate configuration for each Google product you want to forward your audience data to.
Make sure you have access to the following:
Google Product | Previous Product Name | Required ID |
---|---|---|
Authorized Buyer | DoubleClick Ad Exchange | Account ID To find your Account ID, log into your Authorized Buyer account, and look for your ID at the top of the Authorized Buyers page, just below your account name. |
Google Ad Manager | DoubleClick For Publishers (DFP by Google) | Audience Link ID To find your Audience Link ID, log into your Ad Manager account, and navigate to Admin > Global Settings > Network Settings. |
Display & Video 360 (Invite Advertiser) | DoubleClick Bid Manager | Advertiser ID To find your Advertiser ID, log into your DV360 account and navigate to Advertiser Settings > Basic Details. |
Display & Video 360 (Invite Partner) | DoubleClick Bid Manager | Partner ID To find your Partner ID, log into your DV360 account and navigate to Partner Settings > Basic Details. |
Google Ads | AdWords | Customer ID To find your Customer ID, log into your Google Ads account and look for the 10 digit ID next to your account email address in the right corner of the top nav bar. |
In order to forward an mParticle audience to Google, mParticle must be “whitelisted” to access to your Google Marketing Platform account. To whitelist your mParticle account, follow these instructions. If you need assistance, reach out to your Google Technical Account Manager for help whitelisting your account.
There are two stages to setting up an audience integration with Google Marketing Platform.
Enter the ID for the Google product you want to send your audiences to under Client Customer ID.
Select one of the following products within Google Marketing Platform that you want to send your audience data to. Note that some products are now referred to by a different name by Google:
Invite Advertiser (Display & Video 360 Advertiser)
Invite Partner (Display & Video 360 Partner)
Under Membership Lifespan, enter the number of days you want users to remain in the audience. The maximum membership lifespan is 540 days.
Make sure the Process Consent checkbox is checked if you have collected user consent info to forward to Google. If this box is unchecked, no data will be forwarded to Google.
true
to Google. By checking this box, you acknowledge that you have gathered your users’ consent as per Google’s requirements. mParticle forwards the following user identities to Google Marketing Platform:
All Google Marketing Platform user lists have a property that dictates the membership lifespan of a user. This membership duration represents the maximum amount of time a user stays on the list.
The default membership lifespan is 30 days, but this is configurable up to a maximum of 540 days.
For example, If you created an audience of users who have viewed a particular screen, and your membership lifespan is set to 30 days, a new member will only remain in the downstream Google Marketing Platform list for 30 days, unless they view the screen again, at which point the 30 day timer is reset.
Google has several notions of user-provided consent. One of these applies to Google Marketing Platform Audience:
process_consent
The consent mapping can be configured for downstream forwarding via the Process Consent connection setting. By default, this setting is set to True
to send data downstream as consented, indicating that proper legal consent has been gathered to share data with Google.
Note: If process_consent
is False
, Google will not process incoming user data and requests will be dropped. This includes, but is not limited to, abiding to Google’s EU User Consent Policy.
For collected user data which is not subject to affirmative end-user consent, partners are still required to indicate a valid legal basis for sharing data by setting Process Consent to True
.
The Google Marketing Platform Audience integration uses bulk forwarding. This means that data is stored in a queue before being forwarded to Google.
Your audiences will be sent to Google when either of the following conditions are met:
Before activating your new connection, or when troubleshooting issues, please check the following:
Have you entered each required ID, token, and mapping correctly?
While mParticle forwards data to integrations in real-time, there may be a 24-48 hour delay before your audience is accessible from your Google Marketing Platform tools.
The table below describes the configuration settings for each audience integration account. You will need to create a separate integration account for each Google ad product that you’d like to forward your audiences to.
Setting Name | Data Type | Default Value | Description |
---|---|---|---|
Client Customer ID | string |
The specific ID for the Google Product within the Google Marketing Platform you want to forward your data to. For more information, see Prerequisites. | |
Product | string |
ADX Buyer | The Google Ad Product you would like to forward audience data to. |
Partner Provided ID Type | string |
None | The identity mParticle should send to Google as a Partner Provided Identity (PPID). |
Setting Name | Data Type | Default Value | Description |
---|---|---|---|
Membership Lifespan | int |
30 | The number of days that users remain as part of an audience list after they’re added, if they take no further action that renews their membership. A minimum of 30 and a maximum of 540 days are accepted. |
Process Consent | bool |
true |
If enabled, the Process Consent will be forwarded as true to Google for these users. |