This article is useful for you if you are familiar with and have already successfully implemented the WebTag API authentication flow. For more information, see Authentication for website and app implementations.
The mParticle integration aims at implementing the capabilities of the WebTag on your mobile app. When a customer browses the mobile application and adds products to their basket, you want to ensure that this information is fed through Customer Data Platform (CDP).
This integration is using the mParticle SDK. It pushes the Customer and Event objects to CDP. It pushes the following event types:
- login
- logout
- onsiteSearch
- productBrowsed
- categoryBrowsed
- brandBrowsed
- cartUpdated
Use cases
- Collect abandoned session, cart, browse on the app and include them in your email journey
- Identify app users to target them on Facebook with an app-specific offer
Setup
CDP’s integration with mParticle was developed and documented by mParticle, c.f. Event.
mParticle has experience implementing this integration. You can leverage your mParticle account manager to go through the details.
- Provide your CDP Customer Value Manager with your estimated traffic for your mobile app. Min/max/average number of users, that is, cookies/ devices in this case, average number of Page Views per day in a typical scenario and in the “worst-case” scenarios, such as Black Friday.
- CDP provides you with mParticle WebTag credentials for the development environment.
- In the mParticle configuration tool, enter your username, password, tenant ID, SourceOrganizationNumber.
- Assisted by your mParticle account manager, turn OFF/ON the events as needed in the mParticle setup and review the default settings.
- Once validated in Dev, CDP provides you with Production credentials.
Be careful with the following:
- Do not turn on Transaction and TransactionItem unless they are also enabled on your website.
- Referential integrity: The Product Number, Customer Number, Category Number, Organization Number, and Transaction Number, must match the data that you send through other sources (website, daily data feeds, Google Analytics.
- If you use the same application in multiple countries, work with your mParticle account manager to ensure that you only send data from the relevant countries to CDP.
- When the authentication token is no longer valid (or is close to becoming invalid), “delete” and re-enter the CDP mParticle user credentials in the mParticle configuration screen. This forces the mParticle to request a token again and this token is valid for the same period as the previous one.
mParticle
This article is useful for you if you are familiar with and have already successfully implemented the WebTag API authentication flow. For more information, see Authentication for website and app implementations.
The mParticle integration aims at implementing the capabilities of the WebTag on your mobile app. When a customer browses the mobile application and adds products to their basket, you want to ensure that this information is fed through Customer Data Platform (CDP).
This integration is using the mParticle SDK. It pushes the Customer and Event objects to CDP. It pushes the following event types:
- login
- logout
- onsiteSearch
- productBrowsed
- categoryBrowsed
- brandBrowsed
- cartUpdated
Use cases
- Collect abandoned session, cart, browse on the app and include them in your email journey
- Identify app users to target them on Facebook with an app-specific offer
Setup
CDP’s integration with mParticle was developed and documented by mParticle, c.f. Event.
mParticle has experience implementing this integration. You can leverage your mParticle account manager to go through the details.
- Provide your CDP Customer Value Manager with your estimated traffic for your mobile app. Min/max/average number of users, that is, cookies/ devices in this case, average number of Page Views per day in a typical scenario and in the “worst-case” scenarios, such as Black Friday.
- CDP provides you with mParticle WebTag credentials for the development environment.
- In the mParticle configuration tool, enter your username, password, tenant ID, SourceOrganizationNumber.
- Assisted by your mParticle account manager, turn OFF/ON the events as needed in the mParticle setup and review the default settings.
- Once validated in Dev, CDP provides you with Production credentials.
Be careful with the following:
- Do not turn on Transaction and TransactionItem unless they are also enabled on your website.
- Referential integrity: The Product Number, Customer Number, Category Number, Organization Number, and Transaction Number, must match the data that you send through other sources (website, daily data feeds, Google Analytics.
- If you use the same application in multiple countries, work with your mParticle account manager to ensure that you only send data from the relevant countries to CDP.
- When the authentication token is no longer valid (or is close to becoming invalid), “delete” and re-enter the CDP mParticle user credentials in the mParticle configuration screen. This forces the mParticle to request a token again and this token is valid for the same period as the previous one.
Acquia CDP