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
{{ message }}
This repository has been archived by the owner on Mar 1, 2019. It is now read-only.
Tried to pass an address object however this is can not be translated into seperate object into woopra.
[object Object] is what is seen in woopra under user address field.
This is what is passed from Segment:
address: {
city: 'Amsterdam',
country: 'NL',
county: 'Noord-Holland',
housenumber: '',
postalcode: '1032 HP',
street: ''
},
** taken out as personal info.
Should we just not use objects?
The text was updated successfully, but these errors were encountered:
@jpknegtel if the tool doesn't support a certain data structure, we should be flattening/coercing them into something readable by the tool. It's worth mentioning, however, that it may not be ideal for downstream analysis.
Hi @jpknegtel, as part of the monorepo migration, this issue has been moved to new issue. Our engineers have been notified and will prioritize and work on it ASAP. Thank you!
Tried to pass an address object however this is can not be translated into seperate object into woopra.
[object Object] is what is seen in woopra under user address field.
This is what is passed from Segment:
address: {
city: 'Amsterdam',
country: 'NL',
county: 'Noord-Holland',
housenumber: '',
postalcode: '1032 HP',
street: ''
},
** taken out as personal info.
Should we just not use objects?
The text was updated successfully, but these errors were encountered: