The CPO Playbook
Process
29 avril 2026 · Dernière mise à jour
Contenu à réviser
FR / EN
Login

PRODUCT REFERENCE

Naming Convention
& Tagging

The standard for naming pages and tracking user behaviour consistently across all product, analytics, and marketing tools.

📐
Why this matters Consistent naming is the foundation of reliable analytics. Every analyst, PM, developer, and marketer should be able to look at a page name or event name and immediately understand what it refers to — without asking anyone. This convention must be applied uniformly across all tools: Amplitude, Google Analytics, GTM, Intercom, and any future tracking stack.

Naming Rules

Before diving into the taxonomy, these rules apply to every name in the system — page names, event names, and properties alike.

Page Naming Convention

Every page on the site has a canonical name used in analytics tools. These names are set in the data layer and must match exactly between the front-end implementation and the tracking plan.

📄
Content Pages
Informational pages — no transactional intent. Used to measure reach, engagement, and brand exposure.
Page Name URL Pattern Description
homepage / Main entry point. Tracked for first-session attribution and entry channel analysis.
about_page /about Brand story and mission page. Indicator of consideration and brand interest.
blog_home /blog Blog index listing all editorial articles.
blog_article /blog/[slug] Individual article. Pass article_slug and article_category as properties.
lookbook_page /lookbook/[slug] Editorial/campaign lookbook. Track lookbook_name and season.
press_page /press Press mentions and media coverage. Low-frequency, brand credibility signal.
sustainability_page /sustainability Brand values and environmental commitment page.
contact_page /contact Contact form or information page.
faq_page /faq Frequently asked questions. Track which questions are expanded.
404_page /404 Error page. Always track with referrer and intended URL for UX audit.
🛍️
Shopping Pages (pages of interest)
Core conversion pages. Every interaction here is tracked with full property context.
Page Name URL Pattern Description
category_page /[category] Top-level category listing (e.g. /shoes, /bags). Track category_name and applied filters.
subcategory_page /[category]/[subcategory] Subcategory listing (e.g. /shoes/heels). Track subcategory_name, sort order, filters.
product_detail_page /p/[product-slug] Individual product page (PDP). Track product_id, product_name, price, color, size_selected, in_stock.
search_results_page /search?q= Search results. Track search_query, results_count, has_results.
wishlist_page /wishlist User's saved items. Track items_count and whether the user is logged in.
cart_page /cart Shopping cart. Track cart_value, items_count, has_promo.
sale_page /sale Sale or promotional listing. Track promotion_name and discount_level.
new_arrivals_page /new New in or latest drops page. Track session entry vs. navigated-to.
ℹ️
Pages of Interest Shopping pages are flagged as "pages of interest" in the user segmentation model. A user who visits product_detail_page or cart_page is automatically scored for higher intent and may shift segment (e.g. from Cold to Hot prospect) if thresholds are met. This linkage between page tracking and segmentation is managed by the data team. See User Segments for thresholds.
🔁
Funnel Pages
The checkout and conversion path. Every step is tracked individually for funnel analysis.
Page Name Step Description
checkout_start Step 1 Entry into checkout. Track cart_value, items_count, user_type (guest/logged-in).
checkout_address Step 2 Delivery address form. Track address_autocompleted, country.
checkout_shipping Step 3 Shipping method selection. Track method_selected, estimated_delivery.
checkout_payment Step 4 Payment entry. Track payment_method, promo_applied, promo_code.
checkout_review Step 5 Order review before confirmation. Track total_value, item_count.
order_confirmation Step 6 Purchase confirmed. Track order_id, revenue, is_first_purchase, user_segment.
checkout_error Error Payment or validation error during checkout. Track error_type, step_from, payment_method.
⚙️
Admin & Post-Funnel
Account and post-purchase pages. Important for LTV and retention tracking.
Page Name URL Pattern Description
account_login /account/login Login page. Track method (email/google/apple), from_page.
account_register /account/register Account creation. Track referral_source, promo_opt_in.
account_dashboard /account My account overview. Track logged-in status, order_count.
account_orders /account/orders Order history. Track orders_displayed.
account_order_detail /account/orders/[id] Single order detail. Track order_id, order_status, days_since_purchase.
account_returns /account/returns Returns portal. Track return_reason, order_id, product_id.
account_settings /account/settings Profile and preferences settings. Track section visited.
loyalty_page /account/loyalty Loyalty programme status. Track tier, points_balance.
tracking_page /track/[id] Shipment tracking. Track order_id, carrier, delivery_status.

