@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?

From @reinpk on June 27, 2014 14:46

https://github.com/segmentio/analytics.js-integrations/blob/master/lib/kissmetrics/index.js#L65

should call .page() rather than .trackPage(), otherwise the default pageview doesn't get generated at all (here I have to manually trigger it from the console on our own site):
https://cloudup.com/cX6Q4dbQ4U2

our kissmetrics account shows no default pageviews either, and a helpful user pointed out that they're not seeing them either

Copied from original issue: segmentio/analytics.js-integrations#250

I was tracking "Completed Order" from the client side with analytics.js, sending the revenue property, but I noted Segment wasn't "translating" that into KM's "expected" (configurable, but still) Billing Amount property.

I changed to start tracking the same event from my server using your analytics-ruby gem, sending exactly the same properties and then the Billing Amount property started being sent correctly to KISSmetrics.

Here you have proof from KM's live view:

So I conclude your JS integration has some bug. Right?