{"id":2044,"date":"2020-10-08T12:56:25","date_gmt":"2020-10-08T03:56:25","guid":{"rendered":"https:\/\/mem.quarka.org\/manual\/about-the-communication-done-by-qa-heatmap-analytics\/"},"modified":"2022-12-15T18:04:23","modified_gmt":"2022-12-15T09:04:23","slug":"about-the-communication-done-by-qa-heatmap-analytics","status":"publish","type":"ht_kb","link":"https:\/\/mem.quarka.org\/en\/manual\/about-the-communication-done-by-qa-heatmap-analytics\/","title":{"rendered":"The communication performed by QA Analytics"},"content":{"rendered":"\n<p>QA Analytics communicates mainly in three ways: with site readers (visitors), with administrators on the administration screen, and with license authentication.<\/p>\n\n<h2 id=\"communication-with-site-readers-viewers-side\" >Communication with site readers (viewers) side<\/h2>\n\n<p>When a reader visits a site with QA Analytics installed, JavaScript in QA Analytics runs in the reader&#8217;s browser and performs the standard WordPress Ajax communication asynchronously every few seconds.<\/p>\n\n<p>The data sent from the reader browser through Ajax communication includes scroll position and clicked DOM data. The content is mainly text, often only a few tens or hundreds of bytes in size, and does not occupy or burden the communication bandwidth.<\/p>\n\n<h2 id=\"communication-with-the-administrator-side-and-the-admin-screen\" >Communication with the administrator side and the admin screen<\/h2>\n\n<h3 id=\"overview-of-the-process-in-the-administration-screen\" >&#8211; Overview of the process in the administration screen<\/h3>\n\n<p>On the admin screen, QA Analytics primarily accesses data stored in the DB to display site access status and heatmaps, which are then processed for graphs and other visualizations.<\/p>\n\n<p>Since this large processing volume may overload the DB, QA Analytics responds by creating cache files for frequently used functions.<\/p>\n\n<h3 id=\"about-communications\" >&#8211; About Communications<\/h3>\n\n<p>The data required for drawing, which is loaded from the cache file, is sent from the server to the administrator&#8217;s browser, and the drawing process is mainly performed by the JavaScript in the administrator&#8217;s browser.<\/p>\n\n<p>Therefore, there is no load on the server for general processing. Still the larger the data volume, the more communication with the administrator&#8217;s browser, so it may take longer to display. However, during this time, the server database is not accessed unless complex data display processing is performed, so you can browse at any time.<\/p>\n\n<h2 id=\"communication-during-license-authentication\" >Communication during license authentication<\/h2>\n\n<p>For users of the licensed version of QA Analytics, license activation is performed once a day, at a fixed time for each server. If you are using the free version, there will be no communication associated with the activation.<\/p>\n\n<p>The communication that takes place during license authentication is mainly text data exchange, which is small in size, only a few kilobytes, and takes place once a day, so it would not be a particular problem.<\/p>\n","protected":false},"author":1,"comment_status":"closed","ping_status":"closed","template":"","format":"standard","meta":{"_bbp_topic_count":0,"_bbp_reply_count":0,"_bbp_total_topic_count":0,"_bbp_total_reply_count":0,"_bbp_voice_count":0,"_bbp_anonymous_reply_count":0,"_bbp_topic_count_hidden":0,"_bbp_reply_count_hidden":0,"_bbp_forum_subforum_count":0},"ht_kb_category":[333],"ht_kb_tag":[],"uagb_featured_image_src":[],"uagb_author_info":{"display_name":"QA Analytics Support","author_link":"https:\/\/mem.quarka.org\/en\/author\/qa-analytics-support\/"},"uagb_comment_info":0,"uagb_excerpt":"QA Analytics communicates mainly in three ways: with site readers (visitors), with administrators on the administration screen, and with license authentication. Communication with site readers (viewers) side When a reader visits a site with QA Analytics installed, JavaScript in QA Analytics runs in the reader&#8217;s browser and performs the standard WordPress Ajax communication asynchronously every&hellip;","_links":{"self":[{"href":"https:\/\/mem.quarka.org\/en\/wp-json\/wp\/v2\/ht_kb\/2044"}],"collection":[{"href":"https:\/\/mem.quarka.org\/en\/wp-json\/wp\/v2\/ht_kb"}],"about":[{"href":"https:\/\/mem.quarka.org\/en\/wp-json\/wp\/v2\/types\/ht_kb"}],"author":[{"embeddable":true,"href":"https:\/\/mem.quarka.org\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/mem.quarka.org\/en\/wp-json\/wp\/v2\/comments?post=2044"}],"version-history":[{"count":9,"href":"https:\/\/mem.quarka.org\/en\/wp-json\/wp\/v2\/ht_kb\/2044\/revisions"}],"predecessor-version":[{"id":3632,"href":"https:\/\/mem.quarka.org\/en\/wp-json\/wp\/v2\/ht_kb\/2044\/revisions\/3632"}],"wp:attachment":[{"href":"https:\/\/mem.quarka.org\/en\/wp-json\/wp\/v2\/media?parent=2044"}],"wp:term":[{"taxonomy":"ht_kb_category","embeddable":true,"href":"https:\/\/mem.quarka.org\/en\/wp-json\/wp\/v2\/ht_kb_category?post=2044"},{"taxonomy":"ht_kb_tag","embeddable":true,"href":"https:\/\/mem.quarka.org\/en\/wp-json\/wp\/v2\/ht_kb_tag?post=2044"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}