Marketing Automation · Beta

mParticle
API integration

Ship Marketing Automation features without building the integration. Full mParticle API access via Proxy, normalized data through Unified APIs, and 90+ MCP-ready tools for AI agents — all extensible to your exact use case.

Built for specific customer use cases. Issues are resolved quickly.

Talk to us

Use Cases

Why integrate with mParticle

Common scenarios for SaaS companies building mParticle integrations for their customers.

Enrich support agent context with unified customer profiles

Customer support and helpdesk SaaS companies can query mParticle's Profile API to surface calculated attributes like LTV, subscription tier, and recent in-app activity directly in the agent workspace — giving reps instant context without switching tools.

Sync audience segments into your marketing or engagement platform

Marketing automation SaaS companies can receive dynamic audience memberships from mParticle so their users can target campaigns based on segments built by their marketing teams inside the CDP, without requiring custom data pipelines.

Push product events back into the customer data stack

Any SaaS product — from survey tools to billing platforms — can send structured events back into mParticle via the Events API, ensuring actions taken in your product (e.g., survey completed, invoice paid) are available across every downstream tool in your customer's stack.

Ingest mParticle's event stream instead of shipping another SDK

Analytics and product intelligence SaaS companies can consume the real-time event firehose from mParticle as an Event Destination, removing the need for their customers to install yet another tracking SDK into mobile or web apps.

Resolve and unify user identities across your product and the CDP

SaaS companies dealing with anonymous-to-known user transitions can leverage mParticle's IDSync framework to ensure identity merges in their product are reflected in the broader customer profile, maintaining data consistency across the entire tool ecosystem.

What You Can Build

Ship these features with Truto + mParticle

Concrete product features your team can ship faster by leveraging Truto’s mParticle integration instead of building from scratch.

Real-time customer profile sidebar

Display a user's unified identity, calculated attributes (LTV, subscription tier), and recent event timeline pulled from mParticle directly inside your product's UI.

Bidirectional event sync pipeline

Push events generated in your product (e.g., Email Opened, Ticket Escalated, Survey Completed) back into mParticle while ingesting their standardized event stream into your own features.

Audience-driven feature targeting

Use mParticle audience memberships to gate features, trigger in-app prompts, or personalize experiences based on segments your customers' marketing teams already maintain.

User directory sync with workspace mapping

Leverage Truto's Unified User Directory API to read users and workspaces from mParticle, keeping your product's user records aligned with the CDP's identity graph.

NPS and feedback attribute writeback

After capturing survey responses or feedback scores, write those values back to mParticle as user attributes so every downstream tool in your customer's stack has access to sentiment data.

Automated identity resolution on login events

Trigger identity transitions in mParticle when users authenticate in your product, merging anonymous device profiles with known customer records via the IDSync framework.

SuperAI

mParticle AI agent tools

Comprehensive AI agent toolset with fine-grained control. Integrates with MCP clients like Cursor and Claude, or frameworks like LangChain.

list_all_m_particle_users

List the users of an mParticle account. Returns user records with their id plus content-type-specific user fields defined upstream. Required: account_id.

get_single_m_particle_user_by_id

Get a single mParticle user by id. Returns the user record with its id plus content-type-specific user fields defined upstream. Required: id, account_id.

list_all_m_particle_workspaces

List the workspaces in an mParticle account. Returns workspace records including id. Required: account_id.

list_all_m_particle_accounts

List mParticle accounts. Returns: id, name, data_type, created_on, last_modified_on. Required: account_id.

get_single_m_particle_account_by_id

Get a single mParticle account by id. Returns: id, name, data_type, created_on, last_modified_on. Required: id, account_id.

create_a_m_particle_account

Create an account.

update_a_m_particle_account_by_id

Update an account. Required: id.

delete_a_m_particle_account_by_id

Delete an account. Required: id.

list_all_m_particle_apps

Get all apps.

get_single_m_particle_app_by_id

Get a single app. Required: id.

create_a_m_particle_app

Create an app.

update_a_m_particle_app_by_id

Update an app. Required: id.

delete_a_m_particle_app_by_id

Delete an app. Required: id.

list_all_m_particle_app_platforms

Get all app platforms. Required: app_id.

get_single_m_particle_app_platform_by_id

Get a single app platform. The id is the platform OS (e.g. ios, android). Required: id, app_id.

create_a_m_particle_app_platform

Create an app platform. Required: app_id.

update_a_m_particle_app_platform_by_id

Update an app platform. The id is the platform OS (e.g. ios, android). Required: id, app_id.

delete_a_m_particle_app_platform_by_id

Delete an app platform. The id is the platform OS (e.g. ios, android). Required: id, app_id.

list_all_m_particle_app_platform_services

