Skip to content

Product detail tracking ​

This implementation extends tracking to the current production PDP. Release activation requires migration 036_analytics_pdp, the collector, CMS and Next.js changes together. The newer PDP on the development branch is a separate implementation and must be instrumented before it replaces the current page.

Configure in CMS ​

  1. Open the existing product editor.
  2. In Pemesanan and CTA Banner Produk, keep the existing Tracking ID field as the button identifier. Save the product after editing its ID or URL.
  3. Expand Analytics inside each section. Section Tracking IDs and labels are editable; switches use On / Off.
  4. Analytics switches are shared by the PDP template across products. The Product CTA buttons setting under ordering controls both order and banner buttons. They can share an ID only for the same product and exact destination.
  5. Save Analytics separately from the product content. The public configuration and page cache must refresh before a saved change appears on the website.

What is recorded ​

InteractionEventIdentity
Open a productpage_viewpage_key=pdp, page_entity_id=<CMS product UUID>
View introduction, details, detail item, FAQ, related articles or CTA bannercomponent_impressionCMS section Tracking ID; repeated item ID in entity_id
Open FAQaccordion_openFAQ section Tracking ID and FAQ entity_id
Choose product CTAcomponent_clickExisting button Tracking ID
Choose related article or return to catalogcomponent_clickCMS interaction Tracking ID; article ID where available
Scroll pagepage_scroll25, 50, 75 and 90 percent milestones

The product UUID is present on every PDP event. anonymous_id and session_id use the same reusable identity mechanism as other pages. Product titles, HTML and raw URLs are not sent as free-text properties.

WhatsApp and UTM ​

A normal click on a supported CRM or first-party short link uses the existing journey endpoint. It carries bm_click_id, the button ID, product ID, browser/session identity and allowed UTM parameters. The existing CRM short reference is placed in the WhatsApp message. Opening WhatsApp does not mean a message was sent; the message link appears only after CRM/Yellow receives a matching message and the processing pipeline runs.

The migration fills missing button IDs and resolves collisions. It does not replace CTA destinations or UTM values. CMS can edit the stored IDs afterwards; the Next.js code does not hardcode emitted IDs.

Read the data ​

Filter core_butics.fact_base_events or page visits by page_key = 'pdp'. core_butics.dim_base_pages names this type Product details. The existing GA bridge carries the same event/product identifiers. WhatsApp references and message joins follow the existing core_master_analytics pipeline.

Validation ​

Test a page view, section view, FAQ open and order CTA. Confirm the same product UUID and browser/session IDs in the event and journey. Verify the final WhatsApp reference remains short and the original UTM values are retained. Test both top and bottom CTAs, missing-ID migration, duplicate-ID handling, and navigation from one product to another. Never infer a received message from a redirect alone.

Bumame Engineering · Butics — Butech Analytics