Page Data Tracking and SPM for Front-End Development

Front‑end developers often encounter mixed metrics such as PV, UV, click‑through rate and conversion rate when communicating with business teams. Understanding what these numbers actually represent is essential for building data‑driven products.

The basic unit is a page. A page can be a homepage, a detail page, or any other entry point. To turn a page into a source of value, we must track three core aspects:

How many users visited the page (page traffic).

Where the users came from (page source).

What users did on the page and where they went next (user interaction and navigation path).

These metrics enable targeted optimizations, such as increasing promotion on low‑traffic sources, improving content to keep users longer, or making call‑to‑action buttons more prominent.

Identifying a page

Each page is given a unique identifier via URL parameters. For example, adding an id parameter selects a product, and a from parameter records the source page:

www.item.taobao.com?id=1111111111&from=首页

The front‑end must read the from parameter and include its own identifier when generating outbound links, so the next page can know its origin.

Implementation steps

Traffic reporting – log the page’s own parameters on load.

Source reporting – log the from parameter together with traffic data.

Source propagation – attach the current page’s identifier to the URL of the next page.

Down‑stream pages read the incoming identifier and repeat the process.

The SDK provided by the organization automates exposure reporting and link hijacking. It intercepts a tag clicks, appends the current page’s SPM (Super Position Model) identifier, and optionally adds block‑level identifiers (spmC, spmD) for finer‑grained analysis.

Limitations

If navigation is performed via JavaScript instead of a tags, the SDK cannot automatically attach the identifiers, so developers must manually concatenate the parameters. Sharing a page URL also propagates the original from value, which can inflate source metrics unless additional handling (e.g., preSpm ) is added.

Key metrics derived from the data

Page PV and exposure (golden arrow).

Page source‑to‑destination flow.

Block‑level exposure and guide‑to‑purchase conversion.

Guide types: direct guide, indirect guide, full guide, and their breakdown into “guide to product” and “guide to store”.

Guide‑to‑purchase (conversion) combines a successful guide path with an order event.

All these metrics are visualized in the internal “Look‑Data” platform, where a single SPM identifier can retrieve traffic, source, conversion, and block analysis reports.

In summary, front‑end developers need to embed unique page identifiers, consume incoming identifiers, and ensure proper propagation. Mastering these practices turns page rendering into a valuable data source that drives product optimization, business growth, and informed decision‑making.