Fullstory Page Properties Assistant FAQs

Question 1

What is the benefit of using the Page Properties API?

Accepted Answer

It allows for semantic naming and the addition of contextual metadata—like cart value or search terms—that enriches every event on that page, making segmentation and journey mapping much more powerful than simple URL tracking.

Question 2

Does this skill support Single Page Applications (SPAs)?

Accepted Answer

Yes, it includes guidance on handling SPA navigation where traditional page loads don't occur, ensuring properties are merged or reset correctly during client-side routing transitions.

Question 3

Are page properties persistent across the entire session?

Accepted Answer

No, page properties are session-scoped but reset whenever the URL host or path changes. This ensures that metadata remains relevant only to the specific page the user is currently viewing.

Question 4

What kind of data can I track with page properties?

Accepted Answer

You can track search terms, active filters, pricing data, inventory status, article categories, checkout steps, and any other context relevant to the current page view.

Question 5

How does this skill help with Fullstory's 1,000 page limit?

Accepted Answer

It teaches the 'Generic Name + Properties' strategy. By using a single pageName like 'Product Detail' and using properties to distinguish between products, you avoid exhausting the 1,000 unique page name limit.

Fullstory Page Properties Assistant

主要功能

使用场景

Fullstory Page Properties Assistant

主要功能

使用场景