Get all services for an app platform. Required: app_id, os.

m_particle_app_platform_services_bulk_update

Configure a service for an app platform. Required: app_id, os.

list_all_m_particle_audiences

Get all audiences. Returns an array containing all active audiences within an account, where the account ID is set as a query parameter.

delete_a_m_particle_audience_by_id

Delete an audience. Deletes the audience with the given audience ID. The audience ID is labeled "id" in the responses to the Get all audiences and the Get all audiences for a workspace endpoints. Required: id.

list_all_m_particle_workspace_audiences

Get all audiences for a workspace. Returns an array containing all active audiences within a workspace, where the workspace ID is set as a path parameter and the account ID is set as a query parameter. Required: workspace_id.

list_all_m_particle_app_data_points

Get data points for an app. Retrieves a list of DataPoints that exist for an App. The 1 after /apps/ is a placeholder for the Application ID. Required: app_id.

create_a_m_particle_app_data_point

Create a data point. Adds a new DataPoint for an App. Required: app_id.

get_single_m_particle_service_filter_by_id

Get a service filter. Get default filtering behavior for a service. The id is the service module name (e.g. GoogleAnalyticsEventForwarder). Required: id, app_id.

update_a_m_particle_service_filter_by_id

Update a service filtering. The id is the service module name (e.g. GoogleAnalyticsEventForwarder). Required: id, app_id.

list_all_m_particle_service_data_point_filters

Get all data point filters. Retrieve a list of DataPoint filters for a specific App and Service. Required: app_id, module_name.

m_particle_service_data_point_filters_bulk_update

Update a data point filter. Required: app_id, module_name.

list_all_m_particle_partner_feeds

Get all partner feeds for a workspace. Returns a list of partner feeds set up for a workspace. Required: workspace_id.

get_single_m_particle_partner_feed_by_id

Get a specific feed. Get details and settings for a specific partner feed. Required: id.

create_a_m_particle_partner_feed

Create a new feed. Creates a new feed. Required: workspace_id.

update_a_m_particle_partner_feed_by_id

Update a feed. Updates an existing feed. Required: id, workspace_id.

list_all_m_particle_output_configurations

Get all output configurations. List all available configurations for a particular module Required: workspace_id, module_name.

create_a_m_particle_feed_subscription

Create a new feed subscription. Creates and configures a new feed subscription. Required: module_id.

list_all_m_particle_services

Get all services for an account.

get_single_m_particle_service_by_id

Get a specific service with settings. The id is the service module name (e.g. Indicative). Required: id.

list_all_m_particle_calculated_attributes

Get all calculated attributes. Required: workspace_id.

create_a_m_particle_calculated_attribute

Create a new calculated attribute. Required: workspace_id.

get_single_m_particle_calculated_attribute_by_id

Get a calculated attribute. Required: id, workspace_id.

update_a_m_particle_calculated_attribute_by_id

Update a calculated attribute. Use this endpoint to create or update a draft of your Calculated Attribute definition. When a Calculated Attribute is updated, the draft_definition is changed. Required: id, workspace_id.

delete_a_m_particle_calculated_attribute_by_id

Delete a calculated attribute. Required: id, workspace_id.

get_single_m_particle_calculated_attribute_activation_by_id

Get a calculated attribute activation status. A calculated attribute’s activation status tells you whether the calculated attribute has been activated and when and who activated it. The id is the calculated attribute ID. Required: id, workspace_id.

create_a_m_particle_calculated_attribute_activation

Activate a calculated attribute. Use this endpoint to activate a calculated attribute. You must activate the Calculated Attribute before it can be used elsewhere in the system. Required: workspace_id, calculated_attribute_id.

delete_a_m_particle_calculated_attribute_draft_by_id

Delete a calculated attribute draft definition. Use this endpoint to discard a calculated attribute’s draft definition. The id is the calculated attribute ID. Required: id, workspace_id.

get_single_m_particle_calculated_attribute_calculation_by_id

Get a calculated attribute status. A calculated attribute’s calculation status gives you the calculation progress and an estimated completion date. The id is the calculated attribute ID. Required: id, workspace_id.

list_all_m_particle_data_plans

Get all Data Plans. Required: workspace_id.

create_a_m_particle_data_plan

Create Data Plan. Required: workspace_id.

get_single_m_particle_data_plan_by_id

Get Data Plan. Required: id, workspace_id.

update_a_m_particle_data_plan_by_id

Update Data Plan. Required: id, workspace_id.

delete_a_m_particle_data_plan_by_id

Delete Data PLan. Required: id, workspace_id.

create_a_m_particle_data_plan_version

Create Data Plan Version. Required: workspace_id, plan_id.

