Sprig Device Mode

Send events to Sprig using RudderStack web device mode.

RudderStack lets you send your event data to Sprig via web device mode, that is, using the native Sprig web SDK.

Find the open source code for this destination in the GitHub repository.

Identify

You can use the identify call to identify a user in Sprig.

A sample identify call is shown:

rudderanalytics.identify('1hKOmRA4GRlm', {
  firstName: 'Alex',
  lastName: 'Keener',
  email: "alex@example.com"
});

Supported mappings

RudderStack maps the following optional user attributes in the identify events to the corresponding Sprig fields:

RudderStack propertySprig property
userIduserId
context.traitsattributes
context.traits.emailemail

Track

The track call lets you record any user actions along with the associated properties.

A sample track call is shown:

rudderanalytics.track('Sample Survey', {
  plan: "Annual",
  accountType: "Pro"
});

If you send a track event called Signed Out, then RudderStack automatically maps it to the logoutUser event before sending it to Sprig. Otherwise, it maps the following event/properties to the corresponding Sprig fields:

RudderStack propertySprig property
event
Required
eventName
userIduserId
propertiesproperties

Sprig expects the event name to be present in the eventName key. Hence, if you send a track event named Product Added, RudderStack maps it to Sprig’s eventName key before sending it across to Sprig.



Questions? Contact us by email or on Slack