Ripe.identify
Set up to start sending your lead/users data to Ripe
You should call Ripe.identify when you set a unique identifier for a lead/user, preferably a UID from your database. You should also call Ripe.identify every time a user either logs in or updates any of the attached traits, e.g., email, etc.
Here is an example of what you send could look like:
If a user_id
is not provided, an automatically generated anonymous_id will be used.
It's important always to share email
and format it like in the example whenever it's known. This enables us to enrich and group your leads into companies inside the Ripe app.
Reserved traits
In addition to email
we may use other reserved traits now or in the future, so it's best to map appropriate data for them whenever it's available.
Reserved trait | Type | Description |
---|---|---|
| Object | Street address of a user optionally containing: |
| Number | Age of a user |
| String | URL to an avatar image for the user |
| Date | Userβs birthday |
| String | Description of the user |
| String | Email address of a user |
| String | First name of a user |
| String | Gender of a user |
| String | Unique ID in your database for a user |
| String | Last name of a user |
| String | It is reccomended to pass firstName and lastName for a lead. If you pass a first and last name Ripe automatically fills in the full name for you. |
| String | Phone number of a user |
| String | Title of a user, usually related to their position at a specific company. Example: βVP of Productβ |
| String | Userβs username. This should be unique to each user, like the usernames of Twitter or GitHub. |
| String | Website of a user |
Last updated