In the previous version of the people search API (people_v2_search) the following query worked successfully, and gave me the correct results:

curl -i 'https://query.kissmetrics.com/v2/products/PRODUCT-ID/reports/REPORT-ID/run'  \
  -H 'Authorization: Bearer MY-API-TOKEN'  \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json'  \
  -X POST  \
  -d '{"start_date": "START-DATE", "end_date": "END-DATE"}'

where the start_date and end_date data is in the ISO 8601 format (e.g.: 2016-05-14T00:00:00+01:00)

Now that some of our products only have reports of type people_v3_search, the request above seems to ignore the data sent with the request (start_date & end_date), and just default to the date parameters set to in the kissmetrics reports admin/website.

I've also tried to use the alleged new format to run the report (retrieved using the products/PRODUCT-ID/reports request on the product):

curl -i 'https://api.kissmetrics.com/query/reports/REPORT-ID/run'  \
  -H 'Authorization: Bearer MY-API-TOKEN'  \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json'  \
  -X POST  \
  -d '{"start_date": "START-DATE", "end_date": "END-DATE"}'

And it always returns:

{"meta":{"status":400,"message":"Error initializing report: Only people search reports supported at this time.","errors":["bad_request"]},"links":[]}

I was wondering if the request parameters have changed/the way I built the request is now wrong and if there is any documentation on how to run the new people_v3_search reports that you can point me to for any reference (as I failed to find one anywhere).

Hope you can help,
Dennis

You recommend that we go to a URL at the end, but the URL is broken :-/

This is the URL I'm referring to: http://support.kissmetrics.com/misc/event-library

Add swiftype include data-attribute to main column; remove all other swiftype exclude data-attributes

The nature of our app is such that users use it generally while disconnected from the 'Net. Are there any limits on how many events you'll store while offline, for later transmission?

There's a little documentation page about hosting the JavaScript library yourself, but no download links (and possibly extra instructions on including it in the page) are provided.

https://github.com/kissmetrics/km-support/blob/gh-pages/_posts/2012-10-19-hosting-js-yourself.md

