Recherche avancée

Sur d’autres sites (8056)

• A Guide to GDPR Sensitive Personal Data

  13 mai 2024, par Erin

  The General Data Protection Regulation (GDPR) is one of the world’s most stringent data protection laws. It provides a legal framework for collection and processing of the personal data of EU individuals.

  The GDPR distinguishes between “special categories of personal data” (also referred to as “sensitive”) and other personal data and imposes stricter requirements on collection and processing of sensitive data. Understanding these differences will help your company comply with the requirements and avoid heavy penalties.

  In this article, we’ll explain what personal data is considered “sensitive” according to the GDPR. We’ll also examine how a web analytics solution like Matomo can help you maintain compliance.

  What is sensitive personal data ?

  The following categories of data are treated as sensitive :

  1. 1. Personal data revealing :
        • Racial or ethnic origin ;
        • Political opinions ;
        • Religious or philosophical beliefs ;
        • Trade union membership ;
     2. Genetic and biometric data ;
     3. Data concerning a person’s :
        • Health ; or
        • Sex life or sexual orientation.

  

  Sensitive vs. non-sensitive personal data : What’s the difference ?

  While both categories include information about an individual, sensitive data is seen as more private, or requiring a greater protection. 

  Sensitive data often carries a higher degree of risk and harm to the data subject, if the data is exposed. For example, a data breach exposing health records could lead to discrimination for the individuals involved. An insurance company could use the information to increase premiums or deny coverage. 

  In contrast, personal data like name or gender is considered less sensitive because it doesn’t carry the same degree of harm as sensitive data. 

  Unauthorised access to someone’s name alone is less likely to harm them or infringe on their fundamental rights and freedoms than an unauthorised access to their health records or biometric data. Note that financial information (e.g. credit card details) does not fall into the special categories of data.

  

  Legality of processing

  Under the GDPR, both sensitive and nonsensitive personal data are protected. However, the rules and conditions for processing sensitive data are more stringent.

  Article 6 deals with processing of non-sensitive data and it states that processing is lawful if one of the six lawful bases for processing applies. 

  In contrast, Art. 9 of the GDPR states that processing of sensitive data is prohibited as a rule, but provides ten exceptions. 

  It is important to note that the lawful bases in Art. 6 are not the same as exceptions in Art. 9. For example, while performance of a contract or legitimate interest of the controller are a lawful basis for processing non-sensitive personal data, they are not included as an exception in Art. 9. What follows is that controllers are not permitted to process sensitive data on the basis of contract or legitimate interest. 

  The exceptions where processing of sensitive personal data is permitted (subject to additional requirements) are : 

  • Explicit consent : The individual has given explicit consent to processing their sensitive personal data for specified purpose(s), except where an EU member state prohibits such consent. See below for more information about explicit consent. 
  • Employment, social security or social protection : Processing sensitive data is necessary to perform tasks under employment, social security or social protection law.
  • Vital interests : Processing sensitive data is necessary to protect the interests of a data subject or if the individual is physically or legally incapable of consenting. 
  • Non-for-profit bodies : Foundations, associations or nonprofits with a political, philosophical, religious or trade union aim may process the sensitive data of their members or those they are in regular contact with, in connection with their purposes (and no disclosure of the data is permitted outside the organisation, without the data subject’s consent).
  • Made public : In some cases, it may be permissible to process the sensitive data of a data subject if the individual has already made it public and accessible. 
  • Legal claims : Processing sensitive data is necessary to establish, exercise or defend legal claims, including legal or in court proceedings.
  • Public interest : Processing is necessary for reasons of substantial public interest, like preventing unlawful acts or protecting the public.
  • Health or social care : Processing special category data is necessary for : preventative or occupational medicine, providing health and social care, medical diagnosis or managing healthcare systems.
  • Public health : It is permissible to process sensitive data for public health reasons, like protecting against cross-border threats to health or ensuring the safety of medicinal products or medical devices. 
  • Archiving, research and statistics : You may process sensitive data if it’s done for archiving purposes in the public interest, scientific or historical research purposes or statistical purposes.

  In addition, you must adhere to all data handling requirements set by the GDPR.

  Important : Note that for any data sent that you are processing, you always need to identify a lawful basis under Art. 6. In addition, if the data sent contains sensitive data, you must comply with Art. 9.

  Explicit consent

  While consent is a valid lawful basis for processing non-sensitive personal data, controllers are permitted to process sensitive data only with an “explicit consent” of the data subject.

  The GDPR does not define “explicit” consent, but it is accepted that it must meet all Art. 7 conditions for consent, at a higher threshold. To be “explicit” a consent requires a clear statement (oral or written) of the data subject. Consent inferred from the data subject’s actions does not meet the threshold. 

  The controller must retain records of the explicit consent and provide appropriate consent withdrawal method to allow the data subject to exercise their rights.

  Examples of compliant and non-compliant sensitive data processing

  Here are examples of when you can and can’t process sensitive data :

  • When you can process sensitive data : A doctor logs sensitive data about a patient, including their name, symptoms and medicine prescribed. The hospital can process this data to provide appropriate medical care to their patients. An IoT device and software manufacturer processes their customers’ health data based on explicit consent of each customer. 
  • When you can’t process sensitive data : One example is when you don’t have explicit consent from a data subject. Another is when there’s no lawful basis for processing it or you are collecting personal data you simply do not need. For example, you don’t need your customer’s ethnic origin to fulfil an online order.

  Other implications of processing sensitive data

  If you process sensitive data, especially on a large scale, GDPR imposes additional requirements, such as having Data Privacy Impact Assessments, appointing Data Protection Officers and EU Representatives, if you are a controller based outside the EU.

  Penalties for GDPR non-compliance

  Mishandling sensitive data (or processing it when you’re not allowed to) can result in huge penalties. There are two tiers of GDPR fines :

  • €10 million or 2% of a company’s annual revenue for less severe infringements
  • €20 million or 4% of a company’s annual revenue for more severe infringements

  In the first half of 2023 alone, fines imposed in the EU due to GDPR violations exceeded €1.6 billion, up from €73 million in 2019.

  Examples of high-profile violations in the last few years include :

  • Amazon : The Luxembourg National Commission fined the retail giant with a massive $887 million fine in 2021 for not processing personal data per the GDPR. 
  • Google : The National Data Protection Commission (CNIL) fined Google €50 million for not getting proper consent to display personalised ads.
  • H&M : The Hamburg Commissioner for Data Protection and Freedom of Information hit the multinational clothing company with a €35.3 million fine in 2020 for unlawfully gathering and storing employees’ data in its service centre.

  One of the criteria that affects the severity of a fine is “data category” — the type of personal data being processed. Companies need to take extra precautions with sensitive data, or they risk receiving more severe penalties.

  What’s more, GDPR violations can negatively affect your brand’s reputation and cause you to lose business opportunities from consumers concerned about your data practices. 76% of consumers indicated they wouldn’t buy from companies they don’t trust with their personal data.

  Organisations should lay out their data practices in simple terms and make this information easily accessible so customers know how their data is being handled.

  Get started with GDPR-compliant web analytics

  The GDPR offers a framework for securing and protecting personal data. But it also distinguishes between sensitive and non-sensitive data. Understanding these differences and applying the lawful basis for processing this data type will help ensure compliance.

  Looking for a GDPR-compliant web analytics solution ?

  At Matomo, we take data privacy seriously. 

  Our platform ensures 100% data ownership, putting you in complete control of your data. Unlike other web analytics solutions, your data remains solely yours and isn’t sold or auctioned off to advertisers. 

  Additionally, with Matomo, you can be confident in the accuracy of the insights you receive, as we provide reliable, unsampled data.

  Matomo also fully complies with GDPR and other data privacy laws like CCPA, LGPD and more.

  Start your 21-day free trial today ; no credit card required. 

  Disclaimer

  We are not lawyers and don’t claim to be. The information provided here is to help give an introduction to GDPR. We encourage every business and website to take data privacy seriously and discuss these issues with your lawyer if you have any concerns.

  Try Matomo for Free

  21 day free trial. No credit card required.

  
  

  Your email address
  

  Your website address
  

  Your Analytics subdomain will be .matomo.cloud (change)

  Choose your analytics subdomain
  

  .matomo.cloud

  I accept the terms and conditions and data processing agreement (DPA)

  
  Your information will be used to create an account on our cloud service. For more information please consult our privacy policy.
  
  
  

  Start improving your websites now

  