Event Naming

Events capture specific user actions. They are the raw material of all funnel analysis, A/B testing, and behaviour-based segmentation. Follow the verb-object pattern without exception.

Discovery & Navigation discovery
Event Name
When Fired
Key Properties
view_page
Every time a page is loaded or navigated to
page_name, referrer, utm_source
search_query_submitted
User submits search from search bar
query, results_count
filter_applied
User applies or changes a filter on a listing page
filter_type, filter_value, page_name
sort_applied
User changes sort order on a listing
sort_by, page_name
image_gallery_viewed
User navigates through product images on PDP
product_id, image_index
Cart & Conversion conversion
Event Name
When Fired
Key Properties
click_add_to_cart
User clicks Add to Cart button
product_id, price, quantity, size, color
cart_item_removed
User removes an item from cart
product_id, price, cart_value_after
checkout_started
User clicks Proceed to Checkout
cart_value, items_count, has_promo
promo_code_applied
User successfully applies a promo code
promo_code, discount_amount, discount_type
purchase_completed
Order successfully placed and confirmed
order_id, revenue, items_count, is_first_purchase, payment_method
checkout_abandoned
User starts checkout but does not complete within 30 min
step_abandoned, cart_value, time_in_checkout
Account & Identity account
Event Name
When Fired
Key Properties
account_created
New user successfully registers
method, referral_source, promo_opt_in
login_completed
User successfully logs in
method, from_page
wishlist_item_added
User saves a product to wishlist
product_id, from_page
return_initiated
User starts a return request
order_id, product_id, reason

Data Ownership

Every part of the tracking system has a designated owner. No new events, page names, or properties should be created without approval from the relevant owner.

Master Owner
Head of Data / Analytics Lead
Owns the tracking plan master document. All new events must be approved here. Maintains the single source of truth across all tools.
Product Domain
Product Manager
Defines what needs to be tracked per feature. Writes tracking requirements in the Product Spec. Responsible for aligning with data before dev starts.
Implementation
Front-End Developer
Implements events in the data layer per spec. Cannot deviate from approved names or properties without sign-off. Validates in staging with QA.
Validation
QA Engineer
Verifies that all specified events fire correctly in staging and production. Confirms payload structure matches the approved spec before release sign-off.
Marketing Stack
Growth / Marketing Analyst
Owns the mapping of tracking events to marketing platforms (Google Ads, Meta, CRM). Responsible for maintaining conversion event accuracy.
Governance
CPO / Head of Product
Accountable for overall data quality and naming discipline. Reviews and ratifies naming convention changes. Escalation point for disputes.

📊
ROI Calculus Methodology The naming convention directly feeds into the ROI analysis layer. Each event and page name is mapped to a feature via the tracking plan, enabling per-feature revenue attribution and impact measurement. See the ROI / Impact Log deliverable for the full methodology on how tracked events are converted into feature-level business impact estimates. The formula accounts for influenced revenue, conversion lift, and cost savings, segmented by user type and cohort.
⚠️
Breaking changes policy Renaming an existing page or event is a breaking change. It will break all historical charts, funnels, and segments that reference the old name. If a rename is necessary, keep the old event active in parallel for a minimum of 30 days while migrating all dashboards and automations. Document the migration in the tracking plan with the deprecation date.