Reporting & Analytics

Tinka
Member

User-defined property field -> not overwritable

SOLVE

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 🙂

0 Upvotes
1 Accepted solution
Krystal-Little
Solution
Member

User-defined property field -> not overwritable

SOLVE

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!

View solution in original post

0 Upvotes
1 Reply 1
Krystal-Little
Solution
Member

User-defined property field -> not overwritable

SOLVE

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!

0 Upvotes