Website Measurement & Analytics Choices

Optional Google Analytics

Google Analytics is optional. The Google script is not requested and no Google Analytics measurement is sent until a visitor affirmatively chooses Allow optional analytics. Choosing to continue without analytics does not restrict the website or its public request paths.

If allowed, the site sends the canonical site origin plus an approved public pathname. When the separately controlled campaign feature is enabled, it may also send the exact pre-registered campaign labels described below. Raw browser URLs, query strings, fragments, and uncontrolled referrers are removed. The implementation does not send form entries, names, phone numbers, email addresses, VINs, property addresses, request descriptions, uploaded-file information, customer or company identifiers, internal Operations routes, advertising click IDs, or a user ID.

Google may process ordinary technical information associated with permitted page-view or inquiry-count requests, such as browser or device details, timestamp, network information, and approximate location. Google Analytics may set first-party _ga cookies only after permission is granted. Advertising storage, advertising user data, advertising personalization, Google Signals, and targeted advertising are disabled by this implementation.

The site stores the fixed choice granted or denied under versioned preference keys in the visitor's browser. The current purpose uses version 2. An older permission for page views is not renewed automatically; the updated panel asks again before enabling this measurement. Existing refusals and staff or test exclusions remain respected. A legacy preference is retained only to keep older open tabs' withdrawal controls compatible. Old campaign-storage records are not carried into the new purpose. After a choice, the persistent Analytics choices button can reopen the panel. Continuing without analytics withdraws permission, disables later measurement, and asks the browser to expire first-party Google Analytics cookies that this site can remove.

Limited Campaign Attribution

A public campaign link may contain a code-owned, pre-registered source, medium, campaign, and placement code. The site considers those codes only after the visitor makes the same affirmative optional-analytics choice, the separate campaign-attribution setting is enabled, the browser is not marked as staff or test traffic, and the landing page is an exact canonical public route. It then keeps only an exact approved combination for the current browser tab. It discards unknown or duplicated values, search terms, advertising click IDs, full landing URLs, full referrer URLs, and arbitrary query parameters. An approved external referrer is reduced to its origin, such as https://www.google.com, without a path or query.

Campaign attribution is not a visitor profile. After permission, the exact registered source, medium, campaign, and placement codes may be sent to Google Analytics as standard campaign labels on an explicit public-page-view event so that event can be grouped by the outreach registration it carries. Arbitrary query values, landing paths, advertising click identifiers, and full referrers are not used as campaign labels. The same limited record may also leave the browser as part of a customer-submitted request through an approved direct intake path. It is not added to a prepared email fallback. If browser session storage is unavailable, the service-request path continues without attribution.

Optional Confirmed Inquiry Counts

With renewed permission and the separate inquiry-measurement setting enabled, the website may send Google Analytics a generate_lead event after the direct request path confirms receipt. It identifies Yampa Basin Property Works or Yampa Basin Advanced Automotive Solutions using a fixed division label, an approved public form path, and the exact registered campaign labels when available. A registered campaign may start on that division's homepage and lead to its request form; another division's campaign is not credited to the inquiry.

These counts do not include names, email addresses, phone numbers, vehicle or property details, form descriptions, uploaded files, or request reference numbers. A request reference is held only in the current form's memory to reduce duplicate signals; it is not sent to Google Analytics or written to persistent browser storage. Failed requests and prepared email fallback are not counted.

A small temporary queue can hold sanitized events while the approved Google script loads. Withdrawing permission clears queued events, and earlier unconsented requests are not replayed after permission is given. Analytics or browser restrictions may prevent a count even when a request was saved. An inquiry event is not proof of a qualified customer, accepted work, a completed job, payment, or revenue.

Release & Test Controls

Analytics is fail-closed: it requires a valid production measurement identifier, an explicit analytics setting, the production hosting context, and the visitor's permission. Campaign attribution additionally requires its own explicit enablement setting. Confirmed inquiry measurement requires its separate setting and the renewed purpose-version-2 choice. These features remain absent on local builds, automated tests, deploy previews, branch previews, protected Operations routes, APIs, and the release-hold route. Staff and controlled-test browsers can also be excluded locally so internal visits do not become customer-performance evidence.

Google Analytics Enhanced Measurement, Google Signals, advertising personalization, and any advertising link must remain off until a separate reviewed release changes this contract. The production data-retention setting must be recorded and reviewed before analytics is enabled. No measurement result should be treated as proof that a request was received, qualified, accepted, completed, or paid.

Provider Information

Review Google's own data practices in the Google Privacy Policy. Questions about this site's measurement design can use the contact method listed in the main privacy notice without including sensitive service-request information.