Skip to main content
Version: 3.x

Choose your integration

TapResearch offers four integration paths. They share the same survey supply and reward callbacks, 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.

Mobile vs. web

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.

At a Glance

ComparisonHosted LinkSDKEligibility APISurvey Feed API
What you buildA button and the linkAn entry point and reward handlingA server-side check + hand-off linkSurvey list UI, webview, reward handling
Survey runs inMobile browserIn-app, we renderMobile browserYour in-app webview
User stays in your app
Control over presentationLowLowLowFull
Effort and time to launchLowestLowLowHighest
Reward notificationsServer-to-serverIn-app callback or server-to-serverServer-to-serverServer-to-server
Native Survey Tiles
Quick Questions
In-app promotions
Who handles survey abandonsWe doWe doWe doYou do
Eligibility check
Choosing for mobile?

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.