• How to stream webcam video over RTSP using ffmpeg on Windows 10 ? [closed]

  15 mai 2024, par let me down slowly

  I am trying to stream my laptop's webcam using RTSP protocol using ffmpeg. I am trying to simulate an actual IP Camera. I have already tried different tools already including using VidGear python package, and gstreamer but could not get it working. Note : I am on Windows 10. I have tried this command :

  


  ffmpeg -f dshow -s 320x240 -rtbufsize 2147.48M -r 30 -vcodec mjpeg -i video="HD Camera" -f rtsp -rtsp_transport tcp rtsp://localhost:8554/mystream


  


  It turns on the webcam with but prints these logs to the console :

  


  ffmpeg version 7.0-full_build-www.gyan.dev Copyright (c) 2000-2024 the FFmpeg developers
  built with gcc 13.2.0 (Rev5, Built by MSYS2 project)
  configuration: --enable-gpl --enable-version3 --enable-static --disable-w32threads --disable-autodetect --enable-fontconfig --enable-iconv --enable-gnutls --enable-libxml2 --enable-gmp --enable-bzlib --enable-lzma --enable-libsnappy --enable-zlib --enable-librist --enable-libsrt --enable-libssh --enable-libzmq --enable-avisynth --enable-libbluray --enable-libcaca --enable-sdl2 --enable-libaribb24 --enable-libaribcaption --enable-libdav1d --enable-libdavs2 --enable-libuavs3d --enable-libxevd --enable-libzvbi --enable-librav1e --enable-libsvtav1 --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxavs2 --enable-libxeve --enable-libxvid --enable-libaom --enable-libjxl --enable-libopenjpeg --enable-libvpx --enable-mediafoundation --enable-libass --enable-frei0r --enable-libfreetype --enable-libfribidi --enable-libharfbuzz --enable-liblensfun --enable-libvidstab --enable-libvmaf --enable-libzimg --enable-amf --enable-cuda-llvm --enable-cuvid --enable-dxva2 --enable-d3d11va --enable-d3d12va --enable-ffnvcodec --enable-libvpl --enable-nvdec --enable-nvenc --enable-vaapi --enable-libshaderc --enable-vulkan --enable-libplacebo --enable-opencl --enable-libcdio --enable-libgme --enable-libmodplug --enable-libopenmpt --enable-libopencore-amrwb --enable-libmp3lame --enable-libshine --enable-libtheora --enable-libtwolame --enable-libvo-amrwbenc --enable-libcodec2 --enable-libilbc --enable-libgsm --enable-libopencore-amrnb --enable-libopus --enable-libspeex --enable-libvorbis --enable-ladspa --enable-libbs2b --enable-libflite --enable-libmysofa --enable-librubberband --enable-libsoxr --enable-chromaprint
  libavutil      59.  8.100 / 59.  8.100
  libavcodec     61.  3.100 / 61.  3.100
  libavformat    61.  1.100 / 61.  1.100
  libavdevice    61.  1.100 / 61.  1.100
  libavfilter    10.  1.100 / 10.  1.100
  libswscale      8.  1.100 /  8.  1.100
  libswresample   5.  1.100 /  5.  1.100
  libpostproc    58.  1.100 / 58.  1.100
