Woopra Analytics is rendering a cookie id instead of a userid

[kim-tsao]

/kind bug

Which area this bug is related to?

/area registry
/area telemetry

Bug Summary

Describe the bug:

Woopra is displaying visitors with cookie ids instead of visitor ids. This is a problem since the cookie ids are not part of the visitor schema, we may run into issues analyzing the data or producing reports

To Reproduce:

Expected behavior

Any logs, error output, screenshots etc? Provide the devfile that sees this bug, if applicable.

Additional context

Any workaround?

Suggestion on how to fix the bug

[kim-tsao]

Woopra support suggested we use an identify call before calling our track event. This approach forces the userid to be set in local storage (as part of the traits object) which eventually gets passed to Woopra and the events are now rendered correctly.