You could add some 3rd-party libraries to download (eg what you do here: http://support.kissmetrics.com/apis/other).

Sass, Less, Google Closure

I was trying to figure out how churn is calculated; in the Quick Reference table, Churn is linked:
http://support.kissmetrics.com/tools/revenue-report.html#churn__what_about_customers_who_stop_paying ... but that link doesn't go anywhere.

The description of churn in that table reads, "How this is counted depends on whether you are using your report configurations." Whether or not I am using my report configuration? or HOW I am configuring the report? This is unclear.

Hi, can you please add some docs on querying metrics? (Or link me to the page I'm struggling to find if it exists)

Also how do I query a metric and get a total value back?

If I request a metric I get back a link

{
        "name": "Metrics Over Time Query",
        "rel": "metric-over-time",
        "href": "https://api.kissmetrics.com/query/metrics/4ec26890-b767-0132-875f-22000ab4dcd7/over-time",
        "templated": false
    }

which I've had to hack around with to find I need to POST to with start_at and end_at date in the body. However I now want a total for the range like I get from the UI (see below)

However the API just seems to return me

[{"timestamp":"2015-10-14","year":2015,"month":10,"day":14,"value":12}]

(after jumping through the status update/results request cycle)

So how do I ask the API to give me a total? Because the total is obviously unique users, where as if I add up the various values they won't be unique.

Hope you can help
Steve

http://kissmetrics-support-files.s3.amazonaws.com/assets/troubleshooting/advanced-properties/advancedproperties1.png
http://kissmetrics-support-files.s3.amazonaws.com/assets/troubleshooting/advanced-properties/advancedproperties2.png
http://kissmetrics-support-files.s3.amazonaws.com/assets/troubleshooting/advanced-properties/advancedproperties3.png
http://kissmetrics-support-files.s3.amazonaws.com/assets/troubleshooting/advanced-properties/advancedproperties4.png
http://kissmetrics-support-files.s3.amazonaws.com/assets/troubleshooting/advanced-properties/advancedproperties5.png

Hi, I'm trying to extract the results of a people report and seem to be following the steps you outline correctly but in the final step I don't get any results. Can you see what the problem is? Thanks in advance.

curl -i 'https://query.kissmetrics.com/v2/products/6693c344-ab13-1030-97f2-22000a91b1a1/reports/4e128050-1ed8-0132-72e3-22000ab4dcd7/run'  \
  -H 'Authorization: Bearer  XXXX_XXXXX_XXXX'  \
  -H 'Content-Type: application/json'  \
  -X POST  \
  -d '{"start_date": "2015-06-01T20:00:00-04:00", "end_date": "2015-08-01T19:59:59-04:00"}'


curl -i 'https://query.kissmetrics.com/v2/queries/f3eb894b-7688-49d8-8950-dd1d5da136bc/status'  \
  -H 'Authorization: Bearer XXXX_XXXXX_XXXX'


curl -i 'https://query.kissmetrics.com/v2/queries/f3eb894b-7688-49d8-8950-dd1d5da136bc/results'  \
  -H 'Authorization: Bearer XXXX_XXXXX_XXXX'

HTTP/1.1 200 OK
Cache-Control: max-age=0, private, must-revalidate
Content-Type: application/json; charset=utf-8
Date: Wed, 20 Jan 2016 20:16:02 GMT
ETag: "9709970ac74827545a69b0c646f5a18d"
Link: <https://query.kissmetrics.com/v2/queries/f3eb894b-7688-49d8-8950-dd1d5da136bc/results?limit=50&offset=0>; rel="self"; templated="false",<https://query.kissmetrics.com/v2/queries/f3eb894b-7688-49d8-8950-dd1d5da136bc/export>; rel="export"; templated="false"
Server: nginx/1.0.15
Status: 200 OK
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
X-Request-Id: 9b917b51-e39f-4cb1-830f-9e1857322417
X-Runtime: 0.832931
X-XSS-Protection: 1; mode=block
Content-Length: 400
Connection: keep-alive

{"meta":{"status":200},"data":[],"pagination":{"limit":50,"offset":0,"total":0},"links":[{"name":"Self","rel":"self","href":"https://query.kissmetrics.com/v2/queries/f3eb894b-7688-49d8-8950-dd1d5da136bc/results?limit=50\u0026offset=0","templated":false},{"name":"Export","rel":"export","href":"https://query.kissmetrics.com/v2/queries/f3eb894b-7688-49d8-8950-dd1d5da136bc/export","templated":false}]}

What's the behavior of KISSMetrics when it detects a duplicate event; will one clobber the other, or will you merge metadata from both?

For instance, say I send an event from the browser using the JS API, but send the same event with the same params/timestamp from the server. Will one clobber the other, or will I get the browser-y metadata from the JS API tracking call merged with the server tracking call?

Filing this here, because the documentation on de-duping doesn't cover this.

Could we look at improving the navigation/usability of our sidenav?

Example:

Hello,

I'm trying to upload survey results to kissmetrics with csv way however it's written "You can include up to 10 property columns."

As you can understand that surveys generally more than 10 questions and answers. We thought to add survey questions with "prob:"

Do we can do that?

Seeing a dead link (http://support.kissmetrics.com/data/data-export-setup) on this page http://support.kissmetrics.com/apis/data/

Looking at the source of the tracking script, one could adapt our helper functions to replicate our trackSubmit function, but in jQuery:

$('form').submit(function(event) {  // modify the jQuery selector if needed
  var props = {'foo':'bar'};  // define any initial KM properties here
  if ( typeof(KM_SKIP_FORM_FIELDS) == 'undefined' || !KM_SKIP_FORM_FIELDS)
    {
      var form;
      // KM.sre(event) finds the originating element that triggered an event
      if ( form = KM.sre(event) )
        // KM.fp(form) returns the hash of properties found from scanning the form inputs
        // KM.mg(hash1, hash2) merges two hashes together
        props = KM.mg(props, KM.fp(form));
    }
  KM.record('Form Submitted', props)  // indicate the name of the KM event to record
});

The question is whether we ought to support calling our helper functions directly.

1. You may want to update this to reflect new Google Tag Manager user interface.
2. Can you clarify whether the KissMetrics tag needs to be added above the Google Analytics tag? I believe there are instructions to this effect when you sign up for a Kiss Metrics trial. If so, how does one accomplish this if one is using Google Tag Manager?

I'm using jQuery.trigger() to fire an event when the KM object is ready. That allows me to wrap code that needs a callback in a jQuery ready function. I could see this method being really useful to folks so you may want to add to documentation on callbacks if you agree.

Step 1: Trigger the event right after the Kissmetrics Library Call:

_kmq.push(function() {
    $.event.trigger("kmLoaded");
});

Step 2: For stuff that requires the KM object to be ready, wait for that custom event:

$("body").on("kmLoaded", function() {
   doStuff;
});

Another idea would be to fire your own events as part of the Kissmetrics library, then provide documentation so users know what events they can bind to.

At http://support.kissmetrics.com/use-cases/roi-campaigns.html, it says to click the Revenue tab. We no longer have a revenue tab. Revenue has been moved under the Reports tab.

The link on the page http://support.kissmetrics.com/integrations/qualaroo.html should actually point to http://help.qualaroo.com/hc/en-us/articles/201541157-Publishing-Qualaroo-Data-To-KISSmetrics as the existing one is broken.

I might be missing something, but the PHP API documentation points to the kissmetrics/kissmetrics-php repo. However, the API described in the documentation doesn't appear to resemble the API in the code at all. For example there is no KM class, nor even a km.php file.

Is it possible to have the PHP API doc updates to reflect the current API?

http://support.kissmetrics.com/api-update.html#request-3

For this query:
https://query.kissmetrics.com/v2/queries/6ba99c31-1456-4684-8d2b-29ba09670ca9/results?offset=50&limit=50

Response is

{
    "meta":{
      "status":400,
      "message":":offset must be an integer",
      "errors":"invalid_parameter"]
    },
    "links":[]
}

offset is integer

It should be easier to tell what code snippets should belong where.

The regex that's putting the script tag after the a tags are causing issues w/ some other JavaScripts.

Can this be changed so that instead of a tag followed by script tag, that at the end of the content a single script tag is placed w/ each of the push calls foreach of the matched links in the content?

Hi, I'm not sure what's the best way to refer to a given file, but let's give it a try...

On the Common Methods docs, you're missing the alias method. It is not mentioned anywhere while most libs offer it.