Back

This article describes how to set up the Userlist.io connector in your Universal Data Hub (UDH) account.

Table of Contents Placeholder

Connector Actions

Action Name AudienceStream EventStream
Track User Data
Track Event

Configure Settings

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.io, 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: https://docs.userlist.io/article/15-integration-guide

Action Settings - Parameters and Options

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.

Action - Track User Data

Parameters

Parameter Description
Identifier
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.

Action - Track Event

Parameters

Parameter Description
Name
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.