Home/HighLevel/Features/Sites/Understanding tracking code omission when cloning pages in HighLevel

Funnels, Websites and Forms

Understanding tracking code omission when cloning pages in HighLevel

In short

When a funnel step or website page is duplicated in HighLevel, any page level tracking scripts are not copied to the new page. This prevents old pixels or analytics from running on the wrong page. You can add the needed script again either on the single page or across the whole funnel or website.

AreaSites · Funnels and Websites
Used forEcommerce store, SaaS company, Local service agency
Setup steps15 steps in 2 tasks
Last updatedNovember 17, 2026

01Who this is for

  • Agencies that clone funnel steps for multiple clients, because they need to avoid carrying over client specific pixels.
  • Ecommerce owners who use thank you pages for purchase confirmations, to ensure conversion scripts run only on the appropriate page.
  • Local service businesses that embed contact form tracking, to keep each location’s analytics separate when pages are duplicated.

02Tracking code, explained

Cloning a page in HighLevel copies the design and content but deliberately excludes any tracking code that was entered directly on that page. This design choice stops scripts that belong to one page from automatically firing on another.

Page level tracking is added inside the page builder using the Tracking Code icon, where you can place scripts in Header Tracking or Footer Tracking. Site wide tracking is set in the funnel or website Settings, using the Head tracking code or Body tracking code fields, so the same script runs on every step.

To manage tracking, open the page in the builder for page specific scripts, or open the funnel/website Settings for scripts that should apply to all pages. Save and test after adding code to confirm proper operation.

03How businesses use tracking code

  • Ecommerce store. After cloning a checkout page, the owner opens the page in the builder, clicks the Tracking Code icon, and pastes the order confirmation pixel into Footer Tracking. This ensures the pixel fires only on the new thank you page.
  • SaaS company. The team adds a general Google Analytics base script in the funnel Settings’ Head tracking code field, so every page in the sales funnel reports to the same analytics property without needing page level inserts.
  • Local service agency. When duplicating a location specific landing page, the agency opens the copied page, adds a custom event script to Header Tracking, and saves, guaranteeing the event tracks only for that location’s page.

04Before you start

  • Check whether the same script is already configured at the funnel or website level before adding page level code.

05How to set up and use tracking code in HighLevel

Add tracking to one page

  1. Go to Sites.
  2. Select Funnels or Websites where the cloned page resides.
  3. Open the chosen funnel or website.
  4. Open the copied page in the builder.
  5. Click the Tracking Code or code icon.
  6. Paste the script into Header Tracking or Footer Tracking as the provider directs.
  7. Click Save.
  8. Preview the page and test the script before sending live traffic.

Add tracking across the entire funnel or website

  1. Open the relevant funnel or website.
  2. Open its Settings.
  3. Locate the Head tracking code or Body tracking code field.
  4. Paste the required script into the appropriate field.
  5. Save the changes.
  6. Verify the script appears on the published pages that should use it.
  7. Do not add the same base script at the page level if it already exists in the funnel or website settings.

06What it looks like in HighLevel

07Settings that matter

  • Header Tracking. Controls scripts that are injected into the head section of a specific page.
  • Footer Tracking. Controls scripts that are injected into the footer section of a specific page.
  • Head tracking code. Controls site wide scripts placed in the head of every page in the selected funnel or website.
  • Body tracking code. Controls site wide scripts placed in the body of every page in the selected funnel or website.

08Things to know before you rely on it

  • Page level tracking code is intentionally excluded when a page is cloned.
  • Adding the same script at both page and site levels can cause duplicate events.
  • Tracking code may be injected dynamically and not appear in the static page source.

09If something goes wrong

  • Tracking disappeared after copying a page. Open the copied page and add the correct page specific script if it is still required.
  • The copied page records no analytics events. Check both the copied page's Tracking Code area and the funnel or website Settings to confirm where the script is installed.
  • Events fire twice. Check whether the same script is installed at both the page level and the funnel or website level.
  • The wrong conversion fires on the cloned page. Confirm that the copied page uses the correct event code, tracking ID, analytics property, pixel, and destination URL.
  • Code does not appear in View Page Source. Tracking code can be injected dynamically. Test with browser network tools or the tracking provider's diagnostic tools instead.
  • Custom code affects page rendering. Temporarily remove custom code, page level tracking code, and custom CSS to isolate the script causing the issue.

10How it connects to the rest of HighLevel

  • Learn how to add tracking scripts to funnels and websites. Add tracking code
  • Overview of creating and publishing sites in HighLevel. Website setup
  • View HighLevel pricing and plan options. Pricing

Michael's take

Michael Reimer
Michael ReimerFounder of CRM Pros, HighLevel Commander and Certified Admin

Tracking code is deliberately left out of cloned pages to keep old pixels and analytics from leaking into the wrong place.

If you rely on page specific events, you’ll need to paste the script back in after cloning; skip this if you only use site wide tracking.

Get More InformationOpens on HighLevelPublished November 3, 2026 · Updated November 17, 2026

Common questions

Common questions about tracking code.

Does page level tracking code copy when I duplicate a funnel step or website page?

No. Page level tracking code is intentionally excluded from the copied page.

Do I always need to add the tracking script again?

No. First check whether the script is already configured at the funnel or website level. If it is site wide, the copied page may already receive the required base tracking without another page level copy.

Can I use page level tracking for a conversion or thank you page?

Yes. Page level tracking is useful when an event or script should run only on a specific page rather than across the entire funnel or website.

Why am I seeing duplicate events after adding the code back?

Check whether the same tracking script is installed both site wide and on the individual page. Duplicate installations can cause the same event to fire more than once.

Why can’t I find my tracking script in the page source?

Tracking code can be injected dynamically by the browser. Use your analytics provider’s testing tools or browser developer tools to confirm whether the script and events are running.

Next step

Pick the features that matter. Then get the plan that unlocks them.

Explore the features you want, start with the five at the top, and upgrade through my link when you are ready. The bonuses and the team come with it.

The features directory explains every HighLevel feature in plain English. Browse it to see what the platform can do.

Back to the FeaturesSee the full details
⌃

Site preview

Explore the next page

This destination is reserved in the page inventory and is not built yet.