First-Party Cookies, Consent and Browser Privacy Questions
First Party Cookies: 51 questions with model answers on cookies, click IDs, consent, ITP and privacy laws, from Basic to Advanced.
- Model answers
- Basic to Advanced
- Search and filter
First-party cookies, click ID persistence, Consent Mode, ITP and Safari. Questions are grouped from Basic to Advanced, each with a model answer. Use the filters or search to find what you need, then take the free Conversion Tracking test to check your score.

First, read each question and try to answer it in your own words. Then, open the model answer and compare it with yours. After that, note the points you missed and review that topic again. Finally, take the free test to check your progress and unlock the next level.
What these First Party Cookies questions cover
These questions cover first-party and third-party cookies, keeping click IDs such as gclid and fbclid alive, Consent Mode v2 and CMPs, GDPR and the Saudi and UAE data laws, and what Safari ITP and Chrome changed for tracking.
Privacy questions test whether you can track well and stay compliant. Explain both the technical fix and the legal limit in your answers.
All First Party Cookies questions, from Basic to Advanced
Basic questions
What is a CMP?
- Consent Management Platform (OneTrust, Cookiebot, Usercentrics, Didomi) that collects and stores user consent choices.
Consent Mode v2 parameters?
- ad_storage, analytics_storage, ad_user_data, ad_personalization (plus functionality/personalization/security_storage).
Basic vs Advanced consent mode?
- Basic: tags don't load until consent; Advanced: tags load with cookieless pings when denied, enabling conversion modeling.
Safari ITP cookie caps?
- JS-set first-party cookies capped at 7 days (24 hours when landing URL has click IDs from known trackers in some cases); third-party cookies blocked.
Firefox Enhanced Tracking Protection?
- Blocks known trackers and partitions third-party cookies (Total Cookie Protection).
HttpOnly cookie?
- Cookie not readable by JavaScript; set by server; more secure and durable.
Secure attribute?
- Cookie sent only over HTTPS.
SameSite?
- Controls cross-site sending (Lax, Strict, None).
Intermediate questions
Why was Consent Mode v2 required?
- From March 2024 Google requires it for EEA/UK users to keep personalization, remarketing and measurement features (Digital Markets Act).
Expert insight: Since March 2024 (Digital Markets Act), Google requires ad_user_data and ad_personalization signals for EEA/UK users to keep remarketing, personalization and full measurement. Advanced mode also enables conversion modeling for non-consented users.
Default consent state?
- Set before tags load (Consent Initialization trigger) – e.g. denied for EEA, granted where lawful; update after user choice.
GDPR key principles for tracking?
- Lawful basis (consent for marketing cookies), transparency, data minimization, purpose limitation, user rights.
UAE PDPL?
- Federal Decree-Law 45/2021 on personal data protection – consent/lawful basis, rights, cross-border rules (executive regulations phased).
Saudi PDPL?
- Personal Data Protection Law enforced by SDAIA (effective Sept 2023, compliance from Sept 2024) – consent, data transfer limits, breach notifications.
Hashing ≠ anonymization?
- Hashed PII is still personal data under GDPR (pseudonymized); requires lawful basis.
Expert insight: SHA-256 hashed emails are pseudonymized personal data – GDPR and Saudi/UAE PDPL still apply. Never claim hashing makes sending data "anonymous" in an interview.
Consent in server-side tracking?
- Server must receive and respect consent signals; you can't bypass consent by moving to server.
Conversion modeling?
- Google models conversions from non-consented users using consented patterns (requires thresholds).
TCF 2.2?
- IAB Transparency & Consent Framework string standard used by ad tech in Europe.
What did Chrome decide about third-party cookies?
- April 2025: Google kept third-party cookies (no deprecation, no new user-choice prompt).
Expert insight: April 2025: Chrome keeps third-party cookies and won't add a choice prompt; Oct 2025: most Privacy Sandbox APIs retired (Attribution Reporting, Topics, Protected Audience). But Safari/Firefox/iOS restrictions remain – first-party/server strategy is still required.
Privacy Sandbox status (Oct 2025)?
- Google announced retiring Attribution Reporting API, Topics, Protected Audience, IP Protection, Private Aggregation, Related Website Sets, SelectURL, SDK Runtime, On-Device Personalization, Protected App Signals; keeps CHIPS, FedCM, Private State Tokens.
What is CHIPS?
- Cookies Having Independent Partitioned State – partitioned third-party cookies per top-level site.
Safari 26 Advanced Fingerprinting Protection (Sept 2025)?
- On by default for all browsing: known fingerprinting scripts get noisy APIs, can't set long-lived storage, lose query params and referrer.
Expert insight: AFP is on for all browsing: classified fingerprinting scripts lose query params/referrer and long-lived storage. UTMs are exempt from link tracking protection, but click IDs may be stripped in private mode and from Mail/Messages links – rely on server-side storage, hashed PII and enhanced conversions.
Link Tracking Protection?
- Safari strips known click IDs (e.g. gclid, fbclid) in Private Browsing and in links from Mail/Messages; UTMs exempt; expansion to regular browsing being tested – verify.
ATFP in Safari?
- Advanced Tracking and Fingerprinting Protection blocks requests to known tracker domains (e.g. googletagmanager.com) – default only in Private Browsing.
Cookie prefix rules (Safari 26)?
- __Host- prefixed cookies set programmatically must meet Secure/attribute rules or throw errors.
Why server-set cookies last longer on Safari?
- ITP caps JS-set cookies; HTTP Set-Cookie from same-site server (matching IP range) avoids 7-day cap (rules evolve).
Storing click IDs at landing?
- Read URL params on first page, set first-party cookies (server ideally), save to session/user record.
Persisting click IDs to CRM?
- Hidden fields, server session, or user table keyed by email/lead ID.
User ID strategy?
- Hashed internal customer ID as external_id/user_id across platforms.
Probabilistic vs deterministic identity?
- Deterministic: logins/emails; probabilistic: IP/UA patterns (privacy-limited).
Advanced questions
Interview: "Does server-side tracking let us ignore cookie banners?"
- No – consent laws apply regardless of where data is processed; server-side improves reliability/control, not legality.
Consent mode audit steps?
- Check default/updated states in Tag Assistant, region settings, tag behavior when denied, GA4 consent settings, modeled data eligibility.
GCC privacy practicalities?
- Privacy policy, consent for marketing cookies (best practice), data processing agreements with vendors, cross-border transfer review, PDPL compliance.
Data retention settings?
- GA4 event data retention (2 or 14 months standard), CRM retention policies, delete on request.
Sensitive data restrictions?
- Never send health, religion, financial account data to ad platforms; Meta restricts health/finance event data.
Privacy-safe measurement methods?
- Aggregated reporting, MMM, incrementality, clean rooms, modeled conversions.
Data clean rooms?
- Secure environments (Ads Data Hub, Amazon Marketing Cloud, LiveRamp, Snowflake) for joining data without exposing PII.
Ad blockers vs consent?
- Different issues: blockers block requests; consent is legal requirement; first-party/server reduces blocking but must honor consent.
Mitigations for Safari tracking loss?
- First-party serving (Google tag gateway, sGTM custom domain/same-origin), server-set cookies, CAPIs with hashed PII, store click IDs server-side at landing, UTMs for analytics, modeling/MMM.
Why UTMs survive LTP but click IDs may not?
- Apple targets user-identifying parameters; UTMs are campaign-level.
Chrome IP Protection status?
- Retired in Oct 2025 Privacy Sandbox announcement.
Impact of Chrome keeping cookies?
- Third-party cookie retargeting continues on Chrome; Safari/Firefox still restrictive – mixed environment.
Interview: "iOS 26 strips gclid – what do you do?"
- Rely on gbraid/wbraid + enhanced conversions, Google tag gateway, sGTM first-party cookies, UTMs for reporting, offline imports with hashed identifiers.
Bounce tracking protections?
- Browsers clear storage of domains used only as redirect trackers; avoid redirect chains.
Storage partitioning?
- Third-party iframes get partitioned storage – affects embedded widgets/booking engines.
Cookie keeper/restore techniques?
- Server-side restore of cookies from server storage when browsers clear (e.g. Stape Cookie Keeper) – ensure consent.
Click ID expiration?
- Google gclid conversions within account window (up to 90 days); Meta fbc formatted with timestamp.
Identity across subdomains?
- Set cookies on root domain (.example.com).
Interview: "How do you keep attribution alive for 30-day cycles on Safari?"
- Server-set first-party cookies, store click IDs server-side on landing, hashed emails at conversion, enhanced conversions/CAPI.
Fingerprinting – allowed?
- Against Apple policies and many privacy laws; avoid.
Login walls and identity?
- Logged-in users enable deterministic matching – encourage account creation with value.
Email hashing consistency?
- Same normalization across all platforms to match.
More Conversion Tracking question topics
Want an expert to run your Conversion Tracking?
Book a free strategy call and get your pixels, CAPI and conversion tracking set up right.