In-app product tours: from first login to mapped fields

Why we added in-app tours

Setting up scraping means several steps: register a URL, choose schedule and options, then map HTML fields in the visual mapper. Docs help, but the fastest path is contextual guidance on the screen you’re already on.

We shipped product tours short, skippable walkthroughs that highlight the controls that matter and let you interact with the form while the tour is open.

What’s included

Dashboard tour

On your first visit to the dashboard, a tour introduces:

• Primary navigation (Pages, API, billing)
• Credits and plan usage
• Recent pages or the empty-state prompt to create your first page

You can replay it anytime from Take a tour in the header.

Pages tour — create your first scrape target

The Pages tour walks through the create form:

1. Title — a name you’ll recognize in lists
2. URL — the address Gluedly scrapes
3. Schedule — how often we revisit the page
4. Multi-page scrape — optional pagination when the site has a real “Next” link
5. JS rendering — for SPAs and JavaScript-heavy pages (higher credit cost)
6. Save — register the page

After you save a new page, a short post-create tour points you to Mappings so you can open the element mapper immediately.

Tours remember completion in your browser (localStorage), so they autostart once per tour—not on every visit.

Elements mapper tour — map fields in the preview

The Mapping tour covers the mapper workflow:

• Live preview — click elements in the iframe to capture XPaths
• Mapped fields — rename fields and group layout variants
• Save mappings — persist to the server for scheduled scrapes

New default behavior: each preview click creates a new field with that XPath. You no longer need to click Add field before every selection—ideal during the tour and for fast first-time setup.

Use Add layout on a field when the same data appears in different HTML structures (e.g. list tile vs carousel). The next preview click goes into that field as an extra layout variant.

Click a highlight again to remove a mapping, or use Remove on the right.

Embed preview improvements

The mapper preview loads a sanitized snapshot of the target page in an iframe. Two fixes shipped with this release:

Styled previews for more sites

Some sites serve CSS from paths like /dist/css/style.css. Our stylesheet inliner was rewriting those URLs incorrectly, so previews looked unstyled (fonts only, no layout). We fixed asset-path detection so main stylesheets inline correctly on embed load.

If a stored preview was saved before the fix, open the mapper or use Refetch preview to refresh.

Clear warnings for unmappable targets

When the scraper receives an error page instead of real content—common for Facebook groups/pages or blocked targets—the mapper now shows an amber warning above the preview explaining that mapping may not reflect the live site.

Replay and skip

• Header buttons: Take a tour (dashboard), Pages tour, Mapping tour
• Skip and Next on every step; progress is saved when you finish or skip
• To see autostart again locally, clear product-tour-completed:* keys in browser storage and reload

Who this is for

• New accounts — less guesswork on first page and first mappings
• Teams onboarding colleagues — replay tours instead of writing internal docs
• Power users — optional; nothing blocks manual workflow if you dismiss the tour

Try it

1. Log in and open the Dashboard — the workspace tour autostarts on first visit (or click Take a tour).
2. Go to Pages — follow the create-form tour; add title, URL, schedule, and optional multi-page / JS settings, then Save.
3. Click Continue setup — open element mapper (or Mappings on the page row).
4. Click headings, prices, or links in the preview — each click adds a field on the right.
5. Use Add layout only when you need a second XPath variant under the same field name.
6. Submit to save mappings; scheduled scrapes use those paths on the next run.

FAQ

Do I have to complete the tour? No. Skip anytime; all features remain available without the walkthrough.

Will preview clicks always create new fields? Yes, by default. Use Add layout when you want another XPath under an existing field name.

Why does my preview look unstyled? Try Refetch preview. If the target blocks scrapers or returns an error page, check the warning banner above the iframe.