sinapse-ai 1.0.0

package/squad-growth/tasks/create-topic-cluster-map.md

@@ -0,0 +1,106 @@
+---
+task: create-topic-cluster-map
+responsavel: "@ga-seo-strategist"
+responsavel_type: Agent
+atomic_layer: Task
+elicit: false
+
+Entrada:
+  - campo: context
+    tipo: object
+    origem: "workflow ou manual"
+    obrigatorio: true
+
+Saida:
+  - campo: resultado
+    tipo: document
+    destino: "stakeholders"
+
+Checklist:
+  - "[ ] Validar inputs e pre-condicoes"
+  - "[ ] Executar steps conforme documentado"
+  - "[ ] Verificar criterios de qualidade"
+  - "[ ] Gerar output no formato especificado"
+---
+
+# Task: Create Topic Cluster Map
+
+## Metadata
+- **Squad:** squad-growth
+- **Agent:** Rank (ga-seo-strategist)
+- **Complexity:** Standard
+
+## Objetivo
+Criar mapa de topic clusters — organizar conteudo em pillar pages e cluster content com internal linking estrategico para dominar topicos no Google.
+
+## Entrada
+- Keyword strategy
+- Existing content audit
+- Business topics
+- Competitor content analysis
+
+## Passos
+
+### 1. Topic Cluster Model
+```
+        ┌─── Cluster Article 1
+        │
+Pillar ─┼─── Cluster Article 2
+ Page   │
+        ├─── Cluster Article 3
+        │
+        └─── Cluster Article 4
+
+Each cluster article links back to pillar page.
+Pillar page links out to all cluster articles.
+```
+
+### 2. Cluster Definition Template
+| Campo | Descricao |
+|-------|----------|
+| Cluster name | Topic area |
+| Pillar page | Comprehensive guide (2000-5000 words) |
+| Pillar keyword | Head term (high volume, high KD) |
+| Cluster articles | Supporting content (800-2000 words each) |
+| Cluster keywords | Long-tail, related terms |
+| Internal links | Bidirectional linking plan |
+| Content gap | Articles to create |
+
+### 3. Topic Clusters Map
+| Cluster | Pillar Keyword | Vol | Pillar Page | Cluster Articles (count) | Status |
+|---------|---------------|-----|------------|------------------------|--------|
+| Topic A | | | /guides/topic-a | 8 articles | Planning |
+| Topic B | | | /guides/topic-b | 6 articles | Existing |
+| Topic C | | | /guides/topic-c | 10 articles | Partial |
+
+### 4. Internal Linking Strategy
+| Regra | Descricao |
+|-------|----------|
+| Cluster → Pillar | Every cluster article links to its pillar |
+| Pillar → Cluster | Pillar page links to all cluster articles |
+| Cross-cluster | Related clusters link to each other (sparingly) |
+| Anchor text | Descriptive, keyword-relevant (not "click here") |
+| Link placement | In-content, contextual (not just footer/sidebar) |
+| Max links/page | 3-5 internal links per 1000 words |
+
+### 5. Content Gap Analysis
+| Cluster | Existing Articles | Needed Articles | Gap | Priority |
+|---------|-----------------|----------------|-----|---------|
+| Topic A | 3 | 8 | 5 new | P1 |
+| Topic B | 6 | 6 | 0 (optimize) | P3 |
+| Topic C | 2 | 10 | 8 new | P2 |
+
+## Saida
+- Topic cluster map (visual)
+- Cluster definitions
+- Internal linking strategy
+- Content gap analysis
+- Content creation roadmap
+
+## Validacao
+- [ ] Clusters definidos com pillar + cluster articles
+- [ ] Keywords mapeados por cluster
+- [ ] Internal linking strategy documentada
+- [ ] Content gaps identificados
+- [ ] Prioridades de criacao definidas
+- [ ] Handoff para squad-content

package/squad-growth/tasks/create-tracking-plan.md

