Ad Reporting and Attribution

Objective: Improve metric tracking, lead distribution, and internal communication among user groups within the platform. Current Problem: Currently, GHL only allows the addition of individual users without the ability to organize them into teams. This limitation impacts: Group Metrics: It’s impossible to analyze conversion rates, performance, or productivity by team (e.g., sales team vs. support team). Uneven Lead Distribution: Leads are assigned to individuals, not teams, which can overload some users while leaving others underutilized. Fragmented Communication: There’s no way to send targeted notifications to specific groups (e.g., alerts to the sales team about hot leads). Proposed Solution: Introduce a "Teams" feature within GHL, with the following functionalities: Team Creation Hierarchical Organization: Allow admins to create teams (e.g., "Sales SP", "24/7 Support") and assign users to multiple teams if needed. Customizable Permissions: Define access levels by team (e.g., sales team can edit pipelines, marketing team can only view reports). Team Metrics Custom Dashboard: View total conversion by team (e.g., how many leads from Team X became customers). Compare performance between teams (close rates, response times, etc.). Filter reports by team for strategic analysis. Automatic KPIs: Generate metrics like "Team Conversion Rate" or "Leads Assigned per Team" in charts and tables. Lead Distribution to Teams Automated Rules: Distribute leads evenly among team members (e.g., round-robin). Prioritize teams with lighter workloads or higher conversion rates. Assign leads based on tags or specific criteria (e.g., SP leads → SP sales team). Workload Balancing: Prevent overload by monitoring how many leads each team is handling. Internal Notifications by Team Targeted Alerts: Send real-time notifications to entire teams (e.g., "New urgent lead for the sales team"). Integrate with channels like Slack, email, or push notifications within GHL. Automated Reminders: Notify teams about pending tasks (e.g., follow-ups for unattended leads). Strategic Importance for GHL: Scalability: Larger businesses need to manage multiple teams without losing the big-picture view. Decision-Making: Team metrics help leaders identify gaps and reallocate resources effectively. Customer Experience: Evenly distributed leads are attended to faster, boosting satisfaction. Competitiveness: Platforms like HubSpot and Salesforce already offer this feature – GHL needs to keep up. Example Use Case: A marketing agency with 3 teams (Sales, Onboarding, Support) would use GHL to: Measure which team converts the most leads into meetings. Distribute 100 leads/day evenly among 10 sales reps. Send an automatic alert to the support team when a client opens a critical ticket. Technical Implementation Suggestion: Simple UI: Add a "Teams" section in the settings menu, with drag-and-drop user assignment. APIs for Automation: Allow teams to be used in workflows (e.g., "Send lead to Team X if tag is Y"). Integration with Existing Features: Link teams to pipelines, calendars, and campaigns. Why This is Urgent: Businesses are migrating to GHL for its flexibility, but the lack of team management limits its use for medium/large organizations. This feature would transform GHL into a truly competitive all-in-one platform.

Some of our users absolutely need 2-way sync on as they are using snippets and want to send stuff via HL to see links clicked, HOWEVER, they do not want every single non related email to that contact synced for everyone to see... it should be an option!

High Level can take SEO capabilities to the next level by integrating Rich Results (Structured Data / Schema Markup) directly into the Website, Funnel, and Blog Builder. This would allow businesses to enhance their Google search presence with Review Snippets, Breadcrumbs, FAQs, Product Listings, and other rich search features—all without needing third-party tools or custom coding. Suggested Features: SEO & Schema Panel – A dedicated section inside the builder to enable/disable specific rich result types. Automated Schema Generation – JSON-LD markup automatically added based on page content. Types of Schema Markup Supported: Review Snippets – Display star ratings & testimonials. Breadcrumbs – Help users & search engines understand page hierarchy. FAQ & How-To Schema – Expandable FAQs in Google Search. Article & Blog Schema – Optimized visibility for blog posts. Product Schema – Structured data for eCommerce pages. Local Business Schema – Enhance local business search results. Event Schema – Rich results for event listings. Video & Recipe Schema – Optimize embedded content for search engines. Why This Matters: Most businesses rely on SEO for growth, and Rich Results increase organic traffic, trust, and engagement. This feature would position High Level ahead of competitors by offering built-in advanced SEO capabilities for websites, funnels, and blogs—without requiring technical expertise. 🚀 Would love to see this feature added to help businesses rank higher and get more visibility online! ✅

We need to be able to edit the agency's logo and favicon independently. https://www.loom.com/share/14ca7abf7e8a414db281449ee1382966

We need more elements in the form builder. At the very least it would be great to have a horizontal line element. Currently we use the HTML element with an <hr> tag and it's just clunky. can we get access in the show/hide conditional logic to ALL elements? Currently you can only have it hide fields. but what about text and HTML elements? we just need to be able to say "if this field selection is "this", unhide this text element, html element, and these 3 fields."

With SaaS mode becoming a bigger part of high level, it would be helpful to have the date that populates in reporting to be based off of the date won. I don't know of many businesses that count a deal/income on the date it was created. A majority mark a sale and income on the actual day it closes. HIGHLVL-I-3371

I’d like to suggest a feature that allows emails to be separated based on the email address they are sent to, by enabling multiple inbound channels that can be monitored by assigned users. For example: Support Channel → Monitors emails sent to support@yourdomain.com Sales Channel → Monitors emails sent to sales@yourdomain.com Billing Channel → Monitors emails sent to billing@yourdomain.com Each channel could have designated users who are responsible for handling emails within that category, improving efficiency and organization. This would be extremely useful for teams managing multiple departments within a single GHL account. Additionally, this would likely be an important step in the consideration of enabling Email as a channel for Conversational AI, expanding automation capabilities and improving customer engagement. Please let me know if this is something that could be considered! Conversational Ai Discussions: "'Right' now the conversational ai is only available for SMS, Facebook, Instagram. Can we add email as an option to this? https://ideas.gohighlevel.com/conversation-ai/p/conversation-ai-email-option " "If someone sends an email to hello@mywonderfulagency they should get an entirely different AI persona than if they send an email to help@mywonderfulagency or hailie@mywonderfulagency. https://ideas.gohighlevel.com/automations/p/contact-replied-trigger-does-not-fire-on-cold-inbound-emails https://ideas.gohighlevel.com/automations/p/customer-replied-trigger-add-a-separate-trigger-for-new-messages "

We want to be able to choose more than 1 lost reasons for marking their opportunity if the situation calls for it.

Find myself being a little lost without the Big X. See both screenshots for more info. Also having a title and description for all posts makes it clunky. Facebook has billions of posts I'm sure with only one required field.

To be able to create roulette or other types of games in forms to increase lead conversion and data capture in funnels. That this can be applied to custom forms, emails, pop-ups and calendars. That the information is automatically transmitted to the profile of the contact of the prize that you won from the roulette or game that has been configured.