Recherche avancée

Sur d’autres sites (6712)

• 11 ways Piwik Analytics helps you to protect your visitors privacy

  11 janvier 2017, par InnoCraft — Community

  At Piwik and at InnoCraft, we think Privacy matters. From the beginning, Piwik has had a strong focus on privacy and ensures the privacy of your visitors and analytics data. As a result, Piwik has been recommended as a privacy-compliant analytics tool for example by the Independent Center for Privacy Protection in Germany (ULD) and by the Center for Data Privacy Protection in France (CNIL). In France, Piwik is the only web analytics tool that does not require Cookie Consent.

  Here are some ways how you can ensure your users and visitors privacy by using Piwik.

  1. You own the data

  Whether you host Piwik on premise yourself, managed on premise by InnoCraft, or whether you use our Piwik cloud, when you use Piwik, YOU keep control of your data and nobody else. This also means you can decide where your data should be located physically.

  2. Anonymized IP addresses

  For better privacy by default, Piwik will not record the full IP address of your visitors because otherwise the browsing history could be easily tracked across several days and even across websites within the same Piwik server. Some countries even require to anonymize the IP address, considered Personally Identifiable Information (PII).

  To change the IP anonymization settings go to “Administration > Privacy”. Optionally, you can use the full IP to still get for example accurate location data.

  

  3. Delete old visitor logs

  The visitor logs contain information all the collected raw data about every visitor and every action. You can configure Piwik to automatically delete logs from the database. When you delete old logs, only the real time and visitor log reports will no longer work for this old time period, all other aggregated reports will still work.

  For privacy reasons, we highly recommend that you keep the detailed Piwik logs for only 3 to 6 months and delete older log data. This has one other nice side effect : it will free significant database space, which will, in turn, slightly increase performance !

  

  4. Support Do Not Track preference

  Do Not Track enables users to opt out of any tracking by websites they do not visit, including analytics services, advertising networks, and social platforms. By default, Piwik respects users preference and will not track visitors which have specified “I do not want to be tracked” in their web browsers. Get more information about DoNotTrack.

  To make sure Do Not Track is respected, go to “Administration => Privacy”.

  5. Include an Opt-Out Feature on your website or app

  By embedding the Opt-Out feature in your website, you give your visitors the possibility to opt-out of the tracking. When you go to “Administration > Privacy”, you will be able to copy and paste an HTML Iframe code to embed the opt-out feature for example into your privacy policy page or in your ‘Legal’ page. Your users can then click on a link to opt-out.

  On the Piwik Marketplace there are also some plugins available to customize the Opt-Out experience. For example AjaxOptOut and CustomOptOut.

  

  6. Disable Live features

  The Real-Time, Visitor Log and Visitor Profile features give you insights into the tracked raw data by showing you details about every visitor and every action they performed. To protect the privacy of your visitors you may decide to prevent access to such features by disabling the “Live” plugin in “Administration => Plugins”. This way only aggregated reports will be shown in your Piwik.

  7. Disable fingerprinting across websites

  By default, when one of your visitors visits several of your websites, Piwik will create a fingerprint for this user that will be different across the websites to increase the visitors’ privacy. You can make sure that this feature is disabled by going to “Administration => Config file” and verifying that the value of “enable_fingerprinting_across_websites” is set to zero.

  8. Disable tracking cookies

  Piwik uses cookies to store some information about visitors between visits. In some countries, the legislation requires websites to provide a way for users to opt-out of all tracking, in particular tracking cookies. You can disable cookies by adding one line in the Piwik Javascript code.

  9. Custom development

  Piwik is an open platform that lets you extend and customize the tracking, the reporting and the Piwik user interface to your needs and to protect your visitors’ privacy the way you want or need it. Learn more in the Piwik Developer Zone. You may also have a look at our Piwik Marketplace where you can find several free and premium features to extend your Piwik.

  10. Transparency

  By default, all information and all collected data in your Piwik server are protected and nobody can access it. However, Piwik allows you to optionally make your collected data public and you can export any Piwik report including the whole dashboard to embed it into your website. This way you can show your users exactly which information you track. When you decide to make reports public, we do our best to protect privacy and automatically hide any Personally Identifiable Information such as the Visitor Profile and we make sure to not show any Visitor IP address and the Visitor ID.

  11. Privacy policy

  When you use Piwik to track your visitors, we recommend to update your Privacy Policy to explain how Piwik is used and what data it gathers. We provide a Privacy Policy template for Piwik users that you can copy on your site.

  Continuous privacy improvements

  We are always interested in improving the privacy. If you miss any feature or have an idea on how to improve the privacy, please let us know.

  More information about all the Piwik features

  If you want to learn more about all the features in Piwik, have a look at our User Guides and FAQ entries.