@@ -0,0 +1,127 @@
+---
+task: create-tracking-plan
+responsavel: "@ga-analytics-engineer"
+responsavel_type: Agent
+atomic_layer: Task
+elicit: false
+
+Entrada:
+  - campo: context
+    tipo: object
+    origem: "workflow ou manual"
+    obrigatorio: true
+
+Saida:
+  - campo: resultado
+    tipo: document
+    destino: "stakeholders"
+
+Checklist:
+  - "[ ] Validar inputs e pre-condicoes"
+  - "[ ] Executar steps conforme documentado"
+  - "[ ] Verificar criterios de qualidade"
+  - "[ ] Gerar output no formato especificado"
+---
+
+# Task: Create Tracking Plan
+
+## Metadata
+- **Squad:** squad-growth
+- **Agent:** Signal (ga-analytics-engineer)
+- **Complexity:** Complex
+
+## Objetivo
+Criar tracking plan completo — documento de referencia que mapeia cada evento, seus parametros, triggers, destinations e responsaveis de implementacao.
+
+## Entrada
+- Event taxonomy
+- User journeys
+- Product features
+- Analytics requirements
+
+## Passos
+
+### 1. Tracking Plan Structure
+| Coluna | Descricao |
+|--------|----------|
+| Event Name | Nome do evento (snake_case) |
+| Category | Categoria do evento |
+| Trigger | O que dispara o evento |
+| Parameters | Parametros enviados |
+| Platform | Web, iOS, Android, All |
+| Destination | GA4, Segment, Amplitude, etc. |
+| Priority | P0 (critical) → P3 (nice-to-have) |
+| Owner | Time responsavel pela implementacao |
+| Status | Not started, In progress, QA, Live |
+
+### 2. Tracking Plan Template
+| Event | Category | Trigger | Parameters | Platform | Dest | Priority | Status |
+|-------|----------|---------|-----------|----------|------|---------|--------|
+| page_view | navigation | Page load | page_path, page_title, referrer | All | GA4 | P0 | |
+| sign_up | auth | Registration complete | method, source | All | GA4, Segment | P0 | |
+| login | auth | Login success | method | All | GA4 | P0 | |
+| button_click | engagement | CTA click | button_text, button_location, destination_url | All | GA4 | P1 | |
+| form_submit | forms | Form submission | form_name, form_id, fields_count | Web | GA4 | P0 | |
+| purchase | ecommerce | Transaction complete | transaction_id, value, currency, items | All | GA4, Segment | P0 | |
+| search | engagement | Search executed | search_term, results_count | All | GA4 | P1 | |
+| error | system | Error occurs | error_type, error_message, page_path | All | GA4, Sentry | P1 | |
+
+### 3. Parameter Specification per Event
+```yaml
+events:
+  - name: purchase
+    category: ecommerce
+    trigger: "Order confirmation page loaded"
+    parameters:
+      required:
+        - name: transaction_id
+          type: string
+          description: "Unique transaction identifier"
+          example: "TXN-2026-001"
+        - name: value
+          type: number
+          description: "Total transaction value"
+          example: 199.90
+        - name: currency
+          type: string
+          description: "ISO 4217 currency code"
+          example: "BRL"
+        - name: items
+          type: array
+          description: "Array of purchased items"
+      optional:
+        - name: coupon
+          type: string
+          description: "Coupon code used"
+        - name: payment_method
+          type: string
+          description: "Payment method"
+          enum: ["credit_card", "pix", "boleto"]
+    destinations: [GA4, Segment, BigQuery]
+    platform: All
+    priority: P0
+```
+
+### 4. Implementation Handoff
+| Step | Responsavel | Deliverable |
+|------|-----------|------------|
+| 1. Spec approval | Signal + Stakeholders | Approved tracking plan |
+| 2. Data layer spec | Signal | dataLayer push specifications |
+| 3. Frontend implementation | squad-design | Events firing in code |
+| 4. GTM configuration | Signal | Tags, triggers, variables |
+| 5. QA verification | Signal | Tracking accuracy report |
+| 6. Go-live | Signal | Production deployment |
+
+## Saida
+- Complete tracking plan spreadsheet/document
+- Parameter specifications per event
+- Implementation handoff guide
+- QA test cases
+
+## Validacao
+- [ ] Todos os user flows cobertos com eventos
+- [ ] Parametros especificados com tipos e exemplos
+- [ ] Prioridades P0-P3 atribuidas
+- [ ] Destinations definidos por evento
+- [ ] Implementation handoff claro
+- [ ] QA test cases para cada evento critico

package/squad-growth/tasks/define-event-taxonomy.md

