All Collections
Real-time Audience Segmentation
How Does the LimeSpot Segmentation Engine Process User Behaviors?
How Does the LimeSpot Segmentation Engine Process User Behaviors?

LimeSpot's segmentation engine works in real time but there are different ways user behaviors are processed.

Written by Will Wadman
Updated over a week ago

LimeSpot's segmentation engine works in real-time, meaning that every user action affects their associated segments immediately. This is assuming that the action matches audience segmentation criteria defined for the store.

Based on the above, all of the user behavioral signals are posted to LimeSpot servers in real-time, but there are 3 different ways these behaviors are processed:

  1. Effective on the "current" page load

    • Some of the behavioral signals are processed upon page load and would have an immediate effect on the user segments within the same page. This means that Segment-based Personalization would be effective starting on the same page load. Behavioral signals with immediate effect include Page details (i.e. URL, URL/UTM parameters, referrer site), Device information and Location details.

  2. Effective on the "consecutive" page loads

    • Some of the signals are processed during the page display and would have an effect on the user segments on their next page loads. This means that the Segment-based Personalization starts on their consecutive page views. Almost all of the user behaviors except for the items mentioned above fall into this category. For example: Product Views and Add-to-Carts.

  3. Effective on "consecutive" sessions

    • Some of the behavioral signals are not immediately available to LimeSpot on the Storefront/client-side and need to be received and processed by our backend servers in an asynchronous manner (e.g. via webhooks), therefore there is no guarantee that those signals would be receivable/processable by our servers in a reasonably short period of time. Examples of this category would be all the Order-related criterion (e.g. Number of Orders, Purchase Amount).
      Although we strive to keep the processing of these signals streamlined as much as possible, these items are affected by external factors such as the delays by which webhooks are sent from the eCommerce platform (e.g. Shopify, BigCommerce) or the length of the processing queues according to the traffic.

Did this answer your question?