[mjpeg @ 0000026201ae9fc0] unable to decode APP fields: Invalid data found when processing input
Input #0, dshow, from 'video=HD Camera':
  Duration: N/A, start: 1285415.793302, bitrate: N/A
  Stream #0:0: Video: mjpeg (Baseline) (MJPG / 0x47504A4D), yuvj422p(pc, bt470bg/unknown/unknown), 320x240, 30 fps, 30 tbr, 10000k tbn
Stream mapping:
  Stream #0:0 -> #0:0 (mjpeg (native) -> mpeg4 (native))
Press [q] to stop, [?] for help
[mjpeg @ 0000026201afe9c0] unable to decode APP fields: Invalid data found when processing input
[swscaler @ 0000026201b5cc40] deprecated pixel format used, make sure you did set range correctly
[swscaler @ 00000262068c57c0] deprecated pixel format used, make sure you did set range correctly
[swscaler @ 0000026201b5cc40] deprecated pixel format used, make sure you did set range correctly
    Last message repeated 1 times
[mjpeg @ 0000026201afe9c0] unable to decode APP fields: Invalid data found when processing input
    Last message repeated 8 times


  


  I tried opening rtsp://localhost:8554/mystream but it shows VLC is unable to open the MRL 'rtsp://localhost:8554/mystream'. Check the log for details.

  


  Killing the running process outputs these additional logs

  


  [out#0/rtsp @ 0000026201aeaf80] Could not write header (incorrect codec parameters ?): Immediate exit requested
[vf#0:0 @ 0000026201af4100] Error sending frames to consumers: Immediate exit requested
[vf#0:0 @ 0000026201af4100] Task finished with error code: -1414092869 (Immediate exit requested)
[vf#0:0 @ 0000026201af4100] Terminating thread with return code -1414092869 (Immediate exit requested)
[out#0/rtsp @ 0000026201aeaf80] Nothing was written into output file, because at least one of its streams received no packets.
frame=    0 fps=0.0 q=0.0 Lsize=       0KiB time=N/A bitrate=N/A speed=N/A
Exiting normally, received signal 2.


  


  Output of the command ffmpeg -list_devices true -f dshow -i dummy :

  


    built with gcc 13.2.0 (Rev5, Built by MSYS2 project)
  configuration: --enable-gpl --enable-version3 --enable-static --disable-w32threads --disable-autodetect --enable-fontconfig --enable-iconv --enable-gnutls --enable-libxml2 --enable-gmp --enable-bzlib --enable-lzma --enable-libsnappy --enable-zlib --enable-librist --enable-libsrt --enable-libssh --enable-libzmq --enable-avisynth --enable-libbluray --enable-libcaca --enable-sdl2 --enable-libaribb24 --enable-libaribcaption --enable-libdav1d --enable-libdavs2 --enable-libuavs3d --enable-libxevd --enable-libzvbi --enable-librav1e --enable-libsvtav1 --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxavs2 --enable-libxeve --enable-libxvid --enable-libaom --enable-libjxl --enable-libopenjpeg --enable-libvpx --enable-mediafoundation --enable-libass --enable-frei0r --enable-libfreetype --enable-libfribidi --enable-libharfbuzz --enable-liblensfun --enable-libvidstab --enable-libvmaf --enable-libzimg --enable-amf --enable-cuda-llvm --enable-cuvid --enable-dxva2 --enable-d3d11va --enable-d3d12va --enable-ffnvcodec --enable-libvpl --enable-nvdec --enable-nvenc --enable-vaapi --enable-libshaderc --enable-vulkan --enable-libplacebo --enable-opencl --enable-libcdio --enable-libgme --enable-libmodplug --enable-libopenmpt --enable-libopencore-amrwb --enable-libmp3lame --enable-libshine --enable-libtheora --enable-libtwolame --enable-libvo-amrwbenc --enable-libcodec2 --enable-libilbc --enable-libgsm --enable-libopencore-amrnb --enable-libopus --enable-libspeex --enable-libvorbis --enable-ladspa --enable-libbs2b --enable-libflite --enable-libmysofa --enable-librubberband --enable-libsoxr --enable-chromaprint
  libavutil      59.  8.100 / 59.  8.100
  libavcodec     61.  3.100 / 61.  3.100
  libavformat    61.  1.100 / 61.  1.100
  libavdevice    61.  1.100 / 61.  1.100
  libavfilter    10.  1.100 / 10.  1.100
  libswscale      8.  1.100 /  8.  1.100
  libswresample   5.  1.100 /  5.  1.100
  libpostproc    58.  1.100 / 58.  1.100
[dshow @ 00000140f18d4200] "HD Camera" (video)
[dshow @ 00000140f18d4200]   Alternative name "@device_pnp_\\?\usb#vid_05c8&pid_03ea&mi_00#6&d0a8c55&0&0000#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\global"
[dshow @ 00000140f18d4200] "Microphone (Realtek(R) Audio)" (audio)
[dshow @ 00000140f18d4200]   Alternative name "@device_cm_{33D9A762-90C8-11D0-BD43-00A0C911CE86}\wave_{06840D8D-1151-4D9C-B865-2FE01BFB9FD2}"
[in#0 @ 00000140f18ba640] Error opening input: Immediate exit requested
Error opening input file dummy.


  


  Output of the command ffmpeg -f dshow -list_options true -i video="HD Camera" :

  


    built with gcc 13.2.0 (Rev5, Built by MSYS2 project)
  configuration: --enable-gpl --enable-version3 --enable-static --disable-w32threads --disable-autodetect --enable-fontconfig --enable-iconv --enable-gnutls --enable-libxml2 --enable-gmp --enable-bzlib --enable-lzma --enable-libsnappy --enable-zlib --enable-librist --enable-libsrt --enable-libssh --enable-libzmq --enable-avisynth --enable-libbluray --enable-libcaca --enable-sdl2 --enable-libaribb24 --enable-libaribcaption --enable-libdav1d --enable-libdavs2 --enable-libuavs3d --enable-libxevd --enable-libzvbi --enable-librav1e --enable-libsvtav1 --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxavs2 --enable-libxeve --enable-libxvid --enable-libaom --enable-libjxl --enable-libopenjpeg --enable-libvpx --enable-mediafoundation --enable-libass --enable-frei0r --enable-libfreetype --enable-libfribidi --enable-libharfbuzz --enable-liblensfun --enable-libvidstab --enable-libvmaf --enable-libzimg --enable-amf --enable-cuda-llvm --enable-cuvid --enable-dxva2 --enable-d3d11va --enable-d3d12va --enable-ffnvcodec --enable-libvpl --enable-nvdec --enable-nvenc --enable-vaapi --enable-libshaderc --enable-vulkan --enable-libplacebo --enable-opencl --enable-libcdio --enable-libgme --enable-libmodplug --enable-libopenmpt --enable-libopencore-amrwb --enable-libmp3lame --enable-libshine --enable-libtheora --enable-libtwolame --enable-libvo-amrwbenc --enable-libcodec2 --enable-libilbc --enable-libgsm --enable-libopencore-amrnb --enable-libopus --enable-libspeex --enable-libvorbis --enable-ladspa --enable-libbs2b --enable-libflite --enable-libmysofa --enable-librubberband --enable-libsoxr --enable-chromaprint
  libavutil      59.  8.100 / 59.  8.100
  libavcodec     61.  3.100 / 61.  3.100
  libavformat    61.  1.100 / 61.  1.100
  libavdevice    61.  1.100 / 61.  1.100
  libavfilter    10.  1.100 / 10.  1.100
  libswscale      8.  1.100 /  8.  1.100
  libswresample   5.  1.100 /  5.  1.100
  libpostproc    58.  1.100 / 58.  1.100
[dshow @ 000002670b4c12c0] DirectShow video device options (from video devices)
[dshow @ 000002670b4c12c0]  Pin "Capture" (alternative pin name "Capture")
[dshow @ 000002670b4c12c0]   vcodec=mjpeg  min s=1280x720 fps=30 max s=1280x720 fps=30
[dshow @ 000002670b4c12c0]   vcodec=mjpeg  min s=640x480 fps=30 max s=640x480 fps=30
[dshow @ 000002670b4c12c0]   vcodec=mjpeg  min s=640x360 fps=30 max s=640x360 fps=30
[dshow @ 000002670b4c12c0]   vcodec=mjpeg  min s=352x288 fps=30 max s=352x288 fps=30
[dshow @ 000002670b4c12c0]   vcodec=mjpeg  min s=320x240 fps=30 max s=320x240 fps=30
[dshow @ 000002670b4c12c0]   vcodec=mjpeg  min s=176x144 fps=30 max s=176x144 fps=30
[dshow @ 000002670b4c12c0]   pixel_format=yuyv422  min s=1280x720 fps=10 max s=1280x720 fps=10
[dshow @ 000002670b4c12c0]   pixel_format=yuyv422  min s=640x480 fps=30 max s=640x480 fps=30
[dshow @ 000002670b4c12c0]   pixel_format=yuyv422  min s=640x360 fps=30 max s=640x360 fps=30
[dshow @ 000002670b4c12c0]   pixel_format=yuyv422  min s=352x288 fps=30 max s=352x288 fps=30
[dshow @ 000002670b4c12c0]   pixel_format=yuyv422  min s=320x240 fps=30 max s=320x240 fps=30
[dshow @ 000002670b4c12c0]   pixel_format=yuyv422  min s=176x144 fps=30 max s=176x144 fps=30
[in#0 @ 000002670b4aa200] Error opening input: Immediate exit requested
Error opening input file video=HD Camera.


  


  Please help me solve the issue or suggest a better approach.

  


• GA360 vs GA4 : Key Differences and Challenges

  20 mai 2024, par Erin

  While the standard Universal Analytics (UA) was sunset for free users in July 2023, Google Analytics 360 (GA360) users could postpone the switch to GA4 for another 12 months. But time is running out. As July is rapidly approaching, GA360 customers need to prepare for the switch to Google Analytics 4 (GA4) or another solution. 

  This comparison post will help you understand the differences between GA360 vs. GA4. We’ll dive beneath the surface, examining each solution’s privacy implications and their usability, features, new metrics and measurement methods.

  What is Google Analytics 4 (Standard) ?

  GA4 is the latest version of Google Analytics, succeeding Universal Analytics. It was designed to address privacy issues with Universal Analytics, which made compliance with privacy regulations like GDPR difficult.

  It completely replaced Universal Analytics for free users in July 2023. GA4 Standard features many differences from the original UA, including :

  • Tracking and analysis are now events-based.
  • Insights are primarily powered by machine learning. (There are fewer reports and manual analysis tools).
  • Many users find the user interface to be too complex compared to Universal Analytics.

  The new tracking, reports and metrics already make GA4 feel like a completely different web analytics platform. The user interface itself also includes notable changes in navigation and implementation. These changes make the transition hard for experienced analysts and digital marketers alike. 

  For a more in-depth look at the differences, read our comparison of Google Analytics 4 and Universal Analytics.

  What is Google Analytics 360

  Google Analytics 360 is a paid version of Google Analytics, mostly aimed at enterprises that need to analyse a large amount of data.

  It significantly increases standard limits on data collection, sampling and processing. It also improves data granularity with more custom events and dimensions.

  Transitioning from Universal Analytics 360 to GA4 360

  You may still use the Universal Analytics tag and interface if you’ve been a Google Analytics 360 customer for multiple years. However, access to Universal Analytics 360 will be discontinued on July 1, 2024. Unlike the initial UA sunset (free version), you won’t be able to access the interface or your data after that, so it will be deleted.

  That means you will have to adapt to the new GA4 user interface, reports and metrics before the sunset or find an alternative solution.

  What is the difference between GA4 360 and free GA4 ?

  The key differences between GA4 360 and free GA4 are higher data limits, enterprise support, uptime guarantees and more robust administrative controls.

  

  GA4 offers most of the same features across the paid and free versions, but there are certain limits on data sampling, data processing and integrations. With the free version, you also can’t define as detailed events using event parameters as you can with GA4 360.

  Higher data collection, accuracy, storage and processing limits

  The biggest difference that GA4 360 brings to the table is more oomph in data collection, accuracy and analysis.

  You can collect more specific data (with 100 event parameters instead of 25 for custom metrics). GA4 360 lets you divide users using more custom dimensions based on events or user characteristics. Instead of 50 per property, you get up to 125 per property.

  And with up to 400 custom audiences, 360 is better for companies that heavily segment their users. More audiences, events and metrics per property mean more detailed insights.

  Sampling limits are also of a completely different scale. The max sample size in GA4 360 is 100x the free version of GA4, with up to 1 billion events per query. This makes analysis a lot more accurate for high-volume users. A slice of 10 million events is hardly representative if you have 200 million monthly events.

  Finally, GA4 360 lets you store all of that data for longer (up to 50 months vs up to 14 months). While new privacy regulations demand that you store user data only for the shortest time possible, website analytics data is often used for year-over-year analysis.

  Enterprise-grade support and uptime guarantees

  Because GA360 users are generally enterprises, Google offers service-level agreements for uptime and technical support response times.

  • Tracking : 99.9% uptime guarantee
  • Reporting : 99% uptime guarantee
  • Data processing : within 4 hours at a 98% uptime guarantee

  The free version of GA4 includes no such guarantees and limited access to professional support in the first place.

  Integrations

  GA4 360 increases limits for BigQuery and Google Ads Manager exports.

  

  The standard limits in the free version are 1 million events per day to BigQuery. In GA4 360, this is increased to billions of events per day. You also get up to 400 audiences for Search Ads 360 instead of the 100 limit in standard GA4.

  Roll-up analytics for agencies and enterprises

  If you manage a wide range of digital properties, checking each one separately isn’t very effective. You can export the data into a tool like Looker Studio (formerly Google Data Studio), but this requires extra work.

  With GA360, you can create “roll-up properties” to analyse data from multiple properties in the same space. It’s the best way to analyse larger trends and patterns across sites and apps.

  Administration and user access controls

  Beyond roll-up reporting, the other unique “advanced features” found in GA360 are related to administration and user access controls.

  

  First, GA360 lets you create custom user roles, giving different access levels to different properties. Sub-properties and roll-up properties are also useful tools for data governance purposes. They make it easier to limit access for specific analysts to the area they’re directly working on.

  You can also design custom reports for specific roles and employees based on their access levels.

  Pricing 

  While GA4 is free, Google Analytics 360 is priced based on your traffic volume. 

  With the introduction of GA4, Google implemented a revised pricing model. For GA4 360, pricing typically begins at USD $50,000/year which covers up to 25 million events per month. Beyond this limit, costs increase based on data usage, scaling accordingly.

  What’s not different : the interface, metrics, reports and basic features

  GA4 360 is the same analytics tool as the free version of GA4, with higher usage limits and a few enterprise features. You get more advanced tracking capabilities and more accurate analysis in the same GA4 packaging.

  If you already use and love GA4 but need to process more data, that’s great news. But if you’re using UA 360 and are hesitant to switch to the new interface, not so much. 

  Making the transition from UA to GA4 isn’t easy. Transferring the data means you need to figure out how to work with the API or use Google BigQuery.

  Plus, you have to deal with new metrics, reports and a new interface. For example, you don’t get to keep your custom funnel reports. You need to use “funnel explorations.”

  Going from UA to GA4 can feel like starting from scratch in a completely new web analytics tool.

  Which version of Google Analytics 4 is right for you ?

  Standard GA4 is a cost-effective web analytics option, but it’s not without its problems :

  • If you’re used to the UA interface, it feels clunky and difficult to analyse.
  • Data sampling is prevalent in the free version, leading to inaccuracies that can negatively affect decision-making and performance.

  And that’s just scratching the surface of common GA4 issues.

  Google Analytics 4 360 is a more reliable web analytics solution for enterprises. However, it suffers from many issues that made the GA4 transition painful for many free UA users last year.

  • You need to rebuild reports and adjust to the new complex interface.
  • To transfer historical data, you must use spreadsheets, the API, or BigQuery.

  You will still lose some of the data due to changes to the metrics and reporting.

  What if neither option is right for you ? Key considerations for choosing a Google Analytics alternative

  Despite what Google would like you to think, GA4 isn’t the only option for website analytics in 2024 — far from it. For companies that are used to UA 360, the right alternative can offer unique benefits to your company.

  Privacy regulations and future-proofing your analytics and marketing

  Although less flagrant than UA, GA4 is still in murky waters regarding compliance with GDPR and other privacy regulations. 

  And the issue isn’t just that you can get fined (which is bad enough). As part of a ruling, you may be ordered to change your analytics platform and protocol, which can completely disrupt your marketing workflow.

  When most marketing teams rely on web analytics to judge the ROI of their campaigns, this can be catastrophic. You may even have to pause campaigns as your team makes the adjustments.

  Avoid this risk completely by going with a privacy-friendly alternative.

  Features beyond basic web analytics

  To understand your users, you need to look at more than just events and conversions.

  That’s why some web analytics solutions have built-in behavioural analytics tools. Features like heatmaps (a visual pattern of popular clicks, scrolling and cursor movement) can help you understand how users interact with specific pages.

  

  Matomo allows you to consolidate behavioural analytics and regular web analytics into a single platform. You don’t need separate tools and subscriptions for heatmaps, session recordings, from analytics, media analytics and A/B testing. You can do all of this with Matomo.

  With insights about visits, sales, conversions, and usability in the same place, it’s a lot easier to improve your website.

  Try Matomo for Free

  Get the web insights you need, without compromising data accuracy.

  Start for free

  No credit card required

  Usability and familiar metrics

  The move to event tracking means new metrics, reports and tools. So, if you’re used to Universal Analytics, it can be tricky to transition to GA4. 

  But there’s no need to start from zero, learning to work with a brand-new interface. Many competing web analytics platforms offer familiar reports and metrics — ones your team has gotten used to. This will help you speed up the time to value with a shorter learning curve.

  Why Matomo is a better option than GA4 360 for UA 360 users

  Matomo offers privacy-friendly tracking, built from the ground up to comply with regulations — including IP anonymisation and DoNotTrack settings. You also get 100% ownership of the data, which means we will never use your data for our own profit (unlike Google and other data giants).

  This is a big deal, as breaking GDPR rules can lead to fines of up to 4% of your annual revenue. At the same time, you’ll also future-proof your marketing workflow by choosing a web analytics provider built with privacy regulations in mind.

  Plus, for legacy UA 360 users, the Matomo interface will also feel a lot more intuitive and familiar. Matomo also provides marketing attribution models you know, like first click, which GA4 has removed.

  Finally, you can access various behavioural analytics tools in a single platform — heatmaps, session recordings, form analytics, A/B testing and more. That means you don’t need to pay for separate solutions for conversion rate optimisation efforts.

  And the transition is smooth. Matomo lets you import Universal Analytics data and offers ready-made Google Ads integration and Looker Studio Connector.

  Join over 1 million websites that choose Matomo as their web analytics solution. Try it free for a 21-days. No credit card required.

  Try Matomo for Free

  21 day free trial. No credit card required.

  
  

  Your email address
  

  Your website address
  

  Your Analytics subdomain will be .matomo.cloud (change)

  Choose your analytics subdomain
  

  .matomo.cloud

  I accept the terms and conditions and data processing agreement (DPA)

  
  Your information will be used to create an account on our cloud service. For more information please consult our privacy policy.
  
  
  

  Start improving your websites now