# How does Dynatrace normalize URLs?

**URL:** <https://community.dynatrace.com/t/how-does-dynatrace-normalize-urls/10696>\
**Category:** Open Q&A\
**Tags:** services-classic, request-attributes\
**Created:** [January 29, 2018, 5:18pm UTC](https://community.dynatrace.com/t/how-does-dynatrace-normalize-urls/10696 "2018-01-29T17:18:51Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![edward\_wong](https://avatars.discourse-cdn.com/v4/letter/e/898d66/32.png) [@edward\_wong](https://community.dynatrace.com/u/edward_wong)\
**Post date:** [January 29, 2018, 5:18pm UTC](https://community.dynatrace.com/t/how-does-dynatrace-normalize-urls/10696/1 "2018-01-29T17:18:51Z")

</div>

I was wondering how Dynatrace normalizes URLs. For example, I know that google analytics & Hubspot appends extra information to the end of the URL:

[Example Domain](http://www.example.com/?ga)\_12345.1234&nbsp; or [www.example.com/](http://www.example.com/)?\_\_hstc12345.12345

When I view the URL entries, it’s able to report it as just "[www.example.com](http://www.example.com)&nbsp;". How does Dynatrace normalize it? Does it have a list of internal rules, or does it do it some other way?

---

<div class="post-metadata">

**Author:** ![JamesKitson](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/jameskitson/32/22460_2.png) [@JamesKitson](https://community.dynatrace.com/u/JamesKitson)\
**Post date:** [January 29, 2018, 5:29pm UTC](https://community.dynatrace.com/t/how-does-dynatrace-normalize-urls/10696/2 "2018-01-29T17:29:06Z")

</div>

A lot of this is done in the web request naming rules with the default option to exclude a lot of the unique aspects of web request URLs:

 ![15626-webnaming.png](https://global.discourse-cdn.com/dynatrace/original/2X/e/efeddd562d08546e8cc14ac5d48f3095f9812c8d.png)

James
