Mixpanel helps you understand your customer behavior in one system: from website, thorough billing and control panels till website builder and payment process, and learn more about your product. You can track how people use it and easily analyse the data with reports that let you see and explore the results in just a few clicks.

We recommend to follow these instructions to be fully compatible with website builder and avoid any additional issues:

1. Connect Mixpanel to Your Website:

• Install Mixpanel. Follow this guide to get more details.

• Identify Users. Follow this guide to get more details.



2. Think of and describe the main events:

Event Syntax:
event_name {eventOrUserProperty = exampleValue}
Short description, when the event is tracked.

1. For the Website*:
• page_view {pageUrl="/website-builder"}
Triggered when a user visits any page on your website.
• click_button {buttonId="sign-up", "start"}
Triggered when a user clicks on any button.
• try_register {userActivationType="email", "google", "apple"}
Activated when a user clicks on the registration button.


2. For the Billing system**:
These events are tracked in your billing system (ex. WHMCS or any other).
• register_user {regButton="Start now"}
Tracked when a user successfully completes the registration.
• activate_user {userActivationMethod="link", "code", "button"}
Recorded when a user activates their email using a specific method.


3. For the Control panel***:
• open_panel
Triggered when a user accesses the control panel.
• open_builder {openerButtonId="cpanel", "whmc"}
Tracked when a user opens the Website Builder from the control panel.


4. For the Website Builder*:
All you need to do is add the Mixpanel token to the Website Builder. All these rest options are pre-configured.
• select_builder_flow
Triggered when a user chooses a template, imports a site, or generates a website.
• publish_builder_website
Triggered when a user publishes their website.
• complete_share
Triggered when a user shares access to their website.
• click_button {buttonId="..."}
Tracked when a user clicks on a button.
These and many other events pre-configured in the Website Builder for Mixpanel tracking. You don't need to implement them by yourself.


5. For the Checkout*:
Automatically logged along with the events in point #4.
• open_payment_form
Triggered when a user opens the payment form.
• open_payment_gateway {paymentGateway="Stripe", "PayPal"}
Tracked when a user opens the payment gateway through WHMCS.
• complete_payment {product_id="Starter", "Standard"}
Tracked when a user completes payment for the Website Builder.



We suggest keeping event and property names as they are for better consistency and efficient analysis. You can expand the list based on your needs and technical capabilities.

If you face any challenges, feel free to reach out — we're here to help you!

3. Track events:

After thinking through all the events, implement them into the website: by track events documentation.

4. Check if all data is sent correctly:
This document walks through best practices for data validation and debugging your Mixpanel implementation.

*     Mandatory for implementation
**   Recommended
*** Optional