Looking to combine on Amplitude for both your Analytics and CDP needs?
This document covers the necessary steps to:
Quickly review the offerings that are available for mParticle and how that stacks up to Amplitude.
mParticle | Amplitude |
---|---|
Connections | Sources & Destinations |
Audiences | Audiences |
Data Management |
Follow a strict release process and configure multiple environments. Validate changes within each environment before deploying.
To add a new source:
For detailed instructions, see the documentation for the source you want to add.
Both mParticle and Amplitude SDKs capture first-party data by tracking user interactions. Other than some nuances around syntax, they work similarly. Here is high level mapping of concepts between mParticle & Amplitude.
mParticle | Amplitude | Notes |
---|---|---|
app_key | api_key | Unique key to validate source of the data. |
Workspace | Project | Projects allow you to organize your data. |
User | User | User who is performing action. |
Identify | Identify | Identify updates properties/attributes of the user. |
Event | Event | Events track the action user is performing. |
Screen | Event | Create an Event to track Screen views. |
Page | Event | Create an Event to track Page views. |
Group | Group is a collection of users. In Amplitude one user could belong to multiple groups. Each group can have properties/attributes that are then available to query/forward on actions performed by any user in the group. | |
Kits | Plugins | Plugins let you extend Amplitude by running a sequence of custom code on every event. |
1var identityRequest = {2userIdentities: { email: 'updated-email@example.com' }3}4mParticle.Identity.modify(identityRequest, identityCallback);
1setUserId('12091906-01011992');2identify(3 Identify()4 .set('email', 'updated-email@example.com')5);
1mParticle.logEvent('Article Completed',2 mParticle.EventType.EVENT-TYPE,3 {4 'title':'How to Create a Tracking Plan',5 'course':'Intro to Analytics'}6);
1track('Article Completed', {2 title: 'How to Create a Tracking Plan',3 course: 'Intro to Analytics',4});
Assign user to a group:
1amplitude.setGroup('Working Group', 'UNIVAC')
Update properties of a group:
1groupIdentify(2 'Working Group',3 'UNIVAC' ,4 new Identify()5 .set('principles', ['Eckert', 'Mauchly']);6 .set('site', 'Eckert–Mauchly Computer Corporation');7 .set('statedGoals', 'Develop the first commercial computer');8 .set('industry', 'Technology')9);
1currentUser?.setUserAttribute("top_region", value: "Europe")
1Amplitude.instance().setUserId("abc")2Amplitude.instance().identify(3 AMPIdentify()4 .set("top_region", value: "Europe")5)
1if let event = MPEvent(name: "Video Watched", type: MPEventType.navigation) {2event.customAttributes = ["category": "Destination Intro", "title": "Paris"]3MParticle.sharedInstance().logEvent(event)4}
1Amplitude.instance().logEvent("Video Watched", withEventProperties: ["category": "Destination Intro", "title": "Paris"] )
Assign user to a group:
1Amplitude.instance().setGroup("orgName", groupName:NSString(string:"xyz"))
Update properties of a group:
1Amplitude.instance().groupIdentifyWithGroupType(2 "orgName",3 groupName:NSString(string:"xyz"),4 groupIdentify:AMPIdentify().set("plan", value: "enterprise")5)
1IdentityApiRequest modifyRequest = IdentityApiRequest.withEmptyUser()2 .email("updated-email@example.com")3 .build()4 5MParticle.getInstance().Identity().modify(modifyRequest)
1amplitude.setUserId("abc")2amplitude.identify(Identify().set("email", "updated-email@example.com"))
1val customAttributes: MutableMap<String, String> = HashMap()2customAttributes["name"] = "Moto 360"3val event = MPEvent.Builder("Product Viewed", MParticle.EventType.Navigation)4 .customAttributes(customAttributes)5 .build()6MParticle.getInstance()?.logEvent(event)
1amplitude.track(2 "Product Viewed",3 mutableMapOf<String, Any?>("name" to "Moto 360")4)
Assign user to a group:
1amplitude.setGroup("orgName", "xyz");
Update properties of a group:
1amplitude.groupIdentify("orgName", "xyz", Identify().set("plan", "enterprise"))
For all other SDKs, see the relevant SDK documentation.
Data validation is a critical step in the instrumentation process. Amplitude lets validate your event data via Amplitude's debugging tools.
To add a new destination:
For detailed instructions, see the documentation for the destination you want to add.
It's important to validate the migration to make sure there is minimal impact on downstream data consumers.
How long does it take to migrate?
What if I don't see an integration that I need?
What if I have an existing CDP contract?
Thanks for your feedback!
November 21st, 2024
Need help? Contact Support
Visit Amplitude.com
Have a look at the Amplitude Blog
Learn more at Amplitude Academy
© 2024 Amplitude, Inc. All rights reserved. Amplitude is a registered trademark of Amplitude, Inc.