Troubleshoot: Interaction Not Working

This guide helps you quickly find why the interaction feature isn’t firing and how to fix it in GemPages v7.

Before you start

Confirm you’re on GemPages v7 and testing the correct page/URL.
Use Preview (or a published page) rather than the Editor canvas to test interactions.
Hard refresh (Ctrl/Cmd+Shift+R) or test in Incognito.
For mobile, use Tap/Click instead of the Hover triggers.

Common Reason Why the Interaction Feature Is Not Working

1. Navigation happens before the action completes

Reason: The trigger element is also a link (e.g., a generic button with Link = ON and After click action = Open page), so the browser navigates away before the interaction (e.g., Scroll to element: FAQs) can run.

Solution: In the element’s settings panel, toggle OFF the Link and keep the Interaction action as Scroll to element (FAQs).

Alternatively, if you prefer native scrolling without Interaction, set the button Link = #faqs and remove the Interaction.

2. Target is hidden, off-canvas, or covered

Reason: CSS (display: none, opacity: 0), off-screen position, or an overlay (modal, banner, sticky header) is covering the target.

Solution: Temporarily remove overlays, check z-index, and ensure pointer-events isn’t set to none. Make the target visible first, then retest.

3. Hover trigger used on mobile

Reason: Hover doesn’t fire on touch devices.

Solution: Create a mobile-specific Interaction using Tap/Click as the trigger. Keep Hover for desktop only.

4. Conflicts with third-party apps or custom code

Reason: Other scripts intercept clicks, stop event propagation, or throw JS errors.

Solution:

Temporarily disable cart drawers, popups, or custom JS and retest.
Open DevTools > Console and fix any errors.
Re-add scripts one by one to find the conflict.

GemPages’ Interaction Use Cases & Tips

Use the quick checks below to verify your setup when your interaction isn’t firing.

1. Show a message after the quantity change	Ensure the quantity selector and the message block are both present when testing Use a Click/Change trigger on the selector and target the message container.
2. Variant-based content	Place the variant picker and the target content inside the same Product module. Avoid targeting elements that reload completely when a variant changes.
3. Upsell pop-up after Add to Cart	Use the Product Cart Button as the trigger. If a cart drawer opens, set the pop-up target to a high z-index and test with the drawer disabled to rule out any conflicts.

For further use cases and best practices for using Interaction in GemPages, refer to this article.

What did you think about this content?

Your comments

Irrelevant: Unexpected or off-topic information.

Inaccurate: The information doesn’t match the product.

Needs small fixes: There are typos or broken links.

I have suggestions: I’d like to suggest improvements for this page.

Email*

Invalid email address.

Something went wrong. Please try again later.

By submitting your email address and comments, you consent to the collection and use of your information as outlined in our Privacy Policy and agree to our Terms of Service.