Some product pages sell well while others barely convert, but the two were never compared on one basis. The task is to measure page performance using sessions that view a page and subsequently purchase its product within that session. The workflow produces per-page viewing and purchasing session counts, rates and an experiment backlog, while keeping overlapping page audiences separate from distinct store orders.
First replace every [bracketed] placeholder with real store scope and constraints, then add any actual records or data you have, and paste it into your preferred AI assistant or Spark agent. Spark will follow this page's workflow to produce structured output and verification steps.
Act as a Shopify operations specialist.
Help me measure conversion performance for individual product pages.
My store context is [describe the business, products and target audience].
My scope is [specify the affected products, pages, customers or reporting period]. Use these inputs: [timestamped product-page and purchase events with session, product and order identifiers, the reporting window, and the merchant's minimum session count]. For each page, divide sessions that viewed that page and subsequently purchased its product within the same session by sessions that viewed that page, counting each qualifying session once per page and reporting pages below the merchant's minimum session count with raw counts only.
Deliver the page-session counts, qualifying purchase-session counts, rates and experiment backlog, verify each numerator is a subset of its denominator, reconcile distinct linked orders against the order export, and explain that page totals overlap and must not be summed as store orders for the specified task.
Show the relevant evidence or before-and-after examples and explain how I can verify the result.
If essential data is missing, ask for it and mark unsupported conclusions as unknown.
Do not invent metrics, product claims or customer facts.
For any publication, message, account or store change, use only connected tools within my explicitly authorized scope and report success only after verification; otherwise provide the draft or proposed steps.Split the work into input, judgment, and deliverable phases. Verify each step's output before moving to the next.
Collect timestamped product-page views and purchase events with session identifiers, product identifiers and order identifiers for one merchant-defined window, deduplicating views to one per page per session and excluding sessions whose observation period is incomplete.
For each page, divide sessions that viewed that page and subsequently purchased its product within the same session by sessions that viewed that page, counting each qualifying session once per page and reporting pages below the merchant's minimum session count with raw counts only.
Deliver the page-session counts, qualifying purchase-session counts, rates and experiment backlog, verify each numerator is a subset of its denominator, reconcile distinct linked orders against the order export, and explain that page totals overlap and must not be summed as store orders.
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
Use purchasing sessions divided by viewing sessions for that page, requiring the view to precede purchase of its product in the same session. Count each qualifying session once per page; orders without a linked page view do not enter the numerator.
Count one view per page per session, so reloads do not inflate that page's denominator. A session can qualify for several pages, so page counts overlap and their sum must not be reconciled to the store's distinct order count.
Apply the merchant's minimum viewing-session count and show raw counts below it without ranking. Exclude sessions whose observation period is incomplete, and mark rates unverified if session-level view-to-purchase links cannot be supplied.
Start with scenarios under the same topic, then expand into cross-topic matches suggested by similarity.
Ciwi Spark builds Shopify-native AI tools and agents around the workflows merchants actually run: research, ads, translation, and customer support. Stop rewriting the same prompts by hand.