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
Data Planning API
Custom Access Roles 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
Content Security Policy
Configuration
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
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
Glossary
Data Hosting Locations
Migrate from Segment to mParticle
Migrate from Segment to Client-side mParticle
Migrate from Segment to Server-side mParticle
Segment-to-mParticle Migration Reference
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 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
Event
Audience
Audience
Feed
Event
Audience
Cookie Sync
Event
Audience
Audience
Audience
Event
Event
Feed
Event
Audience
Event
Data Warehouse
Event
Event
Event
Event
Audience
Event
Event
Event
Event
Event
Event
Audience
Event
Event
Feed
Event
Event
Audience
Feed
Event
Event
Event
Custom Feed
Data Warehouse
Event
Event
Audience
Audience
Audience
Audience
Event
Event
Event
Event
Event
Event
Audience
Audience
Event
Audience
Data Warehouse
Event
Event
Audience
Cookie Sync
Event
Event
Event
Event
Event
Feed
Feed
Event
Event
Event
Audience
Event
Event
Audience
Event
Event
Event
Feed
Audience
Event
Event
Audience
Audience
Event
Audience
Audience
Audience
Event
Audience
Event
Event
Event
Event
Feed
Event
Event
Event
Event
Event
Feed
Audience
Event
Event
Event
Feed
Event
Event
Event
Event
Event
Feed
Audience
Event
Event
Event
Event
Custom Pixel
Feed
Event
Event
Event
Audience
Event
Event
Data Warehouse
Event
Event
Audience
Audience
Audience
Event
Audience
Audience
Cookie Sync
Event
Audience
Feed
Audience
Event
Event
Audience
Audience
Event
Event
Event
Event
Audience
Cookie Sync
Cookie Sync
Audience
Audience
Feed
BigQuery is Google’s fully managed, petabyte scale, low cost analytics data warehouse.
mparticle-gcp-clientfacing@gcp-prod-170221.iam.gserviceaccount.com
as a member with the role of Project Viewer.From the BigQuery page for your project:
mparticle-gcp-clientfacing@gcp-prod-170221.iam.gserviceaccount.com
with the “BigQuery Data Editor” role.Use Storage API Data Sync
configuration setting is set to false and mParticle uses Streaming API endpoint for data sync. However, if you wish to use Storage API, you must first enable access to Storage API in your Google project and then set the Use Storage API Data Sync
configuration setting in mParticle to true
.All of your audience data is stored in a single BigQuery dataset. Multiple audiences can be sent to each dataset. The data sent to BigQuery is not the current state for the audience, but changes to the audience over time as users are added and removed.
For each audience, mParticle creates one table per week, showing all users added to, or removed from the audience each week. Table names are in the format {Audience Name}_{Audience ID}_{Beginning of the week in yyyyMMdd format}
. Audience name is either audience
or the external audience name depending on the Use External Audience Name in Table Name
setting. If a table with the configured name does not exist, a new table will be created the next time memberships are uploaded.
For example, if your audience ID is 7185
and the external audience name is New Users Low Engagement
,
Use External Audience Name in Table Name
is unchecked
, data for the week beginning on March 1, 2020 will be written to a table named audience_7185_20200301
.Use External Audience Name in Table Name
is checked
, data for the week beginning on March 1, 2020 will be written to a table named newuserslowengagement_7185_20200301
.To find the ID of an audience in the mParticle Dashboard, look for your audience name in the Audiences summary page.
Field Name | Data Type | Description |
---|---|---|
androidid |
string |
Android ID |
audienceid |
int |
ID of the Audience |
audiencename |
string |
External Name of the Audience |
customerid |
string |
Customer ID |
email |
string |
|
facebookid |
string |
Facebook ID |
googleaid |
string |
GAID (Google Advertising ID) |
googleuserid |
string |
Google User ID |
idfa |
string |
IDFA (Apple Advertising ID) |
idfv |
string |
IDFV (Apple Vendor ID) |
isadd |
bool |
true for a user added to an audience. false for a user removed |
microsoftid |
string |
Microsoft ID |
mpid |
int |
mParticle ID |
otheruserid |
string |
Other User ID |
otheruserid2 |
string |
Other User ID 2 |
otheruserid3 |
string |
Other User ID 3 |
otheruserid4 |
string |
Other User ID 4 |
otheruserid5 |
string |
Other User ID 5 |
otheruserid6 |
string |
Other User ID 6 |
otheruserid7 |
string |
Other User ID 7 |
otheruserid8 |
string |
Other User ID 8 |
otheruserid9 |
string |
Other User ID 9 |
otheruserid10 |
string |
Other User ID 10 |
pushtoken |
string |
Push Token |
rokuaid |
string |
Roku Advertising ID |
rokupublisherid |
string |
Roku Publisher ID |
fireadvertisingid |
string |
Fire Advertising ID |
timestamp |
string |
Unix timestamp for the update |
twitterid |
string |
Twitter ID |
userattributes |
string |
A list of user attribute name and value pairs |
userattributes.attributename |
string |
The name of an attribute |
userattributes.attributevalue |
string |
The value of an attribute |
yahooid |
string |
Yahoo ID |
You can opt to only send Customer ID to BigQuery by checking Only Send Customer ID in the Configuration Settings
You can run a query similar to the following to get audience membership at a given point in time.
-- selects only mPIDs added based on latest timestamp for each distinct mPID
WITH t1 AS
(
SELECT DISTINCT mpid, MAX(timestamp) AS max_timestamp, isadd
FROM `{BQ Project}.{BQ Dataset}.audience_{audience_id}_*`
GROUP BY mpid, timestamp, isadd
)
SELECT count(mpid)
FROM t1
WHERE isadd = true
You can run a query similar to the following to properly query on fields mParticle schema defines as RECORD, since they can be have multiple values such as device identifiers:
-- selects IDFA from the table, querying over all weekly tables
SELECT idfaid.id AS IDFA
FROM `{project_id}.{data_set}.audience_{audience_id}_*`, UNNEST(idfa) idfaid
The BigQuery Audience Integration uses Bulk Forwarding. Bulk Forwarding means that, instead of uploading updates to an audience in real time, mParticle compiles updates into a queue until either a given amount of time has passed since the last upload, or until a certain number of updates are waiting to be sent.
By default, mParticle uploads to BigQuery whenever at least one of the following conditions is met:
Upload frequency can sometimes be adjusted. Reach out to your mParticle Customer Success Manager if you need to discuss upload frequency.
mParticle doesn’t delete the downstream audience when you delete an audience in mParticle.
Setting Name | Data Type | Default Value | Description |
---|---|---|---|
BigQuery ProjectId | string |
ProjectID for your BigQuery project. | |
BigQuery DatasetId | string |
Target dataset for audience data | |
Only Send Customer ID | bool |
false |
If enabled, only the Customer ID and no other identites will be forwarded. |
Use External Audience Name in Table Name | bool |
false |
If enabled, BigQuery table name starts with audience external name; otherwise starts with “audience”. See here for more details. Note: if a table with the configured name does not exist, a new table will be created. |
Send External Audience Name as Column | bool |
false |
If enabled, a column that has the value of the external audience name will be added to all new tables. |
Send Anonymous Users | bool |
false |
If enabled, users that are only identified by their mParticle ID will be sent. |
Send User Attributes | bool |
false |
If enabled, user attribute values will be forwarded. |
Use Dataset Default Expiration | bool |
false |
If enabled, BigQuery tables will use the dataset’s default expiration. Otherwise, tables will not expire. |
Use Storage API Data Sync | bool |
false |
If enabled, data will be synced with the Storage API endpoint. Otherwise data will be synced with the Streaming API. |
Setting Name | Data Type | Default Value | Description |
---|---|---|---|
Identities to Exclude | List |
An optional setting allowing one to indicate which user and device identities to exclude in outgoing data. |