Skip to main content
All CollectionsAudience SegmentsFAQ
How does the LimeSpot segmentation engine process user behavior?
How does the LimeSpot segmentation engine process user behavior?

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

Updated over a week ago

Note:
This guide is applicable to customers on LimeSpot Max, Premium, Essentials, and other legacy plans.

LimeSpot's segmentation engine works in real-time: Every action a user takes can have an immediate impact on the segments a customer is associated with, assuming that the action matches a defined segmentation criteria.

All of those behavioral signals are sent to LimeSpot servers in real-time, but there are 3 different ways these behaviors are processed which may impact your personalization strategies.

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.

Effective on the "consecutive" page loads

Some of the signals are processed during the page display and have take effect on the next page loads. This means that the segment-based personalization becomes effective 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.

Effective on "consecutive" sessions

Some of the behavioral signals may not immediately available and cannot be reliably used for in-session personalization. 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 or BigCommerce) or the length of the processing queues according to the traffic. This includes all the Order-related criterion (e.g. Number of Orders, Purchase Amount).

Did this answer your question?