Mobile Integration

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 step 1 install and integrate forter's mobile sdks reference the mobile sdk https //docs forter com/mobile sdks 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 https //documentation b2c commercecloud salesforce com/doc1/index jsp?topic=%2fcom demandware dochelp%2focapi%2fcurrent%2fusage%2fgettingstartedwithocapi html 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 https //docs forter com/mobile sdks/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" } }