Recherche avancée

Sur d’autres sites (793)

• 10 Proven Ways Heatmaps Improve Website Conversions

  20 septembre 2021, par Ben Erskine — Analytics Tips, Plugins, Heatmap
  

  Heatmap analytics are critical in improving website conversions. Why ? Because they provide customer-centric insights. 

  In the online market, businesses that are customer-centric are 60% more profitable than businesses that are not.

  Using heatmaps to track factors such as usability, compare A/B landing pages and content engagement across channels optimises online conversions by addressing issues faced by real users. 

  How heatmaps benefit your customers

  Customer experience is one of the most important factors in business success. 

  Website heatmap software like Matomo offers unique insights into customer behaviour that is then used to improve their experience, usability and engagement. 

  Data analysis captures information on how many people complete a sales funnel or bounce from a website. Behavioural analytics like heatmaps can show you why they bounce.

  This benefits your customers (and therefore your bottom line) because it puts the focus on them and their needs.

  10 ways heatmap analytics help increase website conversions

  #1. Improve UX/Usability 

  Heatmap analytics improve usability by identifying where you are losing customers on your website.

  Forrester research indicates that improving user experience can improve conversions by up to 400%, and on average every $1 spent on UX has a return of $100. 

  For example, you may have a CTA button but customers never click it to reach the payment page. 

  Heatmaps show you how customers interact with your website naturally so that you can adjust it according to their needs.

  Using heatmap analytics to improve usability boosts conversions because it improves customer experiences. 88% of online consumers say that they wouldn’t even bother returning to a website after a bad experience. 

  #2. Website design and content structure 

  Another way that heatmaps can improve conversions is to analyse your website design and content structure. 

  You might be wondering how often a specific ad or a banner was displayed and viewed by your visitors on any of your pages and how often a visitor actually interacted with them. These two parts of the analysis are called content impression and content interaction.

  Ideally, your website elements such as banners, listings, buttons and thumbnails will entice customers to click and find out more. 

  Heatmaps and click maps analyse

  1. How many impressions the content has (e.g. a banner), and
  2. What percent of users that see the content click on it 

  For example, you may have a banner with high impressions but low click-through rates. Tracking content interactions optimises your website by showing which elements or CTAs need more visibility. 

  #3. A/B testing

  Heatmaps provide invaluable data on which landing pages are converting the best. Not only that, but session recordings and heatmap data can show you exactly why one is converting better so that you can replicate the results to increase conversions on other landing pages.

  Tracking heatmap updates on different versions of the same sales page will help confirm creative solutions faster than feedback alone. 

  Ultimately this kind of comparison increases your ROI faster because you are not guessing why some customers are converting and others are not. 

  #4. Conversion Funnel

  Using heatmap software in sales funnels lets you visualise user behaviour at each stage of the conversion process. 

  For example, if many customers are dropping off a payment page, heatmaps can indicate whether it is a usability issue such as pop ups, lack of clarity with payment buttons or something web developers haven’t seen from the back end. 

  These analytics improve conversions by reducing friction in sales funnels as much as possible. 

  #5. Content engagement across channels 

  Optimising websites across all channels is now expected for online businesses. 

  Bad mobile optimisation annoys 48% of online shoppers, and if your web page takes longer than 3 seconds to load, 53% of visitors will simply click away. 

  You can use heatmaps to improve engagement by tracking mouse activity, clicks and scrolling. This helps improve conversions by confirming 

  • How invested a user is in the page 
  • How easy it is to navigate your website and content on different devices 
  • What is your most viewed content and what to push more of 
  • How users generally move through your website on different devices 
  • How clear your messaging is (e.g. high click through rate but low engagement could indicate they aren’t finding what they’re looking for once they click on a CTA)

  #6. Above the fold analysis 

  Although a well-used web development term, above the fold is still one of the most important factors in heatmap analysis. 

  Above the fold analysis gives you insight into a customer’s first impression of a page. 

  An example of above-the-fold heatmaps in action could be a page with a video explanation. Say you have a landing page with a video below the fold that explains why someone should buy and has a CTA button underneath. If there are a lot of page visitors but very few people scrolling below the fold, you can see why hardly any visitors are watching the video or engaging with the CTA button. 

  Insights like this would inform further development such as including important video content above the fold or updating header copy to encourage visitors to scroll down the page more often.

  

  #7. Session recording

  Recording features go hand in hand with heatmap visualisations. Recording features like Session Recording shows the flow of each user’s time on your website. 

  For example, a session recording replays all clicks, mouse movements, scrolls, window resizes, form interactions, and page changes (e.g. when a popup appears).

  #8. Scroll heatmap 

  A scroll heatmap shows the percentage of people that have seen a part of the page. 

  For example, the top of a website page will be the “hottest” in a scroll heatmap, and it naturally gets “colder” further down.

  Tracking this shows whether customers are staying on the page, whether they are only seeing information above the fold, and whether sales pages are engaging. 

  It is an effective strategy for improving sales pages because it shows where customers are losing interest and which elements receive the most engagement.

  

  #9. Records clicks 

  With a click heatmap, you can find out what your visitors think is clickable on a webpage.

  This improves conversions in two ways. 

  Firstly, it shows whether customers are clicking where you expect them to. For example, if you create a “buy now” or “free trial” button but nobody ever pushes it, it informs your back end developers that it needs an upgrade. 

  Secondly, it indicates any user experience issues. If there are a lot of clicks on an element that doesn’t link anywhere, it shows that it either needs to be changed or have a link included because customers are trying to engage with it. 

  For even more accurate data, combine click maps with hover maps. This shows where users are paying attention but not clicking through. 

  #10. Records mouse movement/hovering

  Is your website distracting users from the ultimate goal of converting ? Does your website have a logical flow and next step ? Recording mouse movement and attention will help you answer questions like these. 

  Mouse move and hover heatmaps identify where your website visitors engage on the page. Are they naturally drawn to your CTAs ? Is the sidebar taking their attention away from the primary content ? 

  This data increases the likelihood of conversions because it shows where you need to remove distractions or draw their attention in. 

  

  Final thoughts on heatmap analytics 

  Heatmap analytics benefit both you and your customers. By identifying issues that stop them from buying and optimise their engagement, you’ll have happy customers and happy stakeholders. 

  Next, check out these guides on heatmap software and using user behaviour analytics to increase conversions and improve customer experience !

  The Ultimate Guide to Heatmap Software

  Heatmap Video

  Session Recording Video

