Learn what happens to tracking code when a page is copied, why page-level code is excluded, when to use page-level versus site-wide tracking, and how to safely restore and test tracking on the copied page.

Before manually adding tracking code to a copied page, check whether the same script is already configured at the funnel or website level. Adding the same tracking script at both levels can cause duplicate pageviews, events, or conversions.

When a funnel step or website page contains tracking code added directly to that page, copying the page does not copy that page-level tracking code. The page design and supported content can be duplicated, but the copied page starts without the original page's tracking script.

For example, the original page below contains a page-specific analytics script in its Tracking Code area.

After that page is copied, the duplicated page appears alongside the original.

When the copied page's Tracking Code area is opened, the original page-specific code is not carried over.

Keeping page-level tracking code out of copied pages gives you an opportunity to confirm that the new page should use the same tracking configuration before analytics or advertising events begin firing.

• Prevents Duplicate Events: Helps avoid accidentally firing the same pageview or conversion script more than once.
• Protects Page-Specific Tracking: Prevents scripts intended for one page from automatically running on another.
• Reduces Incorrect Attribution: Helps keep analytics and advertising events tied to the intended page or funnel step.
• Safer Sharing: Reduces the chance of account-specific pixels or tracking IDs being carried into another account unintentionally.
• Encourages Intentional Setup: Lets you decide whether the tracking belongs only on one page or across the entire funnel or website.

Page-level tracking scripts are often tied to a specific page, campaign, conversion event, analytics property, advertising account, or business. Automatically carrying those scripts into a copied page can cause inaccurate reporting or expose tracking configuration where it was not intended to be used.

This becomes especially important when a page is reused in another funnel, website, account, or agency. The copied page should be reviewed and assigned the correct tracking configuration for its new purpose.

Choosing the correct tracking level helps prevent unnecessary duplication. Use page-level tracking when a script should run only on one page, and site-wide tracking when the same script should run across the entire funnel or website.

Re-add tracking only after confirming what the copied page should measure. This prevents the new page from using a tracking ID, conversion event, or script that belongs to the original page.

Add Tracking to One Page

1. Go to Sites.
2. Open Funnels or Websites, depending on where the copied page is located.
3. Open the funnel or website containing the copied page.
4. Open the copied page in the builder.
5. Click the Tracking Code or code icon.
6. Paste the correct page-specific script into Header Tracking or Footer Tracking, based on the script provider's instructions.
7. Click Save.
8. Preview and test the page before sending live traffic to it.

Add Tracking Across the Entire Funnel or Website

1. Open the applicable funnel or website.
2. Open its Settings.
3. Locate Head tracking code or Body tracking code.
4. Paste the tracking script into the location required by the provider.
5. Save the changes.
6. Verify the script on the published pages that should use it.

Testing after copying a page confirms that the correct script is running on the correct destination and that events are not being recorded more than once.

1. Save and publish the copied page when it is ready for testing.
2. Open the published page in a new browser session.
3. Complete the action you expect to track, such as viewing the page, submitting a form, or reaching a confirmation page.
4. Use the analytics or advertising provider's testing tool, when available, to confirm the expected event was received.
5. Check that the event is associated with the correct page or URL.
6. Confirm the event fires only the intended number of times.
7. Use browser developer tools and network activity if additional troubleshooting is required.

Missing data and duplicate events usually come from where the script is installed, whether the copied page has been configured, or whether the same code exists at multiple tracking levels.

If tracking is still missing, duplicated, or reporting unexpected events after the page is copied, check the installation level before changing the script.

• Check both the individual page and the funnel or website settings for duplicate scripts.
• Confirm the tracking ID, analytics property, pixel, and event name belong to the copied page.
• Test the published page rather than relying only on the editor preview.
• Use the tracking provider's diagnostic or test-event tools when available.
• Temporarily remove custom scripts one at a time if the page layout or behavior changes unexpectedly.
• Record the affected page URL, script location, expected event, actual result, browser, and timestamp before contacting support.

Do not include private API keys, access tokens, passwords, or other sensitive credentials in screenshots or support requests.