Events Overview.

Just as properties are being pushed from sources, so are events. But while properties are being set for accounts and users, and —best comparable to variable instances in a programming language— represents a certain value for a certain key attribute, events are signals that indicates a certain action occurred. Since these events represent the bases for computed properties —e.g. count amount of logins for the last 7 days— it is extremely important they are managed correctly.

Events Overview

Programmatic tagged events vs journy.io named events.

When a developer decides to send a signal that a user or an account has performed a certain important action, he can do so using our APIs. See Events API. These events are primarily defined by its tag (aka event name).

journy.io allows for logical separation between dev event tags and logical events, defined in journy.io.
Example:
(dev) tag: "login-started" => (journy.io) name: "Login Started"
(dev) tag: "started-login" => (journy.io) name: "Login Started"

If journy.io receives either tags, it will be regarded in journy.io as a logical same name.

Auto-discovery.

Sources are sending events to journy.io. Upon defining app sources, the option is being given to "Add events and update properties for contacts".

If set, sources will be able to push events with tags any way they choose, at random. If event tags were not already previously defined in journy.io, they will be auto-discovered (in Events -> Discover) and journy.io admins will be able to transform them into logical journy.io named events; either into new journy.io named events, or into existing named events.

if the source option "Add events and update properties for contacts" is NOT set, sources will only be allowed to push already previously defined tagged events.

Further journy.io events logic.

Once events are named and defined within journy.io, all calculations for properties or flows or other computed items will work with these logical journy.io named events. Non-defined non-named logical events will in journy.io be represented by 'Others'.

Deleting an event, only deletes the logical named value of an event, but does not delete any native data. So, if an event got deleted, its tags will be pushed back to auto-discovery (in Events->Discover) and you'll be able to re-define it again, without ever losing any data.
Was this article helpful?
Cancel
Thank you!