• Power-Up your Matomo installation with Custom Reports

  13 novembre 2017, par InnoCraft — Plugins

  Would you like to create a report in Matomo (Piwik) with just the data you want and nothing else ? Would you like to be free to decide the shape of it ? Are you struggling with the Matomo database and wish you could have an easy interface to create the report you want ? Are you tired of exporting your data in a spreadsheet ? Since last October, there’s a solution and it’s called Custom Reports.

  With custom reports you will :

  1. get a user-friendly interface to create the report you wish
  2. see all the possible combinations to create the report you desire
  3. reveal new data combinations which were not directly available in Matomo (Piwik)

  User friendly interface

  The time when you created your reports from MySQL database is over. Now with custom reports you can create the report you want and get the data you need in just a few seconds.
  Custom reports are part of the main user interface. You can access them in just one click :

  

  As you can see from above the interface is straightforward, just indicate the name of your report and start to select the dimensions and metrics you would like to see.

  See all the possible combinations to create the report you desire

  As a user the big question has always been, how much data does Matomo (Piwik) collect and where can I find a list of all those data points ? Here you have the solution. Matomo is gathering in custom reports all the possible combinations so you can select only the data you want :

  

  Creating such a report is going to take you no more than a minute. As with any reports within Matomo (Piwik), you can easily get information regarding the specific data you are using by hovering your mouse on the question mark next to each dimension and metric :

  

  Make new combinations which were not directly available in Matomo

  By default, not all combinations are possible within the Matomo (Piwik) user interface. Now thanks to Custom Reports, you can easily design the report you want. Here is for example a report crossing page titles and page url :

  

  You can then identify if there are any duplicate titles within your content and see the associated URL in a single report.

  You could also identify easily what are your most viewed entry page from Google :

  

  Custom reports can also be used with segments and filters in order to get even more specific data.
  Here we have an example of a custom report designed to take into consideration only the visits coming from Wikipedia :

  

  What is the next step ?

  As you understood it, Matomo (Piwik) custom reports is the must-have plugin in order to take your Matomo to the next level. Why wait ? Matomo custom reports are available through the marketplace.

  Get Custom Reports

  If you are not sure yet, you can always give it a try within our Matomo Cloud (formerly Piwik Cloud) infrastructure.

• Why X.Org's X Server has stopped working on Google Colab ?

  20 février 2021, par Rahul

  I am Using X server for the virtual screen on Google Colab and capturing that screen with ffmpeg to record it and live stream it to twitch. (for the reinforcement learning project)

  


  


  The above process was completely working till my last use of my Colab notebook (on mid-January 2021), but now (on 19th February 2021) I am using the same notebook and the streaming code has stopped working.

  


  


  I am adding config and log file data below. (I have never seen these files before because it was working, now it's not so I don't have any idea what wrong)

  


  The config file stored at /etc/X11/xorg.conf have the following data :

  


  # nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 418.67

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0"
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
EndSection

