pixellint

Global Privacy Control Must Fire Before the Pixel, Not After the Rental Search

Check your payload in the playground →

On November 17, 2026, the California Privacy Protection Agency board adopted a stipulated final order against The Hertz Corporation requiring a $1.55 million administrative fine and three years of quarterly opt-out compliance testing. The factual findings are not a generic cookie banner story. They name pixel and cookie vendors on rental booking flows, describe cookie matching between ad-tech companies, and require Hertz to check for a Global Privacy Control signal before loading tracking technologies that sell or share personal information.

Trade coverage on November 18, including All About Cookies, focused on the human failure mode: toggling advertising cookies off in Manage Cookies on Dollar.com and Thrifty.com, then closing the window with the X control without clicking Save Changes, which reverted to defaults that allowed advertising cookies. That UI friction is one branch. The order's separate branch is opt-out preference signals. For a portion of the period from July 1, 2023 through August 25, 2026, Hertz failed to configure its digital properties to detect and honor GPC, continued to sell and share personal information with multiple AdTech companies and data brokers, and violated Civil Code section 1798.120(d) and Code of Regulations title 11 sections 7025(c)(1) and 7026(f).

Measurement engineers should read that sequence as a wire-order problem, not as a privacy policy rewrite. California law has required businesses to honor opt-out preference signals for more than six years per the order's regulatory citations. GPC sends a standardized HTTP header and sets a JavaScript property websites can read. Once a business receives a request to opt-out, including through GPC, it is prohibited from selling or sharing that consumer's personal information unless the consumer subsequently provides explicit consent. A Conversions API row with a hashed email does not rewind browser pixels that already fired while the tag manager ignored the header.

What sale and share mean on a rental funnel

The order defines tracking technologies as scripts, cookies, pixel tags, web beacons, software development kits, or other mechanisms used to collect and analyze consumer activity. Hertz admitted it sold and shared certain consumer personal information to third parties for cross-context behavioral advertising through those technologies on Hertz, Dollar, and Thrifty digital properties.

The stipulated findings list vendors whose tracking technologies were installed: Meta, Google, Pinterest, LinkedIn, Microsoft, TikTok, The Trade Desk, LiveRamp, Adobe, Amazon, Sojern, Criteo, Wunderkind, and other AdTech companies, some registered as data brokers. Those technologies made personal information such as personal identifiers and car rental dates available for cross-context behavioral advertising.

Some vendors engaged in cookie syncing or cookie matching to recognize the same individual across systems. The order describes that sync as deepening cross-context behavioral advertising exposure. For practitioners, the consequence is that one rental search can propagate identifiers across brokers even when the consumer believed a banner choice stopped tracking.

Hertz knew consumers had the right to opt-out of sale and sharing. The enforcement theory is implementation: signals and UI methods must actually gate the tags, not merely document rights in a policy.

GPC is checked before load, not after Events Manager turns green

The non-monetary provisions require Hertz to maintain configurations that recognize consumer requests whether submitted through an opt-out preference signal such as GPC or through another CCPA opt-out method. The order repeats timing language from section 7026(f): Hertz must check whether it has received the consumer's GPC signal before loading tracking technologies that sell or share personal information.

That before-loading requirement is the opposite of post-hoc consent fields on server events. Tag managers that initialize Meta and TikTok on every page view, then set limited data flags only on checkout, miss the legal gate on the first hop. CMP categories that block analytics after the marketing pixel already synchronized cookies are similarly late.

The order also requires implementing documented instructions from tag managers, consent management platforms, and other service providers on how to configure properties to give full effect to opt-outs. Quarterly scans must maintain a full inventory of tracking technologies that sell or share personal information on Hertz.com, Thrifty.com, Dollar.com domains, subdomains, and mobile applications.

For three years after the board decision, Hertz must test at least quarterly that opt-out preference signals and other opt-out methods work, with written records. Agencies auditing other travel and rental stacks should treat that cadence as the new baseline for enterprise QA, not as a one-time CMP retag project.

Signals the order expects before marketing pixels initialize

Global Privacy Control is a browser-level opt-out preference signal cited in CalPrivacy regulations title 11 sections 7025 and 7026. Tag containers must read it before firing sale-or-share pixels named in the Hertz findings.

Sec-GPC: 1

// or, in supporting browsers:
navigator.globalPrivacyControl === true

If your container loads Meta Pixel and TikTok Pixel on DOM ready without a GPC branch, you reproduce the failure mode California fined. The header and property are standardized so sites can adjust operation before collection begins.

Server-side GTM forwarding does not replace that branch. A worker that posts Purchase to graph.facebook.com while the browser still loads fbevents.js for opted-out users violates the same sale-or-share prohibition the order discusses, even if action_source is website and hashes validate.

LiveRamp and Trade Desk identifiers in the vendor list are reminders that broker hops compound once the first pixel fires. Opt-out must suppress the initial sync, not only the obvious social pixels in a marketing slide deck.

Manage Cookies off is not a saved opt-out

On Dollar.com and Thrifty.com, the Manage Cookies window showed toggles indicating advertising cookies were off, per screenshots in the order. Closing the window with the X control without selecting Save Changes reverted to default settings that allowed advertising cookies.

California regulations require methods that do not use confusing interactive elements and require toggles to clearly indicate consumer choice. The agency found the UI visually suggested cookies were already declined while an additional non-obvious step was required for that choice to take effect.

Engineering teams often test only the happy path where Save Changes is clicked. Production users dismiss modals. If revert-on-close is the default, network logs will still show connect.facebook.net and analytics.tiktok.com requests while session recordings show the toggle in the off position at close time.

That bug is independent of GPC. A site can fail both: ignore the browser signal and drop cookie UI state on dismiss. Compliance spreadsheets that map GPC to one Jira ticket and cookie banner to another miss the combined exposure the order describes.

Checklist after the Hertz order

Hertz must check to see if it has received the consumer's GPC signal before loading tracking technologies that sell or share personal information.

CalPrivacy Hertz Stipulated Final Order, Case ENF25-001-V-HE

What changes for buyers and publishers this week

The $1.55 million fine is specific to Hertz, but the injunctive language is portable. Any California-facing site that runs a dozen ad-tech pixels for behavioral advertising inherits the same before-load obligation if it sells or shares personal information as those terms are defined in the CCPA.

Rental parameters and travel dates are high-value intent signals. They are exactly the class of data the order says flowed to AdTech companies. Retail and finance funnels with similar tag density should not assume their CMP vendor already implemented 7026(f) timing because a checkbox in the admin console says California.

Cross-link the VAST gdpr literal replay pixellint published on November 17 only at the consent-on-wire layer: supply-side tracking URLs can carry broken gdpr values while demand-side pixels ignore GPC. Both are consent encoding failures on different hops. Fixing one does not close the other.

If your next ticket is only update the privacy policy link, you are solving section 7011 notice while the order's technology findings were about tag load order and confusing toggles. Prioritize network proof: no facebook.com/tr, no TikTok analytics requests, on a labeled GPC browser profile before any documentation pass.

Sources

Contract pages

The dated argument is above. These pages are the field lists.

Read the consent-on-collector guide Docs