No, in fact it couldn't be more different.

In the original example, the parts after the ? are sent to the web server as a part of the request. As someone has said above, this is normally referred to as the "query string", and on the server side is normally handled by something that was traditionally called CGI as someone else mentioned (but in an incorrect context), although realistically that term has been rarely used since the 90's.

In your example, the parts after the # are NOT sent to the web server. Traditionally the part after the # allowed you to jump part-way through a page, however nowdays they are used as a way of passing data to javascript within the page - so although the items after the # are not passed to the web server directly, they can be read by the webpage itself, and then sent in a subsequent query to the web server.

As far as the OP's original query string, that particular query string is there as a tracking string, so that someone can track you jumping between websites.

Using 90's terminology, the query string becomes the CGI parameters once it hits the "CGI" code running on the webserver. Specifically CGI stands for "Common Gateway Interface" and is the interface between the webserver itself and the code running on the webserver for dynamic code. CGI defines the way that data passes between them, and thus the query string becomes the "parameters" within the CGI interface.