Custom events

Atomic lets you send your own analytics events to Atomic. For example, you can send existing analytics events from your apps, or business events from 3rd party systems.

Atomic stores metadata about custom events in the profile record for the associated customer, and you can then use this metadata when applying filters and building segments.

Atomic currently stores when an event was first and last seen, for each customer.

Let's consider an example. You may want to create a segment of customers who have visited a particular screen in your app, or who have made a support enquiry, or other key action. When a customer enters that segment, you may want to then trigger an Action Flow for them, using a Segment entered trigger.

Sending custom events to Atomic

Read about how to send custom events by API or in-app via the SDKs in the analytics overview article

Configuring custom events

You do not need to pre-configure Atomic to accept custom events. The first time we see an event, we will detect it and add it to the list of known/recognized events. At any time, you can remove an unused event from the custom events configuration area.