analyst-user-profiling

Manage Braze user identity, attributes, and SDK data governance.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/delta-and-beta/braze-agency --skill analyst-user-profiling
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyst-user-profiling
Source: https://github.com/delta-and-beta/braze-agency/tree/main/skills/analyst-user-profiling
Command: npx skills add https://github.com/delta-and-beta/braze-agency --skill analyst-user-profiling

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Establishes reliable user identification, safe attribute management, and privacy-first SDK data controls so teams can target and analyze users without over-collecting or exposing sensitive information.

Core Features & Use Cases

  • User identity: Guidance for assigning stable external_id values, handling anonymous profiles, and using aliases for cross-system stitching.
  • Attribute management: Rules for standard vs custom attributes, supported types, array operations, increment semantics, and unset/expiry patterns.
  • Data governance: SDK initialization and opt-out strategies, wipe and deletion workflows, consent timestamping, and a decision framework to minimize collection.
  • Use Case: Audit an existing Braze integration to produce a remediation plan that replaces email-as-ID, prunes unnecessary attributes, and implements consent-gated initialization.

Quick Start

Audit the integration to produce a prioritized plan for assigning stable external_id values, removing PII from attributes, and implementing consent-gated SDK initialization.

Frequently Asked Questions about analyst-user-profiling

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I assign Braze external_id values correctly and avoid using email as an identifier?

Assigning a stable Braze external_id requires generating a unique, non-PII identifier per user upon first login. Using email as an ID creates profile fragmentation when emails change; this Skill provides remediation strategies to replace email-as-ID with stable identifiers and anonymous profile stitching.

What's the best way to configure Braze SDK data governance and consent-gated initialization?

Braze SDK data governance is configured by gating initialization behind explicit user consent opt-ins. This Skill outlines consent timestamping, opt-out strategies, and initialization workflows to ensure data collection only begins after receiving valid user permission across web and mobile environments.

How do I implement GDPR and CCPA data deletion workflows using Braze wipeData?

GDPR and CCPA deletion workflows utilize the Braze wipeData functionality to clear SDK-stored user data locally. This Skill guides implementing wipe behavior and server-side deletion requests to ensure full compliance with privacy regulations across web, mobile, and server environments.

What are the supported Braze custom attribute types and array update semantics?

Supported Braze custom attribute types include strings, numbers, booleans, dates, and arrays. This Skill defines rules for array operations, increment semantics, and unset or expiry patterns to ensure attributes are updated correctly without storing raw PII or sensitive inferences.

How do I use Braze aliases for cross-system user identity stitching?

Braze aliases stitch cross-system user identities by mapping external system identifiers to anonymous Braze profiles. This Skill provides guidance on alias configuration to merge fragmented profiles safely before assigning a stable external_id.

Can I audit an existing Braze integration to remove PII from custom attributes?

Auditing an existing Braze integration identifies raw PII exposure within custom attributes and produces a prioritized remediation plan. This Skill helps prunes unnecessary attributes, replaces unsafe identifiers, and implements consent-gated SDK initialization to minimize data risk.