UserIQ Destination
UserIQ empowers companies to deliver what each user needs to be successful in every moment, starting with adoption. Our platform collects user engagement data from your product and allows you to communicate to your users when they are most engaged: within the product itself.
This destination is maintained by UserIQ. For any issues with the destination, contact the UserIQ Support team.
- From the Segment web app, click Catalog.
- Search for "UserIQ" in the Catalog, select it, and choose which of your sources to connect the destination to.
- Enter the "API Key" into your Segment Settings UI which you can find from your UserIQ dashboard [Site Settings -> API Key].
Segment sends Page calls to UserIQ as a pageview. See the Page method in the Segment Spec for details. An example call looks like:
analytics.page("pageName")
Segment sends Screen calls to UserIQ as a screenview. See the Screen method in the Segment Spec for details. An example call looks like:
[[SEGAnalytics sharedAnalytics] screen:@"Home"];
Segment sends Identify calls to UserIQ as an identify event. See the Identify method in the Segment Spec for details. An example call looks like:
1analytics.identify('userId123', {2email: 'john.doe@example.com'3});
Segment sends Track calls to UserIQ as a track event. See the Track method in the Segment Spec for details. An example call looks like:
analytics.track('Clicked Login Button')
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 UserIQ 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.
You can find your API key in the accounts page