Troubleshooting Funnels, Websites, and Webinars in Sparkforge

This is a working list of common issues across Sparkforge funnels, websites, and webinars, with the steps that resolve each one.

1. Head tracking code isn't inside the <head> tag

Tracking codes inject on the client side, so they won't show in the static HTML source. The page source you see is the initial render data — Sparkforge layers tracking on top in the browser. Google Tag Manager and similar tools work fine with client-side injection.

Fix: nothing to fix. Check tracking is firing using the GTM preview, browser DevTools network tab, or the analytics tool's debug view.

2. Updated custom fields don't render on the page

Custom field values render from local storage (or cookies) on the next page, not directly from the contact database. Form and survey submissions write to local storage. Backend updates (workflows, automations, score changes) don't.

Fix:

• Check whether the field is set by user input or by automation.
• If it's backend-only, add the field to the form or survey so user input writes it to local storage.
• Or push the value into local storage with a custom script before render.

Only fields populated by direct user input render on the funnel page. Workflow-set fields won't.

3. Blurry or slow-loading images

Image optimization applies a universal quality setting. Aggressive compression can soften high-detail images.

• Disable optimization on specific images in the builder.
• For background images, disable optimization in funnel settings.
• Upload higher-resolution source images so the optimized version still looks clean.

4. Custom values break or don't render in preview

Hyperlink issue: if a custom value has been wrapped in a hyperlink inside a text element, it won't render. Remove the hyperlink.

AI response formatting: AI-generated content often contains \n characters that break funnel rendering. Update the prompt to return HTML, or use a text formatter action to replace \n with <br/>.

5. Identify the funnel, page, or location of a live site

1. Open DevTools and go to the Network tab.
2. Clear the console and enable the XHR filter.
3. Reload the page.
4. Open the relevant event call and inspect the payload for funnel ID, page ID, and location ID.

6. Site renders incorrectly or refreshes in a loop

Strip custom code first.

1. Remove all custom code in code elements, head/footer tracking, and custom CSS.
2. To find code elements, open the builder, inspect the preview, and search for c-custom-code with Ctrl+F (Windows) or Cmd+F (Mac). Remove any you find and retest.
3. Disable any sticky sections, columns, or elements — sticky CSS only works in preview mode.
4. Remove expired timer elements.
5. Open the browser console. If you see a hydration error, file a support ticket.

7. Page speed score is too low

Use PageSpeed Insights or GTMetrix to find the actual bottlenecks.

• Check tracking and code elements for external scripts and CSS.
• Trim long pages and content density.
• Use Sparkforge's image optimization toggle, or compress manually. Above-the-fold images should be under 200KB for good mobile LCP.
• Enable Optimize JavaScript to delay hydration of non-essential JS and tracking. This improves Total Blocking Time.
• Move heavy elements (forms, calendars, review widgets, maps) below the fold.

Benchmark: a well-optimized Sparkforge page typically scores above 80 on mobile and above 95 on desktop, even with tracking codes and high-res images.

8. Security headers blocking site assets

If pages or steps fail to load scripts, images, or styles, restrictive Content-Security-Policy or other security headers in Sites → Settings → Security are usually the cause.

1. Go to Sites → Settings → Security.
2. Review custom headers (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options).
3. Temporarily clear all custom headers and reload. If the page works, one of the headers is the cause.
4. Make sure header values are a single continuous line — no line breaks or stray characters.
5. Avoid restrictive directives unless you understand the impact.

Example of a valid CSP value: default-src 'self'; img-src *; script-src 'self' https://example.com;

If the homepage still fails, try a different URL path temporarily. After changes, clear cache or test in Incognito to confirm.

Validation tip: use Google's CSP Evaluator to check whether your Content-Security-Policy is valid and secure. A well-configured page loads every Sparkforge asset with no Refused to load or Blocked by CSP errors in the console.