Hi @Ankit2709, Seán here from the Intercom engineering support team 🔧
The issue happens because your Product Tour’s CSS selectors aren’t specific enough in a wizard-style workflow where the URL doesn’t change. This causes pointers to appear early, even if the target elements aren’t visible yet. Just to not here selectors like nth-child can match hidden elements and trigger on the wrong step.
To fix this, use unique data-intercom-target attributes for each step explained in more detail here. This ensures Intercom can anchor precisely to the correct element as the page updates.
If you’ve already added these attributes and still see the issue, check that:
-
Each data-intercom-target is unique and appears only on the correct step.
-
The target element is visible only when that step is active.
-
The same data-intercom-target value isn’t reused elsewhere.
For more guidance, see Intercom’s documentation on using CSS selectors for Product Tours.
Let me know if the Intercom div you mentioned was the data-intercom-target attribute or trying the above and its still performing strangely!