Section "Files"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/mouse"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "Unknown"
    HorizSync       28.0 - 33.0
    VertRefresh     43.0 - 72.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "Tesla T4"
    BusID          "PCI:0:4:0"
    MatchSeat      "seat-1"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "AllowEmptyInitialConfiguration" "True"
    SubSection     "Display"
        Virtual     1920 1080
        Depth       24
    EndSubSection
EndSection


  


  The log file stored at /var/log/Xorg.0.log have the following data :

  


  [   464.605] 
X.Org X Server 1.19.6
Release Date: 2017-12-20
[   464.605] X Protocol Version 11, Revision 0
[   464.605] Build Operating System: Linux 4.15.0-124-generic x86_64 Ubuntu
[   464.605] Current Operating System: Linux 9d3fe3949671 4.19.112+ #1 SMP Thu Jul 23 08:00:38 PDT 2020 x86_64
[   464.605] Kernel command line: BOOT_IMAGE=/syslinux/vmlinuz.A init=/usr/lib/systemd/systemd boot=local rootwait ro noresume noswap loglevel=7 noinitrd console=ttyS0 security=apparmor virtio_net.napi_tx=1 systemd.unified_cgroup_hierarchy=false systemd.legacy_systemd_cgroup_controller=false csm.disabled=1 dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 i915.modeset=1 cros_efi loadpin.enabled=0 root=/dev/dm-0 "dm=1 vroot none ro 1,0 4077568 verity payload=PARTUUID=555BDB75-CBD7-CD4A-B24E-29B13D7AC0DF hashtree=PARTUUID=555BDB75-CBD7-CD4A-B24E-29B13D7AC0DF hashstart=4077568 alg=sha256 root_hexdigest=42104d547ac104fb7061529e78f53e4f3e8c3d3cbb040dc6e0f84aad68491347 salt=9dc7f3acc4e2ce65be16356e960c2b21b51a917fa31d2e891fd295490c991e41" mitigations=off
[   464.605] Build Date: 30 November 2020  08:01:56PM
[   464.605] xorg-server 2:1.19.6-1ubuntu4.8 (For technical support please see http://www.ubuntu.com/support) 
[   464.605] Current version of pixman: 0.34.0
[   464.605]    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
[   464.605] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   464.605] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Feb 20 03:10:44 2021
[   464.606] (==) Using config file: "/etc/X11/xorg.conf"
[   464.606] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   464.607] (==) ServerLayout "Layout0"
[   464.607] (**) |-->Screen "Screen0" (0)
[   464.607] (**) |   |-->Monitor "Monitor0"
[   464.607] (**) |   |-->Device "Device0"
[   464.607] (**) |-->Input Device "Keyboard0"
[   464.607] (**) |-->Input Device "Mouse0"
[   464.607] (==) Automatically adding devices
[   464.607] (==) Automatically enabling devices
[   464.607] (==) Automatically adding GPU devices
[   464.607] (==) Automatically binding GPU devices
[   464.607] (==) Max clients allowed: 256, resource mask: 0x1fffff
[   464.607] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[   464.607]    Entry deleted from font path.
[   464.607] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[   464.607]    Entry deleted from font path.
[   464.607] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[   464.607]    Entry deleted from font path.
[   464.607] (WW) The directory "/usr/share/fonts/X11/Type1" does not exist.
[   464.607]    Entry deleted from font path.
[   464.607] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[   464.607]    Entry deleted from font path.
[   464.607] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[   464.607]    Entry deleted from font path.
[   464.607] (==) FontPath set to:
    /usr/share/fonts/X11/misc,
    built-ins
