-
|
In the documentation its mentioned that the client does de-duplication of identical events and that it does this by holding the 2nd and any further identical events over a 60 second period and increments the count. Theres no mention that I could find on how a custom client would pass this count on to the server. Is it just a field in the JSON, or a header and if so are you able to provide some details so I could implement it on my custom client. Also, for usage stats, you send a message with a type of "Usage" but where do you put the usage name ? I have tried in the message and in a tag but all entries seem to be bundled together. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
I found the usage problem I was having. The type needs to be "Usage" as "usage" doesnt seem to work. Also, you need to specify a source with the name of the feature. Still haven't found a solution for the de-dupe |
Beta Was this translation helpful? Give feedback.
-
|
De-dupe is a purely client side thing. The client is storing a hash signature of each event as it's being submitting and checking against that to avoid sending the exact same event. |
Beta Was this translation helpful? Give feedback.
-
Please let us know if you have any other questions. |
Beta Was this translation helpful? Give feedback.
Please let us know if you have any other questions.