get_single_m_particle_data_plan_version_by_id

Get Data Plan Version. The id is the data plan version number. Required: id, workspace_id, plan_id.

update_a_m_particle_data_plan_version_by_id

Update Data Plan Version. The id is the data plan version number. Required: id, workspace_id, plan_id.

delete_a_m_particle_data_plan_version_by_id

Delete Data Plan Version. The id is the data plan version number. Required: id, workspace_id, plan_id.

create_a_m_particle_data_plan_validation

Validate event batch with a data plan version. To validate an event batch using the Data Planning API, submit a POST request to https://api.mparticle.com/platform/v2/workspaces/{{workspace_id}}/plans/validate, including the JSON formatted event batch you want to validate. Required: workspace_id.

list_all_m_particle_field_transformations

Get all field transformations. Required: workspace_id.

create_a_m_particle_field_transformation

Create a new field transformation. Required: workspace_id.

get_single_m_particle_field_transformation_by_id

Get a specific field transformation. Required: id, workspace_id.

update_a_m_particle_field_transformation_by_id

Update a field transformation. Required: id, workspace_id.

delete_a_m_particle_field_transformation_by_id

Delete a field transformation. Required: id, workspace_id.

list_all_m_particle_kms_keys

Retrieve all key pairs.

create_a_m_particle_kms_key

Create a new key pair.

delete_a_m_particle_kms_key_by_id

Delete a key pair. Required: id.

list_all_m_particle_custom_role_tasks

View tasks. Required: org_id.

list_all_m_particle_custom_roles

View custom role manifest. Required: org_id.

m_particle_custom_roles_bulk_update

Create a custom role. Required: org_id.

list_all_m_particle_households

Get all household definitions contained in a workspace. Required: workspace_id.

get_single_m_particle_household_by_id

Get a specific household definition by its household ID. Required: id, workspace_id.

create_a_m_particle_household

Create a new household definition in a workspace. Required: workspace_id.

update_a_m_particle_household_by_id

Update a household definition. Required: id, workspace_id.

m_particle_households_partial_update

Set attributes for a household. Required: workspace_id, group_id.

delete_a_m_particle_household_by_id

Delete a household. Required: id, workspace_id.

m_particle_audit_logs_search

Retrieve audit logs. Retrieve a paginated list of audit logs for your account. You can filter results by specifying values for action_types, actor_email, or resources in the request body, along with an optional date range.

m_particle_audit_logs_export

Export audit logs as CSV. Export all audit logs for a specific account as a CSV file. The endpoint streams data to efficiently handle large exports and supports filtering by date range, action type, and other parameters. Required: start.

get_single_m_particle_user_profile_by_id

Get a profile by mParticle ID. The id is the mParticle ID (MPID). Required: id, org_id, workspace_id, fields.

m_particle_user_profiles_search

Get a profile by immutable ID. Allows you to retrieve a profile without the mParticle ID. To use this method, your account must have an immutable identity configured in your identity strategy. Required: org_id, workspace_id, fields.

list_all_m_particle_warehouse_connections

Get all data warehouse connections. For the workspace specified in the base URI, get all the data warehouse connections. Required: workspace_id.

get_single_m_particle_warehouse_connection_by_id

Get a specific connection. Required: id, workspace_id.

create_a_m_particle_warehouse_connection

Create a connection. Required: workspace_id.

update_a_m_particle_warehouse_connection_by_id

Update an existing connection. Required: id, workspace_id.

delete_a_m_particle_warehouse_connection_by_id

Delete a connection. Required: id, workspace_id.

list_all_m_particle_warehouse_data_models

Get all data models. Required: workspace_id.

get_single_m_particle_warehouse_data_model_by_id

Get a specified data model. Required: id, workspace_id.

create_a_m_particle_warehouse_data_model

Create a data model. Required: workspace_id.

update_a_m_particle_warehouse_data_model_by_id

Update a data model. Required: id, workspace_id.

delete_a_m_particle_warehouse_data_model_by_id

Delete a data model. Required: id, workspace_id.

list_all_m_particle_warehouse_pipelines

Get all pipelines. Required: workspace_id.

get_single_m_particle_warehouse_pipeline_by_id

Get a specific pipeline. Required: id, workspace_id.

create_a_m_particle_warehouse_pipeline

Create a pipeline. Required: workspace_id.

update_a_m_particle_warehouse_pipeline_by_id

Update a pipeline. Required: id, workspace_id.

delete_a_m_particle_warehouse_pipeline_by_id

Delete a pipeline. Required: id, workspace_id.

m_particle_warehouse_pipelines_trigger

Trigger a pipeline. Starts syncing data from a pipeline. The behavior varies depending on the pipeline’s sync mode: If a pipeline is faulted, you can use the trigger endpoint to re-attempt synchronization. Required: workspace_id.

