Custom events in customer360

Introduction:

Once events are defined for a custom integration, they automatically appear on the events page, with events under the particular source/integration (eg: Razorpay).

Each custom event has an integration status and subscription.

• Integration status: This defines whether a particular integration is active or not (eg: event_1 is inactive, which means it's discarded in integrations module)

  
  

• Subscription: This defines whether customer360 can consume a particular event and what is the action necessary to allow the event to be consumed by customer360.

  • Activate the event: The integration needs to be activated to send events to customer360
  • Mapping pending: The mapping for phone number/E-mail (profile identifier) is pending
  • Completed: The events can be consumed by customer360

When we click on an event we get to the mapping screen where properties defined in integrations can be mapped to profile properties in customer360. To complete mapping phone number/E-mail mapping is must and other attributes can be mapped optionally. Post mapping, the attribute values are mapped to a profile and can be subsequently used in segmentation and automated campaigns.

Custom events in segmentation: All custom events with mapping completed status appear in the event drop-down. In the below example all the users who have performed "Signup" on "Website" with "city" = "Mumabi" at least once between the specific dates will be part of the segment. Now we can send a welcome nudge to these users to engage further with them.