![\"flowchart](\"/images/platform-basics/org-acct-workspace.png\")
The mParticle platform is the hub for all of your data. It collects data from any number of inputs - mobile apps, web, feeds from external SAAS providers, data sent via our Events API - and forwards it on to output services to be used for analytics, attribution, storage, audience targeting, push notifications, etc.
\nThe primary task accomplished in the mParticle dashboard is creating Connections between inputs and outputs - to collect your data, enrich and transform it, and forward it to where it needs to go. mParticle forwards two main types of data:
\nmParticle creates a unique organization for you. It’s the container for all data and metadata related to your mParticle. Within an organization, mParticle will create one or more accounts for you, and within each account, you can create one or more workspaces. Your choices for account and workspace setup are important because these choices affect identity and feature provisioning.
\n
These three nested containers provide scoping and functionality for multi-brand and multi-geo use cases, as well as edge use cases. The scope and advantages of each are explained in the following sections.
\nOrganization
\nMost mParticle customers have one organization which contains one or more accounts. However, some large companies have multiple organizations. No information is shared across organization boundaries. mParticle creates the organization(s) for you.
\nA few features apply at the organization level, including profile strategies.
\nYou can think of the organization as representing your company.
\nAccount
\nEach organization has one or more accounts. Accounts often represent different functional groups or goals within an organization, for example regional divisions, or Sales, Marketing, and Customer Support. mParticle creates the account(s) for you.
\nSome information is shared across accounts either by default or by enablement:
\nWorkspace
\nEach account contains one or more workspaces. A workspace is the basic container for data in an mParticle account. mParticle creates your first workspace, but you can add more at any time.
\nFor most use cases, each workspace is its own domain, separate from other workspaces. Some information is shared across workspace boundaries:
\nSome mParticle accounts have over a dozen workspaces, while others have only one. How you organize data from your app ecosystem is entirely up to you.
\nUse organizations, accounts, and workspaces to manage multiple brands, regions, and to manage custom identity configurations and unique input/output requirements. You can also use mParticle features like Audience Sharing or Audiences across multiple workspaces.
\nTo display your current organization, account, and selected workspace: log into mParticle and hover your cursor over the workspace icon in the bottom of the left nav bar.
\nWorkspaces are displayed in an indented list beneath each account within your organization. Your organization name is listed at the top. You can search for an account or workspace using the search bar.
\n![\"image](\"/images/guides/platform-guide/introduction/view-current-org-account-workspace.png\")
The Best Bags company sells handbags under several different names, and in several regions of the globe. They can use organizations and workspaces to provide differentiation when needed:
\nYou can also use identity scope to manage how user data is shared between workspaces and accounts. If you need to share audiences across accounts, use Audience Sharing.
\nTo view and manage your workspaces:
\nLog into mParticle, hover your cursor over the Settings icon in the left nav, and select Workspaces.
\n![\"image](\"/images/guides/platform-guide/introduction/workspace-settings.png\")
From the Workspace Settings page, you can:
\nNote that you can’t delete a workspace that is part of a Multi Workspace Audience. First delete or modify the multiworkspace audience, then you can delete the workspace.
\nmParticle handles Web data — collected from a browser client — a little differently from data collected from native apps.
\nIn most cases, data collected by the mParticle SDK is sent to mParticle, and then forwarded on to integration partners server-to-server.
\nThere are exceptions to this rule: in cases where a server-to-server integration cannot support all the required functionality of an integration partner, an Embedded Kit may be used. Embedded Kits are extra components added to the mParticle SDK that communicate directly with an integration partner from the app client.
\nWhile direct communication between the client and partner is the exception for native apps, it is common for web data. A key reason for this is that most of mParticle’s integration partners are not set up to receive web data server-to-server, as they rely on cookie data only accessible to the cookie owner. To support these integrations, the mParticle Web SDK uses the following workflow:
\nanalytics.js snippet and mParticle’s GoogleAnalyticsEventForwarder.js snippet. We fetch only the integrations that you have enabled in order to keep the page size to a minimum.pageview method.// Example from GoogleAnalyticsEventForwarder.js\n// When mParticle logs a Page View, it automatically calls this function, which invokes Google's `analytics.js` snippet to send the page view to Google Analytics\nfunction logPageView() {\n if (forwarderSettings.classicMode == 'True') {\n _gaq.push(['_trackPageview']);\n }\n else {\n ga(createCmd('send'), 'pageview');\n }\n}To make it easier to work with web integrations, we provide the source code in a public repository, so you can work with the Integration Partner’s documentation and see exactly how we map mParticle methods onto the Partner code. See the mparticle-integrations organization for a complete list of client-side web integrations.
\nmParticle imposes limits on the number and length of attributes that can be associated with events and users.
\nA quick summary of some of the most important limits is below. For more information, see our full Default Service Limits guide.
\nEvents
\nUsers
\nNote that Output Services often have their own limits, which can differ from mParticle’s. When planning your implementation, check the documentation for your Output Services in the Integration Center to make sure you are complying with their limits.
\nBrowsers add third-party tracking protection for end users. The protections affect third-party trackers and their cookies and work in different ways. For example, Firefox Enhanced Tracking Protection (ETP) relies on a list of known trackers to decide what to block. Safari, Chrome for iOS and other browsers with the Apple WebKit engine use Intelligent Tracking Protection (ITP). ITP prevents the browser from loading cookies from a third-party domain.
\nmParticle aligns with this privacy stance.
\n\nmParticle ingests data points that are composed of event attributes and user attributes.
\nFor a given user, attributes are stored at the workspace level, not the device level.
\nUser attributes are ingested according to the following priority:
\nOnce ingested from a particular source type, subsequent source types for that same data won’t be ingested. For example, once you set a user attribute key value using the Web SDK, you won’t be able to set that same value from a partner data feed.
\nWhen mParticle ingests data, there are two timestamps associated with events:
\nIf batches or events have a timestamp that is more than 15 minutes in the future, relative to the server processing the data, that timestamp will be reset to the current server UTC time. Attribute timestamps remain unchanged.
\nIf you load data using CSV Import, the batch timestamp is reset to the current server UTC time.
\nmParticle strives to be as transparent as possible. Part of this transparency is to share information about products, features, or functionality that we expect to deliver in the future.
\nForward-looking statements are as accurate as possible given the knowledge at the time of publication. However, no purchasing decisions should be made on the basis of any forward-looking statement, and mParticle may withdraw or change the products, features, or functionality mentioned in such statements.
\nTo get started with mParticle, set up some data inputs and integrate with at least one output service. See Web End-to-End Tutorial for instructions on how to set up connections, and see your first data flow from input to output. If you aren’t working with Web apps or services, visit Getting Started for more generic instructions.
\nOnce you’re up and running, continue reading the rest of this Platform Guide or browse through the Output Integrations Directory to see the third party tools you can connect with mParticle.
","frontmatter":{"title":"Introduction","order":0.5,"seoTitle":null,"seoDescription":null},"parent":{"__typename":"File","modifiedTime":"October 12, 2026"}}},"pageContext":{"slug":"/guides/platform-overview/introduction/"}},"staticQueryHashes":["2950460867"]}