SDK overview

Resulticks SDK is a small snippet of proprietary code. The code snippet needs to be embedded on the brand’s properties or endpoints to enable tracking of user sessions on the properties and capture of related data. A few examples are:

• Session details (Example: time spent on a webpage, browsing patterns of a user)
• Device fingerprinting
• Real-time data (Example: current time, location)

Resulticks Web SDK code supports Firebase cloud messaging (FCM) or Google cloud messaging (GCM). Resulticks App SDK code supports both Android and iOS apps. It can also be customized to support any digital properties coded in Cordova PhoneGap Ionic, JavaScript, React Native, Flutter and Xamarin.

Usage of SDK

The Resulticks SDK code can be used on web pages and within mobile apps as a standalone tracking feature for analytics. It can also serve as the container encapsulating existing analytic integrations, for example, Resulticks Analytics, Google Analytics, and Adobe Analytics with corresponding connector variables. The SDK ensures the capture of analytics from these existing analytics engines through a single point – the Resulticks SDK code. Besides, this approach also provides maximum code efficiency and ensures page performance with minimal payload.

The SDK code tracks user journeys that may originate from channels such as the following and end in either a brand website or any mobile app page:

• Social media
• Search engines
• Email/SMS communications
• Push notifications
• Beacon* framework
• Voice assistant framework

Note Beacons are small electronic devices that detect a user within a preset range and deliver notifications and marketing campaigns directly to the brand user's mobile app when they are within the range of a beacon.

How does it work?

The SDK recognizes the request received on the web or app page and responds to the request received. The SDK records a request in the form of an event at the back end when a user activity happens on the web or app page. Events may be default or custom events, as discussed in section 4. Some of these are ‘default’ events – app launch, install. Others are custom events – adding product to the cart, On receiving a request, the SDK performs the following activities:

1. Determines whether the identified domain is valid or not.
2. Generate the SDK code and configure the SDK using Resulticks – Web domain settings to enable domain recognition.
3. Parses the request received process to identify the event that has occurred by mapping it to event data registered at the backend.
4. Checks the audience data received on parsing against the data stored on Resulticks (Example: Using device fingerprinting) to determine whether the user is a known or unknown user.
5. Determines the script to load on the web/app page based on the event and the audience identified. By validating the request, the SDK ensures only the necessary scripts are loaded and enables contextual communication to the individual visitor on the page. This approach also enables features like:
   • Progressive profiling
   • Dynamic offer push
   • Re-targeting
   • On-demand personalization