Usermaven (Actions) Destination
Usermaven is an all-in-one analytics solution for online businesses looking to unlock growth and make data-driven decisions - without spending hours on setup.
Usermaven (Actions) provides the following benefits:
- Clear mapping of data. Actions-based destinations enable you to define the mapping between the data Segment received from your source and the data Segment sends to Usermaven.
- Pre-built mapping. Mappings for Usermaven are prebuilt with the prescribed parameters and available for customization.
- No 3rd party tool is involved. Move the data directly from Segment to Usermaven without a 3rd party tool to facilitate the data sync.
- Track events, identify users and companies. You can track events, identify users and companies in Usermaven using Actions-based destinations.
- From the Segment web app, click Catalog, then click Destinations.
- Search for "Usermaven (Actions)" in the Destinations Catalog, and select the destination.
- Click Configure Usermaven (Actions).
- Select an existing Source to connect to Usermaven (Actions).
- Go to the Usermaven App, and navigate to Workspace Settings > General Settings and copy the API Key.
- Enter the "API Key" in the "Usermaven (Actions)" destination settings in Segment.
Found on your general settings page.
Found on your general settings page.
Usermaven (Actions) has the following presets
| Preset Name | Trigger | Default Action |
|---|---|---|
| Identify User | Event type = "identify" | Identify User |
| Group | Event type = "group" | Group |
| Page | Event type = "page" | Page |
| Track Event | Event type = "track" | Track Event |
Build your own Mappings. Combine supported triggers with the following Usermaven-supported actions:
Mapping limits per destination
Sets a user data.
Identify User is a Cloud action.
The user id, to uniquely identify the user
The user email address
Optional
The timestamp when the user was created
Optional
The user first name
Optional
The user last name
Optional
The user custom attributes
Optional
User Anonymous id
Optional
The ID of the event.
Optional
The path of the document.
Optional
The search query of the document.
Optional
The type of the event.
Optional
The title of the page where the event occurred.
Optional
The referrer of the page where the event occurred.
Optional
The URL of the page where the event occurred.
Optional
The user agent of the browser.
Optional
The language of the browser.
Optional
The time of the event in UTC.
Optional
Information about the UTM parameters.
Optional
Information about the screen.
Optional
The timezone of the browser.
Optional
The IP address of the user.
Sends a track event to Usermaven.
Track Event is a Cloud action.
The event name
Optional
Attributes associated with the event
Optional
The user id, to uniquely identify the user
Optional
The user email address
Optional
The timestamp when the user was created
Optional
User Anonymous id
Optional
The ID of the event.
Optional
The path of the document.
Optional
The search query of the document.
Optional
The type of the event.
Optional
The title of the page where the event occurred.
Optional
The referrer of the page where the event occurred.
Optional
The URL of the page where the event occurred.
Optional
The user agent of the browser.
Optional
The language of the browser.
Optional
The time of the event in UTC.
Optional
Information about the UTM parameters.
Optional
Information about the screen.
Optional
The timezone of the browser.
Optional
The IP address of the user.
Send company attributes to Usermaven.
Group is a Cloud action.
The company id, to uniquely identify the company
The user id, to uniquely identify the user
Optional
The company name
Optional
The timestamp when the company was created
Optional
The company custom attributes
Optional
User Anonymous id
Optional
The ID of the event.
Optional
The path of the document.
Optional
The search query of the document.
Optional
The type of the event.
Optional
The title of the page where the event occurred.
Optional
The referrer of the page where the event occurred.
Optional
The URL of the page where the event occurred.
Optional
The user agent of the browser.
Optional
The language of the browser.
Optional
The time of the event in UTC.
Optional
Information about the UTM parameters.
Optional
Information about the screen.
Optional
The timezone of the browser.
Optional
The IP address of the user.
Send pageview events to Usermaven.
Page is a Cloud action.
Optional
The user id, to uniquely identify the user
Optional
The user email address
Optional
The timestamp when the user was created
Optional
The name of the page
Optional
User Anonymous id
Optional
The ID of the event.
Optional
The path of the document.
Optional
The search query of the document.
Optional
The type of the event.
Optional
The title of the page where the event occurred.
Optional
The referrer of the page where the event occurred.
Optional
The URL of the page where the event occurred.
Optional
The user agent of the browser.
Optional
The language of the browser.
Optional
The time of the event in UTC.
Optional
Information about the UTM parameters.
Optional
Information about the screen.
Optional
The timezone of the browser.
Optional
The IP address of the user.
You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule a demo.
For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property order_completed_last_30days: true. When the user no longer satisfies this condition (for example, it's been more than 30 days since their last order), Engage sets that value to false.
When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.
Real-time to batch destination sync frequency
Real-time audience syncs to Usermaven (Actions) may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected.
Segment lets you change these destination settings from the Segment app without having to touch any code.
Found on your general settings page.
Found on your general settings page.