Sending Custom Events

You can send custom events to Reteno simultaneously via

• SDK (frontend events),
• Backend API (Server to Server events)
• Integration with the Amplitude platform

Let’s consider sending custom events in detail.

📘

Note

Event parameter data is stored for 2 years. Communications triggered by an event can reference that event's parameters for up to this period.

Creating Event Plan

Proper event planning lays the groundwork for successful marketing campaigns. Therefore, we recommend first identifying all the events you need to track and then configuring their sending via SDK and API.

API & SDK Event Examples

Events sent via SDK include data about user’s in-app actions. Examples:

• LessonStarted/Completed
• GoalSet/Achieved
• HealthMetricsRecorded
• SleepTracked
• SearchPerformed

Events sent via Backend API typically involve sensitive data or require server-side validation and processing. Examples:

• AccountCreated
• UserUpdated (changes in user profile information that are managed server-side)
• SubscriptionStarted/Renewed/Updated/Canceled
• PaymentCompleted/Failed
• ReferralInviteAccepted

Sending Custom Events via SDK

Follow the steps below to send custom events via SDK:

1. Integrate the SDK:

   • Connect your mobile app to Reteno.
   • Set up the SDK access key.
   • Add the SDK for the platforms you use to your mobile app.

2. Create Event Payloads:

   • Track any custom events on iOS, Android, and other available platforms (see User Behaviour articles in the SDK documentation).

The SDK will handle the communication with Reteno and send the tracked events in real-time.

📘

Note

Follow the link to see the list of system SDK events, which tracking you can turn on or off.

Sending Custom Events via Backend API

Follow the steps below to use the Backend API for server-side events:

1. Set Up API Access:

   • Obtain the API key from Reteno.
   • Configure authentication mechanisms in your backend system.

2. Create Event Payloads:

   • Use the Generate event API method to send custom events in the format described by the link.

3. Send Events via API:

   • Use an HTTP client (e.g., Axios, cURL, Postman) to send POST requests to the https://api.reteno.com/api/v3/event endpoint.

To see transferred events, go to the Automation → Event history tab, click on the event, and verify that the parameters contain data you passed in.

📘

Note

An event with a matching externalCustomerId doesn't automatically appear linked to the contact unless segmentation is enabled for that event type. If a backend-sent event isn't showing up on the contact's card despite a matching identifier, enable segmentation for that event type — this activates the event-to-contact linking.

Sending Custom Events from Amplitude

If you are using Amplitude for event analytics, you can integrate this platform with Reteno to avoid manual event tracking configuration. The integration process does not require the involvement of developers and is completed in a few clicks.

Follow the link to see details >

Managing Events

1. Keep Consistency:

   • Implement checks to ensure that event data sent from the SDK and the Backend API are consistent and accurate.

2. Monitor and Debug:

   • Use Android and iOS debug modes to ensure all SDK events and user properties are logged correctly.
   • Validate events and their parameters — note that contact identifiers are capped at 300 characters and additional event parameter values at 100 characters; if an event doesn't appear in Event history with the data you expect, check whether a parameter value exceeded these limits.
   • Set up alerts for failed event submissions.
   • Track statistical indicators.

By following these steps, you can effectively manage sending events from both the frontend (via SDK) and the backend (via API). This ensures comprehensive tracking of custom events, enabling more accurate analysis and personalized marketing campaigns.