create_technographic_audience

Creates B2B audiences based on technology stack, software usage, and firmographic attributes.

                ESTIMATE-ONLY MODE:
                Pass estimate_only=true to preview audience size (companies + contacts) WITHOUT creating the audience.
                In this mode the tool returns expectedNumberOfCompanies,
                expectedNumberOfContacts, and cappedContactCount. Default is false (audience is created).

                WHEN TO USE:
                - Target companies using specific technologies or software
                - Create audiences based on technology adoption patterns
                - Target by technology categories (CRM, Marketing Automation, Analytics, etc.)
                - Combine technology targeting with firmographic filters
                - Build tech-savvy audience segments for B2B campaigns
                - User wants to target companies and contacts that are familiar/using some specific software like hubspot, g2, etc.

                TECHNOLOGY CATEGORIES:
                - CRM: Salesforce, HubSpot, Microsoft Dynamics, Zoho, Pipedrive
                - Marketing Automation: Marketo, Pardot, Eloqua, HubSpot, Mailchimp
                - Analytics: Google Analytics, Adobe Analytics, Mixpanel, Amplitude
                - E-commerce: Shopify, Magento, WooCommerce, BigCommerce
                - Content Management: WordPress, Drupal, Joomla, Adobe Experience Manager
                - Collaboration: Slack, Microsoft Teams, Zoom, Asana, Monday.com
                - Cloud Infrastructure: AWS, Azure, Google Cloud, Oracle Cloud
                - Database: MySQL, PostgreSQL, MongoDB, Oracle, SQL Server
                - And many more technology categories available

                FIRMOGRAPHIC FILTERS (OPTIONAL):
                - Industries: Use industry IDs (1-148, same as firmographic audiences)
                - Employees: "LESS_THAN_10", "FROM_10_TO_50", "FROM_50_TO_200", "FROM_200_TO_500", "FROM_500_TO_1000", "FROM_1000_TO_5000", "FROM_5000_TO_10000", "OVER_10000"
                - Revenue: "LESS_THAN_1M", "FROM_1M_TO_10M", "FROM_10M_TO_50M", "FROM_50M_TO_100M", "FROM_100M_TO_200M", "FROM_200M_TO_500M", "FROM_500M_TO_1000M", "OVER_1000M"

                CONTACTS CRITERIA:
Use the following parameters to filter and target specific contacts within accounts:

GEOGRAPHIC TARGETING:
- location_country_ids: Array of country IDs (e.g., [29] for Brazil, [229] for United States)
- location_state_ids: Array of state IDs (e.g., [5] for California, [32] for New York)

JOB TITLES:
- job_title_includes: Array of free text strings to include (e.g., ["Software Engineer", "Manager"])
- job_title_excludes: Array of free text strings to exclude (e.g., ["Senior", "Lead"])

JOB FUNCTIONS:
Valid job function IDs and their labels:
- 1: Marketing, 2: Sales, 3: Customer Service, 4: Finance, 5: Human Resources, 6: Public Relations
- 7: Media, 8: Design, 9: Engineering, 10: Operations, 11: Legal, 12: Education
- 13: Health, 14: Real Estate, 15: Accounting, 16: Administrative, 17: Business Development
- 18: Community and Social Services, 19: Consulting, 20: Entrepreneurship, 21: Information Technology
- 22: Military and Protective Services, 23: Product Management, 24: Program and Project Management
- 25: Purchasing, 26: Quality Assurance, 27: Research, 28: Trades

- job_function_include_ids: Array of job function IDs to include (e.g., [9] for Engineering)
- job_function_exclude_ids: Array of job function IDs to exclude

SENIORITY LEVELS:
Valid seniority IDs and their labels:
- 2: Manager, 3: Director, 4: VP, 5: CXO, 6: Unpaid, 7: Training
- 8: Senior, 9: Owner, 10: Entry, 11: Partner

- seniority_include_ids: Array of seniority level IDs to include (e.g., [10, 7] for Entry and Training)
- seniority_exclude_ids: Array of seniority level IDs to exclude

CONTACT LIMITS:
- contacts_per_company_limit: Maximum number of contacts to target per company (optional). Example: 20

USAGE NOTES:
- All ID fields (countries, states, job functions, seniorities) use numeric IDs from the platform
- Job titles are free text strings, not IDs
- Use include parameters to specify which criteria to target
- Use exclude parameters to filter out contacts matching specific criteria
- Combine multiple criteria for precise targeting (e.g., Senior Engineers in California)
- Criteria are combined with AND logic, so all conditions must be met

CONTACTS CRITERIA PARAMETERS(Usually after other initial audience parameters to be described next):
- location_country_ids: Array of country IDs (optional)
- location_state_ids: Array of state IDs (optional)
- job_title_includes: Array of job title keywords to include (optional)
- job_title_excludes: Array of job title keywords to exclude (optional)
- job_function_include_ids: Array of job function IDs (optional)
- job_function_exclude_ids: Array of job function IDs (optional)
- seniority_include_ids: Array of seniority level IDs (optional)
- seniority_exclude_ids: Array of seniority level IDs (optional)
- contacts_per_company_limit: Maximum contacts per company (optional)


                PARAMETERS:
                - name: Audience name (required) - **IMPORTANT: Name MUST NOT exceed 50 characters. This is a mandatory requirement.**
                - technologies: Array of technology names (required)
                - industries: Array of industry IDs (optional)
                - employees: Array of employee count ranges (optional)
                - revenue: Array of revenue ranges (optional)

                RETURNS:
                Audience details with ID, size estimation, and creation status.

                COMMON USE CASES:
                - Target companies using Salesforce and HubSpot
                - Find AWS users in the software industry
                - Build audiences of companies using specific MarTech stacks
                - Combine technology and firmographic targeting for precise B2B campaigns

                IMPORTANT NOTES:
                - **CRITICAL: Audience name MUST NOT exceed 50 characters - this is mandatory and will cause creation to fail if exceeded**
                - name and technologies are required parameters
                - All other parameters are optional for flexible audience creation
                - Technology names should match available technologies in the Metadata platform
                - Contact criteria fields work the same as in other audience types
                - Audience size depends on technology filters and applied criteria