[   464.607] (==) ModulePath set to "/usr/lib/xorg/modules"
[   464.607] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[   464.607] (WW) Disabling Keyboard0
[   464.607] (WW) Disabling Mouse0
[   464.607] (II) Loader magic: 0x556eb77b8020
[   464.607] (II) Module ABI versions:
[   464.607]    X.Org ANSI C Emulation: 0.4
[   464.607]    X.Org Video Driver: 23.0
[   464.607]    X.Org XInput driver : 24.1
[   464.607]    X.Org Server Extension : 10.0
[   464.607] (EE) dbus-core: error connecting to system bus: org.freedesktop.DBus.Error.FileNotFound (Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory)
[   464.609] (--) PCI: (0:0:4:0) 10de:1eb8:10de:12a2 rev 161, Mem @ 0xc0000000/16777216, 0x380000000/268435456, 0x390000000/33554432
[   464.609] (II) no primary bus or device found
[   464.609] (II) LoadModule: "glx"
[   464.609] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[   464.610] (II) Module glx: vendor="X.Org Foundation"
[   464.610]    compiled for 1.19.6, module version = 1.0.0
[   464.610]    ABI class: X.Org Server Extension, version 10.0
[   464.610] (II) LoadModule: "nvidia"
[   464.610] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[   464.610] (II) Module nvidia: vendor="NVIDIA Corporation"
[   464.610]    compiled for 4.0.2, module version = 1.0.0
[   464.610]    Module class: X.Org Video Driver
[   464.610] (II) NVIDIA dlloader X Driver  418.67  Sat Apr  6 02:51:17 CDT 2019
[   464.610] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[   464.610] xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
[   464.610] (II) Loading sub module "fb"
[   464.610] (II) LoadModule: "fb"
[   464.611] (II) Loading /usr/lib/xorg/modules/libfb.so
[   464.611] (II) Module fb: vendor="X.Org Foundation"
[   464.611]    compiled for 1.19.6, module version = 1.0.0
[   464.611]    ABI class: X.Org ANSI C Emulation, version 0.4
[   464.611] (II) Loading sub module "wfb"
[   464.611] (II) LoadModule: "wfb"
[   464.611] (II) Loading /usr/lib/xorg/modules/libwfb.so
[   464.611] (II) Module wfb: vendor="X.Org Foundation"
[   464.611]    compiled for 1.19.6, module version = 1.0.0
[   464.611]    ABI class: X.Org ANSI C Emulation, version 0.4
[   464.611] (II) Loading sub module "ramdac"
[   464.611] (II) LoadModule: "ramdac"
[   464.611] (II) Module "ramdac" already built-in
[   464.637] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the
[   464.637] (EE) NVIDIA:     system's kernel log for additional error messages and
[   464.637] (EE) NVIDIA:     consult the NVIDIA README for details.
[   464.662] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the
[   464.662] (EE) NVIDIA:     system's kernel log for additional error messages and
[   464.662] (EE) NVIDIA:     consult the NVIDIA README for details.
[   464.662] (EE) No devices detected.
[   464.662] (==) Matched modesetting as autoconfigured driver 0
[   464.662] (==) Matched fbdev as autoconfigured driver 1
[   464.662] (==) Matched vesa as autoconfigured driver 2
[   464.662] (==) Assigned the driver to the xf86ConfigLayout
[   464.662] (II) LoadModule: "modesetting"
[   464.662] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[   464.663] (II) Module modesetting: vendor="X.Org Foundation"
[   464.663]    compiled for 1.19.6, module version = 1.19.6
[   464.663]    Module class: X.Org Video Driver
[   464.663]    ABI class: X.Org Video Driver, version 23.0
[   464.663] (II) LoadModule: "fbdev"
[   464.663] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[   464.663] (II) Module fbdev: vendor="X.Org Foundation"
[   464.663]    compiled for 1.19.3, module version = 0.4.4
[   464.663]    Module class: X.Org Video Driver
[   464.663]    ABI class: X.Org Video Driver, version 23.0
[   464.663] (II) LoadModule: "vesa"
[   464.663] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[   464.663] (II) Module vesa: vendor="X.Org Foundation"
[   464.663]    compiled for 1.19.3, module version = 2.3.4
[   464.663]    Module class: X.Org Video Driver
[   464.663]    ABI class: X.Org Video Driver, version 23.0
[   464.663] (II) NVIDIA dlloader X Driver  418.67  Sat Apr  6 02:51:17 CDT 2019
[   464.663] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[   464.663] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[   464.663] (II) FBDEV: driver for framebuffer: fbdev
[   464.663] (II) VESA: driver for VESA chipsets: vesa
[   464.663] xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
[   464.663] (EE) open /dev/dri/card0: No such file or directory
[   464.663] (WW) Falling back to old probe method for modesetting
[   464.663] (EE) open /dev/dri/card0: No such file or directory
[   464.663] (WW) Falling back to old probe method for fbdev
[   464.663] (II) Loading sub module "fbdevhw"
[   464.663] (II) LoadModule: "fbdevhw"
[   464.663] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[   464.663] (II) Module fbdevhw: vendor="X.Org Foundation"
[   464.663]    compiled for 1.19.6, module version = 0.0.2
[   464.663]    ABI class: X.Org Video Driver, version 23.0
[   464.664] (EE) open /dev/fb0: No such file or directory
[   464.664] (WW) Falling back to old probe method for vesa
[   464.664] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[   464.664] (EE) Screen 0 deleted because of no matching config section.
[   464.664] (II) UnloadModule: "modesetting"
[   464.664] (EE) Device(s) detected, but none match those in the config file.
[   464.664] (EE) 
Fatal server error:
[   464.664] (EE) no screens found(EE) 
[   464.664] (EE) 
Please consult the The X.Org Foundation support 
     at http://wiki.x.org
 for help. 
[   464.664] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[   464.664] (EE) 
[   464.664] (EE) Server terminated with error (1). Closing log file.



  


  I am using this github repo to setup the video-streamer

  


  If anyone wants the colab notebook for the example then I will add it over here.

  


  For this problem I am really not sure where to file an issue for this so that's why I am writing this here.