A DataPoint represents a unique data item that has been detected by our system. A DataPoint can be created by calling methods on our SDK such as logEvent, or they can be created using the Events API. Examples of DataPoints are Screen Views, Purchase Events, Navigation Events and Search events among others. All DataPoints are specific to a particular App.
GET
/apps/1/datapoints
Retrieves a list of DataPoints that exist for an App. The 1 after /apps/ is a placeholder for the Application ID.
curl \
-X GET \
-H "Authorization: Bearer YWIxMjdi883GHBBDnjsdKAJQxNjdjYUUJABbg6hdI.8V6HhxW-" \
"https://api.mparticle.com/v1/apps/1/datapoints?accountId=1"
{
"data": [
{
"name": "my event",
"attribute_name": null,
"type": "Event",
"event_type": "navigation",
"data_type": "datapoint",
"created_on": "2015-06-04T18:11:06.027"
},
{
"name": "my event",
"attribute_name": "my event attribute",
"type": "EventAttribute",
"event_type": "navigation",
"data_type": "datapoint",
"created_on": "2015-06-04T18:53:23.25"
},
{
"name": "my screen view",
"attribute_name": null,
"type": "ScreenView",
"event_type": null,
"data_type": "datapoint",
"created_on": "2015-06-04T18:53:23.25"
},
{
"name": "my screen view",
"attribute_name": "my screen view attribute",
"type": "ScreenViewAttribute",
"event_type": null,
"data_type": "datapoint",
"created_on": "2015-06-04T18:53:23.25"
}
],
"dataType": "datapoint",
"errors": null
}
Name | Description |
---|---|
Event | A standard event. |
EventAttribute | An attribute of an event. |
UserAttribute | A user attribute. |
ScreenView | A screen view. |
ScreenViewAttribute | An attribute of a screen view. |
Identity | A user identity type. |
Commerce | A commerce event. |
CommerceAttribute | An attribute of a commerce event. |
If a DataPoint is of type “Event” or “EventAttribute”, then the EventType field will be populated with one of the following values:
Name | Description |
---|---|
unknown | Unknown Event. |
navigation | Navigation Event. |
location | Location Event. |
search | Search Event. |
transaction | Transaction Event. |
user_content | User Content Event. |
user_preference | User Preference Event. |
social | Social Event. |
other | Other Event. |
media | Media Event. |
If a DataPoint is of type Commerce
or CommerceAttribute
, then the EventType field will be populated
with one of the following values:
Name | Description |
---|---|
product_add_to_cart | Add to Cart Event. |
product_remove_from_cart | Remove from Cart Event. |
product_checkout | Checkout Event. |
product_checkout_option | Checkout Option Event. |
product_click | Click Event. |
product_view_detail | View Detail Event. |
product_purchase | Purchase Event. |
product_refund | Refund Event. |
promotion_view | Promotion View Event. |
promotion_click | Promotion Click Event. |
PUT /apps/1/datapoints
Adds a new DataPoint for an App.
curl \
-X PUT \
-H "Authorization: Bearer YWIxMjdi883GHBBDnjsdKAJQxNjdjYUUJABbg6hdI.8V6HhxW-" \
-H "Content-Type: application/json" \
-d "{\"name\":\"my event\",\"type\":"event",\"event_type\": "navigation"}" \
"https://api.mparticle.com/v1/apps/1/datapoints?accountId=1"
[
{
"name": "my event",
"type": "event",
"event_type": "navigation"
}
]
Accepts an array of DataPoint objects, which have the following properties:
Name | Type | Description |
---|---|---|
name | string |
The name of the DataPoint. |
attribute_name | string |
An attribute name (optional). |
type | enum |
The type of DataPoint. |
event_type | enum |
Can only be set if DataPoint type is “Event”, “EventAttribute”, “Commerce” or “CommerceAttribute”. |
The “type” field can be set to one of the following values:
Name | Description |
---|---|
Event | A standard event. |
EventAttribute | An attribute of an event. |
UserAttribute | A user attribute. |
ScreenView | A screen view. |
ScreenViewAttribute | An attribute of a screen view. |
Identity | A user identity type. |
Commerce | A commerce event. |
CommerceAttribute | An attribute of a commerce event. |
The “event_type” field can be set to one of the following values. This field is only required when the “type” is set to “Event” or “EventAttribute”.
Name | Description |
---|---|
unknown | Unknown Event. |
navigation | Navigation Event. |
location | Location Event. |
search | Search Event. |
transaction | Transaction Event. |
user_content | User Content Event. |
user_preference | User Preference Event. |
social | Social Event. |
other | Other Event. |
media | Media Event. |
You can add new DataPoints for an App using the API. DataPoints are automatically detected when data is received from your App, however it may be more convenient to insert this data using the API in advance, rather than waiting until your App is fully instrumented using the mParticle SDK. This will allow you to configure features such as Data Filtering without having to wait for App instrumentation to be completed.
GET /apps/1/GoogleAnalyticsEventForwarder?accountId=1
Get default filtering behavior for a service.
curl \
-X GET \
-H "Authorization: Bearer YWIxMjdi883GHBBDnjsdKAJQxNjdjYUUJABbg6hdI.8V6HhxW-" \
"https://api.mparticle.com/v1/apps/1/GoogleAnalyticsEventForwarder?accountId=1"
{
"data": [
{
"name": "GoogleAnalyticsEventForwarder",
"sendNewDataPointsByDefault": true
}
],
"dataType": "datapoint",
"errors": null
}
This call shows any filtering configuration that exists at the Service level. Currently, this is just one property, "sendNewDataPointsByDefault"
, which controls whether newly detected DataPoints are sent to this Service by default.
PUT /apps/1/GoogleAnalyticsEventForwarder?accountId=1
curl \
-X PUT \
-H "Authorization: Bearer YWIxMjdi883GHBBDnjsdKAJQxNjdjYUUJABbg6hdI.8V6HhxW-" \
-H "Content-Type: application/json" \
-d "{\"sendNewDataPointsByDefault\":false}" \
"https://api.mparticle.com/v1/apps/1/GoogleAnalyticsEventForwarder/datapoints?accountId=1"
{
"sendNewDataPointsByDefault": false
}
Name | Type | Description |
---|---|---|
sendNewDataPointsByDefault | bool | Controls whether newly detected DataPoints are sent to this service by default. |
Setting "sendNewDataPointsByDefault"
to false will prevent newly detected DataPoints from being sent to the specified Service. Any existing DataPoints will not be affected, and will continue to be sent or filtered based on the existing configuration.
GET /apps/1/GoogleAnalyticsEventForwarder/datapoints?accountId=1
Retrieve a list of DataPoint filters for a specific App and Service.
curl \
-X GET \
-H "Authorization: Bearer YWIxMjdi883GHBBDnjsdKAJQxNjdjYUUJABbg6hdI.8V6HhxW-" \
"https://api.mparticle.com/v1/apps/1/GoogleAnalyticsEventForwarder/datapoints?accountId=1"
{
"data": [
{
"name": "my event",
"attribute_name": null,
"type": "Event",
"event_type": "navigation",
"enabled": true,
"data_type": "datapoint_filter"
},
{
"name": "my event",
"attribute_name": "my event attribute",
"type": "EventAttribute",
"enabled": false,
"event_type": "navigation",
"data_type": "datapoint_filter"
}
],
"dataType": "datapoint_filter",
"errors": null
}
Note that this list of DataPoints are filtered by types that are supported by the service. If the service does not support the ScreenView DataPoint for example, then this DataPoint will not appear in the list.
The DataPoint types "EventAttribute"
, "ScreenViewAttribute"
, and "CommerceAttribute"
are child DataPoints that have a parent DataPoint. In these cases, "attribute_name"
will contain the name of the attribute, and "name"
will contain the name of the parent.
PUT /apps/1/GoogleAnalyticsEventForwarder/datapoints?accountId=1
curl \
-X PUT \
-H "Authorization: Bearer YWIxMjdi883GHBBDnjsdKAJQxNjdjYUUJABbg6hdI.8V6HhxW-" \
-H "Content-Type: application/json" \
-d "[{\"name\":\"my event\", \"type\":\"event\", \"event_type\": \"navigation\", \"enabled\": true},{\"name\": \"my event\",\"attribute_name\": \"my event attribute\",\"event_type\": \"navigation\",\"type\": \"eventattribute\",\"enabled\": false}]"
"https://api.mparticle.com/v1/apps/1/GoogleAnalyticsEventForwarder/datapoints?accountId=1"
[
{
"name": "my event",
"type": "Event",
"event_type": "navigation",
"enabled": true
},
{
"name": "my event",
"attribute_name": "my event attribute",
"type": "EventAttribute",
"event_type": "navigation",
"enabled": false
}
]
Accepts an array of DataPoint Filter objects, which have the following properties:
Name | Type | Description |
---|---|---|
name | string |
The name of the DataPoint. |
attribute_name | string |
An attribute name (optional). |
type | enum |
The type of DataPoint. |
event_type | enum |
Can only be set if DataPoint type is “Event”, “EventAttribute”, “Commerce” or “CommerceAttribute”. |
enabled | bool |
Set to false to prevent this DataPoint from being sent to this service. |
The "type"
field can be set to one of the following values:
Name | Description |
---|---|
Event | A standard event. |
EventAttribute | An attribute of an event. |
UserAttribute | A user attribute. |
EventType | Filter all app events of a particular type. |
ScreenView | A screen view. |
ScreenViewAttribute | An attribute of a screen view. |
UserIdentity | A user identity type. |
Commerce | A commerce event. |
CommerceAttribute | An attribute of a commerce event. |
All_User_Attributes | Used to toggle on/off all user attributes. |
All_Workspace_User_Attributes | Used to toggle on/off all workspace level user attributes. |
All_Account_User_Attributes | Used to toggle on/off all account level user attributes, if this feature is enabled. |
If the "type"
is set to "UserIdentity"
, then the "name"
field should be set to one of the following allowed values:
Name | Description |
---|---|
CustomerId | Customer Id. |
Facebook Id. | |
Twitter Handle. | |
Google Id. | |
Microsoft | Microsoft Id. |
Yahoo | Yahoo Id. |
Email Address. | |
Other | Other. |
If the "type"
is set to "Event"
or "EventAttribute"
, the "event_type"
field can be set to one of the following values. If "type"
is set to "EventType"
, then the "name"
field should be set to one of the values below:
Name | Description |
---|---|
unknown | Unknown Event. |
navigation | Navigation Event. |
location | Location Event. |
search | Search Event. |
transaction | Transaction Event. |
user_content | User Content Event. |
user_preference | User Preference Event. |
social | Social Event. |
other | Other Event. |
media | Media Event. |
If the "type"
is set to "Commerce"
or "CommerceAttribute"
, the "event_type"
field can be set to one of the following values:
Name | Description |
---|---|
product_add_to_cart | Add to Cart Event. |
product_remove_from_cart | Remove from Cart Event. |
product_checkout | Checkout Event. |
product_checkout_option | Checkout Option Event. |
product_click | Click Event. |
product_view_detail | View Detail Event. |
product_purchase | Purchase Event. |
product_refund | Refund Event. |
promotion_view | Promotion View Event. |
promotion_click | Promotion Click Event. |
When configuring DataPoints of type "EventAttribute"
or "ScreenViewAttribute"
or "CommerceAttribute"
, you must include the name of the attribute in "attribute_name"
, and the name of the parent DataPoint in "name"
.
When configuring DataPoints of type "Event"
or "EventAttribute"
, you must set the "event_type"
field. Failure to do so will cause an error to occur. The "event_type"
field is ignored for other types of DataPoints other than “Event” and "EventAttribute"
.
If the DataPoint specified does not exist, it will be created automatically. Please note that to avoid creating duplicate DataPoints unintentionally, "type"
, "name"
, "attribute_name"
and "event_type"
should all be set correctly.
Due to the hierarchical nature of DataPoints, disabling some types of DataPoints will cause child DataPoints to also become disabled automatically. For example, turning off EventType "Navigation"
will cause all Events and EventAttributes of that Event Type to become disabled. Turning off an Event will cause all child Event Attributes to become disabled.
Was this page helpful?