Meta Analytics Privacy

Analytics Privacy and Data Governance

Sources: Raaz (c.2023) Web Analytics Blueprint; Hanlon and Tuten (2022) The SAGE Handbook of Digital Marketing

Use When

• Use this skill for reviewing analytics collection, consent, retention and data-sharing risks.
• Confirm that meta-utm-tracking is not the closer route before proceeding.

Do Not Use When

• Use meta-utm-tracking when its narrower output is requested.
• Do not publish, spend, change a live account, certify compliance, or invent missing client evidence.

Required Inputs

Outputs

Evidence Produced

Capability and permission boundary

Read and search access to the supplied artefacts are required; calculation or file-rendering capability is optional. This is read-only by default: inspect and report without changing source records, accounts, skills or campaigns. Editing the deliverable requires explicit authorisation; publishing, production mutation, destructive action, spend, and certification claims require separate explicit authority and evidence.

Degraded mode

If files, platform access, network, rendering, fonts, or calculation tools are unavailable, return the narrowest useful qualified analytics privacy review and remediation register. Mark each blocked check not assessed, state the consequence, and provide the exact evidence needed to resume. Never convert an unavailable check into a pass.

Decision rules

Workflow

1. Confirm the requested decision, consumer, market, period and permission boundary; route to meta-utm-tracking if its contract is closer.
2. Inventory the required inputs and their provenance. Stop any decision whose critical evidence is absent; recover by requesting it or recording a bounded assumption.
3. Apply the domain method in the core sections below, following the decision table whenever evidence conflicts or scope changes.
4. Verify calculations, dates, named platforms and claims against the supplied sources; label inference and uncertainty.
5. Produce the analytics privacy review and remediation register, decision/source register and explicit next owner. Do not mutate live systems without separate authority.
6. Run the repository anti-slop ship gate. If a blocking factual, permission or evidence defect remains, fix it or withhold release.

Quality Standards

The output is client-specific, uses British English and the stated market/currency, distinguishes observed fact from inference, exposes gaps, and gives a checkable acceptance condition. Recommendations must be feasible within the confirmed budget, capacity and permissions.

Anti-Patterns

• Using an undated benchmark as the client's result. Fix: use account evidence or label the benchmark as a provisional comparator.
• Producing the analytics privacy review and remediation register without data-flow inventory. Fix: stop the affected decision or issue a clearly bounded partial output.
• Treating missing access or data as a successful check. Fix: record not assessed, its risk and the recovery input.
• Absorbing meta-utm-tracking into this workflow. Fix: route the neighbouring output and hand over verified inputs.
• Publishing, spending or editing a live account during planning or review. Fix: obtain separate explicit authority and retain action evidence.

Worked example

Given verified data-flow inventory, the skill produces a analytics privacy review and remediation register with source dates and named assumptions. If that evidence cannot be accessed, it returns only the supported sections plus a recovery list; it does not fill gaps with East African defaults.

Read next

• meta-utm-tracking for the neighbouring contract.
• anti-ai-slop during production.
• ai-slop-audit at the release checkpoint.

References

• Anti-AI slop production gate
• Current-source register
• Legal, privacy and market release gate
• Follow the directly linked repository skills above and any domain references named in the core sections below. Verify current platform, price, legal and regulatory claims before use.

Required Inputs

Ask for the following before generating any deliverable:

1. Client business name
2. Industry
3. Country / city (defaults to Uganda / East Africa)
4. Primary goal (e.g. achieve DPPA compliance, configure GA4 privacy settings, set up cookie consent)
5. Website platform (WordPress, Wix, Squarespace, custom-built — affects consent banner implementation)
6. Audience geography (Uganda only; Uganda + Kenya; Uganda + international including EU — determines which frameworks apply)
7. GA4 access level (Admin required for privacy configuration changes)
8. Data currently collected (list all tracking pixels, analytics tools, and third-party tags active on the website)

Why Analytics Privacy Matters in EA

Uganda's Data Protection and Privacy Act 2019 (DPPA) and Kenya's Data Protection Act 2019 (DPA) both require informed consent before collecting personal data — including analytics data linked to individual users. Non-compliance carries financial penalties and significant reputational risk.

For clients with international audiences (e-commerce, NGOs, professional services exporting to EU markets), GDPR (EU, 2018) and CCPA (California, USA) may additionally apply.

This skill provides implementation guidance only. For specific legal advice, data protection impact assessments, or drafting of a privacy policy, refer the client to a qualified data protection lawyer in their jurisdiction.

Regulatory Framework Summary

GDPR applicability test: Does the client's website accept payments or enquiries from EU residents? If yes, GDPR applies — escalate to a data protection lawyer before proceeding.

Cookie Consent Implementation

All websites collecting analytics data must display a cookie consent banner that:

