Recherche avancée

Sur d’autres sites (6668)

• Consent Mode v2 : Everything You Need to Know

  7 mai 2024, par Alex — Analytics Tips

  Confused about Consent Mode v2 and its impact on your website analytics ? You’re not the only one. 

  Google’s latest update has left many scratching their heads about data privacy and tracking. 

  In this blog, we’re getting straight to the point. We’ll break down what Consent Mode v2 is, how it works, and the impact it has.

  What is Consent Mode ?

  What exaclty is Google Consent Mode and why is there so much buzz surrounding it ? This question has been frustrating analysts and marketers worldwide since the beginning of this year. 

  Consent Mode is the solution from Google designed to manage data collection on websites in accordance with user privacy requirements.

  This mode enables website owners to customise how Google tags respond to users’ consent status for cookie usage. At its core, Consent Mode adheres to privacy regulations such as GDPR in Europe and CCPA in California, without significant loss of analytical data.

  

  How does Consent Mode work ?

  Consent Mode operates by adjusting the behaviour of tags on a website depending on whether consent for cookie usage is provided or not. If a user does not consent to the use of analytical or advertising cookies, Google tags automatically switch to collecting a limited amount of data, ensuring privacy compliance.

  This approach allows for continued valuable insights into website traffic and user behavior, even if users opt out of most tracking cookies.

  What types of consent are available in Consent Mode ?

  As of 6 March 2024, Consent Mode v2 has become the current standard (and in terms of utilising Google Advertising Services, practically mandatory), indicating the incorporation of four consent types :

  1. ad_storage : allows for the collection and storage of data necessary for delivering personalised ads based on user actions.
  2. ad_user_data : pertains to the collection and usage of data that can be associated with the user for ad customisation and optimisation.
  3. ad_personalization : permits the use of user data for ad personalisation and providing more relevant content.
  4. analytics_storage : relates to the collection and storage of data for analytics, enabling websites to analyse user behaviour and enhance user experience.

  Additionally, in Consent Mode v2, there are two modes :

  1. Basic Consent Mode : in which Google tags are not used for personalised advertising and measurements if consent is not obtained.
  2. Advanced Consent Mode : allows Google tags to utilise anonymised data for personalised advertising campaigns and measurements, even if consent is not obtained.

  What is Consent Mode v2 ? (And how does it differ from Consent Mode v1 ?)

  Consent Mode v2 is an improved version of the original Consent Mode, offering enhanced customisation capabilities and better compliance with privacy requirements. 

  The new version introduces additional consent configuration parameters, allowing for even more precise control over which data is collected and how it’s used. The key difference between Consent Mode v2 and Consent Mode v1 lies in more granular consent management, making this tool even more flexible and powerful in safeguarding personal data.

  In Consent Mode v2, the existing markers (ad_storage and analytics_storage) are accompanied by two new markers :

  1. ad_user_data – does the user agree to their personal data being utilized for advertising purposes ?
  2. ad_personalization – does the user agree to their data being employed for remarketing ?

  In contrast to ad_storage and analytics_storage, these markers don’t directly affect how the tags operate on the site itself. 

  They serve as additional directives sent alongside the pings to Google services, indicating how user data can be utilised for advertising purposes.

  While ad_storage and analytics_storage serve as upstream qualifiers for data (determining which identifiers are sent with the pings), ad_user_data and ad_personalization serve as downstream instructions for Google services regarding data processing.

  How is the implementation of Consent Mode v2 going ?

  The implementation of Consent Mode v2 is encountering some issues and bugs (as expected). The most important thing to understand :

  1. Advanced Consent Mode v2 is essential if you have traffic and campaigns with Google Ads in the European Union.
  2. If you don’t have substantially large traffic, enabling Advanced Consent Mode v2 will likely result in a traffic drop in GA4 – because this version of consent mode (unlike the basic one) applies behavioural modelling to users who haven’t accepted the use of cookies. And modelling the behaviour requires time.

  The aspect of behavioural modelling in Consent Mode v2 implies the following : the data of users who have declined tracking options begin to be modelled using machine learning. 

  However, training the model requires a suitable data volume. As the Google’s documentation states :

  The property should collect at least 1,000 events per day with analytics_storage=’denied’ for at least 7 days. The property should have at least 1,000 daily users submitting events with analytics_storage=’granted’ for at least 7 of the previous 28 days.

  Largely due to this, the market’s response to the Consent Mode v2 implementation was mixed : many reported a significant drop in traffic in their GA4 and Google Ads reports upon enabling the Advanced mode. Essentially, a portion of the data was lost because Google’s models lacked enough data for training. 

  And from the very beginning of implementation, users regularly report about a few examples of that scenario. If your website doesn’t have enough traffic for behaviour modelling, after Consent Mode v2 switching you will face significant drop in your traffic in Google Ads and GA4 reports. There are a lot of cases of observing 90-95% drop in metrics of users and sessions.

  In a nutshell, you should be prepared for significant data losses if you are planning to switch to Google Consent Mode v2.

  How does Consent Mode v2 impact web analytics ? 

  The transition to Consent Mode v2 alters the methods of user data collection and processing. The main concerns arise from the potential loss of accuracy and completeness of analytical data due to restrictions on the use of cookies and other identifiers when user consent is absent. 

  With Google Consent Mode v2, the data of visitors who have not agreed to tracking will be modelled and may not accurately reflect your actual visitors’ behaviours and actions. So as an analyst or marketer, you will not have true insights into these visitors and the data acquired will be more generalised and less accurate.

  Google Consent Mode v2 appears to be a kind of compromise band-aid solution. 

  It tries to solve these issues by using data modelling and anonymised data collection. However, it’s critical to note that there are specific limitations inherent to the modelling mechanism.

  This complicates the analysis of visitor behavior, advertising campaigns, and website optimisation, ultimately impacting decision-making and resulting in poor website performance and marketing outcomes.

  Wrap up

  Consent Mode v2 is a mechanism of managing Google tag operations based on user consent settings. 

  It’s mandatory if you’re using Google’s advertising services, and optional (at least for Advanced mode) if you don’t advertise on Google Ads. 

  There are particular indications that this technology is unreliable from a GDPR perspective. 

  Using Google Consent Mode will inevitably lead to data losses and inaccuracies in its analysis. 

  In other words, it in some sense jeopardises your business.

