--- title: Eventixa My Account description: "The **Eventixa My Account** page gives registered customers a central place to view and manage their Eventixa activity from the frontend. Customers can use the account area to review their event bookings and access available ticket information without entering the…" url: "https://eventixawp.com/docs/eventixa-my-account/" updated: "2026-09-26" category: "My Account & Customer Experience" --- # Eventixa My Account The **Eventixa My Account** page gives registered customers a central place to view and manage their Eventixa activity from the frontend. Customers can use the account area to review their event bookings and access available ticket information without entering the WordPress admin dashboard. > **Available in:** Eventixa Core > **Shortcode:** `[eventixa_my_account]` > **User Access:** Logged-in customers ## What Is Eventixa My Account? Eventixa My Account is the frontend customer account area for Eventixa. It is designed for customers who have registered for events and need a simple way to return later and review their Eventixa records. The account area keeps customer-facing booking information separate from the WordPress admin. ![Eventixa My Account frontend page showing customer event bookings and account navigation](https://eventixawp.com/wp-content/uploads/2026/09/eventixa-my-account-overview.jpg) The Eventixa My Account page gives logged-in customers a central frontend area for their event registrations. ## What Customers Can Access Depending on the customer's Eventixa activity and the features enabled on the site, the My Account area can provide access to: - Event bookings - Booking details - Event tickets - Registration information - Booking status information - Event information associated with a booking The exact information shown depends on the booking and ticket data available for the current customer. ## My Account Requires Login The Eventixa My Account page is intended for logged-in WordPress users. A customer must sign in to the same WordPress account associated with their Eventixa activity before their account records can be displayed. ## Customer Privacy Eventixa My Account only displays records available to the currently authenticated customer. Customers are not given access to other users' bookings simply by knowing a booking number or visiting the account page. ## Eventixa My Account Shortcode Use the following shortcode to display the Eventixa account area: `[eventixa_my_account]` Add this shortcode to a normal WordPress page. For example, you can create a page named: **My Account** and place the shortcode in the page content. ## Create the My Account Page To create a customer account page: 1. Go to **Pages → Add New** in WordPress. 2. Enter a page title such as **My Account**. 3. Add the Eventixa shortcode. 4. Publish the page. 5. Add the page to your site's navigation or customer workflow where appropriate. ## Recommended Page Name A clear page name such as **My Account**, **Event Account**, or **My Event Account** makes the page easy for customers to find. For most sites, **My Account** is the simplest option. ## Keep the Page Customer-Focused The page should primarily contain the Eventixa account interface. Avoid placing large unrelated content sections above the shortcode, because customers generally visit this page to find their bookings or tickets quickly. ## What Happens When a Customer Opens My Account? When a logged-in customer opens the page, Eventixa identifies the current WordPress user and loads the Eventixa records associated with that customer. The customer can then navigate through the account information available to them. ## Booking Information The account area provides access to the customer's Eventixa bookings. A booking represents an event registration or ticket purchase recorded by Eventixa. Depending on the booking, customers may see information such as: - Event - Booking reference - Registration type - Booking status - Ticket information - Event date - Related booking details ## Multiple Bookings If a customer has registered for several events, the My Account area can show multiple Eventixa booking records. Each booking remains separate so customers can review the correct event and registration information. ## Event Tickets When a booking has eligible Eventixa tickets, the customer can access the ticket information through their account workflow. This is especially useful when the original ticket email is no longer available. ## Ticket Availability Depends on the Booking Not every Eventixa registration necessarily produces the same ticket experience. Ticket availability can depend on: - Registration type - Booking status - Attendee status - Event configuration - Ticket configuration For example, RSVP responses that should not receive a ticket do not behave like normal ticket registrations. ## Booking Status Customers can see the current state of their booking where the account interface exposes booking status information. The exact status reflects Eventixa's booking lifecycle rather than creating a separate customer-only status. ## Account Data Comes from Eventixa The My Account page is not a separate copy of customer information. It displays current Eventixa booking and ticket data associated with the logged-in customer. This means changes made to a booking in Eventixa can be reflected in the customer account experience. ## Logged-In Customer Email For logged-in checkout, Eventixa uses the authenticated customer's email as part of the booking identity workflow. The customer's account page is therefore tied to the WordPress user relationship used by Eventixa. ## Guest Checkout and My Account Eventixa can support guest checkout when that setting is enabled. A guest customer does not automatically have the same persistent logged-in My Account experience as an authenticated WordPress user. If you want customers to return to a frontend account area later, requiring or encouraging account login provides the clearest account workflow. ## My Account Is Different from WordPress Admin Customers do not need access to: **WordPress Dashboard → Eventixa** to review their bookings. The Eventixa My Account shortcode provides the customer-facing interface on the frontend. ## My Account Is Different from WooCommerce My Account If WooCommerce integration is enabled, WooCommerce can also provide its own customer account pages and order history. Eventixa My Account remains the Eventixa-specific frontend account interface. Depending on your site setup, a customer may have both: - WooCommerce order/account information - Eventixa booking/ticket information These interfaces serve related but different purposes. ## WooCommerce Booking Relationship When a paid Eventixa booking uses WooCommerce Checkout, the WooCommerce order and Eventixa booking remain related. The WooCommerce account can expose the order, while the Eventixa account area focuses on the event registration and ticket side of the workflow. ## Customer Experience After Booking A typical logged-in Eventixa customer workflow is: 1. Customer signs in. 2. Customer opens an event. 3. Customer selects a ticket. 4. Customer completes checkout. 5. Eventixa creates the booking and attendee data. 6. Customer receives the configured booking/ticket emails. 7. Customer can later return to the Eventixa My Account page. 8. Customer opens the relevant booking or ticket information. ## Recommended Navigation Placement If My Account is an important part of your event workflow, add the page to your website navigation. Common placements include: - Main site navigation - User/account menu - Header account icon - Footer customer links The best placement depends on your website structure. ## Keep Login Easy to Find Because My Account requires an authenticated customer, make sure users can easily find your WordPress login or account-login workflow. Avoid creating a My Account link without also giving logged-out users a clear way to sign in. ## Account Page on Membership Sites If the website already has a larger membership or customer dashboard, you can place the Eventixa My Account shortcode inside the appropriate customer area instead of creating an entirely separate account system. The important requirement is that the shortcode loads for the authenticated WordPress user. ## Booking Ownership Eventixa uses booking/customer relationships to determine which records belong to the current account. Site administrators should avoid manually altering booking ownership unless they understand how the change affects the frontend customer account. ## Ticket Access After Booking Changes If an administrator changes a booking, attendee, or ticket-related state, the customer-facing account information can change accordingly. For example, a booking that is no longer eligible for an active ticket should not be treated as though its original booking state still applies. ## Cancelled Bookings Cancelled bookings can remain part of Eventixa's booking history depending on the account workflow and booking data. The displayed status helps distinguish the booking from an active registration. ## Refunded Bookings If a booking is marked refunded, the account information can reflect the updated Eventixa booking state. Refund processing itself is handled by the appropriate payment workflow rather than by the My Account page. ## RSVP Registrations RSVP registrations are still Eventixa registration records, but their behavior differs from paid or normal ticket bookings. For example, **Not Going** RSVP responses do not use the same ticket/check-in workflow as active Going registrations. ## Recurring Event Bookings For recurring events, booking information can include the relevant event occurrence. This helps customers identify which date in a recurring event series their registration belongs to. ## Virtual Events For Virtual or Hybrid events, the customer's Eventixa account can complement Eventixa's controlled virtual-event access workflow. The account page should not be treated as a reason to expose managed Zoom or Google Meet links publicly. Meeting access still follows the event's virtual-access rules. ## QR Tickets When a booking produces an eligible Eventixa ticket, the ticket can include the QR code used for event check-in. The customer account gives attendees another place to access their ticket when supported by the current booking. ## Resent Tickets Administrators can resend eligible Eventixa tickets from the attendee/booking workflow. The My Account page complements that process by allowing logged-in customers to access available booking and ticket records themselves. ## Editing Attendee Information Whether attendee information can be edited depends on the Eventixa capabilities available on the site and the customer-facing workflow provided by your installation. The My Account page should not be assumed to expose every administrative attendee-editing capability. ## Create Only One Primary My Account Page For a straightforward customer experience, use one primary page containing `[eventixa_my_account]`. Creating several different account pages with the same shortcode can confuse customers and make navigation harder to maintain. ## Do Not Cache Private Account Content Publicly The Eventixa My Account page contains user-specific information. If your site uses a page cache, CDN cache, or optimization plugin, make sure authenticated account content is not cached in a way that could expose one customer's information to another. Most well-configured WordPress caching systems exclude logged-in user pages automatically, but the account page should still be checked. ## Recommended My Account Setup A clean setup is: 1. Create a page called **My Account**. 2. Add `[eventixa_my_account]`. 3. Publish the page. 4. Add it to the customer/account menu. 5. Confirm logged-out visitors are directed through your login flow. 6. Complete a test booking with a normal customer account. 7. Sign in as that customer. 8. Open My Account. 9. Confirm the correct booking is visible. 10. Open the booking/ticket information. 11. Confirm another customer cannot see the test booking. ## Test with More Than One Customer When testing customer-account functionality, use at least two separate WordPress customer accounts. This helps verify that booking information is correctly isolated between users. ## Test Different Booking Types If your site uses several registration workflows, test My Account with: - Paid booking - Free ticket booking - RSVP Going - RSVP Not Going - Recurring-event booking - Virtual-event booking - Cancelled booking - Refunded booking where applicable This provides better coverage than testing only one standard booking. ## Logged-Out User Cannot See My Account Data If the user is logged out, they should not receive another customer's private Eventixa booking information. Use your site's normal login workflow so the customer can authenticate before accessing account-specific records. ## Booking Does Not Appear in My Account Check: - The customer is logged into the correct WordPress account. - The booking belongs to that customer. - The booking exists in Eventixa. - The booking was not created under another account/email relationship. - The correct My Account shortcode is being used. ## Wrong Customer Booking Appears This should be investigated immediately. Check the booking ownership/customer relationship and confirm the page or caching layer is not serving cached private account output. ## My Account Page Is Empty First confirm that the logged-in customer actually has Eventixa records associated with the account. A newly created user with no Eventixa bookings can legitimately have no booking data to display. ## Shortcode Is Displayed as Plain Text If `[eventixa_my_account]` appears literally on the page instead of rendering Eventixa content: - Confirm Eventixa is active. - Confirm the shortcode is spelled correctly. - Place it in a WordPress block or content area that processes shortcodes. - Clear page-builder/cache output if necessary. ## My Account Page Is Cached Incorrectly Exclude the customer account page from any full-page cache that serves the same HTML to multiple authenticated users. Also verify that CDN or optimization rules do not cache personalized account output. ## Ticket Is Missing from My Account Check whether the booking and attendee are actually eligible for ticket generation. Review: - Registration type - Booking status - Attendee status - RSVP response - Event ticket configuration A missing ticket is not always a My Account rendering problem. ## Recurring Booking Shows the Wrong Date Confirm the booking is associated with the correct event occurrence. Also review the recurring event's occurrence configuration in Eventixa. ## Virtual Meeting Link Is Not Visible Eventixa virtual-event access can depend on eligibility and access timing. Review the event's Virtual Event configuration and access settings rather than exposing the meeting URL manually. ## WooCommerce Order Exists but Eventixa Booking Is Missing The WooCommerce order and Eventixa booking are related but separate records. Check the corresponding Eventixa booking and WooCommerce synchronization state. ## Recommended Customer-Facing Labels If you customize navigation around the shortcode, use simple customer-facing labels such as: - My Account - My Bookings - My Tickets Avoid technical WordPress terminology in frontend menus. ## Why My Account Improves the Customer Experience Email remains useful for confirmations and ticket delivery, but customers may lose or overlook an email. A persistent account area gives customers another way to return to their event information. It also makes Eventixa feel like a complete registration system rather than a one-time checkout form. ## Important Notes - Eventixa My Account is a frontend customer area. - Use `[eventixa_my_account]` to display it. - The account page is intended for logged-in WordPress users. - Customers can access their own Eventixa booking information. - Eligible ticket information can be accessed through the customer workflow. - My Account is separate from the WordPress Eventixa admin. - WooCommerce My Account and Eventixa My Account serve different purposes. - Guest checkout does not automatically provide the same persistent logged-in account workflow. - Booking and ticket visibility depends on the customer's actual Eventixa records and statuses. - Recurring bookings can carry occurrence-specific information. - Virtual meeting access remains controlled by Eventixa virtual-access rules. - Private My Account output should not be publicly page-cached. - Test the page with multiple customer accounts before launching it. ## Related Documentation - [Viewing Event Bookings](https://eventixawp.com/docs/viewing-event-bookings/) - [Viewing Event Tickets](https://eventixawp.com/docs/viewing-event-tickets/) - [Guest Checkout](https://eventixawp.com/docs/guest-checkout/) - [Managing Bookings](https://eventixawp.com/docs/managing-bookings/) - [Booking Statuses](https://eventixawp.com/docs/booking-statuses/) - [Managing Attendees](https://eventixawp.com/docs/managing-attendees/) - [Resend Event Tickets](https://eventixawp.com/docs/resend-event-tickets/) - [QR Tickets](https://eventixawp.com/docs/qr-tickets/) - [Recurring Event Tickets](https://eventixawp.com/docs/recurring-event-tickets/) - [Virtual Event Access](https://eventixawp.com/docs/virtual-event-access/)