DGDigital InfrastructureGuide
Analytics That Respect Privacy and Still Improve Conversion
Website analytics can show where visitors struggle and which pages lead to inquiries without tracking people more than necessary. This guide covers measurement planning, privacy obligations, data minimization, consent, configuration and the metrics that actually improve conversion.
- Published
- Updated
- Reading
- 3 minutes
- Prepared by
- EngineSpire Technologies
Key points
- Decide which questions analytics must answer before adding any tags.
- Collect the minimum data needed, and keep personal data out of URLs, events and form tracking.
- Be transparent with a clear privacy notice and, where required, consent before non-essential tracking.
- Track meaningful conversions, such as qualified inquiries and form errors, not vanity metrics.
- Keep a tag inventory, restrict access and set short retention periods.
Start with a measurement plan
| Business question | Metric | Data needed |
|---|---|---|
| Which pages lead to inquiries? | Inquiry rate by landing page | Page views and form submissions |
| Where do visitors give up on forms? | Form starts versus submissions, and errors by field | Form interaction events, without the values typed |
| Which channels bring qualified leads? | Qualified inquiries by source | Source information and aggregated qualification status from the CRM |
| Is the site fast enough? | Core Web Vitals | Performance measurements |
Every tag and event should trace back to a question in the plan. If nobody will act on a metric, do not collect it.
Privacy obligations
- The Data Privacy Act's principles of transparency, legitimate purpose and proportionality apply to analytics that process personal information.
- Describe analytics and cookies in your privacy notice in plain language.
- Where consent is your basis for processing, it must be freely given, specific and informed; the National Privacy Commission's Guidelines on Consent (Circular No. 2023-04) explain what that requires.
- Visitors from other countries may bring stricter consent requirements.
Data minimization in practice
- Never send names, email addresses or phone numbers in URLs, page titles or events; Google Analytics' policies prohibit sending such information.
- Strip query parameters that could contain personal data before they reach analytics.
- Record that a form was started, submitted or failed, never what people typed.
- Set the shortest data retention period that still supports your reporting needs.
- Turn off data sharing settings you do not need.
- Limit who can access analytics, and remove access when people leave.
- Avoid session recording on pages with forms, or make sure inputs are masked.
Consent handling
- Offer equally easy choices to accept or reject non-essential cookies, with categories where useful.
- Load non-essential tags only after consent, or use Google's consent mode so tags adjust their behavior to each visitor's choice.
- Record consent choices and let visitors change them at any time.
- Test that tags actually respect choices using the browser's developer tools.
Configuration checklist
- Separate production from preview and test environments, and never track test traffic as real visitors.
- Exclude internal traffic.
- Use consistent event names and document them.
- Mark only meaningful actions as conversions.
- Keep an inventory of every tag: purpose, owner, data collected and consent category.
Metrics that improve conversion
- Inquiry rate by landing page and by device.
- Form completion rate and validation errors per field.
- Clicks on calls to action by position.
- Site search terms that return no results.
- Visits to pages that return 404.
- Page speed on mobile devices.
- Qualified lead rate by channel, reported in aggregate from the CRM.
Improving conversion ethically
- Fix the usability problems the data reveals before redesigning anything.
- Test changes one at a time, and avoid manipulative designs such as hidden options or false urgency.
- Make forms shorter and clearer, and explain what happens after someone submits them.
- Remember that accessible design usually improves conversion for everyone.
Complements to tag-based analytics
- Aggregated server log analysis.
- Privacy-focused analytics tools that avoid cookies.
- Short, optional feedback questions on key pages.
- Conversations with the sales and support teams who talk to customers.
Common questions
Do we need a cookie banner for Google Analytics?
It depends on the laws that apply to your visitors and how analytics is configured. Philippine privacy law requires transparency and a lawful basis for processing personal information, and visitors from other jurisdictions may require consent before analytics cookies are set. Get legal advice and configure consent handling accordingly.
Can we track form submissions without collecting personal data?
Yes. Record that a form was started, submitted or failed validation, and which field had an error, without sending any of the values people typed.
How long should analytics data be kept?
Only as long as it serves your documented purposes. Many organizations choose the shortest retention setting that still supports year-over-year comparisons in aggregated reports.
Sources and further reading
- [1]Consent mode overview — Google for Developers
- [2]Data retention — Google Analytics Help
- [3]Republic Act No. 10173: Data Privacy Act of 2012 — National Privacy Commission
Need this applied to your environment?
We can turn this guide into a scoped assessment of your own sites, systems and constraints.
Keep reading
- DGCorporate Website Architecture for Complex B2B ServicesA B2B services website has to help very different visitors, from owners to IT managers and procurement officers, find the right service, trust the company and start a conversation. This guide covers audiences, information architecture, service pages, trust, conversion paths and technical foundations.4 min read
- DGTechnical SEO Checklist for a Modern Server-Rendered WebsiteServer-side rendering puts content in front of search engines, but it does not fix crawling, indexing and duplication problems on its own. This checklist covers rendering, status codes, canonical URLs, robots rules, sitemaps, structured data, performance and preview environments.4 min read
- DGCustomer Portal Planning: Features, Roles and IntegrationA customer portal replaces email threads and phone calls with self-service requests, status updates and documents. This guide covers use cases, features, roles and permissions, integration with back-office systems, security, privacy, accessibility and a phased launch.3 min read