m_particle_warehouse_pipelines_reset

Reset a pipeline. Resets the specified pipeline. This operation can be used to reset the pipeline’s sync state, for example to force a full re-sync of an incremental pipeline. Required: workspace_id.

get_single_m_particle_warehouse_pipeline_report_by_id

Get the status report for a pipeline. Retrieves the current status of a pipeline, including the latest completed run. The id is the pipeline ID. Required: id, workspace_id.

list_all_m_particle_warehouse_pipeline_runs

Get a list of pipeline runs for a pipeline. Required: workspace_id, pipeline_id.

get_single_m_particle_warehouse_pipeline_run_by_id

Get a specific pipeline run for a pipeline. Required: id, workspace_id, pipeline_id.

Why Truto

Why use Truto’s MCP server for mParticle

Other MCP servers give you a static tool list for one app. Truto gives you a managed, multi-tenant MCP infrastructure across 1000+ integrations.

Auto-generated, always up to date

Tools are dynamically generated from curated documentation — not hand-coded. As integrations evolve, tools stay current without manual maintenance.

Fine-grained access control

Scope each MCP server to read-only, write-only, specific methods, or tagged tool groups. Expose only what your AI agent needs — nothing more.

Multi-tenant by design

Each MCP server is scoped to a single connected account with its own credentials. The URL itself is the auth token — no shared secrets, no credential leaking across tenants.

Works with every MCP client

Standard JSON-RPC 2.0 protocol. Paste the URL into Claude, ChatGPT, Cursor, or any MCP-compatible agent framework — tools are discovered automatically.

Built-in auth, rate limits, and error handling

Tool calls execute through Truto’s proxy layer with automatic OAuth refresh, rate-limit handling, and normalized error responses. No raw API plumbing in your agent.

Expiring and auditable servers

Create time-limited MCP servers for contractors or automated workflows. Optional dual-auth requires both the URL and a Truto API token for high-security environments.

Unified APIs

Unified APIs for mParticle

Skip writing code for every integration. Use Truto’s category-specific Unified APIs out of the box or customize the mappings with AI.

Unified User Directory API

Users

The User object represents a User.

View Docs

Workspaces

Workspaces represent concepts like teams, workspaces, projects in apps that support them

View Docs

How It Works

From zero to integrated

Start with mParticle in a free sandbox, usually ready within one business day. No boilerplate, no maintenance burden.

Link your customer’s mParticle account

Use Truto’s frontend SDK to connect your customer’s mParticle account. We handle all OAuth and API key flows — you don’t need to create the OAuth app.

We handle authentication

Don’t spend time refreshing access tokens or figuring out secure storage. We handle it and inject credentials into every API request.

Call our API, we call mParticle

Truto’s Proxy API is a 1-to-1 mapping of the mParticle API. You call us, we call mParticle, and pass the response back in the same cycle.

Unified response format

Every response follows a single format across all integrations. We translate mParticle’s pagination into unified cursor-based pagination. Data is always in the result attribute.

FAQs

Common questions about mParticle on Truto

Authentication, rate limits, data freshness, and everything else you need to know before you integrate.

What authentication methods does mParticle support?

mParticle's server-to-server APIs use API key and secret pairs scoped to a specific workspace and environment (development or production). Truto handles credential storage and auth lifecycle so your team doesn't manage secrets directly.

What Unified APIs does Truto support for mParticle?

Truto currently maps mParticle to the Unified User Directory API, which covers Users and Workspaces. Additional tools and unified API mappings can be built on request based on your specific use case.

Can I push events into mParticle through Truto?

mParticle's Events API supports server-to-server ingestion of custom events, commerce events, and screen views. While Truto does not yet have a pre-built tool for this, it can be built on request to match your specific event push requirements.

Does mParticle enforce rate limits on API calls?

Yes, mParticle applies rate limits to its APIs, particularly the Profile API and Events API. Exact limits depend on your customer's mParticle plan and environment. Truto can handle retry logic and pagination so your integration degrades gracefully under load.

How fresh is the data when reading user profiles from mParticle?

mParticle processes events in near real-time, so Profile API responses typically reflect the latest known state of a user including recent events, calculated attributes, and audience memberships. Latency depends on event volume and the customer's mParticle configuration.

What if I need a specific mParticle API endpoint that isn't available yet?

Truto builds integration tools on request. If you need access to mParticle's Audience API, Data Planning API, or any other endpoint, reach out and the team will scope and build the integration for your use case.

mParticle

Get mParticle integrated into your app

Our team understands what it takes to make a mParticle integration successful. A short, crisp 30 minute call with folks who understand the problem.