Tag: Data minimisation

All blog posts with this tag.

A submit click is not a lead: reliable B2B form conversions

A submit click is not a lead: reliable B2B form conversions

A contact page reports twenty clicks on "Submit". The analytics dashboard calls them twenty conversions. The CRM contains only twelve inquiries. Which number is correct? Without a documented trigger, the question cannot be answered. Many B2B websites track an interaction because it is easy, then name it after a business outcome that has not yet occurred. A click, submission attempt, server-side acceptance and qualified lead are different states. Conflating them weakens decisions even when the charts themselves look flawless. A lean measurement plan does not require more personal data. It requires a precise definition of success and a repeatable test. Four stages, four distinct claims Intent: the click A primary button click shows an interaction with an offer, such as requesting a demo or quotation. The visitor may stop there, discover an error or abandon an unfinished form. Calling that event a received lead overstates the outcome. Clicks remain valuable for a design question: can people find and use the action? They do not establish how many inquiries the business has received. Attempt: the form submission A form event can be emitted by browser code before a final server confirmation, depending on the implementation. Validation may fail or the request may never reach its destination. Google Analytics documents the automatic "form_submit" event, while recommending that teams define an event for the specific form they intend to treat as important. This is useful guidance, not a guarantee that any submission event proves a successful lead. Confirmed request: accepted by the application For many B2B use cases, the strongest web conversion signal is a confirmed operation, such as the backend acknowledging that a request has been stored or queued for processing. That is still a technical milestone. It does not guarantee that a sales representative has reviewed the request or that the prospect is suitable. But it is a more defensible web conversion than a click. Qualification: a commercial decision A qualified lead usually belongs to a CRM process. It may require verified contact information, account fit, genuine demand and a subsequent conversation. That classification can happen hours or days after the web event. Google's recommended event taxonomy separates lead generation, qualification and downstream conversion. The underlying lesson is independent of the vendor: web analytics and commercial operations have different evidence standards. Define the event before adding instrumentation Ask marketing and engineering to finish one sentence together: "A demo request has succeeded when..." Fill in an observable condition, for example, "the server confirms acceptance using the application's documented success response." Define an event through four fields: stable name, precise trigger, success condition and exclusions. Counting a completed request rarely requires sending the visitor's name, email address or free-form message to an analytics provider.Signal Suggested trigger Safe interpretationForm opened Explicit display or interaction Initial interestSubmission attempted Form action initiated Possible frictionRequest accepted Verified application confirmation Web conversionLead qualified CRM state transition Commercial intermediate outcomeContract signed Commercial system confirmation Acquired customerNot every signal should be collected. Start with the event that supports a real decision. Adding all five is not evidence of better measurement. Five scenarios that corrupt conversion dashboards Invalid form data A missing required field, validation error or rejected challenge is not a successful request. Aggregate error categories can help diagnose design problems, but sending raw field values to analytics is unnecessary for counting completed forms. The network fails A click can trigger a request that times out. If the conversion event fires before a positive response, the report records a success that never occurred. Deliberately test failed requests and broken connectivity. A visitor tries again Two clicks can represent one request. Two submissions can also create two separate backend records. Applications may use an internal idempotency mechanism to prevent duplicates. That mechanism need not become a persistent cross-site analytics identifier. A confirmation page is reloaded Counting every view of a thank-you URL can duplicate conversions on reload or history navigation. Test those cases. A confirmation event tied to a successful operation may be more reliable than the mere presence of a URL. The form is hosted by another service Embeds, booking flows and redirects may prevent the original site from observing completion. Inspect the integration contract and available callbacks. Where confirmation is unavailable, document that limit instead of relabelling an intent click as a completed lead. Run a small but demanding acceptance test Use fictional test values and a test environment whenever possible. The negative paths are as important as the positive path.Scenario Expected conversion outcomeClick then abandon No completed conversionClient-side validation failure No completed conversionServer error or timeout No completed conversionAccepted request One completed conversionDouble click on one request One conversion if the app de-duplicatesConfirmation page refreshed No extra conversionBack and forward navigation No extra conversion without a new requestThird-party form without confirmation Limitation documentedFor each case, record the action, application response, emitted event and appearance in the report. Allow for the reporting delay documented by the vendor. Repeat this test after important changes to forms, frameworks or tags. A good reporting system can only be trusted to the extent that its events represent known application behaviour. Measure less, but define it more precisely It may be tempting to enrich each event with an email, company name, message, declared budget and persistent user identifier. Those details are not generally required to count requests by form type or website section. Avoid transmitting field contents to analytics without a demonstrable need. Review query parameters for tokens and identifiers. Keep narrowly scoped audience measurement separate from marketing, advertising profiling and CRM identity matching. Our guide to URL parameter filtering explains why seemingly ordinary URLs can expose sensitive information. The CNIL also stresses that any exemption from consent for audience-measurement tools depends on specific conditions. Adding marketing purposes changes the analysis. Data minimisation and legal basis are related but distinct topics. A smaller payload is not a blanket compliance certificate. Interpret conversion rates with their denominators A rate has meaning only when the numerator and denominator are defined. "Accepted requests / visits to the contact page" is not the same measure as "accepted requests / campaign visitors." State the population, period, exclusions and successful event. With small counts, display absolute numbers alongside rates. Going from four to six inquiries is a 50% arithmetic increase, but it does not prove a durable business effect. Traffic mix, campaign seasonality and changes in measurement can all alter the outcome. Likewise, do not force marketing and documentation sites to use identical conversion goals. A support article may succeed by solving a problem without producing a sales request. How Pomelo relates to this approach Pomelo's editorial and product philosophy emphasises essential actions and limited collection. When evaluating it, test the capabilities actually available at that time: supported events, form behaviours, configuration and reporting limitations. Do not assume universal compatibility with every form framework, built-in deduplication or automated CRM qualification unless those features are independently demonstrated. Vendor claims should remain separate from measured outcomes. A reconciliation step between website and CRM Even with a confirmed web event, a small reconciliation exercise is useful. Compare a bounded period of accepted application requests with the corresponding CRM intake count. Numbers may diverge because the CRM rejects duplicates, applies validation, delays an import or receives requests from other channels. The comparison should be based on controlled operational counts, not on sending personal identifiers into analytics merely to join every record. If matching is necessary for troubleshooting, keep it within appropriately governed business systems and retain only the aggregate conclusion in the analytics review. A monthly review asks whether definitions changed, whether a form update caused failures and whether an automation in the receiving system was interrupted. It also checks the reverse discrepancy: CRM inquiries without a tracked web event. These may originate through direct contact, offline activity or a missing integration. This prevents the marketing team from making product changes to fix a sales-intake problem, or changing CRM rules to compensate for flawed browser instrumentation. Conclusion: define proof of success Before changing a dashboard, agree on what successful completion means. Then implement the event and exercise the failure cases. Reliable conversions usually come from tighter definitions and better acceptance tests, not from capturing more data. The next useful question is not "how many people clicked?" but "how many requests actually passed the stage we intended to measure?" FAQ Can a button click count as a goal? Yes, when the objective is interaction with an action. It should not be labelled "lead received" if later steps can fail. Do analytics need the individual form field values? Usually not to count completed requests. Raw values add unnecessary exposure; a confirmation state and non-identifying categories are often sufficient. How do we prevent double counting? Choose one confirmation trigger, test double clicks and reloads, and verify the application's handling of repeated requests. Analytics cannot fix a backend that creates duplicate leads. Are cookieless conversion events always exempt from consent? No. An implementation can be cookieless without satisfying every legal condition. Purposes and configuration still require review. SourcesGoogle Analytics Help, measure key events Google for Developers, recommended lead-generation events Google for Developers, single-page application measurement CNIL, audience-measurement exemptions and conditions CNIL, cookies and trackers: the law

