What Gaggle changed

• Added a new detailed cookie consent banner with explicit "Accept All" and "Decline" options.
• Updated the list of tracking cookies, including new entries for YouTube (__Secure-BUCKET) and Mailfloss (mfClientId).
• Reorganized the cookie categorization into Necessary, Preferences, Statistics, and Marketing sections.
• Modified how Cloudflare and Hotjar cookies are identified and stored.

Gaggle has updated its tracking infrastructure and consent management. This shows they are refining how they collect user data for marketing and analytics, likely to improve their ad targeting and sales funnel tracking.

• Added a Cookiebot consent banner with options to Accept All or Decline tracking.
• Introduced a categorized cookie disclosure interface (Necessary, Preferences, Statistics, Marketing).
• Added specific security cookies like XSRF-TOKEN and bot-detection cookies (reCAPTCHA).
• Expanded the list of tracked providers to include Cloudflare and Calendly.
• Updated descriptions and storage durations for existing tracking scripts from Google, HubSpot, and LinkedIn.

Gaggle has updated its website to include a formal cookie consent banner and a detailed disclosure of tracking technologies. This indicates a move toward stricter data privacy compliance and transparency regarding how they track users for marketing and analytics.

• Added links to new case studies for Keene Independent School District, Millburn Township Public Schools, Fillmore Unified School District, and Wichita Falls Independent School District.
• Updated privacy disclosures to state that Google may use IP addresses for ad measurement and personalization.
• Added a new YouTube tracking cookie (ytidb::LAST_RESULT_ENTRY_KEY) to the marketing section.

Gaggle is expanding its library of social proof by adding specific success stories from several school districts. This helps them build trust with educational leaders by showing real-world results in similar environments.