You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, there are two segments per custom variable slot in the DB (one for name and one for value). These segments look only for custom variables in a specific slot, so if a user tracks the same custom variable to two different columns, custom variable segmentation breaks. This is counter-intuitive, just because a custom variable pair is stored in two different places, doesn't mean they shouldn't be considered the same. It's also more complicated to track.
Ideally, there should be just two segments customVariableName and customVariableValue. The segments could result in an SQL OR across all available custom variable columns.
The text was updated successfully, but these errors were encountered:
diosmosis
added
the
duplicate
For issues that already existed in our issue tracker and were reported previously.
label
Feb 11, 2015
Currently, there are two segments per custom variable slot in the DB (one for name and one for value). These segments look only for custom variables in a specific slot, so if a user tracks the same custom variable to two different columns, custom variable segmentation breaks. This is counter-intuitive, just because a custom variable pair is stored in two different places, doesn't mean they shouldn't be considered the same. It's also more complicated to track.
Ideally, there should be just two segments
customVariableName
andcustomVariableValue
. The segments could result in an SQLOR
across all available custom variable columns.The text was updated successfully, but these errors were encountered: