Hi there! I see you’re having trouble booking tickets for the Portsmouth 2026 SailGP event. I’d be happy to help you sort that out.

To start, could you tell me a bit more about what happens when you try to book? For example:
- Are you using the SailGP app or the website?
- Do you get any error messages, or does the booking button not respond?
- Have you managed to book tickets for other events before, or is this your first time?

In the meantime, I can share that tickets for the Portsmouth 2026 Emirates Great Britain Sail Grand Prix are available through the official SailGP ticketing site here: https://tickets.sailgp.com/portsmouth/

Also, members of SailGP’s free VIP fan and loyalty program, SailGP+, get early access to these tickets. If you’re part of that program, you may want to check your access as well.

Once I have more details from you, I can guide you step-by-step through the booking or help troubleshoot further!

I'm logged into Sailgp+ via the website but keep getting the following error message: "Widget settings could not be loaded. Please check that the parameters (channelId, sessionId) are correct." Every time I reload the page I the same message is returned

Thanks for sharing that error message—it gives us a helpful clue. The message "Widget settings could not be loaded. Please check that the parameters (channelId, sessionId) are correct." typically means there’s an issue with the ticketing widget that handles the booking process and it can’t verify your session or the widget’s configuration.

Let’s try a few focused steps to get this resolved:

1. Clear Browser Cache and Cookies: Sometimes outdated or corrupted data can interfere with session parameters. Here’s how on Windows 10:
- Open your browser settings (are you using Chrome, Edge, Firefox, etc.?)
- Find the option to clear browsing data.
- Choose to clear cache and cookies, then restart the browser and log in again.

2. Try a Different Browser or Incognito Mode: This helps see if an extension or browser setting is blocking the widget.
- Open a private or incognito window.
- Log into SailGP+ and try booking again.

3. Check Browser Permissions and Pop-ups: Make sure your browser isn’t blocking scripts or pop-ups from the SailGP site, as this can affect how widgets load.

4. Ensure Your Account Session Is Active: Log out fully from the site, then log back in fresh. This sometimes refreshes session parameters like channelId and sessionId.

5. Network Considerations: Are you connected via a VPN or restricted network? These sometimes block or modify session information. Try from a different network or disabling VPN temporarily.

Please try these steps and let me know if the issue persists after. We can dig deeper or consider other solutions from there.
Are you currently using any particular browser? That will help me tailor instructions if needed.

What are channelId and sessionId parameters in SailGP and how to fix them?

Great question! The channelId and sessionId are parameters used by the SailGP ticketing system to identify the specific booking channel and your current user session. Think of them like unique identifiers that help the system load your ticket booking widget correctly and securely.

- channelId usually represents the specific sales channel or widget configuration being used (for example, the Portsmouth 2026 event).
- sessionId tracks your current login session to keep your interaction personalized and secure.

If these parameters are missing, incorrect, or not properly passed to the booking widget, the widget can’t load, which causes the error message you saw.

How to fix it:
1. As I mentioned before, the most common solution is to refresh the session and clear any old or corrupted data your browser may be holding onto. Clearing your cache and cookies is key here.
2. Logging out completely and logging back in helps establish a fresh, valid sessionId.
3. Using an updated browser version can help ensure your browser correctly handles these parameters.
4. In rare cases, if there is a bug or glitch on the SailGP ticketing backend, the issue will need to be fixed by the technical team. If you have tried the above and the issue persists, I can escalate this for you to get a backend check.

Would you like me to guide you through clearing cache and logging back in, or have you already tried those steps?