Cookie and Storage Schedule
Detailed technical ledger of client storage tokens, Consent Mode v2 signal states, paid advertising click identifiers, and retention clocks for Scott Roofing Company.
Effective Date
Effective Date and Schedule Baseline
This Cookie and Storage Schedule takes effect on 2026-11-10 and applies to all browsers connecting to scottroofingsco.com. The controls described herein reflect current requirements across Google Ads, Microsoft Advertising, and Meta Ads networks operating in Phoenix and the broader state of Arizona.
Scott Roofing Company reviews this inventory whenever we update our client-side dispatch chat, estimating tool hooks, or conversion measurement scripts. All revisions are logged with precise timestamps.
Storage Taxonomy
Cookie and Local Storage Classifications
We group client storage technologies into three distinct functional classifications:
1. Strictly Necessary Storage: Essential for basic navigation, UI accessibility, security honeypots, and maintaining technical chat sessions with our Phoenix dispatch desk. These items do not track personal behavior across third-party websites and cannot be deactivated without disrupting core site functions.
2. Analytics Storage: Measures aggregate site engagement, such as which roofing service pages are consulted most frequently during Phoenix summer monsoon periods. These measurements remain blocked until you grant consent.
3. Advertising and Attribution Storage: Tracks commercial inquiries originating from paid search or social campaigns on Google Ads, Microsoft Advertising, or Meta Ads. These keys correlate conversion events with inbound click identifiers under Consent Mode v2 controls.
Client Storage Keys
Complete Storage Inventory and Technical Specifications
The table below itemizes every cookie, local storage key, and session token utilized on this domain:
| Identifier Name | Provider / Origin | Category | Purpose & Technical Function | Lifespan / Retention |
|---|---|---|---|---|
| site_consent_v2 | Scott Roofing Company (First-Party) | Strictly Necessary | Records your explicit acceptance or decline of analytics and advertising storage signals. | 12 months |
| scott_chat_token | Scott Roofing Company (First-Party) | Strictly Necessary | Maintains session continuity in browser local storage for live conversation with dispatch desk (hafufb2.php). | 12 months |
| _ga | Google LLC (Third-Party / 1st-Party Context) | Analytics | Calculates visitor, session, and campaign engagement metrics for roof inquiry pages. | 13 months (when allowed) |
| _ga_* | Google LLC (Third-Party / 1st-Party Context) | Analytics | Maintains session state across page views during estimator tool calculations. | 13 months (when allowed) |
| _gcl_au | Google LLC / Google Ads | Advertising | Stores ad click attribution data when arriving via Google Ads search links. | 90 days (when allowed) |
| _uetmsclkid | Microsoft Corporation / Bing Ads | Advertising | Correlates paid search clicks from Microsoft Advertising with submitted inspection requests. | 90 days (when allowed) |
| _fbp | Meta Platforms Ireland Ltd | Advertising | Stores browser identifier for conversion attribution on Meta Ads campaigns. | 90 days (when allowed) |
Campaign Parameters
Advertising Platforms and Click Identifiers
Scott Roofing Company receives traffic from google ads, Microsoft Advertising, and Meta Ads to connect Phoenix property owners with our licensed roofing crew (Arizona ROC No. 123456). When you select a sponsored search or display listing, the advertising platforms attach campaign tracking click identifiers to the destination URL:
- Google Ads attaches the gclid parameter to inbound links.
- Microsoft Advertising attaches the msclkid parameter.
- Meta Ads attaches the fbclid parameter.
Our server-side and client-side systems parse these click identifiers solely to confirm campaign efficacy and prevent automated click fraud. When Consent Mode v2 storage is declined, these identifiers are not written into persistent browser cookies or shared with third-party tracking graphs.
Signal Mechanics
Consent Mode v2 Signal Architecture
Our website executes consent mode standards under Consent Mode v2 before any network tracking pixel or script initializes. We configure the default operational state of four privacy signals held denied until the visitor allows storage:
- ad_storage: denied
- ad_user_data: denied
- ad_personalization: denied
- analytics_storage: denied
While these signals remain held denied, tags execute in cookieless ping mode without writing or reading advertising identifiers from your device. When a visitor clicks Accept on our consent banner, our consent controller fires an update event changing all four parameters to granted. If a visitor declines or changes their choice, the controller immediately reasserts and sets them back to denied across all four signals.
Granting & Resetting
How to Grant, Change, or Withdraw Consent
Upon your first visit to scottroofingsco.com, a docked banner appears offering clear Accept and Decline options. Selecting Accept registers your authorization; selecting Decline blocks non-essential storage immediately.
You retain complete control to modify or withdraw your consent choice at any time during your visit. To reopen the preferences interface, click the Consent Settings link positioned in the bottom legal row of every page footer, or use this inline control:
Activating this button redisplays the consent prompt, permitting you to switch from Accept to Decline (or vice versa). You can also clear all stored tokens at any moment through your web browser’s native settings.
Refusal Impact
What Works and What Stops When You Decline
Refusing or revoking consent never limits your access to our roofing services, pricing schedules, or estimate requests.
What Continues Working Without Interruption:
- Browsing all service breakdowns, material specifications, and Phoenix job logs.
- Reviewing confirmed USD price bands (e.g. 8,500 to 30,000 USD for new roofs, 15,000 to 40,000 USD for tile replacements).
- Utilizing the interactive Roof Fit & Scope Checker to calculate project estimates.
- Submitting the on-site inspection inquiry form directly to our estimators via tagac09.php.
- Conversing in real time with our dispatch desk via the support chat widget (hafufb2.php).
What Stops Operating:
- Cross-session analytics logging in Google Analytics.
- Conversion attribution linking your request to Google Ads, Microsoft Advertising, or Meta Ads campaigns.
- Retargeting signals and personalized advertisement delivery on external web properties.
Third-Party Policies
Third-Party Privacy Policies and Documentation
To understand how third-party advertising and analytics providers process telemetry signals, inspect their respective privacy policies:
- Google Ads & Analytics Policies: Review Google’s privacy disclosures, data retention rules, and partner site practices at policies.google.com.
- Microsoft Advertising: Review Microsoft’s data collection policies, ad personalization controls, and privacy statement at privacy.microsoft.com.
- Meta Platforms: Review Meta’s cookie policies and ad setting preferences at facebook.com/privacy/policy.
Direct Assistance
Inquiries Regarding Cookies and Local Storage
If you have technical questions regarding our cookie schedule, Consent Mode v2 implementation, or wish to verify the removal of client storage identifiers, contact our technical officer directly:
Scott Roofing Company
Attention: Web Data & Cookie Compliance
24777 N 15th Ave, Phoenix, Arizona 85085, United States
Telephone: 602-442-7663
Electronic Mail: [email protected]
We address all cookie-related questions within 10 days of receipt.