@@ -0,0 +1,132 @@
+---
+task: define-event-taxonomy
+responsavel: "@ga-analytics-engineer"
+responsavel_type: Agent
+atomic_layer: Task
+elicit: false
+
+Entrada:
+  - campo: context
+    tipo: object
+    origem: "workflow ou manual"
+    obrigatorio: true
+
+Saida:
+  - campo: resultado
+    tipo: document
+    destino: "stakeholders"
+
+Checklist:
+  - "[ ] Validar inputs e pre-condicoes"
+  - "[ ] Executar steps conforme documentado"
+  - "[ ] Verificar criterios de qualidade"
+  - "[ ] Gerar output no formato especificado"
+---
+
+# Task: Define Event Taxonomy
+
+## Metadata
+- **Squad:** squad-growth
+- **Agent:** Signal (ga-analytics-engineer)
+- **Complexity:** Complex
+
+## Objetivo
+Definir taxonomia de eventos completa — naming conventions, event schema, categorias e hierarquia para garantir consistencia e usabilidade dos dados.
+
+## Entrada
+- User journeys and flows
+- Business KPIs
+- AARRR funnel mapping
+- Product feature inventory
+
+## Passos
+
+### 1. Naming Convention
+| Regra | Padrao | Exemplo |
+|-------|--------|---------|
+| Format | snake_case | `button_click` |
+| Structure | object_action | `form_submit`, `video_play` |
+| Max length | 40 chars | Descritivo mas conciso |
+| Prefix (optional) | category_ | `ecommerce_purchase` |
+| No spaces | _ separator | `sign_up` nao `sign up` |
+| No special chars | alphanumeric + _ | Nenhum #, @, - |
+
+### 2. Event Categories
+| Categoria | Eventos Tipicos | Prioridade |
+|-----------|----------------|-----------|
+| Navigation | page_view, screen_view, tab_change | P0 |
+| Engagement | scroll, click, hover, focus | P1 |
+| Forms | form_start, field_fill, form_submit, form_error | P0 |
+| Authentication | sign_up, login, logout, password_reset | P0 |
+| E-commerce | add_to_cart, begin_checkout, purchase, refund | P0 |
+| Content | content_view, content_share, content_save | P1 |
+| Search | search, search_results, search_click | P1 |
+| Media | video_play, video_pause, video_complete | P2 |
+| Social | share, like, comment, follow | P2 |
+| System | error, notification_receive, permission_grant | P1 |
+
+### 3. Event Schema Standard
+```json
+{
+  "event_name": "form_submit",
+  "event_category": "forms",
+  "event_params": {
+    "form_name": "contact_form",
+    "form_id": "contact-main",
+    "form_location": "homepage_bottom",
+    "fields_filled": 5,
+    "time_to_complete_ms": 45000,
+    "has_errors": false
+  },
+  "user_properties": {
+    "user_id": "hashed_id",
+    "user_type": "prospect",
+    "account_age_days": 0
+  },
+  "context": {
+    "page_path": "/contact",
+    "page_title": "Contact Us",
+    "referrer": "https://google.com",
+    "device_category": "mobile",
+    "session_id": "abc123"
+  }
+}
+```
+
+### 4. Parameter Standards
+| Tipo | Convencao | Exemplo |
+|------|----------|---------|
+| Strings | snake_case, lowercase | `form_name: "contact_form"` |
+| Booleans | is_ ou has_ prefix | `is_logged_in: true` |
+| Numbers | No prefix, numeric | `items_count: 3` |
+| Currency | ISO + value | `currency: "BRL", value: 99.90` |
+| IDs | hashed, never PII | `user_id: "sha256_hash"` |
+| Timestamps | ISO 8601 | `event_time: "2026-03-12T10:30:00Z"` |
+| Lists | _list suffix | `categories_list: ["shoes", "running"]` |
+
+### 5. GA4 Event Mapping
+| Custom Event | GA4 Recommended? | Notes |
+|-------------|-----------------|-------|
+| page_view | Yes (automatic) | Enhanced with custom params |
+| sign_up | Yes (recommended) | Add method param |
+| login | Yes (recommended) | Add method param |
+| purchase | Yes (recommended) | Required e-commerce params |
+| add_to_cart | Yes (recommended) | Items array required |
+| search | Yes (recommended) | search_term param |
+| share | Yes (recommended) | method, content_type params |
+| Custom events | No | Follow naming convention |
+
+## Saida
+- Event taxonomy document
+- Naming convention guide
+- Event schema with examples
+- GA4 event mapping
+- Parameter standards reference
+
+## Validacao
+- [ ] Naming convention definida e documentada
+- [ ] Todas as categorias de eventos cobertos
+- [ ] Event schema com exemplos por categoria
+- [ ] GA4 recommended events mapeados
+- [ ] Parameter standards sem PII
+- [ ] Taxonomia revisada por stakeholders

