Query Params

Events	page_view (every link below is a navigation); its query_params reflects the URL.
How	Click a link and read query_params on the resulting page_view (debug console / network tab).
Notes	The pixel merges the real query string (before the #) with the query string inside an SPA hash route (#/route?…). On a key collision the hash-route value wins. Anchor hashes (#section) contribute nothing. Traditional and SPA /{path} links carry params in the real query string; #/ and #!/ links carry them inside the hash; merge links carry them in both.

Traditional — real query string

• ?a=1&b=2 → { a: "1", b: "2" }
• ?q=new%20iphone&page=2 → { q: "new iphone", page: "2" }

SPA /{path} — real query string; no reload when clicked from inside the SPA

• ?a=1&b=2 → { a: "1", b: "2" }

SPA /#/{path} — params inside the hash route

• #/…?a=1&b=2 → { a: "1", b: "2" }

SPA /#!/{path} — hashbang

• #!/…?c=3 → { c: "3" }

Merge — params both before and after the hash (hash wins collisions)

• ?a=1&keep=home#/…?b=2 → { a: "1", keep: "home", b: "2" }
• ?a=1&keep=home#/…?a=2&b=3 → { a: "2", keep: "home", b: "3" }

Edge cases

• repeated key ?a=1&a=2 → { a: "2" } (last wins)
• empty value ?a=&b=2 → { a: "", b: "2" }
• URL-valued param (encoded ? and &) → { next: "https://example.com/p?x=1&y=2" }