Applied to Potions - Potions recorder WIP

Introduction to the technology we use to store in browser user’s data
profile photo
Téo Montlouis

Pain points

Replace identifying cookies and central database to know what a user has done in your website in real-time.
Give users the power to know what data is stored about them and erase it.
Segment in real-time without storing anything

User stories

A developer wants to send the list of UTM a user saw when he converts to be able to attribute a conversion to one or more campaigns in a consent excepted platform
A developer wants to adapt the homepage picture depending on previous navigation.
A developer wants to set up an AB Test

Tech

An on-device event-based database like GA4 and AT Internet
A graphQL API to query this database
Reactive custom elements to display the data stored
A json based segmentation (based on model checking)
Related posts
post image
Potions data model to store events and apply LTL queries to it
post image
Potions core concepts transferred to Potions Framework
post image
Functional programming
Start thinking declaratively
Why move from imperative to declarative code
Powered by Notaku