• avformat/pcm : decrease target audio frame per sec to 10

  3 mars 2024, par Marton Balint

  avformat/pcm : decrease target audio frame per sec to 10
  This makes the wav and pcm demuxer demux bigger packets, which is more
  
  efficient.
  As a side effect of the bigger packets, audio durations can become less exact
  
  for command lines such as "ffmpeg -i $INPUT -c:a copy -t 1.0 $OUTPUT".
  Signed-off-by : Marton Balint <cus@passwd.hu>
  

  • [DH] libavformat/pcm.c
  • [DH] tests/ref/acodec/pcm-s16be
  • [DH] tests/ref/acodec/pcm-s16be_planar
  • [DH] tests/ref/acodec/pcm-s16le_planar
  • [DH] tests/ref/acodec/pcm-s24be
  • [DH] tests/ref/acodec/pcm-s24le_planar
  • [DH] tests/ref/acodec/pcm-s32be
  • [DH] tests/ref/acodec/pcm-s32le_planar
  • [DH] tests/ref/acodec/pcm-s8_planar
  • [DH] tests/ref/acodec/pcm-u16be
  • [DH] tests/ref/acodec/pcm-u16le
  • [DH] tests/ref/acodec/pcm-u24be
  • [DH] tests/ref/acodec/pcm-u24le
  • [DH] tests/ref/acodec/pcm-u32be
  • [DH] tests/ref/acodec/pcm-u32le
  • [DH] tests/ref/acodec/s302m
  • [DH] tests/ref/fate/dcinema-encode
  • [DH] tests/ref/fate/filter-acrossfade
  • [DH] tests/ref/fate/filter-adelay
  • [DH] tests/ref/fate/filter-aecho
  • [DH] tests/ref/fate/filter-aemphasis-50fm
  • [DH] tests/ref/fate/filter-aemphasis-75kf
  • [DH] tests/ref/fate/filter-afade-esin
  • [DH] tests/ref/fate/filter-afade-exp
  • [DH] tests/ref/fate/filter-afade-hsin
  • [DH] tests/ref/fate/filter-afade-iqsin
  • [DH] tests/ref/fate/filter-afade-log
  • [DH] tests/ref/fate/filter-afade-qsin
  • [DH] tests/ref/fate/filter-agate
  • [DH] tests/ref/fate/filter-alimiter
  • [DH] tests/ref/fate/filter-amerge
  • [DH] tests/ref/fate/filter-anequalizer
  • [DH] tests/ref/fate/filter-apad
  • [DH] tests/ref/fate/filter-asegment-samples-absolute
  • [DH] tests/ref/fate/filter-asegment-samples-relative
  • [DH] tests/ref/fate/filter-asegment-timestamps-absolute
  • [DH] tests/ref/fate/filter-asegment-timestamps-relative
  • [DH] tests/ref/fate/filter-asetrate
  • [DH] tests/ref/fate/filter-atrim-mixed
  • [DH] tests/ref/fate/filter-atrim-time
  • [DH] tests/ref/fate/filter-chorus
  • [DH] tests/ref/fate/filter-compand
  • [DH] tests/ref/fate/filter-crystalizer
  • [DH] tests/ref/fate/filter-dcshift
  • [DH] tests/ref/fate/filter-earwax
  • [DH] tests/ref/fate/filter-extrastereo
  • [DH] tests/ref/fate/filter-pan-downmix1
  • [DH] tests/ref/fate/filter-pan-downmix2
  • [DH] tests/ref/fate/filter-pan-mono1
  • [DH] tests/ref/fate/filter-pan-mono2
  • [DH] tests/ref/fate/filter-pan-stereo1
  • [DH] tests/ref/fate/filter-pan-stereo2
  • [DH] tests/ref/fate/filter-pan-stereo3
  • [DH] tests/ref/fate/filter-pan-stereo4
  • [DH] tests/ref/fate/filter-pan-upmix1
  • [DH] tests/ref/fate/filter-pan-upmix2
  • [DH] tests/ref/fate/filter-stereotools
  • [DH] tests/ref/fate/flcl1905
  • [DH] tests/ref/fate/g722-encode
  • [DH] tests/ref/fate/g726-encode-2bit
  • [DH] tests/ref/fate/g726-encode-3bit
  • [DH] tests/ref/fate/g726-encode-4bit
  • [DH] tests/ref/fate/g726-encode-5bit
  • [DH] tests/ref/fate/matroska-move-cues-to-front
  • [DH] tests/ref/fate/mov-channel-description
  • [DH] tests/ref/fate/mov-mp4-pcm
  • [DH] tests/ref/fate/mov-mp4-pcm-float
  • [DH] tests/ref/lavf/ast
  • [DH] tests/ref/lavf/mov
  • [DH] tests/ref/lavf/mov_rtphint
  • [DH] tests/ref/lavf/s16.voc
  • [DH] tests/ref/lavf/smjpeg
  • [DH] tests/ref/lavf/voc
  • [DH] tests/ref/seek/acodec-adpcm-ima_wav
  • [DH] tests/ref/seek/acodec-adpcm-ima_wav-trellis
  • [DH] tests/ref/seek/acodec-adpcm-ms
  • [DH] tests/ref/seek/acodec-adpcm-ms-trellis
  • [DH] tests/ref/seek/acodec-adpcm-yamaha
  • [DH] tests/ref/seek/acodec-adpcm-yamaha-trellis
  • [DH] tests/ref/seek/acodec-pcm-alaw
  • [DH] tests/ref/seek/acodec-pcm-f32be
  • [DH] tests/ref/seek/acodec-pcm-f32le
  • [DH] tests/ref/seek/acodec-pcm-f64be
  • [DH] tests/ref/seek/acodec-pcm-f64le
  • [DH] tests/ref/seek/acodec-pcm-mulaw
  • [DH] tests/ref/seek/acodec-pcm-s16le
  • [DH] tests/ref/seek/acodec-pcm-s24le
  • [DH] tests/ref/seek/acodec-pcm-s32le
  • [DH] tests/ref/seek/acodec-pcm-u8
  • [DH] tests/ref/seek/lavf-al
  • [DH] tests/ref/seek/lavf-au
  • [DH] tests/ref/seek/lavf-mov
  • [DH] tests/ref/seek/lavf-ul
  • [DH] tests/ref/seek/lavf-voc
  • [DH] tests/ref/seek/lavf-wav

• lavu/avsscanf : Do not mix declaration and code.

  18 novembre 2018, par Carl Eugen Hoyos

  lavu/avsscanf : Do not mix declaration and code.
  Fixes the following warning :
  
  libavutil/avsscanf.c : In function 'decfloat' :
  
  libavutil/avsscanf.c:354:9 : warning : ISO C90 forbids mixed declarations and code [-Wdeclaration-after-statement]
  
           int bitlim = bits-3*(int)(rp-9) ;
  
           ^ 
  

  • [DH] libavutil/avsscanf.c