The initial step in implementing Real-Time Triggers (formerly Track & Trigger) is scheduling a kick-off call with Optimove’s Product Integration Team to ensure the smoothest process possible.
Following the call, you can embed the Optimove SDKs in your website and/or mobile apps (iOS and Android native are currently supported).
For detailed information about implementing the various Optimove SDKs, see the following guides:
- Integrating the Optimove Web SDK
- Integrating the Optimove iOS SDK
- Integrating the Optimove Android SDK
- Integrating the Optimove Flutter SDK
- Integrating the Optimove Unity SDK
- Integrating the Optimove Cordova SDK
- Integrating the Optimove React Native SDK
You can implement any combination of the Optimove SDKs according to your business needs – all events reported from the various SDKs are collected by Optimove into a single pool of events to be used for both user activity tracking and triggered campaigns.
There are four different ways to report customer IDs to Optimove using the SDKs:
- Reporting customer IDs that are identical to the customer IDs sent to Optimove in your batch data update process. In this scenario, all customer events reported from your website/app must utilize customer IDs that are identical to the customer IDs included in the batch data update.
- Reporting customer IDs that are different than the customer IDs sent to Optimove in your batch data update. In this scenario, the customer records sent from your system to Optimove as part of the batch data update must contain both the customer IDs used to identify customers in the Optimove database, as well as the customer IDs sent from the SDK.
- Reporting hashed customer IDs. In this scenario, the customer records sent from your system to Optimove as part of the batch data update must contain both the customer IDs used to identify customers in the Optimove database, as well as the hashed customer IDs that are sent from the SDK.
- Reporting encrypted customer IDs to Optimove from the Web or Mobile SDKs. In this scenario, you will share with Optimove a decryption key as part of the SDK onboarding process. Optimove will then use this key to decrypt the customer IDs sent from the SDK.