I am having the issue as detailed in here: segmentio/analytics.js#504 when I try to add a url parameter to a query string hubspot puts its queries in front of the existing queries thereby creating an invalid URL. I have found a way around this that doesn't impact my analytics, but shouldn't the Hubspot query strings be appended to the end of any existing query strings?

The URL I want to create:
https://foo.bar.co/#/register?__hstc=6222316.1d2b332e80357701bf2ef394e3a88e1b.1508536177681.1521725761504.1521729618139.158&__hssc=6222316.4.1521729618139&__hsfp=1692073022&plan=professional

The URL that I get:
https://foo.bar.co/?__hstc=6222316.1d2b332e80357701bf2ef394e3a88e1b.1508536177681.1521725761504.1521729618139.158&__hssc=6222316.11.1521729618139&__hsfp=1692073022#/register?plan=professional

https://help.segment.com/hc/en-us/community/posts/205385493-HubSpot-integration-fails-to-send-identity-on-1st-page-call

I can see the IP address under the context property but I'm not sure how to send it.

Hi!

Here's a string I'm applying to a href attribute of a link:

https://example.com/app#/tree?path=foo.bar

But when its rendered on the page, here's how it ends up looking:
https://example.com/app&__hstc=181257784.ec3b8f50ceac6ae94ada7d99c135638e.1456488482298.1458396994219.1458561178659.71&__hssc=181257784.16.1458561178659&__hsfp=3702051802#/tree?path=foo.bar

Our backend filters results by query params at this point, so the URL does not yield what it's supposed to.

How do I prevent those __hstc, __hssc and __hsfp query qarams from polluting all URLs? Note that I'm unable to prevent them from appearing at the frontend logic level, because at that level URLs are clean and get polluted after rendering by the HubSpot script injected by segmentio/analytics.js.