Independent editorial project
Privacy notice
Lagodiresia.com uses Google Analytics 4 only after explicit consent, with advertising signals disabled and an event contract limited to predefined categories; the preference remains withdrawable. Use this page as initial guidance: every changing detail requires an identified source and a current verification.
Lagodiresia.com uses Google Analytics 4 only after explicit consent, with advertising signals disabled and an event contract limited to predefined categories; the preference remains withdrawable. Cautious editorial content for preparing a visit to Lake Resia.
Optional measurement and consent
Google Analytics 4 loads only after an explicit choice. Default consent denies analytics, advertising, personalisation and Google signals; choosing necessary technologies only keeps the site usable without loading Analytics.
The Google script is inserted after “Accept Analytics”. Before consent, code prepares a denied state only and sends no page views.
Local preferenceThe choice is stored in the browser under lagodiresia_analytics_consent_v1 with its version and date. It remembers consent or refusal.
Sources supporting this section
- European data protection regulationItalian Data Protection Authority · Checked on
- Guidelines on cookies and tracking toolsItalian Data Protection Authority · Checked on
- Privacy controls in Google AnalyticsGoogle Analytics · Checked on
- Identity and independence of Lagodiresia.comLagodiresia.com · Checked on
What is measured
After consent we measure page_view with the page locale and the fixed site content cluster, and Web Vitals through web_vital: TTFB, FCP, LCP, FID, CLS and INP. Editorial events are planner_complete, operator_contact, itinerary_share, webcam_activate and map_open; disclosed commercial events are sponsor_impression, sponsor_click, sponsor_outbound_click and sponsor_enquiry. Among the only allowed business parameters, page_locale identifies the language of the viewed page; content_cluster groups its content family; interaction_target describes the category of the interaction and its target class; record_type identifies the provider record or entity type, such as poi, accommodation, event or webcam; destination_host contains only the sanitized destination hostname. The Google tag automatically adds language, meaning the configured browser language, page_location, meaning by default the complete URL with its path and query but excluding the fragment, page_referrer, meaning the previous URL, page_title, meaning the page title, and screen_resolution, meaning the screen resolution, to every event. Application code overrides page_location with origin plus pathname and no query or fragment, page_referrer with an empty value, and page_title with the fixed value Lagodiresia.com; language and screen_resolution remain provider-added technical fields. For web_vital, metric_name names the metric; metric_value is its rounded value, with CLS multiplied by one thousand; metric_id is the technical metric identifier for that page load, not a declared person identifier; metric_rating is good, needs-improvement or poor; navigation_type describes the navigation kind: navigate means a normal navigation, reload means a reload, and back-forward or back-forward-cache means a history return; non_interaction is true to mark the measurement as not caused by an interaction. Printing is not measured.
We add no planner field or value, email address, phone number or free text to application payloads. The page_location override retains origin and pathname only; it does not prevent the provider from adding the other disclosed technical fields.
Take care with the planner URLThe planner uses a GET request: date and starting place appear in the URL query and may remain in browser history, shared links or technical hosting logs. A provider-generated page_view can also follow rules outside the application payload. Do not enter sensitive data.
Sources supporting this section
- Guidelines on cookies and tracking toolsItalian Data Protection Authority · Checked on
- Privacy controls in Google AnalyticsGoogle Analytics · Checked on
Withdrawal, cookies and notice limits
The “Cookie preferences” button changes the choice. Withdrawal blocks new events, disables the stream and attempts to remove Analytics cookies readable on the domain; it does not retroactively erase data already processed by the recipient.
After the first choice, a button reopens the panel. Switching to “Necessary only” denies new transmissions and removes _ga, _gid and _gat cookies found on the domain.
Remote configuration must be verifiedThe code sets send_page_view to false, preventing the config command’s automatic page_view, and then sends one application page_view per pathname. GA4 Enhanced Measurement can still create page_view events on browser history changes independently: the remote “Page changes based on browser history events” option must be disabled and verified at the provider. The repository proves neither that remote configuration nor the controller’s legal identity, contact or retention, so the page remains non-indexable.
Sources supporting this section
- European data protection regulationItalian Data Protection Authority · Checked on
- Guidelines on cookies and tracking toolsItalian Data Protection Authority · Checked on
- Privacy controls in Google AnalyticsGoogle Analytics · Checked on