Mobile Integration

Mobile Platform Integrations for SFCC

For merchants who have native mobile apps or React mobile Applications Forter offers mobile SDKs for IOS and Android, as well as a React Plugin for both operating systems.

Note that mobile web orders do not require mobile SDK integrations.

Step 1: Install and Integrate Forter's Mobile SDKs

Reference the Mobile SDK integration guide for your relevant mobile applications. You will need your Forter siteId (sandbox or production) to install the SDKs.

Unique IDs

For native mobile apps, integrate the respective mobile SDKs. The SDKs provide methods that generate a unique identifier for the mobile user based on pre-existing, PII compliant persistent device identifiers (IDFV - Identifier For Vendor for iOS and deviceID for Android).

Event Data

The SDKs also provide simple methods that merchants can call to asynchronously send Forter behavioral events. These events include actions like "add_to_cart", "search", or "Accept terms of service".

The mobileUID should be included with the different events so that Forter's models can connect a user's behaviors and actions to the subsequent transaction.

Step 2: Pass the Forter MobileUID back to your SFCC platform

Send the mobileUID generated by the Forter SDKs to your SFCC backend when an order is placed via your native mobile application. This will allow Forter to connect behavioral and cyber data collected on the mobile applications to the order data sent in SFCC. Forter recommends using the Salesforce OCAPI framework to pass the mobileUID securely back to your SFCC platform to include with the order data.

If your app uses a Webview on the checkout page, please see our Android Webview Integration documentation.

Step 4: Include the MobileUID and orderType in the request parameters of the cartridge

You will need to add logic to the ForterOrder.js file of your cartridge that specifies mobile orders. Native Mobile App Orders should have the following designations:

• orderType: should be MOBILE(for either iOS or Android), ANDROID, or iOS
• connectionInformation: object should populate the forterMobileUID field with the mobileUID instead of the forterTokenCookie and the userAgent and mobileAppVersion should be populated with the relevant mobile device information of the end user.

Example Request:

{
  "orderId": "Example_order_fdse0gb449",
  "orderType": "MOBILE",
  "timeSentToForter": 1415287568000,
  "checkoutTime": 1415273168,
  "connectionInformation": {
    "customerIP": "174.255.8.151",
    "userAgent": "testStore 4.92.203 rv:203 (Android; Linux: 24 7.0; en_US; LGL158VL)",
    "forterMobileUID": "f3c6650468a18a",
    "mobileAppVersion": "4.70.103"
  },
  "totalAmount": {
    "amountUSD": "99.95"
  }
}