Before you start this activity, you should have already:
mParticle collects two important kinds of data:
Event data is about actions taken by a user in your app. Some events are collected automatically by mParticle’s native SDKs. These include the Session Start events you saw in the Live stream when you first set up your input. Other events need to be captured by writing code in your app. Of these, the most significant are:
mParticle also captures data about your user, including their identities, information about the device they are using and any custom attributes you set. As with event data, some user data, such as information about the devices they use, is captured automatically by mParticle’s native SDKs. Two important types of user data must be captured by writing code in your app:
User Attributes are key-value pairs that can store any custom data about your user. The value of a user attribute can be:
null- attributes with a
nullvalue function as ‘tags’, and can be used to sort your users into categories.
To start capturing data you will need to go back to your app code. In the previous step you should have installed and initialized the mParticle SDK in at least one of your app platforms. This means you’re already set up to capture Session Start and Session End events, as well as basic data about the device. Grab a friendly developer again, if you need one, and try to add some additional user and event data to your implementation. Here are a few things you might try, with links to the appropriate developer docs:
categoryof content, and the travel
destinationthe video promotes. Later on, you’ll see how events like these can be used to target custom messaging.
Once you’ve added code to your app to start collecting some basic data, start up a development build of your app again and trigger some events. Have another look at the Live Stream. You should start to see new event batches, with the individual events you have added to your app.
If you have at least some data in your Live Stream, such as the session start and session end messages generated in the previous step, but your screen views, custom events or purchases aren’t showing, it’s likely that there is an issue with your app code.
Excellent, you’ve started collecting real custom datapoints from your app. At this point you might want to take a quick break to:
Now that you’re collecting data, it’s time to send it on by connecting an event output.
Was this page helpful?