Saved Pages Management

Overview

This article introduces the Historical Heatmap Save feature in Ptengine.

The feature lets you capture a complete snapshot of a page at any given moment and store it long-term. Even after the page is redesigned or taken down, you can still load that snapshot as the background image to view heatmaps from the corresponding period. This update introduces the new Scheduled Save mode, which automatically creates snapshots on your chosen frequency (weekly, biweekly, or monthly), so you no longer need to remember to save manually after each redesign.

Best suited for pages with a steady revision cadence — for product pages that update on a regular cycle, enable weekly scheduled save and let the system archive automatically; for campaigns or events, manually save a version before launch and another after the close, then compare to see the impact.

Why You Need to Save Pages

Ptengine heatmaps rely on the page itself for visualization. When a page is redesigned (the same URL now shows a completely different design), deleted, or taken offline, the original page becomes inaccessible, and you can no longer view heatmaps for that period. The Page Save feature stores the page's structural files on the server so you can recall them anytime. With a saved version available, you can use it as the background image and overlay visitor data from any past period, restoring the heatmap exactly as it was.

How to Save a Page

After opening the Historical Heatmap panel, choose one of the two save modes based on your needs:

• Manual Save — Runs immediately when you submit. Best for clear milestones such as campaign launches or ends.

• Scheduled Save (new) — Set a frequency once, and the system runs on schedule. Best for pages with ongoing maintenance and a steady update cadence.

You can use both modes together. All saved versions appear in the same version list for unified management.

How to Use Manual Save

1. Open the Historical Heatmap panel and switch to the Manual Save tab

