Skip to main content

User

User is the recipient who can receive notifications from your app. You should use our API or front-end SDK to send your user's data to Engagespot, so that Engagespot can deliver notifications to them.

Why Engagespot needs to identify your users?

When you use a third party service like Engagespot to build your multi-channel product notification infrastructure, we manage the delivery, store your user's notification preferences etc. So it is essential that you share your user's details like email, phone number etc to our system. We store your user's information in a highly secure and encrypted environment.

Structure of user data

Every user should have a unique identifier. It could be the auto-increment id from your database, or any other unique value such as their Email or Phone number.

info

The unique identifier you choose for the user should be unique across your entire application. It should never change.

Additional attributes

Along with the unique identifier, a user can have multiple attributes attached to their profile. This could be their Email id, phone number, FCM token, profile picture, name or anything. Some notification channels requires certain attributes in the user's profile to work. For example, the SMS channel works only for users who have phoneNumber attribute set in their profile. To read more about profiles, and how to set them, read User Profile guide

Here are some of the attributes that is recommended for your users.

AttributeUsage
emailUsed to deliver emails to the user. If you set your identifier itself as the email, then this property will be auto created.
phoneNumberUsed to deliver SMS and WhatsApp messages. Make sure to use the E.164 format

Sending your user's data to Engagespot

You can let Engagespot identify your app users via multiple ways.

If you use Engagespot notification feed component in your front-end app such as React, Angular, Vue or any other Javascript stack, you can directly use the component to initialize and identify a user who logged into your app. Or else you can use the User REST API directly.

<Engagespot apiKey="ENGAGESPOT_API_KEY" userId="XXXX" />

When should you send your user's data?

The simple rule is to send the user's data whenever it is available. For example, during signup, login, or profile update operation in your app. Make sure you share the user's data before sending any notification to them.

danger

If you try to send a notification to a user whose data isn't available in Engagespot, it will be discarded.