# User-defined property field -\> not overwritable **URL:** \ **Category:** Reporting & Analytics\ **Tags:** object\ **Created:** [June 3, 2025, 7:49am UTC](https://community.hubspot.com/t/user-defined-property-field-not-overwritable/133837 "2025-06-03T07:49:23Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Tinka](https://avatars.discourse-cdn.com/v4/letter/t/8dc957/32.png) [@Tinka](https://community.hubspot.com/u/Tinka)\ **Post date:** [June 3, 2025, 7:49am UTC](https://community.hubspot.com/t/user-defined-property-field-not-overwritable/133837/1 "2025-06-03T07:49:23Z")
Hello dear Community! 🇬🇧 **My Challenge:** Keeping track of where exactly the contact came from (source) in the contact. For a long time now, I have been encountering the problem that **Hubspot’s “Original traffic source” property is not sufficient for our purposes.** Although it has what we need: It is automatically filled once and can then no longer be overwritten. Specially created properties, as we need them, are unfortunately overwritten with each additional touchpoint. 🙏Do you have any best practices for me? I would be very happy! **In addition, I would love to have the option of non-overwritable fields from Hubspot 🙂** ---
**Author:** ![Krystal-Little](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/krystal-little/32/70131_2.png) [@Krystal-Little](https://community.hubspot.com/u/Krystal-Little)\ **Post date:** [June 3, 2025, 5:37pm UTC](https://community.hubspot.com/t/user-defined-property-field-not-overwritable/133837/2 "2025-06-03T17:37:18Z")
Not sure if this solves your issue but we have the same situation and what we’ve done is we have a reportable property that gets set one time only through a workflow that when the “original traffic source” property is known it sets the value in the new property (this is a dropdown of choices to make reporting easier). That workflow has no re-enrollment so the reportable property is only ever set once. This has been our solution, hope it helps!