Data collection summary: document what your analytics actually collects

Data collection summary: document what your analytics actually collects

Installing analytics can take minutes. Explaining exactly what it collects often takes much longer. The problem is not only volume. Information is scattered across the tracking plan, vendor documentation, consent manager, source code and cloud configuration. When somebody asks, “Do we transmit the full URL?”, “Is the IP address stored?” or “How long do we keep raw events?”, no single person may have a complete answer. A data collection summary is a short operational document that brings those answers together. It describes the collection that is actually deployed, not the collection implied by a marketing page. It is not legal advice, a replacement for a record of processing activities, or a privacy notice. It is the technical layer that helps keep those documents accurate. What a data collection summary is for The document answers one question:For every data point or signal, do we know where it comes from, why it is collected, where it goes, how long it remains and who can access it?Product teams can use it to challenge new events. Marketing teams can see which dimensions genuinely exist. Engineering teams gain a reference for filtering and transformations. A DPO or legal adviser can compare technical reality with compliance records. Management can see the operational debt behind audience measurement. GDPR principles include purpose limitation, data minimisation, transparency and storage limitation. The Regulation also requires information for individuals and, where applicable, records of processing activities. A data collection summary does not create or replace these duties. It makes the underlying facts easier to establish. It is not the record of processing activities The distinction matters. A record of processing activities describes processing at a governance level: purposes, categories of people and data, recipients, transfers, retention and security measures. A data collection summary goes closer to implementation. It may state that:the page URL is stored without its query string; an IP address is used briefly for a technical operation and not retained; a user-agent is reduced to a browser family; only utm_source, utm_medium and utm_campaign are retained; a form event is emitted only after validation; raw events and aggregate reports have different retention periods.A privacy notice translates the relevant facts into language for visitors. It should not become a copy of the technical inventory, but it cannot be accurate without one.Document Main audience Detail level PurposeRecord of processing Internal compliance Processing and categories Govern and demonstrate complianceData collection summary Product and engineering Fields, flows and controls Describe the deployed collectionPrivacy notice Visitors and users Clear public information Explain relevant processingTracking plan Product, marketing and engineering Events and rules Define what should be measuredThese documents complement one another. They should not contradict one another. The ten columns that make the document useful A spreadsheet is enough. The value comes from the columns and the update discipline. 1. Data point or signal Use concrete names: page path, referrer domain, device class, form event, site ID, UTM parameter, derived country or temporary IP address. Avoid broad labels such as “technical data”. They hide design choices. 2. Example value An example removes ambiguity: /pricing/, newsletter or demo_requested. Use synthetic examples, never real personal data. 3. Source State where the signal originates: browser, server, form, CMS, CDN, analytics script or imported system. This reveals indirect collection. A platform may receive a URL or HTTP header before your tracking code transforms it. 4. Operational purpose Connect the field to a decision. “Identify entry pages that lead to a demo request” is more useful than “marketing analysis”. If a field supposedly serves every purpose, the need has probably not been defined well enough. 5. Transformation before storage Document what is removed, truncated, aggregated or derived:stripping unapproved query parameters; normalising paths; reducing the user-agent; deriving coarse geography and discarding the IP address; hashing an identifier, while recognising that hashing is not automatically anonymisation; daily or monthly aggregation.This separates what the system receives from what it keeps. 6. Destination and processors List every relevant destination: collection endpoint, raw storage, aggregate database, BI tool, export, cloud provider and analytics vendor. Record hosting regions and relevant transfers when they are documented. Do not infer a legal location from a cloud region label alone. 7. Retention Separate the layers:technical logs; raw events; pseudonymised records; aggregate statistics; backups; manual exports.A single global period is often misleading. The CNIL notes that retention should follow the purpose and remain limited to what is necessary. For audience-measurement trackers that may fall within the French consent-exemption framework, it recommends a tracker lifetime of thirteen months and a maximum of twenty-five months for collected information. Those benchmarks do not replace an assessment of the actual setup. 8. Access Describe roles rather than only names: administrators, analysts, agency, support or hosting provider. Specify whether access covers aggregate reports, raw events or exports. “Marketing has access” is not enough when a shared account can download the entire dataset. 9. Consent or configuration dependency Keep this factual:collected only after a consent signal; excluded from audience measurement; enabled for defined campaigns only; subject to local ePrivacy assessment; used for limited audience measurement, provided every applicable condition is met.Do not write “exempt” without documenting scope, conditions and configuration. 10. Deletion and owner Explain how the field disappears: automated deletion, scheduled job, vendor purge, manual procedure, contract termination or export deletion. Add an internal owner and a last-review date. Without ownership, the summary starts ageing at the next deployment. A minimal SaaS exampleSignal Purpose Before storage Retention AccessPage path Understand content usage Query string removed, path normalised 25 months for reports Product, marketingReferrer domain Understand visit sources Origin only when transmitted 25 months Marketingutm_source Identify a declared campaign Values normalised to a taxonomy 25 months Marketingdemo_requested Measure a B2B conversion No form content transmitted 25 months Product, aggregate sales viewIP address Security and coarse geolocation Used temporarily, not stored in the event Documented technical period Restricted operationsUser-agent Technical distribution Reduced to browser and device categories 25 months ProductThe table proves nothing by itself. It must match the observed network traffic, source code and vendor settings. Start with a real tracker audit and compare the results with your minimal tracking plan. A five-step method Step 1: start with network traffic Open browser developer tools, reload representative pages and inspect requests. Test before and after each consent choice, across several journeys and devices. Record domains, payloads, URL parameters and events. The network panel shows what leaves the browser. It may not expose every server-side transformation, but it gives you a verifiable starting point. Step 2: inspect code and configuration Review the collector, tag manager, CMP rules, environment variables and filters. Generic vendor documentation does not tell you which options your site enabled. Check adjacent capabilities too: session replay, advertising enrichment, CRM connections, user identifiers and exports. Step 3: ask vendors closed questions Request testable answers:Is the full URL received and stored? Can query parameters be removed before storage? Is the IP address logged outside the event dataset? Which backups still contain data after deletion? Does the vendor reuse data for its own purposes? Which subprocessors and transfers apply? Do exports follow the same retention policy?“Privacy-friendly” fills no column. Step 4: reconcile the documents Compare the summary with the processing record, data-processing agreement, privacy notice and consent interface. Contradictions matter more than the writing quality of each document in isolation. A common example is a notice saying that only aggregate statistics are collected while the tag manager sends a user identifier to a third party. Step 5: tie review to change Review the summary whenever you add or change:a tool; an event; a collection domain; an export; a retention period; consent behaviour; a processor; a site or property.A light quarterly review can detect silent drift. Mistakes that make the summary unreliable Copying vendor marketing Vendor documents describe a possible product. Your summary must describe your instance and configuration. Treating pseudonymisation as anonymisation A hashed or rotating identifier may still be personal data if it can distinguish or reconnect a person. Use precise terms and document re-identification risk. Forgetting URLs Full URLs can expose email addresses, order IDs, internal search terms or tokens. Even a minimal analytics tool can receive excessive data when the website places it in the address. Documenting only the dashboard The visible report is only one surface. Logs, raw events, backups, exports and integrations count too. Leaving the document ownerless An accurate but unmaintained inventory can become more dangerous than no inventory because it creates misplaced confidence. Validation checklist Before approval, verify that:every field has a specific purpose; received and stored data are distinguished; URL parameters and free-text fields were audited; retention is defined by layer; recipients and access roles are named; consent and configuration dependencies are explicit; deletion can be tested; the summary matches public and contractual documents; an owner and review date are recorded; every anonymisation claim has technical evidence.Conclusion A data collection summary is not another document for a compliance folder. It is a shared interface between product, marketing, engineering and legal work. Its value comes from precision. A team that knows exactly what it collects can remove unnecessary fields, explain the useful ones, configure tools correctly and answer questions faster. Start with one web property and its ten most important signals. Verify them in the network and code, then expand only when the deployed collection justifies it. FAQ Is a data collection summary legally required? This exact format is not prescribed by the GDPR. It can support documents and processes that are required or necessary, including processing records and transparent information for individuals. Should it be public? Not necessarily. It often contains internal technical details. Relevant information for individuals should be expressed clearly in the privacy notice or another appropriate notice. Should a non-stored IP address be listed? Yes, if it is received or used even briefly. Distinguish receipt, temporary processing, transformation and storage. Can one summary cover multiple sites? Only when their flows and configuration are genuinely identical. For multi-site operations, maintain a common reference and document property-specific differences. How often should it be reviewed? At every material collection or destination change, plus a periodic review. Quarterly review is a practical operating rhythm for a small team, not a universal legal rule. SourcesRegulation (EU) 2016/679, including Articles 5, 13, 25 and 30 CNIL, Record of processing activities CNIL, Audience-measurement cookies and consent conditions EDPB, Guidelines 4/2019 on data protection by design and by default Chrome for Developers, Network features reference OWASP, Information exposure through query strings in URL

Just the right measure, for all your websites.

Pomelo is opening gradually. Join the first teams measuring right and help shape what comes next.