Why Tracking Code Is Missing After You Copy a Page

When you duplicate a funnel step or website page, the layout and content come along but the page-level tracking code does not. This is deliberate. It stops pixels, analytics events and conversion scripts meant for one page from firing on another.

Page-Level Versus Site-Wide

• Page-level: scripts for one page only, such as a purchase event on a thank-you page. Add them from the editor using the Tracking Code (code) icon, in Header Tracking or Footer Tracking.
• Site-wide: scripts for every page, such as a base analytics tag or ad pixel. Add them in the funnel or website Settings, in the Head tracking code or Body tracking code fields.

Restore Tracking on the Copy

1. Decide what the copy should measure.
2. Check whether the script already exists site-wide. If it does, do not add it again.
3. Open the copied page in the editor and click the Tracking Code icon.
4. Paste the page-specific script into the header or footer box, following the tool provider's instructions.
5. Click Save, then publish.

Test It

Open the published page in a fresh browser session, perform the action you track, and use your analytics provider's testing tool to confirm the event arrives once and is tied to the correct URL. Injected code often will not show in View Page Source, so rely on the provider's debugger or your browser's network tab.

Common Problems

• Events fire twice: the same script exists on both the page and site-wide.
• Wrong conversion on the clone: update the event code, ID, pixel and destination.
• Page renders oddly: temporarily remove custom code and CSS to find the culprit.

A copied page also starts with fresh statistics, since history does not transfer.

Good to know: Put base scripts site-wide and keep page-level code for events unique to a single step.