Current Limitation

In GoHighLevel workflows, goals currently have limited conditions for when a contact can be marked as having met the goal. These conditions are restricted to:

• Received an Email Event

• Clicked a Trigger Link

• Added a Contact Tag

• Removed a Contact Tag

• Appointment Status Updated

However, this approach forces users to create additional workflows or use unnecessary tags to track goal completion for common actions. This adds complexity, redundancy, and extra automation steps that could be avoided if goal conditions aligned with the broader set of workflow triggers.

Proposed Solution

Expand Goal Conditions to include ALL possible triggers available in the If/Else conditions. This would allow users to directly set goals based on any meaningful event, eliminating unnecessary tags and redundant workflows.

Use Case Scenarios

1️⃣ Form Submission as a Goal Condition

• A lead submits an application form.

• Current Setup: Requires adding a tag like “Form Submitted” just to track progress toward a goal.

• Proposed Solution: Let “Submitted Form” be a direct goal condition, reducing the need for extra workflows.

2️⃣ Page Visit as a Goal Condition

• A lead lands on a thank-you page after signing up.

• Current Setup: Requires adding a trigger link or tracking script to apply a tag.

• Proposed Solution: Make “Visited Page” a direct goal condition, allowing workflows to update without extra tagging.

3️⃣ Product Purchase as a Goal Condition

• A customer purchases a product via Stripe or Shopify integration.

• Current Setup: Requires tagging the contact as “Purchased” to mark goal completion.

• Proposed Solution: “Purchased a Product” should be a direct goal condition.

4️⃣ Survey Completion as a Goal Condition

• A lead completes a multi-step survey.

• Current Setup: Requires adding a tag like “Survey Completed.”

• Proposed Solution: Let “Survey Submitted” be a direct goal condition.

5️⃣ Replied to SMS as a Goal Condition

• A lead responds to an SMS in a follow-up campaign.

• Current Setup: Requires manually checking replies or setting a separate workflow with a tag.

• Proposed Solution: “Replied to SMS” should be a native goal condition.

6️⃣ Membership Access as a Goal Condition

• A user logs in or accesses a membership course.

• Current Setup: Requires applying a tag or using a webhook to track logins.

• Proposed Solution: “Logged into Membership” should be a direct goal condition.

Why This Matters

✅ Reduces Redundant Workflows – No need to create extra automation just to apply tags.

✅ Improves Workflow Simplicity – More intuitive goal-tracking based on direct actions.

✅ Enhances Reporting & Tracking – Allows more precise goal tracking without additional steps.

✅ Saves Time & Effort – Eliminates manual workarounds, letting users focus on optimization.

Upvote This Feature!

If you agree that GoHighLevel should expand Goal Conditions to include all If/Else triggers, click Upvote to support this enhancement! 🚀