Understanding User Activities

Properties are user traits. Activities are actions that the user has actively performed. Activities can come from behaviors that users performed while interacting with your product or from behaviors users performed while interacting with you on third-party products.

Imagine that, before signing up for your product, your user interacted with your Drift livechat or with your Customer Support on Zendesk.

Those touch points are activities that your users performed with you, just not on your product. This is valuable information that you should be aware of when designing your customer journeys.

While Drift and Zendesk are not yet available as our initial integrations, these are planned on our roadmap. Let us know about any use cases youโ€™d like to implement by sending an email or by chatting to us in the livechat below.

Activities coming from your product ๐Ÿ‘จ ๐Ÿ’ป

Events are actions that people perform in your product. Events can be things like button clicks, scrolling to the bottom of a page, or even things that happen behind the scenes like a successful credit card charge. Once you send us event data, you can segment your users based on events that they have or have not performed in your app.

To send events to Plainflow, you will need to integrate the front-end tracking plainlow.js.

To send server side events you will need to install one of our SDKs.

Activities coming from your integrations ๐Ÿ‘ฉ ๐Ÿ’ป

While some integrations (like Clearbit Enrichment and MadKudu output additional traits of your users and those traits will be saved as user properties, others like email notifications can generate user interactions (such as when a user clicks a link or opens an email).

Plainflow will record those user activities so you can use those interactions either to better refine your segments or to create a new workflow.


Not using Plainflow yet? Get your free account here. ๐Ÿ‘ˆ