In short: Use aggregate pricing page traffic to judge demand, and act on individual visits only for known contacts who have been told how their data is used, ideally within a day or two. Never try to name anonymous visitors, and keep your privacy notice and cookie settings accurate.
- Intent
- Medium
- Act within
- Within a day or two, for known contacts
What this signal means
Visitors to your own website are looking at pages that suggest they are weighing a purchase: pricing, plans, comparisons, case studies or a quote calculator. This is first-party data. It comes from your own site, and only you can see it.
There are two very different versions of this signal. The first is aggregate: more people than usual are looking at pricing this month. The second is individual: a known contact, already in conversation with you, has returned to the pricing page several times. The second is far more useful for sales, and far more sensitive.
Why it predicts a purchase
People rarely read pricing pages for fun. Repeat visits to pricing and comparison pages usually mean someone is building a shortlist, checking budget or preparing to recommend an option internally. For a contact you already know, a return visit after a proposal or demo suggests the evaluation is live.
Aggregate data predicts less about any one buyer, but it tells you which offers draw interest and whether a campaign is working.
Where to find it in Singapore
- Your web analytics. Free or paid depending on the tool. Page-level reports show how many visits your pricing pages receive and where visitors came from. They are designed for aggregate reporting. Google’s guidance for Google Analytics states that Google policies mandate that no data be passed to Google that it could recognise as personally identifiable information.
- Your CRM or marketing email tool. Some tools can link page visits to a contact who has identified themselves, for example by filling in a form or clicking a link in an email you sent them. Check what your own tool does and what you told contacts before relying on it.
What the PDPA guidance says
PDPC’s Advisory Guidelines on the PDPA for Selected Topics (revised May 2024) say the PDPA applies to collecting, using or disclosing personal data using cookies. They also note that an IP address alone may not be personal data, but the more data points an organisation ties to it over time, the more likely an individual becomes identifiable. Where advertisement targeting involves collecting personal data through cookies, consent is required, and PDPC suggests letting users set cookie preferences on the site.
The Advisory Guidelines on Key Concepts explain the Notification Obligation: tell individuals the purposes for collecting, using and disclosing their personal data on or before collection.
How to monitor it
- Watch aggregate trends weekly. Note pricing page visits, the pages visited before them and the sources that sent the traffic.
- Make it easy to raise a hand. A clear “request a quote” or “talk to us” option on pricing pages turns an anonymous visit into an inbound enquiry.
- For known contacts only, use your CRM’s activity record if your privacy notice and consent cover it, and flag repeat visits to the account owner.
- Review your privacy notice and cookie settings so they describe what you actually track.
How fast to act
For a known contact already in conversation with you, within a day or two of a cluster of visits. For aggregate trends, act within the week by adjusting content, follow-up or campaigns. Do not try to turn anonymous visits into named outreach.
Example first message
Illustrative example, sent to a contact who requested a proposal last week:
Subject: Your proposal for Meridian Freight
Hi Daniel, a quick follow-up on pricing for the proposal I sent Meridian Freight last week. Questions often come up once a proposal goes round internally, especially on the per-site charges. I can walk you or your finance lead through the options in 15 minutes. Would Wednesday or Thursday afternoon work?
Regards, Sarah
The message picks up the pricing question the visits suggest, without saying you saw them browse. Telling someone you watched their visits rarely helps.
Pitfalls and rules
- Do not identify individuals without consent. Avoid tools or tactics that try to name anonymous visitors.
- Your own team visits too. Exclude internal traffic before reading the trend.
- One visit is not evaluation. Look for repeat visits from a known contact over a short period.
- Say what you track. Your privacy notice and cookie settings should match what you collect.
- Check the outreach rules in B2B outreach in Singapore: what PDPA and the Do Not Call rules allow. This page is not legal advice.
FYAdvisers can help you turn pricing page interest into clear enquiry routes and timely follow-up through our speed-to-lead response service.
Frequently asked questions
Can I find out which person visited my pricing page?
Not from standard web analytics, and you should not try to without consent. Google's policy, for example, says no data Google could recognise as personally identifiable should be sent to Google Analytics. Person-level activity is only appropriate for contacts who have identified themselves and been told how their data is used.
Does the PDPA apply to website tracking?
It applies when cookies or other tracking collect personal data. PDPC's guidelines say the PDPA applies to collecting, using or disclosing personal data using cookies, and that consent is required where advertisement targeting involves collecting personal data through cookies.
What is the safest way to use this signal?
Use aggregate pricing page traffic to judge demand and content, and act on individual activity only for known contacts, such as people already in a conversation with you, who have been told how their data will be used.