• Tracking User Acquisition and Social Media Activity with Piwik

  25 avril 2017, par Florian Hieß — Community

  Being able to monitor user acquisition and social media activity is essential for determining whether the outcome of your campaigns is in line with the business objectives. Determining the source of each website visit that gets you closer to your business goals enables you to focus your efforts in the directions that are worth it. In this article you will learn why it is important to identify your traffic sources and how you can track user acquisition with Piwik Analytics.

  Why Is It Important to Identify Traffic Sources on Your Website ?

  Since brands nowadays use multiple channels for promotion and advertising, identifying the touch points and traffic sources of a lead or customer seems to become more and more difficult. And yet, this channel multiplication is what makes the source of a purchase more important. Once you identify the traffic origin and how each source is performing you are able to increase your efforts on the best performers, both in terms of human resources and monetary investments, to attract more leads or customers in these marketing channels.

  The default referrer types are defined by :

  • Search engine
  • Direct traffic
  • Websites and
  • Campaigns

  But consider that within the “Campaigns” type, each of the following referrers is a possible traffic source for your website and can be tracked with the Piwik URL builder :

  • Google AdWords
  • Display Ads, Banners
  • Links in Newsletters, Emailing
  • Affiliate links
  • Tweets
  • Facebook Ads

  Measure your performance and conversion

  With so many options, wouldn’t you like to know which one of them worked best ? To rate channels based on their performance, you first need to establish conversion goals and attribution.

  A conversion can be anything from sign-ups or downloads to leads, registered users and even paying customers. Define conversions based on what you want people to do once they’ve landed on your website.

  

  You need to define each conversion type in the Piwik dashboard, so that the analytics platform knows what to track. As far as attribution goes, Piwik by default links the conversion and attributes to the last seen (non-direct) referrer. You are able to change that to the first referrer in the attribution line by following the instructions in this conversion attribution FAQ.

  Track Your User Acquisition Right with Piwik

  Using the Piwik URL Builder tool, you can tag each URL you promote in your campaigns using relevant keywords. Provided that your URLs are tagged, whenever someone clicks on them, the campaign will be listed as the referrer in the Piwik dashboard. Once you’ve generated trackable URLs, you can include them in your social media posts which could be planned and scheduled using a social media management tool such as Swat.io.

  

  Campaign URLs work wonders for telling which campaign helped you reach your goals faster, more efficiently and so on but they do have a downside. They only work for URLs that you’ve shared. If someone decides to share a link of yours on social media they won’t be tagged beforehands. This is where the Referrers section of Piwik comes in handy, as it acts as a backup for tracking traffic sources. The overview tab features a graph that can help you identify when spikes occurred.

  

  As well as a numerical representation of the main referrer categories for the selected time period.

  

  Switching from Overview to Websites & Social, you can see a graphical representation of the social networks acting as referrers. The visualization can be changed to bar graphs or table, and can be easily exported in various formats for reports.

  

  The websites list features not only the social referrers, but all of the websites generating visits to your website. With Piwik you should not have issues with referrer spam, as the Piwik core team has tackled this problem early on, as detailed in how to stop referrer spam. Our analytics spam blacklist is a public project on GitHub.

  

  Assuming that you’re relying only on Facebook and VK.com for your campaigns, as the above screenshot would suggest, you might want to give paid advertising a try on these two social networks. Paid ads can increase reach and engagement, can get more relevant visitors to your website and can have a snowball effect in a short period of time.

  What Social Networks Can Piwik Track ?

  Piwik’s built-in social network list is quite extensive, as it currently features 70 platforms. The entries range from popular social networks such as Facebook, Twitter and LinkedIn to more obscure ones such as Renren. However, this list is not available by default, and to see it or alter it, you would need a third-party plugin.

  How Does the Referrers Manager Plugin for Piwik Work ?

  The Referrers Manager plugin for Piwik provides access to the list of search engines and social networks that this analytics platform can handle by default. The simple plugin can come in handy when sorting out referrers. First of all, it displays a list of all search engines and social networks that Piwik can handle by default. Secondly, it enables users to disable/enable the platform’s default social network list. And using Referrers Manager, you can add custom engines or social networks to the referrers list in case they’re not already available.

  

  Conclusions

  Piwik is a very capable analytics platform as it is, but combined with third-party plugins such as Referrers Manager, it can provide even better insights on where your visitors are coming from. Remember to correlate the referrers with goals in order to determine which website or social network performs best in your context. And don’t forget to assign a monetary revenue value to each goal, in order to determine your social media ROI with greater accuracy.

