Just as source properties are being pushed from sources, so are events. But while properties are being separately 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 indicate certain actions occurred. Since these events often represent the bases for computed properties โ€”e.g. count amount of logins for the last 7 days and compare it to the previous 7โ€” it is extremely important they are managed correctly.

An event to linked to either 1 user, either 1 account, or both 1 user and 1 account.

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.


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


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.

Add events manually

In case of sources not being allowed to "push new events and create/update properties", you can create events manually, forcing the developers to use only pre-defined events. This is an additional security layer.

Here's what you need to do step by step:

  • Go to the Data Catalog menu, Events submenu, to the Setup section.

  • Press the [ + ] button in the upper right corner.

  • Give a name to that event, as well as an event name (aka tag).

  • Select the event group the event is part of.

  • Press the "Add Event" button.

You'll see the event appearing in the list.

Add event, from auto-discovered tag

In most cases, set as default, sources will be pushing new event tags to journy.io. You can easily add those tags as new logical events in journy.io, or add them tho existing logical journy.io events.

Here's what you need to do step by step:

  • Go to the Data Catalog menu, Events submenu, to the Discovery section.

  • Over over the event tag you want to add and press the [ + ] button that appears.

  • Choose to ether add new event, or to add it to an existing event.

Delete an event, restore to Discover

If you don't want an event to be counted into journy.io's event scheme, you can easily delete it.

If the event had previously been auto-discovered, or if the event actually occured, you will find the representing event tags back in the Discover section.

Here's what you need to do step by step:

  • Go to the Events menu, to the Setup section.

  • Hoover over the event you want to delete and press the [...] menu button.

  • Select "Delete event" and press the "Remove" button.

You'll see the event disappear from the list.

If you then go back to the Discover section, you'll see the raw event tags that were associated with the recently deleted logical event.

Tip: journy.io offers free onboarding! ๐Ÿš€

Go to the Onboarding Page and book your 60 minute spot!

Did this answer your question?