Not to anchor in a product tour

Matej's answer is spot on technically — Pointers require an anchor, and Posts are your unanchored option.

But I'm curious about the use case here. What experience are you trying to create?

A few questions that might help surface the right solution:

• Why tooltip over Post? Is it the visual style (smaller, less intrusive than a centered modal)? Or something about the interaction pattern?
• What's the context? Is this onboarding, feature announcement, or something else? For announcements, a Banner might actually work better than a Tour.
• Why "click anywhere"? Are you trying to let users explore freely while seeing hints, rather than a step-by-step guided flow?

Depending on your answers, you might be better served by:

• A single-step Post with auto-dismiss after a few seconds
• A Banner (non-blocking, stays visible while users interact)
• A Checklist approach where users self-direct rather than a linear tour

Happy to suggest a specific setup once I understand what you're optimizing for.

Hi Matej and Christopher,

Thank you both for your replies!

To give you a bit more context: 

My company provides data processing services for solar farms, whether they are in the construction or operational phase. We offer different data products, and I want to create separate product tours for each one. Customers have several sites with different data product. To trigger the correct tour at the right site, customers need to select the appropriate site. I cannot link directly to the site’s URL since each site has a unique code. Therefore, using a post that doesn’t direct the customer to the intended site is not feasible. The context for the tour is onboarding users after the first operational data has been uploaded to the platform.

Could you elaborate on single-step post with auto dismiss a bit more?

I will see how i can make use of checklist and banner.

Thanks for your assistance again!

Hi ​@Sitemark Support my pleasure, 

Thanks for the context — this makes much more sense now.

The core challenge is that URL-based targeting won't work because of the dynamic site codes. But before jumping to more technical solutions, let me ask one clarifying question:

What do your site URLs actually look like?

If the URL structure includes the product type (not just the unique site code), you might be able to use native URL matching with "contains." For example, if your URLs look like:

• app.sitemark.com/sites/ABC123/operational
• app.sitemark.com/sites/XYZ789/construction

You could target tours where URL contains /operational or contains /construction — and it wouldn't matter that the site codes are unique. This would be the simplest approach if your URL structure supports it.

If that won't work for your setup, here are the other options:

Option 1: JavaScript API (most flexible)

You can programmatically launch a specific tour when a user selects a site:

Intercom('startTour', tourId);

This gives your app full control — when a user clicks into a site, your code determines which product they're viewing and fires the corresponding tour. No URL matching needed.

Docs: Intercom JavaScript API Methods

Option 2: Event-based triggering

If your platform sends Intercom events (or could), you can trigger tours based on events rather than URLs. Fire an event like operational_data_ready with metadata about the product type, then target different tours to users who triggered that event.

See: Automatically show your Product Tour to the right customers

Option 3: Checklist for self-directed onboarding

Instead of auto-triggering tours, present users with a Checklist after their first data upload. Each item links to the relevant product tour. Users self-select based on what they need. There's also Intercom('startChecklist', checklistId) if you want to trigger it programmatically.

This works well when users have multiple products/sites and might want to revisit tours later.

Apologies on the auto-dismiss question — my bad, I confused it with another tool.

Happy to help sketch out whichever approach fits your setup best.

Hi Christopher,

Thanks again for your assistance, much appreciated!

I’ll review these options with my team and reach out if we have any further questions.

All the best,
Bengisu