analyst-data-management

Audit and govern Braze data lifecycles across campaigns, canvases, and segments.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Braze data flows often span multiple sources and tools, creating governance gaps around dispatch tracking, data types, and analytics partnerships. This skill provides structured guidance for auditing, standardizing, and hardening Braze data operations.

Core Features & Use Cases

  • Dispatch tracking governance across campaigns, canvases, and message events.
  • Change management for custom data types to maintain segmentation and reporting accuracy.
  • Blocklisting vs deletion workflows to safely retire data while preserving historical context.
  • Cross-source attribute resolution to align identifiers across Liquid, REST API, and Currents.
  • Analytics partner integration guidance for Currents exports and downstream analytics workflows.

Quick Start

Load the skill to begin auditing Braze data flows, implement governance, and connect analytics partners.

Frequently Asked Questions about analyst-data-management

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

FAQPage Schema
What is the best way to govern Braze data lifecycles across campaigns and canvases?

Braze data lifecycle governance involves auditing dispatch tracking, custom data types, and partner integrations to maintain reporting accuracy and data hygiene across campaigns, canvases, and segments.

How do I resolve cross-source attribute identifiers across Liquid and the REST API?

Cross-source attribute resolution aligns identifiers across Liquid, REST API, and Currents by standardizing custom data types and implementing structured governance workflows for accurate segmentation.

When should I use blocklisting versus deletion for retiring Braze custom attributes?

Blocklisting should be used instead of deletion when you need to safely retire Braze custom attributes while preserving historical context for past analytics and reporting accuracy.

How do I validate analytics partner integrations using Braze Currents exports?

Analytics partner integration validation uses Braze Currents exports to connect downstream analytics workflows, ensuring cross-source data flows and partner integrations are correctly configured and audited.

Does implementing change management for custom data types affect existing Braze segmentation?

Change management for custom data types directly affects Braze segmentation by standardizing attribute governance, preventing segmentation errors, and maintaining reporting accuracy across campaigns.