SCORING : Introduce Transaction ID for Conversion Deduplication in GHL
A
Arnaud UTILLE
Hi everyone,
I'd love to suggest introducing a "Transaction ID" concept into GoHighLevel workflows to help accurately track conversions and avoid duplicate counting.
Why is this useful?Imagine you score user logins, but only once per day per user. Currently, it's challenging without complex workarounds. If we had a transaction ID like userID-dayOfYear (e.g., 455-3 for user #455 on January 3rd), GHL could easily prevent double-counting.
This would simplify accurate scoring, enhance reporting clarity, and improve campaign effectiveness.
Would anyone else find this helpful?
Thanks!
Log In
A
Arnaud UTILLE
Just like GA4 does