Claspo gives you several ways to control when a widget appears and who should see it. Used well, these rules turn a simple popup into something helpful and relevant.
Different ways to trigger widgets in Claspo
Claspo supports multiple triggering methods, so you can match the right UX pattern to the right situation:
Rule-based triggers and targeting — set conditions based on behavior, audience attributes, pages, and more. Best when you want full control over timing, audience, and pages. Ideal for shaping the journey across the whole site without writing code.
Teaser and launcher click-based — show a small launcher button that visitors can open when they’re ready. Useful when you don’t want to interrupt visitors. They can open the widget when they’re curious, which often leads to higher-intent interactions.
HTML element click-based — open a widget when a visitor clicks any element on your site — buttons, links, banners, icons, etc. Instead of building new UI, you attach the widget to what’s already there.
JS API-based triggering — the strongest option for custom logic. Developers can trigger widgets exactly when internal conditions are met — after registration, after a purchase, or when an event fires in your system.
Together, these options let you build the exact interaction pattern your site needs.
Signals you can work with
Claspo lets you decide when a widget should appear based on real behavior. For example, you can wait until someone has spent enough time reading, scrolled far down the page, viewed several pages, or paused for a moment. These are good indicators of interest — and a natural time to offer help or show a promotion.
You can also respond to context. A visitor on mobile might need a shorter layout, while someone from a specific country might see a localized offer. Traffic source, campaigns, and UTM parameters help match your message to intent.
For even more control, advanced data such as Data Layer events, cookies, Local Storage keys, or JavaScript variables let you trigger widgets based on what your site already knows. This is useful for login state, customer type, cart status, or any custom condition that matters to your business.
Combined, these options make it easy to keep simple flows lightweight or build highly personalized journeys.