• About Us
  • Blog
  • Basket
  • Account
  • Sign In
  •  

Forums

PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 07 Jul 2017 07:07 AM by  gib
How to identify failed device detections
 4 Replies
Sort:
You are not authorized to post a reply.
Author Messages

gib



New Member


Posts:3
New Member


--
22 Jun 2017 12:35 PM
    Hello,

    What would be the best way to identify a failed/not correct detection?

    Thank you in advance.
    0

    Joseph Dix



    New Member


    Posts:21
    New Member


    --
    23 Jun 2017 10:09 AM
    Hi,

    Thanks for contacting 51Degrees.

    When performing a detection the 51Degrees API returns a match object. In this object there is a field called Match Method. This field will allow you to determine how confident the API is with the detection. The 4 methods are Exact, Nearest, Numeric and Closest. There is a fifth outcome as well called 'None' where the API has not been ale to find a match. This page on our site describes each method in detail: https://51degrees.com/support/docum...on/pattern

    For an example on how to use the Match Methods, take a look at our Match Metrics example here: https://51degrees.com/Developers/Do...ch-Metrics

    Let me know if you have any further questions.

    Kind regards,
    Joe

    0

    gib



    New Member


    Posts:3
    New Member


    --
    03 Jul 2017 09:32 AM
    Hello Joe,

    thank you for the reply. Unfortunately the approach with the match methods seems not really work properly.
    I'm not sure, maybe I'm doing something wrong but I tried to pass a random character String and the method was not "None".

    I'm trying to find out the amount of failed matches but even for obviously wrong/bad user agents the match seems to result in "Desktop".

    Best regards,

    Grigorij
    0

    Joseph Dix



    New Member


    Posts:21
    New Member


    --
    05 Jul 2017 01:21 PM
    Hi Grigoij,

    Strictly speaking, anything but an Exact match could be considered a failed match, you could try excluding everything that isn't. As for why random strings seems to come back as desktop, well the 51Degrees API strives to come back with a result. When you have a string, say: 'yqvwkvuvmk', it matches the 'yq' part because there is a User-Agent that exists which comprises of that string of characters. The rest of the characters are ignored as they are unimportant to the detection.

    You may find the User-Agent tester on our site useful: https://51degrees.com/resources/use...ent-tester

    Kind Regards,
    Joe
    1

    gib



    New Member


    Posts:3
    New Member


    --
    07 Jul 2017 07:07 AM
    Hi Joe,

    thank you very much for the explanation.

    Best regards,

    Grigorij
    0
    You are not authorized to post a reply.