Skip to main content
Version: 3.x

Hosted Link

The Hosted Link is the fastest, no-code way to connect your users to TapResearch surveys. You integrate a single URL — TapResearch handles eligibility, survey selection, presentation, and reward callbacks on our side. There is no SDK to install and no API to call.

Creating your app

In the Supplier Dashboard, create a new app and select Hosted Link. See the Setup checklist for the full flow.

How it works​

You embed one hosted link in your app or web experience. The link contains a few placeholder tokens that you swap out per user before sending the user to it — most importantly, a unique identifier for the user.

  1. Build the link per user. Take the hosted link from your dashboard and substitute the placeholder tokens (such as the user identifier) with that user's real values.
  2. Send the user to the link. When they tap your call-to-action, open the built link.
  3. TapResearch handles the rest. Eligibility, targeting, and survey matching all happen on TapResearch's side — there is no eligibility call for you to make.
  4. Rewards arrive via callback. When a user earns a reward, TapResearch notifies your backend with a server-to-server postback.

When to use it​

The Hosted Link trades control for speed — it's the fastest launch, with eligibility and presentation handled for you. Reach for a different path if you need:

  • Native survey tiles or in-app placements — use the SDK path.
  • An eligibility check before you send a user — use the Eligibility API path.
  • A survey feed you render yourself, or profile / impanel support — use the Survey Feed API path.
Integrating a mobile app?

If you want native placements inside a mobile app, the SDK path is recommended over the Hosted Link.

What you need​

  • The hosted link for your placement, from the Publisher Dashboard.
  • A unique user identifier to substitute into the link for each user.

No API token or server-side request is required — the Hosted Link is no-code.

Next steps​

  • Implementation — the URL format, the placeholder tokens to substitute per user, and the redirect behavior.
  • Callbacks — receive reward notifications on your backend with the server-to-server postback.