Userlist Connector Setup Guide | Server-Side Connectors

Connector Actions

Action Name	AudienceStream	EventStream
Track User Data	✓	✓
Track Event	✓	✓

Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector.

After adding the connector, configure the following settings:

Push API key
- To start sending data into Userlist, you first have to get your Push API Key, which is used to authenticate your requests to the Push API and connect the data with your account.
- Keep this Push API Key secure.
- For more information, see: Getting Your User Data into the System.

Click Next or go to the Actions tab. This is where you configure connector actions.

This section describes how to set up parameters and options for each action.

Parameter	Description
Identifier	Unique identifier for this user. This can be either the user’s primary key in your database, a generated tracking identifier or their email address. For more information, see: Getting Your User Data into the System Integration Guide.
Email	The email address that will be used to send messages to this user.
Signed Up At	The time the user signed up, formatted using ISO 8601. If it is not set, Userlist will use the current time.
Last Seen At	The time the user was last seen inside your application. Formatted using ISO 8601. If it is not set, Userlist will use the current time. Userlist will update this property whenever an event happens for this user.
Properties	Custom properties that further describe the user. What you store here is totally up to you. The object’s keys are normalized to `snake_case`. If they are set, we will use `name`, or `first_name` and `last_name` to represent the user inside of Userlist.

Parameter	Description
Name	The name of the event that is triggered. The name will be normalized to `snake_case`. For more information, see Getting Your User Data into the System.
User	If the identifier is not known to the system, it will create a new user. If the user already exists it will update it using the given information.
Occurred At	The time at which the event occurred. Formatted using ISO 8601. The system will use the current time if you do not provide input.
Properties	Custom properties that further describe the event. What you store in there is totally up to you. The object’s keys will be normalized to `snake_case`.