Diagnostics

Sprig Survey Engagement Diagnostics

To ensure your Sprig Surveys are being delivered to users as expected, you can review its Engagement Report, which can be found within each survey’s Summary page.

Within the Engagement Report, you’ll see all users who have engaged with this study, along with how deeply they engaged (study has been sent/delivered, seen, started, or completed). You can also review how your aggregate engagement with the study has changed over time, which can be especially helpful for continuous in-product Surveys.

If the study’s Engagement Report data doesn’t match up with your expectations, we recommend reviewing the study’s Audience settings to ensure that your targeting is accurate and that any Events and/or Attributes that are included have the expected usage in the last hour, day, or week.

Note that the response rate graph is calculated by dividing the number of responded surveys by the number of seen surveys within a day based in Universal Time Coordinated (UTC).

SDK Diagnostics

SDKs, or Software Development Kits, are toolkits for software developers. When you think of a toolkit from your garage or a contractor’s perspective, you might find important tools like a hammer, screwdriver, nails, etc. These tools are essential for making it easier for you to build a structure, make additions, and make repairs when something goes awry. However, instead of hammers and nails, you'll often find libraries and code samples inside of an SDK. In fact, SDKs often contain a wide variety of resources, including:

• Libraries
• Documentation
• Tutorials
• Code samples
• Debugging tools

Developers use all these tools to create applications for specific platforms. In the case of the Sprig SDKs, our toolkits are primarily designed to give your developers the resources they need to layer in studies directly within your iOS, Android, React or Browser-based application.

Warning Messages

Depending on the SDK your company chooses and how a developer integrates it with your codebase, it may be necessary to download the latest Sprig SDK versions. Sprig makes that easy for those teams that have specific package management needs. Listed below is an outline of decisions you may take:

Learn

Locate the recommended version from the error code that you experienced on the matrix below to learn more about the change impact for that Question Type or Sprig Feature you selected in your Study Design.

Upgrade to Latest

Decide to launch the study as is and know that you may have a slower than desirable study fill rate or
encourage your development team to refresh your application’s use of the Sprig SDK, e.g. upgrade to the latest Sprig SDK and push out as part of your product release schedule to the app stores or your browser-based experiences.

Release

Ensure that your users uptake the latest version of your product’s application to be eligible for your study in the way it was designed.

Features and SDK Versions

Sprig provides a variety of ways to install SDKs. If you’re seeing that some percentage of your users cannot see the study, be sure to connect with your Web or Mobile App Engineer to pick up the latest version.

The following table shows when a Feature was supported by a corresponding SDK version for each platform.

SDK Versions by Feature

Upgrading SDKs

We adhere to Semver for versioning our SDKs so upgrading between minor versions or patches (e.g. 2.0.0 -> 2.1.0 or 3.1.0 > 3.2.1) should not present any breaking changes. You can view the release logs for iOS and Android.

iOS SDK

Upgrading from 3.1.1 to 3.2.0/4.x.x

Note: 3.2.0 is the same as 4.0.0, we've bumped the major version to signify that versions below 3.2.0 will be disabled/deprecated by Feb 12, 2021

Changes:

• Sprig.shared.visitorIdentifier which returns NSNumber? will always return nil for new visitors. Use the Sprig.shared.visitorIdentifierString which returns String?

Upgrading from 2.x.x to 3.1.1

There are 2 breaking changes in this upgrade:

1. Visitor Identifier Getter

   • To better support the Objective-C runtime, we have changed the return type of Sprig.shared.visitorIdentifier from Int? to NSNumber?. If you are using visitorIdentifier in your codebase and expect it to be an Int, call intValue on that value if it is non-nil.

2. UserLeap init() calls are officially deprecated

   • As with all versions of this SDK, use the provided single Sprig.shared instead.

Android SDK

Upgrading from 1.x.x to 2.x.x

• Sprig.visitorIdentifier which returns Int? will always return null for new visitors. Use the new Sprig.visitorIdentifierString which returns String?

The latest Sprig SDK release is shown here.