1. Appears before any tracking cookies are set — not after the page loads with cookies already active
2. Explains what data is collected and why — in plain language, not legal boilerplate
3. Provides a genuine opt-out — a real "Reject all" button, not a dark pattern that buries the opt-out
4. Remembers the user's choice — for a minimum of 12 months
5. Distinguishes cookie categories — at minimum: Necessary (no consent required) vs. Analytics (consent required) vs. Marketing (consent required)

Recommended tools for EA clients:

• CookieYes — free tier available; integrates with WordPress, Wix, and custom sites; generates a consent log
• Usercentrics — more robust for GDPR requirements; paid but affordable
• Custom implementation — acceptable if the client has a developer and the implementation meets all five requirements above

Dark patterns to avoid: Pre-ticked "Accept" boxes; hiding the "Reject" option in small text; making "Accept all" one click and "Manage preferences" three clicks. Dark patterns are explicitly prohibited under GDPR and are increasingly scrutinised under DPPA.

GA4 Privacy Configuration

Complete these steps in order. All require Admin access in GA4.

Step 1 — Data Retention Admin → Data Settings → Data Retention Set to 14 months maximum. This reduces the volume of personal data retained and is the minimum recommended setting for DPPA/GDPR alignment.

Step 2 — Google Signals Admin → Data Settings → Data Collection → Google Signals Disable Google Signals unless the client has a specific, documented need for cross-device tracking. Google Signals links analytics data to Google Account profiles — this is personal data linkage that requires explicit consent.

Step 3 — IP Anonymisation Admin → Data Streams → [select stream] → Configure tag settings → Show all → Redact visitor IP addresses Enable this setting. It masks the user's location to city level only — the user's precise IP address is not stored. This is recommended for all clients regardless of regulatory framework.

Step 4 — Consent Mode Configuration Configure GA4 consent mode so the tag fires in "consent pending" state by default and only collects full analytics data after the user grants consent via the cookie banner. This requires integration between the consent management platform (CookieYes or equivalent) and the GA4 tag via Google Tag Manager.

Step 5 — Data Deletion Requests Admin → Data Deletion Document the process for responding to a user's right-to-erasure request. Under DPPA 2019, the client must be able to delete an individual user's data within a reasonable timeframe. In GA4, use the Data Deletion tool to remove data associated with a specific user identifier.

Data Minimisation Principle

Collect only the data necessary for the stated analytics purpose. Before adding any tracking pixel, custom dimension, or third-party tag to a client's website, document:

1. What data this collects — list every data point captured
2. Why it is needed — the specific analytics or business purpose it serves
3. How long it will be retained — the retention period before deletion or anonymisation
4. Who has access — which internal and external parties can view this data

This documentation is both an ethical and legal requirement under DPPA 2019. Maintain it in a simple data register (a Google Sheet is sufficient for most EA clients).

Audit prompt: Review all active tags in Google Tag Manager. Remove any tag that has not been used in the past 90 days or whose purpose cannot be clearly stated.

WhatsApp and Social Media Data Governance

WhatsApp Business does not provide personal analytics data about individual users. However, client-side records — broadcast lists, contact databases, conversation histories — constitute personal data under DPPA 2019.

Advise clients to:

1. Document the data: Maintain a record of all WhatsApp contacts — name, number, source of contact, consent basis, date added
2. Honour opt-out requests within 48 hours: If a contact asks to be removed from a broadcast list, remove them immediately and confirm removal
3. Do not share contact data with third parties without documented consent from each individual contact
4. Store contact data securely: WhatsApp contact lists exported to spreadsheets must be stored in access-controlled files (Google Drive with restricted sharing), not in unsecured email attachments

Social media data note: Facebook, Instagram, and TikTok analytics dashboards provide aggregate data only — they do not expose individual user personal data to page administrators. No additional consent is required for using native platform analytics. However, installing the Meta Pixel on a website does constitute personal data collection and requires cookie consent.

International Framework Escalation

If any of the following conditions apply, pause implementation and refer the client to a qualified data protection lawyer before proceeding:

• The client's website serves EU residents and currently has no GDPR-compliant consent mechanism
• The client collects and stores health, financial, or biometric data of any kind
• The client is a public institution or processes data on behalf of government bodies
• The client has experienced a data breach in the past 12 months
• The client operates in multiple East African jurisdictions with different regulatory frameworks

Quality Criteria

Output meets the standard for this skill if:

• The applicable regulatory frameworks (DPPA, DPA, GDPR, CCPA) are identified based on the client's audience geography before any implementation guidance is given
• All five GA4 privacy configuration steps are included and sequenced correctly
• Cookie consent implementation meets the five requirements: pre-load, plain language, genuine opt-out, remembered choice, and category distinction
• The data minimisation principle is applied — a documentation requirement is included, not just a configuration checklist
• WhatsApp contact data is addressed as personal data subject to DPPA 2019
• Legal referral triggers are clearly stated — the skill does not overreach into legal advice
• Language is British English throughout; imperative in all instructional sections