The integration is overwriting an asynchronous queue

[lucasoptimizely]

@hankim813 The Kissmetrics integration is ignoring all information set before Segment is loaded by executing this line in initialize: window._kmq = []; here: https://github.com/segment-integrations/analytics.js-integration-kissmetrics/blob/master/lib/index.js#L50

This breaks the Optimizely/Kissmetrics integration. Is it possible to fix this?

[hankim813]

Ahhh so we should be doing window._kmq = window._kmq || [];?

[lucasoptimizely]

To be honest: I think that should work but I haven't read through the
entire code of the integration. I was just looking for scripts that were
overwriting the _kmq variable and found this line.

On Wed, Jun 15, 2016 at 8:27 PM, Han notifications@github.com wrote:

Ahhh so we should be doing window._kmq = window._kmq || [];?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#17 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/ADv9sWnYpVwJTkv7Tqt496VUxPSv0NNtks5qMMKagaJpZM4I2-pD
.

Lucas Swartsenburg
Partner Solution Architect | Optimizely, Inc. http://www.optimizely.com/
lucas@optimizely.com | (1) 415 996 97 96
We're hiring! http://www.optimizely.com/jobs Talk to me if you're
interested!

[chriso]

This was fixed in d1e7b30.

[hankim813]

@lucasoptimizely yep will close this once the fix is deployed. Right now we're undergoing a rollout of new version of analytics.js so I'm hoping to be able to release the new KM fixes/changes sometime next week

[SegmentDestinationsBot]

Hi @lucasoptimizely, 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!

For more information, see README.md.