package/squad-growth/tasks/define-north-star-metric.md

@@ -0,0 +1,159 @@
+---
+task: define-north-star-metric
+responsavel: "@ga-growth-hacker"
+responsavel_type: Agent
+atomic_layer: Task
+elicit: false
+
+Entrada:
+  - campo: context
+    tipo: object
+    origem: "workflow ou manual"
+    obrigatorio: true
+
+Saida:
+  - campo: resultado
+    tipo: document
+    destino: "stakeholders"
+
+Checklist:
+  - "[ ] Validar inputs e pre-condicoes"
+  - "[ ] Executar steps conforme documentado"
+  - "[ ] Verificar criterios de qualidade"
+  - "[ ] Gerar output no formato especificado"
+---
+
+# Task: Define North Star Metric
+
+## Metadata
+- **Squad:** squad-growth
+- **Agent:** Lever (ga-growth-hacker)
+- **Complexity:** Standard
+
+## Objetivo
+Definir North Star Metric — identificar a metrica unica que melhor captura o core value entregue aos clientes e serve como bussola de alinhamento para todas as equipes e decisoes de growth.
+
+## Entrada
+- Business model
+- Product value proposition
+- Current KPIs
+- Customer success definition
+
+## Passos
+
+### 1. North Star Metric Criteria
+| Criterio | Descricao | Peso |
+|----------|----------|------|
+| Value-driven | Reflete valor entregue ao cliente | Essencial |
+| Leading indicator | Prediz revenue/growth futura | Essencial |
+| Actionable | Times podem influenciar diretamente | Essencial |
+| Measurable | Pode ser medida com precisao | Essencial |
+| Understandable | Toda a empresa entende | Importante |
+| Non-gameable | Dificil de manipular artificialmente | Importante |
+| Timely | Muda rapido o suficiente para feedback | Importante |
+
+### 2. North Star por Tipo de Negocio
+| Modelo | North Star Metric | Exemplos Reais |
+|--------|------------------|---------------|
+| SaaS B2B | Weekly Active Teams using core feature | Slack: Messages sent |
+| SaaS B2C | Daily Active Users performing key action | Spotify: Time spent listening |
+| E-commerce | Weekly purchases from repeat customers | Amazon: Purchase frequency |
+| Marketplace | Weekly transactions completed | Airbnb: Nights booked |
+| Content/Media | Daily engaged reading time | Medium: Total reading time |
+| Ad-supported | Daily Active Users × Engagement time | Facebook: DAU |
+| Freemium | Free-to-Paid conversion within 30 days | Dropbox: Files synced |
+| Fintech | Weekly active transacting users | Nubank: Monthly transactions |
+| Gaming | Daily Active Users × Session length | Any game: DAU + time |
+
+### 3. North Star Discovery Process
+| Step | Atividade | Output |
+|------|----------|--------|
+| 1 | Map value moments | Lista de "aha moments" por persona |
+| 2 | Correlate with retention | Qual acao prediz retencao D30+? |
+| 3 | Correlate with revenue | Qual acao prediz revenue growth? |
+| 4 | Candidate selection | 3-5 metricas candidatas |
+| 5 | Validation | Testar correlacao estatistica |
+| 6 | Team alignment | Apresentar e alinhar com lideranca |
+| 7 | Instrumentation | Implementar tracking confiavel |
+
+### 4. North Star Validation
+| Teste | Metodo | Criterio de Aprovacao |
+|-------|--------|---------------------|
+| Correlation with revenue | Pearson/Spearman correlation | r > 0.7 |
+| Leading indicator test | Granger causality | p < 0.05 |
+| Team alignment test | Survey all team leads | > 80% agree |
+| Actionability test | Can teams define experiments to improve it? | Yes |
+| Anti-gaming test | Can it be artificially inflated without value? | No |
+
+### 5. Input Metrics (Drivers)
+```
+North Star Metric: [Definir]
+    │
+    ├── Input 1: [Reach/Acquisition]
+    │   What: Number of users exposed
+    │   Owner: Marketing
+    │
+    ├── Input 2: [Activation]
+    │   What: % reaching aha moment
+    │   Owner: Product
+    │
+    ├── Input 3: [Engagement Depth]
+    │   What: Frequency/intensity of usage
+    │   Owner: Product
+    │
+    └── Input 4: [Retention]
+        What: Users continuing to derive value
+        Owner: Product + CS
+```
+
+### 6. Counter-Metrics
+| North Star | Counter-Metric | Por que |
+|-----------|---------------|---------|
+| DAU | Revenue per user | Evita crescimento sem monetizacao |
+| Revenue | Customer satisfaction (NPS) | Evita short-term revenue extraction |
+| Transactions | Customer support tickets | Evita volume sem qualidade |
+| Signups | Activation rate | Evita vanity signups |
+| Time in app | Task completion rate | Evita engagement sem valor |
+
+### 7. Communication Template
+```
+OUR NORTH STAR METRIC
+
+[Metric Name]: [Definition in plain language]
+
+WHY THIS METRIC:
+- It reflects the core value we deliver: [explanation]
+- It correlates with [revenue/retention/growth] (r = X.XX)
+- Every team can influence it through their work
+
+CURRENT STATE:
+- Current value: [X]
+- 90-day trend: [up/down/flat]
+- Target (6 months): [Y]
+
+HOW EACH TEAM CONTRIBUTES:
+- Marketing: Drive [input 1]
+- Product: Improve [input 2] and [input 3]
+- Engineering: Enable [supporting metric]
+- Customer Success: Maintain [input 4]
+
+COUNTER-METRIC:
+We also track [counter-metric] to ensure healthy growth.
+```
+
+## Saida
+- North Star Metric definition
+- Validation evidence (correlations)
+- Input metrics framework
+- Counter-metric selection
+- Communication document
+- Tracking implementation plan
+
+## Validacao
+- [ ] NSM atende todos os 7 criterios
+- [ ] Correlacao com revenue validada (r > 0.7)
+- [ ] Input metrics definidos com owners
+- [ ] Counter-metric selecionado
+- [ ] Lideranca alinhada (> 80% concordancia)
+- [ ] Tracking implementado e confiavel
+- [ ] Communication template distribuido

