# Sign Up Type and Content Value Reference Guide


**Last Updated:** 2025-11-20

**Date:** 2025-11-20  
**Purpose:** Quick reference guide for sign_up_type__c and content values across all HubSpot-integrated forms

> **📚 For comprehensive documentation:** See [HUBSPOT_SIGNUP_CONTENT_COMBINATIONS.md](./HUBSPOT_SIGNUP_CONTENT_COMBINATIONS.md) for complete details including all dynamic value combinations, normalization rules, code references, and usage guidelines.

## sign_up_type__c Values

### "Tools Page"
**Used by:**
- collect-lead.php
- export-workdays.php
- shiftops-hubspot.php
- shiftops-nps.php

**When to use:** For all tool/calculator pages and ShiftOps-related forms

### "Template Download"
**Used by:**
- submit-template.php

**When to use:** For template download forms

### "Add-on Pricing Inquiry"
**Used by:**
- addon-request.php

**When to use:** For add-on pricing inquiry forms

### "Lead Capture Form"
**Used by:**
- lead-capture.php

**When to use:** For lead capture popup forms

### "Webinar Registration"
**Used by:**
- webinar-registration.php
- payroll-webinar-registration.php

**When to use:** For webinar registration forms

## content Values

### Dynamic Tool Description
**Used by:**
- collect-lead.php

**Value:** `$toolDescription` (dynamic, from input)

**When to use:** For tool/calculator forms where description varies

### Dynamic Content Type
**Used by:**
- submit-template.php

**Value:** `$content_type` (dynamic, from input, e.g., "Dienstplan Vorlage - Template")

**When to use:** For template forms where content type varies

### Static Tool Names
**Used by:**
- export-workdays.php: "Arbeitstage-Rechner"
- shiftops-hubspot.php: "ShiftOps"
- shiftops-nps.php: "ShiftOps NPS"

**When to use:** For specific tool pages with fixed names

### Addon Name
**Used by:**
- addon-request.php

**Value:** `$addon` (dynamic, e.g., "Zeiterfassung", "Schichtplanung", "Enterprise") or "Add-on Pricing Inquiry" as fallback

**When to use:** For add-on pricing forms - use addon name when available

### Page-Specific Lead Capture
**Used by:**
- lead-capture.php

**Value:** "Lead Capture - {sourcePage}" or "Lead Capture" if sourcePage is empty

**When to use:** For lead capture forms - include source page when available

### Webinar Names
**Used by:**
- webinar-registration.php: "Ordio Produkt-Webinar"
- payroll-webinar-registration.php: "Ordio Payroll Webinar"

**When to use:** For webinar registration forms - use specific webinar name

## Value Patterns and Conventions

### Naming Conventions
1. **Sign Up Type:** Use descriptive, consistent values
   - Tools → "Tools Page"
   - Templates → "Template Download"
   - Pricing → "Add-on Pricing Inquiry"
   - Leads → "Lead Capture Form"
   - Events → "Webinar Registration"

2. **Content:** Use descriptive values that identify the specific form/page
   - Tool names: "Arbeitstage-Rechner", "ShiftOps"
   - Template types: Dynamic from content_type
   - Addon names: Dynamic from addon parameter
   - Lead capture: Include source page when available
   - Webinars: Specific webinar name

### Best Practices
1. **Consistency:** Use same sign_up_type__c for similar form types
2. **Specificity:** Content should be specific enough to identify the exact form/page
3. **Dynamic Values:** Use dynamic values when they provide useful information
4. **Fallbacks:** Always provide fallback values when dynamic values might be empty

## Form Field Requirements

### Forms API v3
Forms using Forms API v3 require fields to be present in the HubSpot form:
- shiftops-nps: Needs sign_up_type__c and content fields (manual addition required)
- addon-request: Needs content field (manual addition required) - **Note:** Currently capturing without field
- lead-capture: Needs content field (manual addition required) - **Note:** Currently capturing without field

### CRM API v3
Forms using CRM API v3 can set properties directly:
- webinar-registration: ✅ No form fields needed
- payroll-webinar-registration: ✅ No form fields needed

## Implementation Checklist

When adding a new form:

1. ✅ Determine appropriate sign_up_type__c value (use existing patterns)
2. ✅ Determine appropriate content value (be specific and descriptive)
3. ✅ Add fields to form submission code
4. ✅ Add fields to HubSpot form (if using Forms API v3)
5. ✅ Update property-mapping.php
6. ✅ Test submission and verify capture
7. ✅ Update documentation