Integrations
Indicative is a customer journey analytics platform designed for product and marketing teams to leverage complex analysis to build better products that drive conversion, increase engagement, and retain customers.
Indicative supports the following user and device identities.
Indicative supports the following event types:
Indicative accepts data from any timeframe.
Indicative uses mParticle’s MPID as the Indicative eventUniqueId
. The MPID is therefore the only user identity to match incoming event and audience updates to the correct user profile in Indicative. Therefore, the configuration of IDSync and the identity strategy for your mParticle account will be applied to events in Indicative.
The following mParticle event types are translated into Indicative events.
mParticle Event Type | Indicative Event Name | Note |
---|---|---|
ApplicationStateTransition | App Install, App Upgrade, App Initialize, App Exit, App Background, App Foreground | |
Commerce: Impression | Impression | |
Impression Item | These events are sent only if Process Impression Item Events is set to True | |
Commerce: ProductAction | $action | For example, “Purchase” |
$action Item | For example, “Purchase Item”. These events are only processed If Process Product Action Item Events is enabled. | |
Commerce: PromotionAction | Promo $action | For example, “Promo Click” |
Commerce: PromotionAction | Promo $action Item | For example, “Promo Click Item.” These events are only processed if Process Promotion Item Events is enabled. |
Custom Event | CustomEvent.name | |
Custom Event - type Attribution | Attribution | |
Crash Report | Error | |
PushMessageReceived | Push Received | |
PushSubscription | Push $action | $action will be either “Subscribe” or “Unsubscribe.” |
ScreenView | Screen View | |
SessionEnd | Session End | |
SessionStart | Session Start |
If you have a custom attribute name that is the same as an event name in Indicative, for example screen_name
, you can keep both values by requesting that the prefix mp_
be added to one of the names. If you don’t do this, Indicative chooses one value at random and drops the other, leading to unpredictable results.
To request this, submit a request to Support.
mParticle attributes are converted to Indicative properties automatically when forwarded. The Indicative naming conventions closely match mParticle, with the following exceptions:
mParticle Property Value or Path | Indicative User Property Name | Note |
---|---|---|
platform | mp_rt_env | |
ip | mp_rt_ip | |
sdk_version | mp_rt_sdkversion | |
http_header_user_agent | mp_rt_useragent | |
ErrorEvent.breadcrumbs | breadcrumbs | A comma-delimited string of breadcrumbs |
CustomEvent.name | custom_event_name | |
CustomEvent.customType | custom_event_type | |
ImpressionEvent.impression_list_name | list_name | |
CommerceEvent.product.$key | product_$key | A comma-delimited string of values. |
Impression[].Product[].key | product_$key | For example, “product_brand” for Impression[].Product[].brand or “product_id” for Impression[].Product[].id |
PushSubscriptionEvent | is_push_subscribed | True or False, depending on the action |
mParticle user attributes are included in a UserAttributeChangeEvent or directly from event types. The following user attributes are converted to Indicative user properties when forwarded:
mParticle Property Value or Path | Indicative User Property Name | Note |
---|---|---|
user_identities | user_id.$type | For example, user_id.customer |
device_info | device_id.$type | For example, device_id.ios_advertising_id |
user_attributes | ua_$key | For example, ua_$firstname and ua_color=’red’ |
UserAttributeChangeEvent.added{}.value | ua_$key | |
UserAttributeChangeEvent.removed{}.key | ua_$key | Indicative does not support unsetting a user attribute, so the value is replaced with “$unset”. For example, userattr_color=”$unset”. |
You can set configuration values for different inputs, and connection setting values to control the behavior of data once it is input.
Setting Name | Data Type | Default Value | Description |
---|---|---|---|
API Key | string |
Input your project API key found within your Indicative project settings. | |
User Identity Field | string |
MPID |
Select which user identity to identify users in Indicative. Must be one of CustomerId, Email, MPID, or Other. |
Setting Name | Data Type | Default Value | Description |
---|---|---|---|
Process Impression Item Events | boolean |
False | Choose whether to record additional events for each Product in an Impression event. Enabling this may increase your Indicative event volume significantly. |
Process Product Action Item Events | boolean |
True | Choose whether to record additional events for each Product in a Product Action event. Enabling this may increase your Indicative event volume significantly. |
Process Promotion Item Events | boolean |
True | Choose whether to record additional events for each Promotion in an Promotion Action event. |
Was this page helpful?