FAQ

1. IS THERE ANY TEST PERIOD?
   In order to receive a test period please contact: sales@statscore.com or visit our website: statscore.com/products/livematchpro.
   

2. WHO IS USING YOUR SERVICES?
   We have many customers from affiliates, sports portals or bookmakers.
   

3. WHAT KIND OF INFORMATION IS INCLUDED?
   Innovative extended version of a traditional livescore, including attack visualizations and positional data of all important event incidents. All stats and incidents from the selected event are being delivered in real-time. The tracker posses head to head comparisons or all sort of standings from the biggest range of sports on the market.
   

4. CAN I USE LIVEMATCHPRO TRACKER IN BETTING SHOPS?
   Yes, the trackers can be used in Betting Shops or Self Service Betting Terminals (SSBT).
    

5. DO I NEED TO HOST IT ON MY OWN SERVER?
   No, it's a hosted solution, everything is on our servers.
    

6. ARE YOUR SERVICES CUSTOMIZABLE?
   Yes, you can choose layout, colours, icons etc.
   

7. IS IT POSSIBLE TO PLACE ADVERTISING BANNERS?
   Although the tracker is generally a small widget and has other purposes, we found a place to put two small advertising slots on the bands below the pitch. We can put the adverts there during the integration process (bands can be requested or switched off).
   

8. HOW MANY LANGUAGES DO YOU COVER?
   We support over 30 languages (here you can find the full list). We are able to have any language ready for you in two weeks. By default, the content will be displayed in English.
   

9. DO YOU HAVE A MOBILE VERSION?
   We provide our content solutions in a responsive design, this means the LivematchPro Trackers will fit and work perfectly on mobile devices.
    

10. WHAT ARE THE TRACKER SIZES?
    LivematchPro Tracker has no defined values for width and height because it has a responsive design. This means the Tracker will always adapt to the size of the section element (Tracker placeholder).
    

    Size limits for Natural version:

    • 320px - minimum width no matter what the sport is (the trackers will not be visible below this value)

    • minimum height for Natural trackers depends on the width:
      

      • 345px for 320px - 479px range

      • 395px for 480px - 599px range

      • 490px for 600px >= rang

    Size limits for Lite version:

    • 320px - minimum width no matter what the sport is (the trackers will not be visible below this value)

    • 305px - minimum height for all the sports
      

11. HOW LONG DOES IT TAKE TO INTEGRATE THIS SOLUTION?
    As shocking as it sounds, it shouldn't take more than a few hours on our side. On client's side it just involves placing two elements into the source of the website, a small HTML and a JavaScript code. If the client wants special customization we will need to estimate how long it will take, it depends on the customization level, but even then it should not make the integration process much longer.
     

12. DO I NEED YOUR IDENTIFIERS TO PLACE THE VISUALIZATION?
    You can use both - YOURS and STATSCORE’s identifiers in the placement scripts. You can set the type of used Identifiers by parameter: data-use-mapped-id.
    

13. HOW DO I FIND YOUR EVENT IDENTIFIERS?
    In the administration panel: https://backoffice.statscore.com/livescorepro/admin/lmp/events there is an information about the ID of each event booked. We also provide a JSON feed in our API, from which you can get the identifiers based on your event ID. The method is called: booked-events.index.
    

14. HOW TO USE SPORTSAPI - BOOKED-EVENTS.INDEX METHOD?
    The API method: booked-events.index shows list of all events available for the client. Please note the list could be paginated.
    

    Example: https://api.statscore.com/v2/booked-events.xml?product=livescorepro&events_details=no&client_id=X

    In the above example: 
    X - should be replaced by your individual client identifier (client ID)
     

    STATSCORE EVENT ID

    In the returned data you will find your event ID in the field "client_event_id". STATSCORE EVENT ID is placed in the corresponding field "id".

    JSON example: [{"id":2107848,"client_event_id":"345397"}]

    Detailed information about the method (output elements, possible filters etc.) is included in proper section of this documentation.
    

15. HOW TO FIND SINGLE EVENT ID WHEN I GOT MY EVENT IDENTIFIER?
    When STATSCORE events offer is mapped with the clients events identifiers you can use booked-events.index method to find your event. You should use query parameters: client_id and client_event_id to find the event you want.
    

    Example: https://api.statscore.com/v2/booked-events.xml?product=livescorepro&events_details=no&client_id=X&client_event_id=Y

    In the above example: 

    X - should be replaced by your individual client identifier (client ID)
    Y - should be replaced by your event identifier (event ID)

    Please note: if the event is not mapped with STATSCORE ID then you will get empty <data/> node.
    

16. WHAT ARE THE POTENTIAL ERRORS IN THE PROCESS OF INTEGRATION?
    The table below shows possible errors which can be displayed in the browser console during the Tracker integration.

The message is visible in the console browser (F12).

e.g.:

1. WHAT ARE THE TRACKER CONFIGURATION PARAMETERS?
   The list below explains the parameters of the Tracker (Tracker placeholder script).
   

• id - it's a unique identifier for the Tracker on your website (in your DOM).
  You can display a few different Trackers at once, but each of them should have a unique id.

• data-event – STATSCORE's unique identifier for the event (match). It should be a numeric value.

• data-config - unique identifier of the client's configuration.
  This value is given by STATSCORE to customers. You can have many configurations for the LivematchPro Tracker. By default, STATSCORE prepares one configuration for each customer.

• data-lang - sets the language in which the LivematchPro Tracker will be generated. The default value is "en" (English).

• data-zone - optional parameter to set timezone. If set, then the event start date will be converted to the proper time for selected timezone. 
  If timezone parameter isn't set or is set as an empty value (time zone='') then the timezone will be automatically detected by the system.