• CVAT error during installation of development version

  28 novembre 2022, par Raman

  I'm trying to install development version of CVAT according to official instruction but struggling at the step of requirements.txt applying :

  


  pip install -r cvat/requirements/development.txt


  


  ... with following error :

  


  Skipping wheel build for av, due to binaries being disabled for it.
Skipping wheel build for datumaro, due to binaries being disabled for it.
Installing collected packages: wrapt, tf-estimator-nightly, termcolor, tensorboard-plugin-wit, Shapely, rules, rope, rjsmin, rcssmin, pytz, pyasn1, patool, mistune, mccabe, libclang, keras, itypes, flatbuffers, entrypoint2, EasyProcess, dj-pagination, diskcache, av, addict, Werkzeug, urllib3, uritemplate, typing-extensions, tqdm, tornado, toml, threadpoolctl, tensorflow-io-gcs-filesystem, tensorboard-data-server, sqlparse, smmap, six, ruamel.yaml.clib, rsa, redis, PyYAML, pyunpack, pyrsistent, pyparsing, pylogbeat, pyjwt, Pygments, pycparser, pyasn1-modules, protobuf, Pillow, oauthlib, numpy, networkx, natsort, MarkupSafe, Markdown, lxml, lazy-object-proxy, kiwisolver, joblib, jmespath, isort, inflection, idna, google-crc32c, gast, fonttools, dnspython, django-extensions, deprecated, defusedxml, cycler, click, charset-normalizer, certifi, cachetools, attrs, asgiref, absl-py, tensorboardX, snakeviz, scipy, ruamel.yaml, rq, requests, python3-openid, python-ldap, python-dateutil, pdf2image, packaging, orderedmultidict, opt-einsum, opencv-python-headless, opencv-python, keras-preprocessing, jsonschema, jinja2, isodate, h5py, grpcio, googleapis-common-protos, google-resumable-media, google-pasta, google-auth, gitdb, Django, cffi, astunparse, astroid, scikit-learn, requests-oauthlib, pylint, pandas, matplotlib, limits, google-api-core, GitPython, furl, djangorestframework, django-sendfile2, django-rq, django-filter, django-cors-headers, django-auth-ldap, django-appconf, cryptography, croniter, coreschema, botocore, azure-core, s3transfer, rq-scheduler, python-logstash-async, pylint-plugin-utils, pycocotools, open3d, msrest, google-cloud-core, google-auth-oauthlib, drf-spectacular, django-rest-auth, django-compressor, coreapi, tensorboard, pylint-django, google-cloud-storage, django-allauth, datumaro, boto3, azure-storage-blob, tensorflow
  Running setup.py install for av ... error
  error: subprocess-exited-with-error
  
  × Running setup.py install for av did not run successfully.
  │ exit code: 1
  ╰─> [50 lines of output]
      running install
      /Users/dd/cvat/.env/lib/python3.9/site-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
        warnings.warn(
      running build
      running build_py
      creating build
      creating build/lib.macosx-12.4-x86_64-cpython-39
      creating build/lib.macosx-12.4-x86_64-cpython-39/av
      copying av/deprecation.py -> build/lib.macosx-12.4-x86_64-cpython-39/av
      copying av/datasets.py -> build/lib.macosx-12.4-x86_64-cpython-39/av
      copying av/__init__.py -> build/lib.macosx-12.4-x86_64-cpython-39/av
      copying av/__main__.py -> build/lib.macosx-12.4-x86_64-cpython-39/av
      creating build/lib.macosx-12.4-x86_64-cpython-39/av/video
      copying av/video/__init__.py -> build/lib.macosx-12.4-x86_64-cpython-39/av/video
      creating build/lib.macosx-12.4-x86_64-cpython-39/av/codec
      copying av/codec/__init__.py -> build/lib.macosx-12.4-x86_64-cpython-39/av/codec
      creating build/lib.macosx-12.4-x86_64-cpython-39/av/container
      copying av/container/__init__.py -> build/lib.macosx-12.4-x86_64-cpython-39/av/container
      creating build/lib.macosx-12.4-x86_64-cpython-39/av/audio
      copying av/audio/__init__.py -> build/lib.macosx-12.4-x86_64-cpython-39/av/audio
      creating build/lib.macosx-12.4-x86_64-cpython-39/av/subtitles
      copying av/subtitles/__init__.py -> build/lib.macosx-12.4-x86_64-cpython-39/av/subtitles
      creating build/lib.macosx-12.4-x86_64-cpython-39/av/filter
      copying av/filter/__init__.py -> build/lib.macosx-12.4-x86_64-cpython-39/av/filter
      creating build/lib.macosx-12.4-x86_64-cpython-39/av/sidedata
      copying av/sidedata/__init__.py -> build/lib.macosx-12.4-x86_64-cpython-39/av/sidedata
      creating build/lib.macosx-12.4-x86_64-cpython-39/av/data
      copying av/data/__init__.py -> build/lib.macosx-12.4-x86_64-cpython-39/av/data
      running build_ext
      running config
      PyAV: 8.0.2 (unknown commit)
      Python: 3.9.10 (main, Jun 28 2022, 17:49:16) \n[Clang 13.1.6 (clang-1316.0.21.2.5)]
      platform: macOS-12.4-x86_64-i386-64bit
      extension_extra:
          include_dirs: [b'include']
          libraries: []
          library_dirs: []
          define_macros: []
          runtime_library_dirs: []
      config_macros:
          PYAV_COMMIT_STR="unknown-commit"
          PYAV_VERSION=8.0.2
          PYAV_VERSION_STR="8.0.2"
      Could not find libavformat with pkg-config.
      Could not find libavcodec with pkg-config.
      Could not find libavdevice with pkg-config.
      Could not find libavutil with pkg-config.
      Could not find libavfilter with pkg-config.
      Could not find libswscale with pkg-config.
      Could not find libswresample with pkg-config.
      [end of output]
  
  note: This error originates from a subprocess, and is likely not a problem with pip.
error: legacy-install-failure

× Encountered error while trying to install package.
╰─> av


  


  I have already tried suggested fixes, but no luck :
https://github.com/openvinotoolkit/cvat/issues/4406

  


  Environment :

  


  

  • MacBook Pro (Intel x64)

  


  • macOS Monterey (Version 12.4)

  


  • (pyenv) Python 3.9.10

  


  


  What other options could be applied to fix it ?