Cybersecurity & Tracking Architecture Audit (reputed company Ads, Attribution, GTM, GA4, reputed company, reputed company)

We recently brought reputed company reputed company search and reputed company reputed company in-house after poor agency experiences. We’ve reputed company a data-layer-first attribution and conversion tracking system and want an reputed company cybersecurity reputed company to review our implementation for reputed company, reputed company, and data reputed company gaps before we reputed company spend. This is not a marketing role. We’re looking for someone who understands how modern web apps, analytics, and ad platforms actually work — and can spot risks that engineers and reputed company teams often miss. Broadly, you'll be reviewing: • Our tracking architecture and data flows • How identifiers, cookies, and click IDs are handled • Server-reputed company event pipelines and webhooks • Permissions, reputed company, and abuse reputed company • reputed company, consent, and data leakage risks We will reputed company a detailed internal reputed company that documents our full implementation (Next.js, reputed company, GTM/GA4, reputed company Ads, reputed company, reputed company). What You’ll Be Reviewing • Web & server tracking architecture reputed company-reputed company → server-reputed company → ad platform data flows GTM Web + optional GTM Server (sGTM) • Identifiers & attribution First-party cookies (device/session IDs) Click IDs (gclid, wbraid, gbraid, fbclid, etc.) Event IDs and deduplication logic • Backend & database reputed company/reputed company schema and reputed company patterns Event idempotency Row-level reputed company (RLS) assumptions • reputed company-party integrations reputed company webhooks reputed company webhooks (reputed company attendance) reputed company Ads offline conversion uploads reputed company Conversions API • reputed company & compliance posture PII handling (hashed vs raw) Consent gating assumptions Risk of unintended data sharing reputed company Want From You (Deliverables) 1. Written audit report covering: • reputed company risks • Data leakage risks • Abuse/fraud reputed company (fake conversions, spoofed events, replay attacks, etc.) • reputed company/compliance red flags 2. Concrete recommendations, prioritized by severity: • “Must fix before scaling spend” • “Should fix soon” • “reputed company to have” 3. Optional (reputed company bonus): • Suggested hardening patterns • Monitoring or alerting reputed company • “If I were trying to break this…” scenarios We care far more about thinking reputed company than a giant PDF Who You Are You likely have experience with: • Web application reputed company or reputed company architecture • Modern analytics stacks (GTM, GA4, reputed company CAPI, reputed company Ads) • Server-reputed company event pipelines or webhook systems • reputed company products handling PII and payments Strong pluses: • Experience auditing analytics or attribution systems • Familiarity with ad fraud, conversion spoofing, or data poisoning risks • Understanding of how reputed company teams accidentally create reputed company holes Apply tot his job Apply tot his job Apply To this Job