Choose your integration
TapResearch offers four integration paths. They share the same survey supply and reward postbacks, but differ in how much you build versus how much TapResearch handles for you — and in how you check whether a user is eligible before you send them. Use the cards below to jump straight to a path, or compare them feature-by-feature in the At a Glance matrix.
The SDK is for native mobile apps (iOS / Android). On web or desktop, use the Hosted Link, Eligibility API, or Survey Feed API — they're a URL or a server-side call, so they work anywhere.
Our full-featured native integration. The SDK renders survey placements in your app and handles eligibility, ranking, profiling, and reward callbacks for you. Its hidden-webview logic updates on TapResearch's side, so behavior improves without you shipping a new SDK release.
View Documentation →The fastest, low-code path. Integrate a single URL — the same link for every user — and TapResearch handles eligibility and survey selection. There is no SDK to install and no API to call; you only template the link per user.
View Documentation →A lightweight server-side API that tells you whether a user has an eligible survey before you show a call-to-action — a simple yes/no plus a hand-off link, not the survey list.
View Documentation →Full control over the experience. Fetch the surveys themselves and render them in your own UI, with profile / impanel support for a profile-first flow. This is the only path that impanels participants.
View Documentation →At a glance
| Comparison | SDK | Hosted Link | Eligibility API | Survey Feed API |
|---|---|---|---|---|
| What you build | An entry point and reward handling | A button and the link | A server-side check + hand-off link | Survey list UI, webview, reward handling |
| Survey runs in | In-app, we render | Mobile browser | Mobile browser | Your in-app webview |
| User stays in your app | ✓ | ✕ | ✕ | ✓ |
| Control over presentation | Low | Low | Low | Full |
| Effort and time to launch | Low | Lowest | Low | Highest |
| Reward notifications | In-app callback or server-to-server | Server-to-server | Server-to-server | Server-to-server |
| Native Survey Tiles | ✓ | ✕ | ✕ | ✓ |
| Quick Questions | ✓ | ✕ | ✕ | ✕ |
| In-app promotions | ✓ | ✕ | ✕ | ✕ |
| Who handles survey abandons | We do | We do | We do | You do |
| Eligibility check | ✓ | ✕ | ✓ | ✓ |
If you're integrating a mobile app (iOS or Android), start with the SDK path. It delivers the richest, most native experience — in-app survey tiles, Quick Questions, and automatic profiling — and its hidden-webview logic keeps improving without you shipping a new SDK release.