Skip to main content

FAQs and Basic Troubleshooting for Funnels, Websites, and Webinars

This guide offers troubleshooting steps for common issues you might encounter while using Stack's funnels, websites, and webinars. Here, you'll find solutions for problems related to tracking codes, custom fields, images, rendering issues, and more.

Common Issues and Troubleshooting Steps​

1. Head Tracking Code Not in <head> Tag​

Issue
Tracking codes are injected on the client side (browser), so they won't appear inside the <head> tag in the static source code. This is because Stack dynamically injects these codes when the page is rendered in the browser.

Explanation
The source code you see is the initial HTML data for rendering the page, not the dynamically injected tracking codes. Even with custom tracking solutions like Google Tag Manager (GTM), scripts function as expected due to client-side injection compatibility.

2. Updated Custom Fields Not Rendering in Preview/Site​

Issue
Custom field values don't show up when updated via backend processes like automations or workflows.

Explanation
Custom fields are stored in the contact database, but the site fetches this data from local storage or cookies. If custom fields are updated on the backend without user input, they aren't saved locally and won't render on the page.

Troubleshooting Steps

  • Include relevant custom fields directly in forms or surveys. When users fill these out, the values are stored in local storage.
  • This ensures that values persist across pages and display correctly.

3. Blurry or Slow-Loading Images​

Issue
Images may appear blurry or load slowly due to image optimization settings.

Explanation
While image optimization improves page speed, it can sometimes reduce image clarity if settings are too aggressive.

Troubleshooting Steps

  • Disable image optimization for specific images in the builder.
  • For background images, adjust settings in the funnel.
  • Upload higher-resolution images to maintain clarity after optimization.

4. Custom Values Breaking or Not Rendering in Preview​

Issue
Custom values may not render properly in the funnel.

Possible Causes & Fixes

  • Hyperlink Issue: Check if a custom value in a text element is a hyperlink. Remove hyperlinks as they can break rendering.
  • Formatting Issue: ChatGPT-generated content may contain special characters like \n that disrupt the page. Update prompts to return HTML-formatted content or use a "text formatter" action to replace \n with <br/>.

5. Identifying the Funnel, Page, or Location of a Live Site​

Steps to Identify

  1. Open the Network tab in your browser.
  2. Clear the console and enable the XHR filter.
  3. Reload the page.
  4. Check the event call in the network logs.
  5. Open the payload section to find the required details.

6. Site Not Rendering Correctly (Alignment Issues, Refresh Loops, etc.)​

Issue
The site may display improperly, with elements misaligned or continuous page refreshing.

Troubleshooting Steps

  • Remove all custom code from code elements, head/footer tracking code, and custom CSS.
  • Inspect the page in the builder and search for c-custom-code to identify and remove problematic code elements.
  • Ensure no sections, columns, or elements have the sticky option enabled.
  • Remove expired timer elements.
  • Check the browser console for errors. If a hydration error appears, contact support.

7. Page Speed Score or Speed is Too Slow​

Issue
The page loads slowly, or speed analysis tools report low performance scores.

Recommended Tools

  • PageSpeed Insights
  • GTMetrix

These tools analyze page performance and suggest improvements.

Troubleshooting & Optimization Steps

  • Check for external scripts or CSS loading via tracking code or custom code elements.
  • Evaluate page length and content density.
  • Optimize images using Stack’s image optimization toggle or manually compress them.
  • Ensure images above the fold are under 200kb to improve LCP scores on mobile.
  • Enable "Optimize JavaScript" to delay non-essential JS and tracking codes, improving Total Blocking Time (TBT).
  • Move heavy elements like forms, calendars, and maps below the fold.

Benchmark
A well-optimized Stack page typically scores:

  • Above 80 on mobile
  • Above 95 on desktop

This includes scenarios with tracking codes and high-resolution images.

For further assistance, please reach out to the support team.