package/squad-growth/tasks/define-utm-strategy.md

@@ -0,0 +1,170 @@
+---
+task: define-utm-strategy
+responsavel: "@ga-campaign-analyst"
+responsavel_type: Agent
+atomic_layer: Task
+elicit: false
+
+Entrada:
+  - campo: context
+    tipo: object
+    origem: "workflow ou manual"
+    obrigatorio: true
+
+Saida:
+  - campo: resultado
+    tipo: document
+    destino: "stakeholders"
+
+Checklist:
+  - "[ ] Validar inputs e pre-condicoes"
+  - "[ ] Executar steps conforme documentado"
+  - "[ ] Verificar criterios de qualidade"
+  - "[ ] Gerar output no formato especificado"
+---
+
+# Task: Define UTM Strategy
+
+## Metadata
+- **Squad:** squad-growth
+- **Agent:** Pulse (ga-campaign-analyst)
+- **Complexity:** Standard
+
+## Objetivo
+Definir estrategia de UTM — criar taxonomia padronizada de UTM parameters para garantir atribuicao precisa de trafego, consistencia entre canais e confiabilidade dos dados de campanha.
+
+## Entrada
+- Marketing channels in use
+- Campaign naming conventions (current)
+- Analytics platform (GA4)
+- Team structure (who creates campaigns)
+
+## Passos
+
+### 1. UTM Parameters Reference
+| Parametro | Obrigatorio | Descricao | Exemplo |
+|----------|-----------|----------|---------|
+| utm_source | Sim | Plataforma/site de origem | google, facebook, newsletter |
+| utm_medium | Sim | Tipo de canal/trafego | cpc, social, email, referral |
+| utm_campaign | Sim | Nome da campanha especifica | black-friday-2026, product-launch |
+| utm_term | Nao | Keyword (paid search) | running-shoes, crm-software |
+| utm_content | Nao | Variante/creative | hero-banner-v2, cta-red |
+
+### 2. Naming Convention Standards
+| Regra | Padrao | Exemplo |
+|-------|--------|---------|
+| Case | Sempre lowercase | `google` nao `Google` |
+| Separador | Hifens entre palavras | `black-friday` nao `black_friday` |
+| Espacos | Nunca usar espacos | `email-newsletter` nao `email newsletter` |
+| Acentos | Nunca usar acentos | `promocao` nao `promoção` |
+| Abreviacoes | Usar lista padronizada | `fb` para Facebook, `gg` para Google |
+| Datas | YYYYMM quando relevante | `202611` para Nov 2026 |
+| Idioma | Ingles para parametros | Consistencia global |
+
+### 3. UTM Taxonomy
+**utm_source (padronizado):**
+| Valor | Plataforma |
+|-------|-----------|
+| google | Google (all products) |
+| facebook | Facebook (Meta) |
+| instagram | Instagram |
+| linkedin | LinkedIn |
+| twitter | X (Twitter) |
+| youtube | YouTube |
+| tiktok | TikTok |
+| newsletter | Email newsletter |
+| partner-{name} | Partner referral |
+| direct-mail | Direct mail |
+
+**utm_medium (padronizado):**
+| Valor | Tipo de Trafego | GA4 Channel Group |
+|-------|----------------|------------------|
+| cpc | Paid search | Paid Search |
+| paid-social | Paid social | Paid Social |
+| display | Display advertising | Display |
+| video | Video advertising | Video |
+| email | Email marketing | Email |
+| organic-social | Organic social posts | Organic Social |
+| referral | Partner/affiliate | Referral |
+| affiliate | Affiliate program | Affiliates |
+| sms | SMS marketing | SMS |
+| push | Push notifications | Push |
+
+**utm_campaign (formato):**
+```
+{objective}-{audience}-{offer}-{date}
+
+Exemplos:
+- awareness-prospecting-brand-202603
+- conversion-retargeting-30off-202611
+- retention-existing-loyalty-202604
+- launch-all-newproduct-202607
+```
+
+### 4. UTM Builder Template
+| Campo | Valor | Notas |
+|-------|-------|-------|
+| Base URL | https://example.com/page | Sem trailing slash |
+| utm_source | | Da lista padronizada |
+| utm_medium | | Da lista padronizada |
+| utm_campaign | | Formato: obj-audience-offer-date |
+| utm_term | | Opcional: keyword |
+| utm_content | | Opcional: creative variant |
+| **URL Final** | | Auto-gerada |
+
+### 5. Common Mistakes & Prevention
+| Erro | Problema | Prevencao |
+|------|---------|----------|
+| Inconsistent casing | google vs Google vs GOOGLE | Enforce lowercase |
+| Missing parameters | Trafego cai em (direct)/(none) | UTM builder obrigatorio |
+| Duplicate naming | Mesma campanha com nomes diferentes | Central naming doc |
+| Internal links com UTM | Sobrescreve source original | Nunca usar UTM em links internos |
+| UTM em links organicos | Perde organic attribution | UTM apenas para paid/owned |
+| Spaces in values | Broken URLs | URL encode ou hifens |
+
+### 6. UTM Governance Process
+| Acao | Responsavel | Ferramenta |
+|------|-----------|-----------|
+| Create UTM | Marketing team | UTM Builder (sheet/tool) |
+| Validate UTM | Campaign manager | Automated validation |
+| Central registry | Analytics team | Shared spreadsheet/database |
+| Audit monthly | Analytics team | GA4 source/medium report |
+| Training | Analytics team | Quarterly session |
+
+### 7. GA4 Channel Group Mapping
+| Default Channel Group | utm_source + utm_medium Rules |
+|----------------------|------------------------------|
+| Organic Search | source matches search engine, medium = organic |
+| Paid Search | medium matches `^(cpc|ppc|paid.search)$` |
+| Paid Social | medium matches `^(paid.social|paidsocial)$` |
+| Email | medium = email |
+| Display | medium = display |
+| Affiliates | medium = affiliate |
+| Direct | source = (direct), medium = (none) |
+
+*Custom channel groups podem ser criados em GA4 Admin > Channel Groups.*
+
+### 8. UTM Audit Checklist
+| Check | Metodo | Frequencia |
+|-------|--------|-----------|
+| Unknown sources | GA4: source/medium = (not set) | Weekly |
+| Inconsistent naming | GA4: source report, check variants | Monthly |
+| Missing campaigns | Active campaigns without UTM data | Monthly |
+| Internal UTM usage | Check for UTM on same-domain links | Monthly |
+| Channel group accuracy | GA4 default vs expected grouping | Monthly |
+
+## Saida
+- UTM naming convention document
+- UTM taxonomy (source, medium, campaign values)
+- UTM builder tool/template
+- Governance process
+- Audit checklist
+
+## Validacao
+- [ ] 5 UTM parameters documentados com exemplos
+- [ ] Naming conventions padronizadas
+- [ ] Taxonomia de source/medium completa
+- [ ] Campaign naming format definido
+- [ ] UTM builder disponivel para equipe
+- [ ] Governance process estabelecido
+- [ ] GA4 channel groups alinhados