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
Feature | Web SDK | iOS SDK | Android SDK | React Native SDK |
---|---|---|---|---|
Mobile Trigger Delay | N/A | v4.11.0 (2022-10-31) | v2.9.0 (2022-11-02) | v2.12.0 (2022-11-03) |
Required Questions | v2.19.1 (2022-10-14) | v4.10.0 (2022-10-21) | v2.8.0 (2022-10-17) | v2.10.0 (2022-10-18) |
Event Properties | v2.18.2 (2022-10-11) | v4.9.0 (2022-10-13) | v2.7.0 (2022-10-10) | v2.10.0 (2022-10-28) |
Rating Scale | v2.17.3 (2022-08-24) | v4.8.5 (2022-08-31) | v2.6.4 (2022-09-02) | v2.8.0 (2022-08-31) |
Other (Specify) Option | v2.17.0 (2022-08-09) | v4.8.5 (2022-08-31) | v2.6.4 (2022-09-02) | v2.8.0 (2022-08-31) |
Recorded Task Question Type | v2.16.0 (2022-05-02) | Not supported | Not supported | Not supported |
"Skipped" Skip Logic | v2.15.14 (2022-04-06) | v4.8.5 (2022-08-31) | v2.6.1 (2022-07-25) | v2.8.0 (2022-08-31) |
Consent/Legal Question Type | v2.15.10 (2022-03-30) | v4.8.5 (2022-08-31) | v2.6.1 (2022-07-25) | v2.8.0 (2022-08-31) |
Enrich URL in Text/URL Prompts Question Type | v2.15.2 (2022-03-14) | v4.8.5 (2022-08-31) | v2.6.3 (2022-08-01) | v2.8.0 (2022-08-31) |
Video & Voice Question Type | v2.2.4 (2021-08-23) | Not supported | Not supported | Not supported |
Text/URL Prompt Question Type | v1.13.1 (2021-06-15) | v4.3.0 (2021-06-02) | v2.3.0 (2021-06-02) | v2.4.0 (2021-06-03) |
Multi-select Skip Logic | v1.11.0 (2021-03-02) | v4.2.0 (2021-03-22) | v2.2.0 (2021-03-22) | v2.2.0 (2021-03-23) |
Customized Question Subheader | v1.8.0 (2021-02-13) | v4.1.0 (2021-02-09) | v2.1.2 (2021-02-11) | v2.1.3 (2021-03-08) |
Customized Continue Button | v1.8.0 (2021-02-13) | v4.1.0 (2021-02-09) | v2.1.2 (2021-02-11) | v2.1.3 (2021-03-08) |
Customized Open Text Placeholder | v1.8.0 (2021-02-13) | v4.1.0 (2021-02-09) | v2.1.2 (2021-02-11) | v2.1.3 (2021-03-08) |
Customized "Thank You" Card | v1.8.0 (2021-02-13) | v4.1.0 (2021-02-09) | v2.1.2 (2021-02-11) | v2.1.3 (2021-03-08) |
NPS Question Type | v1.3.0 (2020-07-01) | v2.1.0 (2020-07-15) | v1.1.0 (2020-07-16) | v1.1.0 (2020-07-16) |
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 returnsNSNumber?
will always returnnil
for new visitors. Use theSprig.shared.visitorIdentifierString
which returnsString?
Upgrading from 2.x.x to 3.1.1
There are 2 breaking changes in this upgrade:
-
Visitor Identifier Getter
- To better support the Objective-C runtime, we have changed the return type of
Sprig.shared.visitorIdentifier
fromInt?
toNSNumber?
. If you are usingvisitorIdentifier
in your codebase and expect it to be anInt
, callintValue
on that value if it is non-nil.
- To better support the Objective-C runtime, we have changed the return type of
-
UserLeap init() calls are officially deprecated
- As with all versions of this SDK, use the provided single
Sprig.shared
instead.
- As with all versions of this SDK, use the provided single
Android SDK
Upgrading from 1.x.x to 2.x.x
Sprig.visitorIdentifier
which returnsInt?
will always return null for new visitors. Use the newSprig.visitorIdentifierString
which returnsString?
The latest Sprig SDK release is shown here.
Updated 17 days ago