--- title: mParticle API Integration on Truto slug: mparticle category: Default canonical: "https://truto.one/integrations/detail/mparticle/" --- # mParticle API Integration on Truto **Category:** Default **Status:** Beta ## Unified APIs ### Unified User Directory API - **Users** — The User object represents a User. - **Workspaces** — Workspaces represent concepts like teams, workspaces, projects in apps that support them ## How it works 1. **Link your customer's mParticle account.** Use Truto's frontend SDK; we handle every OAuth and API key flow so you don't need to create the OAuth app. 2. **Authentication is automatic.** Truto refreshes tokens, stores credentials securely, and injects them into every API request. 3. **Call Truto's API to reach mParticle.** The Proxy API is a 1-to-1 mapping of the mParticle API. 4. **Get a unified response format.** Every response uses a single shape, with cursor-based pagination and data in the `result` field. ## Use cases - **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 - **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. ## FAQs ### 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.