Skip to main content

Understanding Membership Triggers in Mariana Tek: Activated, Purchased, Suspended & Deactivated

This guide explains the four key membership events from Mariana Tek and how to use them to trigger specific automations in Go HighLevel.

J
Written by Jared Gobler

This guide explains the four key membership events from Mariana Tek and how to use them to trigger specific automations in Go HighLevel via SYNX. These events are:

  • Membership Purchased

  • Membership Activated

  • Membership Suspended

  • Membership Deactivated

Each of these events can fire separate workflows depending on how the membership is billed, activated, or changed—giving you fine-grained control over member communications and internal processes.


1. Membership Purchased

Triggered When: A client buys a membership (regardless of when it starts).

How to Use It:

  • Trigger: Use Membership Purchased as the automation trigger in Go HighLevel.

  • Data to Capture:

    • Full Name

    • Email

    • Phone Number

    • Client ID

    • Membership Name

    • Membership Status (e.g., Pending Activation)

  • Recommended Add-On:

    • Add a dynamic tag like membership-purchased-[Membership Name].

Notes:

  • This trigger fires even if the membership isn't active yet.

  • It always works alongside the Order Completed trigger, which fires for any product purchase (e.g., retail, water bottles, memberships).


2. Membership Activated

Triggered When: A membership becomes active. This can happen:

  • Immediately upon purchase (if set to start "today")

  • Upon first check-in (if delayed activation is configured)

How to Use It:

  • Trigger: Use Membership Activated in a new workflow.

  • Data to Capture:

    • Full Name

    • Email

    • Phone Number

    • Client ID

    • Membership Name

    • Membership Status (e.g., Frozen)

  • Add a Condition: Use a date comparison to ensure it’s a true new activation:

    • Format the membership start date

    • Compare it to today’s date

    • If it matches, continue the workflow (e.g., send a welcome email series)

Why the Condition Matters:

  • Mariana Tek may re-fire the "activated" trigger on every billing cycle (common across membership platforms).

  • Without a condition, clients might repeatedly enter "new member" automations.


3. Membership Suspended

Triggered When: A membership is temporarily frozen (e.g., failed payment, freeze request).

How to Use It:

  • Trigger: Use Membership Suspended

  • Data to Capture:

    • Full Name

    • Email

    • Phone Number

    • Client ID

    • Membership Name

    • Membership Status (e.g., Frozen)

Example Use Cases:

  • Notify internal team of the freeze

  • Pause automated communications

  • Add dynamic tag: membership-suspended-[Membership Name]


4. Membership Deactivated

Triggered When: A membership is canceled or terminated.

How to Use It:

  • Trigger: Use Membership Deactivated

  • Data to Capture:

    • Full Name

    • Email

    • Phone Number

    • Client ID

    • Membership Name

    • Membership Status (e.g., Frozen)

  • Recommended Actions:

    • Capture the same member details as above

    • Add a dynamic tag like membership-terminated-[Membership Name]

    • Use this for:

      • Re-engagement campaigns

      • Retention team outreach

      • Account cleanup or CRM updates


Real-World Automation Example

Let’s walk through a scenario for clarity:

Scenario 1: Purchase with Delayed Activation

  • Membership Purchased: Fires immediately.

  • Order Completed: Fires (generic purchase event).

  • Membership Activated: Fires only after first check-in.

Scenario 2: Purchase with Immediate Activation

  • All three fire at once:

    • Membership Purchased

    • Order Completed

    • Membership Activated

Scenario 3: Membership Freeze

  • After freezing the membership in Mariana Tek, the Membership Suspended trigger fires, allowing Go HighLevel to take appropriate actions.

Scenario 4: Membership Cancellation

  • The Membership Deactivated trigger fires.

  • Useful for tagging the account or routing to retention automations.


Final Tips

  • Always test your automations using a test user to ensure triggers work as expected.

  • Use dynamic tagging to help with segmentation and reporting.

  • Ensure proper date formatting when comparing activation dates.


For help implementing or troubleshooting any of these automations, please contact [email protected]

Did this answer your question?