Documentation
Developers
API References
Data Subject Request API
Data Subject Request API Version 1 and 2
Data Subject Request API Version 3
Platform API
Platform API Overview
Accounts
Apps
Audiences
Calculated Attributes
Data Points
Feeds
Field Transformations
Services
Users
Workspaces
Warehouse Sync API
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
Client SDKs
AMP
AMP SDK
Android
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
Cordova Plugin
Identity
Direct Url Routing
Direct URL Routing FAQ
Web
Android
iOS
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
React Native
Getting Started
Identity
Unity
Upload Frequency
Getting Started
Opt Out
Initialize the SDK
Event Tracking
Commerce Tracking
Error Tracking
Screen Tracking
Identity
Location Tracking
Session Management
Web
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
Xamarin
Getting Started
Identity
Web
Alexa
Quickstart
Android
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
iOS Quick Start
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
Web
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
Python Quick Start
Step 1. Create an input
Step 2. Create an output
Step 3. Verify output
Server SDKs
Node SDK
Go SDK
Python SDK
Ruby SDK
Java SDK
Guides
Partners
Introduction
Outbound Integrations
Outbound Integrations
Firehose Java SDK
Inbound Integrations
Compose ID
Glossary
Data Hosting Locations
Migrate from Segment to mParticle
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
Guides
Getting Started
Create an Input
Start capturing data
Connect an Event Output
Create an Audience
Connect an Audience Output
Transform and Enhance Your Data
Platform Guide
The New mParticle Experience
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)
Analytics
Introduction
Setup
Sync and Activate Analytics User Segments in mParticle
User Segment Activation
Welcome Page Announcements
Settings
Project Settings
Roles and Teammates
Organization Settings
Global Project Filters
Portfolio Analytics
Analytics Data Manager
Analytics Data Manager Overview
Events
Event Properties
User Properties
Revenue Mapping
Export Data
UTM Guide
Query Builder
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
Analyses Introduction
Segmentation: Basics
Getting Started
Visualization Options
For Clauses
Date Range and Time Settings
Calculator
Numerical Settings
Segmentation: Advanced
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
Funnels: Basics
Getting Started with Funnels
Group By Settings
Conversion Window
Tracking Properties
Date Range and Time Settings
Visualization Options
Interpreting a Funnel Analysis
Funnels: Advanced
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
Dashboards––Getting Started
Manage Dashboards
Dashboard Filters
Organize Dashboards
Scheduled Reports
Favorites
Time and Interval Settings in Dashboards
Query Notes in Dashboards
User Aliasing
Analytics Resources
The Demo Environment
Keyboard Shortcuts
Tutorials
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
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
Data Master
Group Identity
Overview
Create and Manage Group Definitions
Introduction
Catalog
Live Stream
Data Plans
Data Plans
Blocked Data Backfill Guide
Personalization
Predictive Attributes
Predictive Attributes Overview
Create Predictive Attributes
Assess and Troubleshoot Predictions
Use Predictive Attributes in Campaigns
Predictive Audiences
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
Import Data with CSV Files
CSV File Reference
Glossary
Video Index
Analytics (Deprecated)
Identity Providers
Single Sign-On (SSO)
Setup Examples
Introduction
Developer Docs
Introduction
Integrations
Introduction
Rudderstack
Google Tag Manager
Segment
Data Warehouses and Data Lakes
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)
Developer Basics
Aliasing
Integrations
24i
Event
Abakus
Event
Aarki
Audience
ABTasty
Audience
Actable
Feed
AdChemix
Event
AdMedia
Audience
Adobe Marketing Cloud
Cookie Sync
Event
Adobe Audience Manager
Audience
Adobe Target
Audience
Adobe Campaign Manager
Audience
AgilOne
Event
Algolia
Event
AdPredictive
Feed
Alooma
Event
Amazon Advertising
Audience
Amazon Kinesis
Event
Amazon Redshift
Data Warehouse
Amazon S3
Event
Amazon SNS
Event
Amazon SQS
Event
Adobe Marketing Cloud
Event
Amobee
Audience
Anodot
Event
Apptentive
Event
Apptimize
Event
Apteligent
Event
Microsoft Azure Blob Storage
Event
Attractor
Event
Bidease
Audience
Bing Ads
Event
Bluecore
Event
Bluedot
Feed
Branch S2S Event
Event
Bugsnag
Event
Cadent
Audience
Census
Feed
comScore
Event
Conversant
Event
Crossing Minds
Event
Custom Feed
Custom Feed
Databricks
Data Warehouse
Datadog
Event
Didomi
Event
Dynalyst
Audience
Edge226
Audience
Emarsys
Audience
Everflow
Audience
Epsilon
Event
Facebook Offline Conversions
Event
Flurry
Event
Google Analytics for Firebase
Event
Flybits
Event
ForeSee
Event
Google Ad Manager
Audience
FreeWheel Data Suite
Audience
Google Analytics
Event
Google BigQuery
Audience
Data Warehouse
Google Analytics 4
Event
Google Enhanced Conversions
Event
Google Marketing Platform
Audience
Cookie Sync
Event
Google Pub/Sub
Event
Google Marketing Platform Offline Conversions
Event
Heap
Event
Google Tag Manager
Event
Herow
Feed
Hightouch
Feed
Hyperlocology
Event
Ibotta
Event
Impact
Event
InMarket
Audience
Inspectlet
Event
Intercom
Event
ironSource
Audience
Kafka
Event
Kissmetrics
Event
Kubit
Event
LaunchDarkly
Feed
LifeStreet
Audience
LiveLike
Event
Localytics
Event
Liveramp
Audience
MadHive
Audience
mAdme Technologies
Event
Marigold
Audience
MediaMath
Audience
Mediasmart
Audience
Microsoft Azure Event Hubs
Event
Mintegral
Audience
Movable Ink
Event
Movable Ink - V2
Event
Monetate
Event
Multiplied
Event
Nami ML
Feed
Nanigans
Event
Neura
Event
NCR Aloha
Event
OneTrust
Event
Oracle BlueKai
Event
Paytronix
Feed
Persona.ly
Audience
Personify XP
Event
Plarin
Event
Primer
Event
Antavo
Feed
Quadratic Labs
Event
Quantcast
Event
Qualtrics
Event
Regal
Event
Reveal Mobile
Event
RevenueCat
Feed
Rokt
Audience
Salesforce Mobile Push
Event
Scalarr
Event
Signal
Event
SimpleReach
Event
Shopify
Custom Pixel
Feed
Singular-DEPRECATED
Event
Skyhook
Event
Slack
Event
Smadex
Audience
SmarterHQ
Event
Snapchat Conversions
Event
Snowflake
Data Warehouse
Snowplow
Event
Splunk MINT
Event
StartApp
Audience
Tapad
Audience
Tapjoy
Audience
Taplytics
Event
Taptica
Audience
The Trade Desk
Audience
Cookie Sync
Event
Teak
Audience
Ticketure
Feed
Triton Digital
Audience
Valid
Event
TUNE
Event
Vkontakte
Audience
Vungle
Audience
Webtrends
Event
Webhook
Event
Wootric
Event
White Label Loyalty
Event
Xandr
Audience
Cookie Sync
Yahoo (formerly Verizon Media)
Cookie Sync
Audience
YouAppi
Audience
Yotpo
Feed
Data Warehouse
mParticle’s Data Warehouse integration with Snowflake forwards all your incoming data to a Snowflake cluster, allowing you to query the raw data directly.
The integration creates a table in your Snowflake database for each custom event name and each eCommerce event name with a volume above a defined threshold. Less common events are recorded in a single table, labeled otherevents.
By default, the integration begins loading current data into Snowflake from the time it is enabled. You can work with your mParticle Customer Service Manager to load historical data.
Enable the Integration
Snowflake Database Setup
All setup tasks can be accomplished from a Snowflake Worksheet.
Note that you can use any names you choose for your warehouse, database, schema, role, and user, as long as you provide the correct names to mParticle in the integration settings. Also note that we currently don’t support Snowflake’s double-quoted identifiers (https://docs.snowflake.net/manuals/sql-reference/identifiers-syntax.html#double-quoted-identifiers), and thus please make sure no double quotes are used when you create your warehouse, database, schema, role, and user.
1. Create a Database and Schema
-- Create a warehouse and choose the appropriate size. We use AUTO_SUSPEND of 10 minutes (600 seconds) as an example. Please adjust accordingly if needed.
CREATE WAREHOUSE mPTravelWarehouse WITH WAREHOUSE_SIZE = 'XSMALL' AUTO_SUSPEND = 600 AUTO_RESUME = TRUE;
-- Create database
CREATE DATABASE mPTravelDatabase;
-- Create schema
CREATE SCHEMA mPTravelSchema WITH managed access;2. Create roles and users to manage permissions
Once your database is ready, you need to create a dedicated role with permissions to manage the database.
-- Create new role:
CREATE ROLE data_loader;
-- Grant access to your warehouse, database and schema
GRANT USAGE ON WAREHOUSE mPTravelWarehouse TO ROLE data_loader;
GRANT USAGE ON DATABASE mPTravelDatabase TO ROLE data_loader;
GRANT ALL ON SCHEMA mPTravelSchema TO ROLE data_loader;
-- Create user with your new role. Make sure to set your new user as a LEGACY_SERVICE user to avoid Snowflake's MFA requirement.
CREATE USER mparticle_user
MUST_CHANGE_PASSWORD = FALSE
DEFAULT_ROLE = data_loader
PASSWORD = "STRONG_PASSWORD_HERE"
TYPE = LEGACY_SERVICE;
GRANT ROLE data_loader TO USER mparticle_user;mParticle Setup
After adding Snowflake from the integrations Directory, you can find the settings UI at Setup > Data Warehouse.
From the main page for your Snowflake configuration, select the Settings tab to provide the necessary settings to get your Snowflake integration working.
Your full account name may include region. For example, xy12345.us-east-1.
To forward data subject erasure requests to Snowflake, set the Forwarding Status toggle to Active and select I understand after reading the disclaimer. Once the status has been set to Active, erasure requests are sent to Snowflake immediately upon being received by mParticle.
Configuration Settings
| Setting Name | Data Type | Default Value | Description |
|---|---|---|---|
| Account | string |
Your Snowflake account name. Your full account name may include region. | |
| Database Name | string |
The database name created in your Snowflake setup. | |
| Data Warehouse Name | string |
The warehouse name created in your Snowflake setup. | |
| User ID | string |
User ID for the user you created in your Snowflake setup. These credentials will be used to manage the schema and load data. | |
| User Password | string |
The password for the user created in your Snowflake setup. | |
| Schema Name | string |
The name of the schema created in your Snowflake setup. | |
| Events Threshold | number |
10000 | The number of times a custom or commerce event name must be received in a 30 day period for mParticle to create a dedicated table for that event. |
| Single Table Mode | boolean |
false | If enabled, events will be saved in a single table and the Events Threshold setting will not be applied. |
| Configuration Name | string |
The name you are giving to this configuration. | |
| Delay Between Loading Sessions in Minutes | number |
15 | Allows you to adjust how often you want to load data into the data warehouse. Note that the minimum time is 1 minute and the maximum time is 24 hours (60 minutes x 24). |
If you check the Use same settings for Development and Production box, the same configuration is used for both development and production environments.
Once your Data Warehouse integration is configured, connect individual inputs to the Snowflake output from the Connections page. You must connect every input for which you want to store data.
Connection Settings
| Setting Name | Data Type | Default Value | Platform | Description |
|---|---|---|---|---|
| Snowflake Table Name | string |
Feed | Table name for this partner feed. If not set, the partner name will be used. Only applicable to feeds inputs, no effect on apps inputs. If “Split Partner Feed Data by Event Name” checkbox is enabled, this setting is not used. | |
| Split Partner Feed Data by Event Name | boolean |
False | Feed | If enabled, split partner feed data by event name. Otherwise load data into the same table. |
| Send Batches without Events | boolean |
True | All | If enabled, an event batch that contains no events will be forwarded. |
Data Schema
All tables created in Snowflake have the same schema, consisting of a single column of type variant (a dedicated Snowflake type to efficiently handle JSON data) with the name "data". Each row in a table is a JSON string with multiple key/value pairs.
For example:
{
"accumulatedltvvalue": 0,
"accuracy": 2,
"appenvironment": "Development",
"appid": 4245,
"applicationbuildnumber": "2",
"appname": "Acme testing",
"appplatformid": 8140,
"appversion": "2.0",
"audiencemembership": ["123", "456", "789"],
"batchid": -6520741417792989986,
"batchtimestamp": 1553009917073,
"brand": "google",
"cityname": "Sierra View",
"clientip": "75.154.15.95",
"clientipv6": "75.154.15.95",
"countrycode": "US",
"customerid": "9172349@gmail.com",
"dataconnectiontype": "wifi",
"devicemodel": "Nexus 7",
"devicename": "Unknown",
"deviceutcoffset": -5,
"email": "7309226@acme.com",
"entrypointtype": 128,
"eventattributes": {
"$Amount": "5.37769004487325",
"Navigation 0 Attr 0": "12.3",
"another new attribute": "value",
"first_name": "First",
"last_name": "Last",
"newattribute": "value",
"yet another new attribute": "value"
},
"eventdate": "2019-03-19",
"eventhour": "2019-03-19 15:00:00",
"eventid": 351939524822094163,
"eventlength": 0,
"eventltvvalue": 5.37769004487325,
"eventname": "Navigation 0",
"eventstarttimestamp": 1553009774253,
"eventtimestamp": 1553009774253,
"eventtypeid": 1,
"firstseentimestamp": 1553009917073,
"googleaid": "9a8cd090-1a4f-4cb9-b76f-1bbca598d985",
"isdebug": true,
"latitude": 41.033192,
"localecountry": "US",
"localelanguage": "EN",
"longitude": -75.449047,
"manufacture": "LGE",
"messagetypeid": 4,
"mparticleuserid": -5045766802590845105,
"networkcarrier": "Sprint",
"networkcountry": "US",
"osversion": "4.2.1",
"osversionint": 0,
"packagename": "com.mparticle.demo",
"platform": "Android",
"product": "occam",
"regioncode": "PA",
"screendpi": 160,
"screenheight": 736,
"screenwidth": 1280,
"sdkversion": "5.1.0",
"sessionid": 3021067757087817833,
"sessionstarttimestamp": 1553009774253,
"upgradedate": 0,
"userattributes": {
"$Age": "85",
"$Gender": "male",
"$Zip": "95450",
"LiveInNewYork": "true",
"another new user attribute": "56",
"status": "gold"
},
"workspaceid": 4254,
"yahoouserid": "1940141@yahoo.com"
}mParticle also creates two types of views under the schema:
- For each table, a view called
mp_vw_{tableName}is created that allows you to run regular SQL queries against each table. For example, to queryworkspaceidfrom each table, instead of usingdata:workspaceidto query the table, you can useworkspaceidto query the view. Each user attribute and event attribute has its own column in the view. For user attribute namedSome Sample User Attributeand event attribute namedSome Sample Event Attribute, the column name in the view is"ua Some Sample User Attribute"and"ea Some Sample Event Attribute", respectively. Attribute column names have double quotes and are case sensitive. - mParticle also creates a view called
eventsviewthat unions all per table views to give you easy access to all data under the schema.
Querying From the Data Column
Use syntax data:key_name. Here are some sample queries:
-- select some "columns" to look at, if querying the table directly
select data:appid, data:eventname, data:eventtimestamp, data:customerid, data:mparticleuserid
from sample_table
limit 10-- select some "columns" to look at, if querying the view
select appid, eventname, eventtimestamp, customerid, mparticleuserid
from mp_vw_sample_table
limit 10-- count unique eventid's by hour by event name
select date_trunc('hour', to_timestamp(cast(data:eventtimestamp / 1000 as int))), data:eventname, count(distinct data:eventid)
from sample_table
group by 1, 2
order by 3 descSnowflake IP Whitelisting
If you have chosen to create an IP whitelist as part of your Snowflake Network Policy, you can access a current list of IP addresses used by mParticle here.
Partner Feed Data
Events from each connected Partner Feed will be stored under a single table unless the Split Partner Feed Data by Event Name checkbox is enabled. You can choose the table name for each Feed in the Connection Settings. If you do not provide a name, mParticle will use the name of the Partner.
Device Application Stamp Forwarding
Events can be forwarded with a Device Application Stamp stored in the device ID column. You can enable this in the settings page for your data warehouse configuration by toggling the Store Device Stamp checkbox.
Error Handling
mParticle loads data into Snowflake via Amazon S3 and can tolerate the Snowflake cluster being unavailable for up to 30 days, depending on data volume. In the event of extended downtime on your cluster, a data replay can be arranged.
- Last Updated: December 20, 2024