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
One of the most powerful pieces of functionality Analytics offers is the ability to identify groups of users based on their behavioral characteristics. These groups are known in Analytics as User Segments. This functionality is now available as an API so that you can programmatically export segments for use within your own or third-party platforms.
Almost any data point in Analytics can be saved as a User Segment. For example, if you run a segmentation query representing Registrations in the Last 7 Days, you can save the output of that query as a User Segment named Recent Registrants, which will contain all users who performed a Registration event in the Last 7 Days. Once these User Segments are built, they can be used as filters in all other queries. Continuing on the above example, you would be able to filter any analysis based on whether users included in that analysis are in (or not in) the Recent Registrants set of users.
Using Analytics’ User Segments Export API, you will be able to export your User Segments for use in downstream systems.
Analytics’ Export API is accessible only to Pro or Enterprise customers.
The User Segments Export API is an asynchronous API. Upon invoking a request for a User Segments export, Analytics will schedule a job to asynchronously process and upload the final result to Amazon S3, where you’ll then be able to download the file to access the contents.
Analytics’ User Segments Export API allows you to perform three operations related to User Segment exports:
User Segment exports typically complete within a matter of seconds, but can potentially take up to several hours to complete with a large result set.
The expected usage of this API works as follows:
Analytics’ Export API requires HTTPS/SSL and uses Basic Authentication header for all requests. Basic Authentication is a simple authentication scheme built into the HTTP protocol. The client sends HTTP requests with the Authorization header that contains the word Basic followed by a space and a Base64-encoded string username:password.
Use your API Key as the username and your Access Token as the password. This information can be found on the Project Page in the Analytics web application. Please treat your Access Token as you would a password, as it is meant to only be known to you.
An example curl:
curl -v -u "apiKey:accessToken" https://query.indicative-prod.mparticle.com
curl’s -u parameter automatically encodes the username and password and inserts them into the Authorization header. Depending on your client implementation you may need to do this manually.
The resulting HTTP Response should have a 200 OK status.
All API responses are in JSON format.
Status Code | Description |
---|---|
200 | Success: Your request was successful. |
401 | Unauthorized: Your request was rejected because we could not validate your credentials. Please check that your API key and access token are correct. |
403 | Forbidden: Your request was rejected because the specified project does not have access to the Export API. Please upgrade your account or contact Analytics support to gain access. |
429 | Too Many Requests: Too many requests have been attempted in a given amount of time. |
500 | Internal Error: An error occurred while processing your API request. This will automatically raise a ticket with the Analytics team. Please try your request at a later time. |
This endpoint lists all User Segments in a project.
User Segment Object Response
Field | Type | Nullable? | Description |
---|---|---|---|
segmentId | String | No | The unique ID of the User Segment. |
name | String | No | The human-readable name of the User Segments. |
description | String | Yes | The human-readable description of the User Segments. |
category | String | Yes | The human-readable category of the User Segments. |
projectId | String | No | The project ID associated to the segment ID. |
type | Enum | No | The type of the user segment, either Static (One-time in the UI) or Dynamic (Daily in the UI). Static segments never change while Dynamic segments may be refreshed. |
lastRun | DateTime | Yes | The timestamp of the last refresh of the User Segments. |
Example: List User Segments
$ curl -s -u "5a6646c4-ae5a-4de4-9d47-eb6f228405b2:nux06hkn870v0ni4fhtd81kf" https://query.indicative-prod.mparticle.com/service/v1/segments/list
[
{
"segmentId": "82200474-c131-4f7b-a35e-381469af31a7",
"name": "My Segment",
"description": "This is my segment",
"category": null,
"projectId": "5a6646c4-ae5a-4de4-9d47-eb6f228405b2",
"type": "Static",
"lastRun": "2019-04-09T12:25:06.000Z"
}
]
This endpoint invokes a new export request for the specified User Segments.
POST https://query.indicative-prod.mparticle.com/service/v1/segments/export/
Request Parameters: POST body, containing the following fields:
Request Headers:
Field | Type | Nullable? | Description |
---|---|---|---|
exportId | String | No | The unique ID of the User Segment export request. |
segment | Object | No | An object encapsulating information about the target User Segment for this export. |
status | Enum | No | The status of the User Segment export. Values are either PENDING, COMPLETE, or FAILED. |
projectId | String | No | The project ID of the User Segment export. |
startTime | DateTime | No | The time at which the User Segment export started. |
endTime | DateTime | Yes | The time at which the User Segment export completed. This field will remain null until the export is completed. |
filename | String | No | The fully qualified location of the file to download. |
Example: Request User Segments Export
$ curl -s -u "5a6646c4-ae5a-4de4-9d47-eb6f228405b2:nux06hkn870v0ni4fhtd81kf" -H 'Content-Type: application/json' https://query.indicative-prod.mparticle.com/service/v1/segments/export/ -d'{
"segmentId": "82200474-c131-4f7b-a35e-381469af31a7",
"outputFormat": "csv"
}'
{
"exportId": "8f9fdd71-204c-41e1-a2ab-de7f85002f65",
"segment": {
"segmentId": "82200474-c131-4f7b-a35e-381469af31a7",
"name": "My Segment",
"description": "This is my segment",
"category": null,
"projectId": "5a6646c4-ae5a-4de4-9d47-eb6f228405b2",
"type": "Static",
"lastRun": "2019-04-09T12:25:06.000Z"
},
"status": "PENDING",
"startTime": "2019-04-09T14:45:07.000Z",
"endTime": null,
"filename": null
}
This endpoint checks the status of a previously submitted export request. Once the request has finished processing, it will include a URL to download the results.
Once the request has been completed, the file will remain in Amazon for no more than 48 hours. Otherwise, a new request must be submitted.
GET https://query.indicative-prod.mparticle.com/service/v1/segments/export/{exportId}
Request Parameters:
Example: Check User Segment Export Status
$ curl -s -u "5a6646c4-ae5a-4de4-9d47-eb6f228405b2:nux06hkn870v0ni4fhtd81kf" https://query.indicative-prod.mparticle.com/service/v1/segments/export/8f9fdd71-204c-41e1-a2ab-de7f85002f65
{
"exportId": "8f9fdd71-204c-41e1-a2ab-de7f85002f65",
"segment": {
"segmentId": "82200474-c131-4f7b-a35e-381469af31a7",
"name": "My Segment",
"description": "This is my segment",
"category": null,
"projectId": "5a6646c4-ae5a-4de4-9d47-eb6f228405b2",
"type": "Static",
"lastRun": "2019-04-09T12:25:06.000Z"
},
"status": "COMPLETE",
"startTime": "2019-04-09T14:45:07.000Z",
"endTime": "2019-04-09T14:45:42.000Z",
"filename": "s3://upload-bucket/path/to/8f9fdd71-204c-41e1-a2ab-de7f85002f65.csv"
}
Was this page helpful?