2. Enter the following and click Save to submit

   • Version name (use a name that's easy to recognize)

   • Note (optional)

   • Apply to combined pages and their original pages (optional): when enabled, this saved version will apply to both pages with and without URL parameters. For example, both example.com and example.com?param=test can use this version

   

   Manual Save panel
3. Wait 1–10 minutes for the snapshot to complete

   You don't need to stay on the page during capture, and the process won't interrupt your other work.

How to Set Up Scheduled Save

1. Open the Save Historical Heatmap panel from the heatmap report

   Click + Save current page in the page-switcher dropdown at the top, or click the Save current page icon on the right-side toolbar — either entry opens the panel.

   

   Two entry points for opening the Save Historical Heatmap panel from the heatmap report
2. Complete the settings in the Scheduled Save tab, then click Save to submit

   • Choose a save frequency

     • Weekly — for pages with a fast update cycle; specify the day of the week

     • Biweekly — for pages that update roughly every two weeks; specify the day of the week

     • Monthly — for relatively stable pages; specify a date (1–28)

   • Add a note (recommended): briefly describe the purpose of this scheduled task to make later maintenance easier

   • Apply to combined pages and their original pages (optional): when enabled, the historical heatmap saved by this task will apply to both pages with and without URL parameters. For example, both example.com and example.com?param=test can use the saved version

   

   Scheduled Save panel

   Tip: Days 29 through 31 are not selectable because some months don't have those dates. The 1–28 range guarantees the task runs reliably every month.

3. The setting takes effect immediately after saving

   The system runs on schedule starting from the next matching day at 00:00 (JST).

How to Modify or Disable Scheduled Save

You can adjust or disable a scheduled task at any time, from either of two locations.

Option 1: From the heatmap report

1. Reopen the Save Historical Heatmap panel. The Scheduled Save tab shows the current frequency and next scheduled date.

   

   Scheduled save in active state
2. Click Edit Schedule to enter edit mode. Adjust the frequency and note as needed. To disable the task, turn off the Enable scheduled save switch.

   

   Edit mode — turn off the Enable scheduled save switch to disable
3. Click Save to apply the changes

Option 2: From the management page

Go to Ptengine Settings → Heatmap Settings → Version Management and use the controls at the top right of each page entry to adjust or cancel.

Note: Disabling a task does not delete saved versions. Existing versions are preserved; only future automatic runs stop.

How to View Saved Pages

You can view and manage saved snapshots in two places.

Viewing from the Heatmap Report

In the heatmap report, click the page switcher dropdown at the top and choose Change historical page version to see all historical versions of the current page.

Opening the full list of historical versions from the heatmap report

Version name prefixes indicate the source:

• [Scheduled] Historical Heatmap (yyyy/mm/dd) — created automatically by scheduled save

• [Manual] Historical Heatmap (yyyy/mm/dd) — created via manual save

• No prefix — versions saved before this feature update

Selecting a version switches the background image to that snapshot, overlaid with the actual visitor data from the selected period.

Viewing and Managing on the Management Page

Open it via Settings menu (top right) → Heatmap Settings, or Sidebar → Version Management.

Historical Heatmap Management page

On this page, you can:

Page expanded view showing header and version list

1. Usage: check your current quota at the top, shown as Historical Heatmap Usage: 1/1 URLs

2. In Use / Archived: switch between the two tabs to filter pages by status

3. Edit scheduled save: modify or disable the scheduled save for a page

4. Delete: clear all versions and the scheduled task for a page at once

5. Version actions: expand a page to preview, rename/edit note, or delete each version

"In Use" vs "Archived" Tabs

Tab	Meaning	Counts Toward Plan Usage
In Use	Pages currently within plan usage — pages with manually saved versions, or pages with an active scheduled save	Counts
Archived	Pages no longer within plan usage — versions saved before this feature update, or pages removed from the usage range after plan downgrade	Doesn't count

How Usage Is Calculated

Your usage limit is set by your plan and is counted by the combination of page URL and page type. Ptengine has three page types — Original pages, Combined pages, and Page groups — and the same URL under different page types each counts as a separate unit. All versions under the same page (URL + type) still count as 1 unit, regardless of how many versions accumulate.

How Usage Is Recalculated After Downgrade

After the downgrade takes effect, the system re-evaluates which pages stay In Use as active entries consuming the new plan's quota. The rules:

• Pages with scheduled save enabled are prioritized. If these still exceed the new cap, the system sorts them by most recent creation time (newest first) and automatically disables the excess scheduled tasks, moving those pages to Archived.

• The remaining pages are sorted by most recent creation time (newest first) and filled into the remaining quota in order; any excess also moves to Archived.

For pages moved to Archived: all previously saved versions remain fully preserved and viewable, but scheduled save no longer runs, and new versions can no longer be saved manually either.

Additional Notes

Cases Where Saving May Fail

• Some external resources not saved: Specific third-party resources referenced via relative or absolute paths may fall outside the saving scope

• Invalid or offline URL: the domain cannot be resolved or no longer exists, so the system cannot reach the target page

• Server-side error: the target site returned a server error (5xx), preventing capture

• Blocked by anti-bot or WAF: the target site's bot-protection system (e.g. Cloudflare, AWS CloudFront) identified the capture service as a bot and denied access

These cases apply only to a small number of special pages. The vast majority of standard sites are not affected.

Pages Requiring Login or Restricted Access

Scheduled save works by having the system access the target page as a visitor and capture its content. The system cannot get the complete page content in the following cases:

• Pages that require a logged-in session to display correctly (member-only pages, admin pages, etc.)

• Pages restricted by IP allowlist

• Personalized pages that rely on specific cookies to render correctly

We don't recommend setting up scheduled save on pages like these. If you need to save them, please contact customer support for help with manual save handling.

Frequently Asked Questions

Q. Can I use both scheduled and manual save on the same page?

Yes, and we recommend combining them. All versions go into the same list, distinguished by the [Scheduled] and [Manual] prefixes.

Q. How long are individual versions kept?

Retention follows the Historical Heatmap retention period set by your plan (for example, 12 months). Versions older than the limit are automatically archived.

Q. Does redesigning or taking down the original page affect saved versions?

No. Each saved version is a complete snapshot at the time of capture (HTML and static resources included), stored independently on the server. No matter how the original page changes later — or even if it is taken down completely — the archived version remains unaffected and can always be previewed.

Q. When do scheduled tasks run?

Each run happens at 00:00 (JST) on the scheduled day. This off-peak timing minimizes any impact on your visitors' access.

Q. Can I interact with a saved page — for example, open a menu or submit a form?

In most cases, yes. However, due to compatibility limitations between certain modern frontend frameworks and the capture environment, some pages are currently saved as a static snapshot — visually complete, but clicks and interactions won't respond:

• Sites built with certain modern frameworks (such as Next.js App Router, Shopify Hydrogen, Wix, Shoplazza, or Bubble.io): these frameworks rely on a client-side runtime to activate interactions, a process that cannot complete correctly in the capture environment

• Pages that embed interactive maps (Google Maps, Mapbox, etc.): map tiles are generated dynamically and cannot be bundled into a snapshot

In static mode, any JavaScript-driven interactions — such as opening menus or submitting forms — will not respond.

Visual content (text, images, layout) and heatmap data are fully intact and viewable.

Related Pages

• Smart Heatmap Overview

• Comparison Heatmap

• Toolbar Features