These are predefined categories supported by the WP Consent API:
functionalpreferencesstatisticsstatistics-anonymousmarketingGoogle Consent Mode uses two primary consent signals:
analytics_storagead_storagefunctionality_storagepersonalization_storagesecurity_storagead_user_dataad_personalizationIAB defines 10 purposes and additional special features and stacks:
| Google Consent Mode | IAB TCF v2.2 Purposes / Features | WP Consent API Category | Purpose |
|---|---|---|---|
analytics_storage | 7. Measure content performance 8. Product development | statistics | Analytics, measurement, insights |
ad_storage | 2. Select basic ads 3–6. Ad profiling & measurement | marketing | Ads, targeting, remarketing, campaign performance |
functionality_storage | 10. Technically deliver ads/content | functional | Core site functionality, session cookies |
personalization_storage | 1. Store/access info 4. Personalized content or UI | preferences | UI customization, recommendations, saved settings |
security_storage | 9. Security, fraud prevention | functional | Bot protection, login/session security |
ad_user_data | Special Feature 1 (Use of precise geolocation or device data) | marketing | Targeted advertising based on detailed personal data |
ad_personalization | Purpose 4 (Create a personalized ads profile) | marketing | Personalized ad delivery |
Notes:
statistics-anonymous is an optional WP Consent API category that can be used to separate fully anonymized analytics. You may choose to use it if your analytics tools allow zero data storage/tracking until full consent is granted.
ad_user_data and ad_personalization are Consent Mode v2 extensions and represent deeper levels of ad tracking. These still fall under the marketing category in WP Consent API because they serve advertising purposes.
functional in WP Consent API overlaps with both functionality and security categories in Consent Mode. These functions are usually considered essential and might not require explicit consent depending on local regulations.