See how it works: Test websites with a tag or extension

The tag on your website

Alternative to the extension, works on mobile.

2 minutes read

On this page

Instrument a real website task using a compatible method.

Purpose

Observe how a participant carries out an assigned website task.

When to use it

When the interface is already on an accessible website.

Before you start

  • An HTTPS URL and defined task
  • Permission to install the tag or a compatible extension

Example

Find the returns policy and confirm when reaching its page.

Step by step

  1. Define the task. Add Website test. Write an instruction, enter the HTTPS start URL and define success by URL or manual confirmation. Returns policy · Start URL.
  1. Choose instrumentation. Use Website tag if your team can install code, including for mobile. Use Extension when participants can install it in a compatible browser. Website tag · Extension.
  1. Install and verify. For the tag, copy the shown snippet and install it on tested pages; use the provided verification. For the extension, follow the installation instructions shown in the test. Correct domain · Code loaded.
  1. Rehearse the round trip. Test opening the website, the success criterion and returning to the study. Set timeout and give-up behavior so nobody gets stuck. Goal reached · Return to study.
  1. Read available data. After collection, open the block in Results and review pages and paths. Interpret its map according to the method and available screenshots. Tag without a background image · Extension according to available screenshots.

Validate before collecting responses

The side preview lets you inspect a block; for Figma it is static. To validate draft rules and order, use Test full flow, without creating sessions or taking quota slots. Figma, recording, voice and AI follow-up require the published link. Test published opens the real /r/[token] link: it can create responses and consume quota. Separate these tests when analyzing your collection.

How to read the result

  • Pages, clicks and task route
  • Screenshots only when the method produces them

Cautions and limitations

  • The test tag does not provide a page background image.
  • The extension may capture visible content in screenshots even without recording keystrokes.
  • Available installation does not replace testing in your audience’s browser.

Continue with the interactive guide

Test websites with a tag or extension

Was this helpful?

Is something missing? Write to contato@uxtap.app.