Recherche avancée

Médias (91)

Autres articles (39)

  • Personnaliser les catégories

    21 juin 2013, par

    Formulaire de création d’une catégorie
    Pour ceux qui connaissent bien SPIP, une catégorie peut être assimilée à une rubrique.
    Dans le cas d’un document de type catégorie, les champs proposés par défaut sont : Texte
    On peut modifier ce formulaire dans la partie :
    Administration > Configuration des masques de formulaire.
    Dans le cas d’un document de type média, les champs non affichés par défaut sont : Descriptif rapide
    Par ailleurs, c’est dans cette partie configuration qu’on peut indiquer le (...)

  • Ajouter notes et légendes aux images

    7 février 2011, par

    Pour pouvoir ajouter notes et légendes aux images, la première étape est d’installer le plugin "Légendes".
    Une fois le plugin activé, vous pouvez le configurer dans l’espace de configuration afin de modifier les droits de création / modification et de suppression des notes. Par défaut seuls les administrateurs du site peuvent ajouter des notes aux images.
    Modification lors de l’ajout d’un média
    Lors de l’ajout d’un média de type "image" un nouveau bouton apparait au dessus de la prévisualisation (...)

  • Contribute to translation

    13 avril 2011

    You can help us to improve the language used in the software interface to make MediaSPIP more accessible and user-friendly. You can also translate the interface into any language that allows it to spread to new linguistic communities.
    To do this, we use the translation interface of SPIP where the all the language modules of MediaSPIP are available. Just subscribe to the mailing list and request further informantion on translation.
    MediaSPIP is currently available in French and English (...)

Sur d’autres sites (7562)

  • First-party data explained : Benefits, use cases and best practices

    25 juillet, par Joe

    Third-party cookies are being phased out, and marketers who still depend on them for user insights need to find alternatives.

    Google delayed the complete deprecation of third-party cookies until early 2025, but many other browsers, such as Mozilla, Brave, and Safari, have already put a stop to them. Plus, looking at the number of data leak incidents, like the one where Twitter leaked 200 million user emails, collecting and using first-party data is a great alternative. 

    In this post, we explore the ins and outs of first-party data and examine how to collect it. We’ll also look at various use cases and best practices to implement first-party data collection.

    What is first-party data ?

    First-party data is information organisations collect directly from customers through their owned channels. 

    Organisations can capture data without intermediaries when people interact with their website, mobile app, social media accounts or other customer-facing systems.

    For example, businesses can track visitor behaviour, such as bounce rates and time spent browsing particular pages. This activity is considered first-party data when it occurs on the brand’s digital property.

    Some examples include :

    • Demographics : Age, gender, location, income level
    • Contact information : Email addresses, phone numbers
    • Behavioural insights : Topics of interest, content engagement, browsing history
    • Transactional data : Purchase history, shopping preferences

    A defining characteristic is that this information comes straight from the source, with the customer’s willingness and consent. This direct collection method is why first-party data is widely regarded as more reliable and accurate than second or third-party data. With browsers like Chrome fully phasing out third-party cookies by the end of 2025, the urgency for adopting more first-party data strategies is accelerating across industries.

    How to collect first-party data 

    Organisations can collect first-party data in various ways. 

    Website pixels

    In this method, organisations place small pieces of code that track visitor actions like page views, clicks and conversions. When visitors land on the page, the pixel activates and collects data about their behaviour without interrupting the user experience. 

    Website analytics tools

    With major browsers like Safari and Firefox already blocking third-party cookies (and Chrome is phasing them out soon, there’s even more pressure on organisations to adopt first-party data strategies.

    Website analytics tools like Matomo help organisations collect first-party data with features like visitor tracking and acquisition analysis to analyse the best channels to attract more users. 

    Multi-attribution modelling that helps businesses understand how different touchpoints (social media channels or landing pages) persuade visitors to take a desired action (like making a purchase). 

    Various web analytics features of Matomo

    (Image Source)

    Other activities include :

    • Cohort analysis 
    • Heatmaps and session recordings 
    • SEO keyword tracking
    • A/B testing 
    • Paid ads performance tracking
    Home page heat map showing user clicks

    Heatmap feature in Matomo

    Account creation on websites

    When visitors register on websites, they provide information like names, email addresses and often demographic details or preferences.

    Newsletters and subscriptions 

    With email subscriptions and membership programs, businesses can collect explicit data (preferences selected during signup) and implicit data (engagement metrics like open rates and click patterns).

    Gated content

    Whitepapers, webinars or exclusive articles often ask for contact information when users want access. This approach targets specific audience segments interested in particular topics.

    Customer Relationship Management (CRM) systems

    CRM platforms collect information from various touchpoints and centralise it to create unified customer profiles. These profiles include detailed user information, like interaction history, purchase records, service inquiries and communication preferences.

    Mobile app activity

    Mobile in-app behaviours can assist businesses in gathering data such as :

    • Precise location information (indicating where customers interact with the app)
    • Which features they use most often
    • How long they stay on different screens
    • Navigation patterns

    This mobile-specific data helps organisations understand how their customers behave on smaller screens and while on the move, insights that website data alone cannot provide.

    Point of Sale (PoS) systems

    Modern checkout systems don’t just process payments. PepsiCo proved this by growing its first-party data stores by more than 50% through integrated PoS systems. 

    Today’s PoS technology captures detailed information about each transaction :

    • Item(s) sold
    • Price (discounts, taxes, tip)
    • Payment type (card, cash, digital wallet)
    • Time and date
    • Loyalty/rewards number
    • Store/location

    Plus, when connected with loyalty programs where customers identify themselves (by scanning a card or entering a phone number), these systems link purchase information to individuals. 

    This creates valuable historical records showing how customer preferences evolve and offering insight into :

    • Which products are frequently purchased together
    • The time of the day, week, month, or year when items sell best
    • Which promotions or special offers are most effective

    Server-side tracking 

    Most websites track user behaviour through code that runs in the visitor’s web browser (client-side tracking). 

    Server-side tracking takes a different approach by collecting data directly on the company’s own servers. 

    Because the tracking happens on company servers rather than browsers, ad-blocking software doesn’t block it. 

    Organisations gain more consistent data collection and greater control over their customer information. This privacy-friendly approach lets companies get the data they need without relying on third-party tracking scripts.

    Now that we understand how organisations can gather first-party data, let us explore its use cases. 

    Use cases of first-party data 

    Businesses can use first-party data in many ways, from creating customer profiles to personalising user experiences.

    Developing comprehensive customer profiles

    First-party data can help create detailed customer profiles

    Here are some examples :

    • Demographic profiles : Age, gender, location, job role and other personal characteristics.
    • Behavioural profiles : Website activity, purchase history and engagement with marketing campaigns that focus on how users interact with businesses and their offerings
    • Psychographic profiles : Customer’s interests, values and lifestyle preferences.
    • Transactional profiles : Purchase patterns, including the types of products they buy, how often they purchase and their total spending.

    The benefit of developing these profiles is that businesses can then create specific campaigns for each profile, instead of running random campaigns. 

    For example, a subscription service business may have a behavioural profile of ‘inactive users’. To reignite interest, they can offer discounts or limited-time freebies to these users.

    Crafting relevant content

    First-party data shows what types of content customers engage with most. 

    If customers love watching videos, businesses can create more video content. If a blog gets more readership for its tech articles, it can focus on tech-related content to adjust to readers’ preferences. 

    Uncovering new marketing opportunities

    First-party data lets businesses analyse customer interactions in a way that can reveal untapped markets. 

    For example, if a company sees that many website visitors are from a particular region, it might consider launching campaigns in that area to boost sales. 

    Personalising experiences

    89% of decision-makers believe personalisation is key to business success in the next three years. 

    First-party data helps organisations to tailor experiences based on individual preferences. 

    Personalised experiences increases customer satisfaction

    For example, an e-commerce site can recommend products based on previous purchases or browsing history. Shoppers with abandoned carts can get reminders. 

    It’s also helpful to see how customers respond to different types of communication. Certain groups may prefer emails, and some may prefer text messages. Similarly, some users spend more time on quizzes and interactive content like wizards or calculators. 

    By analysing this, businesses can adjust their strategies so that users get a personal experience when they visit a website.

    Optimising operations

    The use cases of first-party data don’t just apply to the marketing domain. They’re also valuable for operations. When businesses analyse customer order patterns, they can spot the best locations for fulfilment centres that reduce shipping time and costs.

    For example, an online retailer might discover that most customers are concentrated in urban areas and decide to open fulfilment centres closer to those locations.

    Or, in the public sector, transport companies can use first-party data to optimise routes and fine-tune fare simulation tools. By analysing rider queries, travel preferences and interaction data, they can :

    • Prioritise high-demand routes during peak hours 
    • Adjust fare structures to reflect common trip or rider patterns
    • Make personalised travel suggestions based on individual user history.

    Benefits of first-party data 

    First-party data offers two significant benefits : accuracy and compliance. It comes directly from the customers and can be considered more accurate and reliable. But that’s not it. 

    First-party data aligns with many data privacy regulations, like the GDPR and CCPA. That’s because first-party data collection requires explicit consent, which means the data remains confidential. This builds compliance, and customers develop more trust in the business.

    Best practices to collect and manage first-party data 

    Though first-party data comes with many benefits, how should organisations collect and manage it ? What are the best practices ? Let’s take a look. 

    Define clear goals

    Though defining clear goals seems like overused advice, it’s one of the most important. If a business doesn’t know why it’s collecting first-party data, all the information gathering becomes purposeless. 

    Businesses can think of different goals to achieve from first-party data collection : improving customer relationships, enhancing personalisation or increasing ROI. 

    Once these goals are concrete, they can guide data collection strategies and help understand whether they’re working.

    Establish a privacy policy

    A privacy policy is a document that explains why a business is collecting a user’s data and what it will do with it. By being open and honest, this policy builds trust with customers, so customers feel safe sharing their information. 

    For example, an e-commerce privacy policy may read like : 

    “At (Business name), your privacy is important to us. We collect your information when you create an account or buy something. This information includes your name, email and purchase history. We use this data to give you a better shopping experience and suggest products that you’ll find useful. We follow all data privacy laws like GDPR to keep your personal information safe.” 

    For organisations that use Matomo, we suggest updating the privacy policy to explain how Matomo is used and what data it collects. Here’s a privacy policy template for Matomo users that can be easily copied and pasted. 

    For a GDPR compatible privacy policy, read How to complete your privacy policy with Matomo analytics under GDPR.

    Simplify consent processes

    Businesses should obtain explicit user consent before collecting their data, as shown in the image below. 

    Have a consent process in place that shares what kind of user data is going ot be accessed

    (Image Source

    To do this, integrate user-friendly consent management platforms that let customers easily access, view, opt out of, or delete their information.

    To ensure consent practices align with GDPR standards, follow these key steps :

    GDPR-compliant consent checklist
    State the purpose clearlyDescribe data usage in plain terms.
    Use granular opt-insSeparate consents by purpose.
    Avoid pre-ticked boxesActive choices only.
    Enable easy opt-outSimple and accessible withdrawal.
    Log consentTimestamp and record every opt-in.
    Review periodicallyAudit for accuracy and relevance.

    Comply with platform-specific restrictions

    In addition to general consent practices, businesses must comply with platform-specific restrictions. This includes obtaining explicit permissions for :

    • Location services : Users must consent to sharing their location data.
    • Contact lists : Businesses need permission to access and use contact information.
    • Camera and microphone Use : Users must consent to using the camera and microphone 
    • Advertising IDs : On platforms like iOS, businesses must obtain consent to use advertising IDs. 

    For example, Zoom asks the user if it can access the camera and the microphone by default.

    Utilise multiple data collection channels

    Instead of relying on just one source to collect first-party data, it is better to use multiple channels. Gather first-party data from diverse sources such as websites, mobile apps, CRM systems, email campaigns, and in-store interactions (for richer datasets). This way, businesses get a more complete picture of their customers.

    Implementing a strong data governance framework with proper tooling, taxonomy, and maintenance practices is also vital for better data usability.

    Use privacy-focused analytics tools 

    Focus on not just collecting data but also doing it in a way that’s secure and ethical

    Use tools like Matomo to track user interactions and gather meaningful analytics. For example, Matomo heatmaps can give you a visual insight into where users click and scroll, all while following all the data privacy laws.

    Matomo's heatmaps giving a visual insight into where users scroll the most

    (Image Source

    What is second-party data ? 

    Second-party data is information that one company collects from its customers and shares with another company. It’s like “second-hand” first-party data because it’s collected directly from customers but used by a different business.

    Companies purchase second-party data from trusted partners instead of getting it directly from the customer. For example, hotel chains can use customer insights from online travel agencies, like popular destinations and average stay lengths, to refine their pricing strategies and offer more relevant perks.

    When using second-party data, it’s essential to :

    • Be transparent : Share with customers that their data is being shared with partners. 
    • Conduct regular audits : Ensure the data is accurate and handled properly to maintain strong privacy standards. If their data standards don’t seem that great, consider looking elsewhere.

    What is third-party data ? 

    Third-party data is collected from various sources, such as public records, social media or other online platforms. It’s then aggregated and sold to businesses. Organisations get third-party data from data brokers, aggregators and data exchanges or marketplaces. 

    Some examples of third-party data include life events from user social media profiles, like graduation or facts about different organisations, like the number of employees and revenue.

    For example, a data broker might collect information about people’s interests from social media and sell it to a company that wants to target ads based on those interests.

    Third-party data often raises privacy concerns due to its collection methods. One major issue is the lack of transparency in how this data is obtained. 

    Consumers often don’t know that their information is being collected and sold by third-party brokers, leading to feelings of mistrust and violation of privacy. This is why data privacy guidelines have evolved. 

    What is zero-party data ? 

    Zero-party data is the information that customers intentionally share with a business. Some examples include surveys, product ratings and reviews, social media polls and giveaways.

    Organisations collect first-party data by observing user behaviours, but zero-party data is the information that customers voluntarily provide. 

    Differences between first-party and zero-party data

    Zero-party data can provide helpful insights, but self-reported information isn’t always accurate. People don’t always do what they say. 

    For example, customers in a survey may share that they consider quality above all else when purchasing. Still, looking at their actual behaviour, businesses can see that they make a purchase only when there’s a clearance or a sale.

    First-party data can give a broader view of customer behaviours over time, which zero-party data may not always be able to capture. 

    Therefore, while zero-party data offers insights into what customers say they want, first-party data helps understand how they behave in real-world scenarios. Balancing both data types can lead to a deeper understanding of customer needs.

    Getting valuable customer insights without compromising privacy 

    Matomo is a powerful tool for organisations that want to collect first-party data. We’re a full-featured web analytics tool that offers features that allow businesses to track user interactions without compromising the user’s personal information. Below, we share how.

    Data ownership

    Matomo allows organisations to own their analytics data, whether on-premise or in their chosen cloud. This means we don’t share your data with anyone else. This aligns with GDPR’s requirement for data sovereignty and minimises third-party risks.

    Pseudonymisation of user IDs

    Matomo allows organisations to pseudonymise user IDs, replacing them with a salted hash function. 

    Image depticting the working of the pseudonymisation feature by Matomo

    (Image Source)

    Since the user IDs have different names, no one can trace them back to a specific person.

    IP address anonymisation

    Data anonymisation refers to removing personally identifiable information (PII) from datasets so individuals can’t be readily identified.

    Matomo automatically anonymises visitor IP addresses, which helps respect user privacy. For example, if the visitor’s IP address is 199.513.1001.123, Matomo can mask it to 199.0.0.0. 

    It can also anonymise geo-location information, such as country, region and city, ensuring this data doesn’t directly identify users.

    Anonymise geo-location information with Matomo

    (Image Source

    Consent management

    Matomo offers an opt-out option that organisations can add to their website, privacy policy or legal page. 

    Matomo tracks everyone by default, but visitors can opt out by clicking the opt-out checkbox. 

    Our DoNotTrack technology helps businesses respect user choices to opt out of tracking from specific websites, such as social media or advertising platforms. They can simply select the “Support Do Not Track preference.”

    These help create consent workflows and support audit trails for regulators. 

    Data storage and deletion

    Keeping visitor data only as long as necessary is a good practice by default. 

    To adhere to this principle, organisations can configure Matomo to automatically delete old raw data and old aggregated report data. 

    Here’s a quick case study summarising how Matomo features can help organisations collect first-party data. CRO:NYX found that Google Analytics struggled to capture accurate data from their campaigns, especially when running ads on the Brave browser, which blocks third-party cookies.

    They then switched to Matomo, which uses first-party cookies by default. This approach allowed them to capture accurate data from Brave users without putting user privacy at stake. 

    The value of Matomo in first-party data strategies 

    First-party data gives businesses a reliable way to connect with audiences and to improve marketing strategies. 

    Matomo’s ethical web analytics lets organisations collect and analyse this data while prioritising user privacy. 

    With over 1 million websites using Matomo, it’s a trusted choice for organisations of all sizes. As a cloud-hosted service and a fully self-hosted solution, Matomo supports organisations with strong data sovereignty needs, allowing them to maintain full control over their analytics infrastructure.

    Ready to collect first-party data while securing user information ? Start your free 21-day trial, no credit card required.

  • Problem with ffplay from webcam stream using complex filters

    29 mai 2022, par efelbar

    I'm trying to stream video from a webcam (at /dev/video2) through ffplay to scale and recolor it, add some text, and then reduce the number of colors with palettes. I don't get any errors, but running the ffplay command :

    


    ffplay -i /dev/video2 -vf "hflip,\
  colorbalance=\
    rs=0.4:\
    bs=-0.4\
  ,\
  scale=\
    trunc(iw/8):\
    trunc(ih/8)\
  ,\
  drawtext=\
    text=\
      'efelbar':\
      fontcolor=white:\
      fontsize=10:\
      box=1:\
      boxcolor=black:\
      boxborderw=5:\
      x=(w-text_w)/2:\
      y=(h-text_h)/2\
  ,\
  split[s0][s1];\
  [s0]palettegen=\
    max_colors=16\
  [p];\
  [s1][p]paletteuse"


    


    seems to stall, and fails to produce video output.

    


    Running the simpler command ffplay -i /dev/video2 -vf "split[s0][s1];[s0]palettegen=max_colors=16[p];[s1][p]paletteuse", which takes a stream from a webcam and (should) reduce the number of colors, results in it just sitting there without showing the actual output stream. This might just be a performance issue because I'm on older hardware, but it doesn't give output relfective of that.

    


    The output of that command is as follows :

    


    ffplay version n5.0 Copyright (c) 2003-2022 the FFmpeg developers
  built with gcc 11.2.0 (GCC)
  configuration: --prefix=/usr --disable-debug --disable-static --disable-stripping --enable-amf --enable-avisynth --enable-cuda-llvm --enable-lto --enable-fontconfig --enable-gmp --enable-gnutls --enable-gpl --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libdav1d --enable-libdrm --enable-libfreetype --enable-libfribidi --enable-libgsm --enable-libiec61883 --enable-libjack --enable-libmfx --enable-libmodplug --enable-libmp3lame --enable-libopencore_amrnb --enable-libopencore_amrwb --enable-libopenjpeg --enable-libopus --enable-libpulse --enable-librav1e --enable-librsvg --enable-libsoxr --enable-libspeex --enable-libsrt --enable-libssh --enable-libsvtav1 --enable-libtheora --enable-libv4l2 --enable-libvidstab --enable-libvmaf --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxcb --enable-libxml2 --enable-libxvid --enable-libzimg --enable-nvdec --enable-nvenc --enable-shared --enable-version3
  libavutil      57. 17.100 / 57. 17.100
  libavcodec     59. 18.100 / 59. 18.100
  libavformat    59. 16.100 / 59. 16.100
  libavdevice    59.  4.100 / 59.  4.100
  libavfilter     8. 24.100 /  8. 24.100
  libswscale      6.  4.100 /  6.  4.100
  libswresample   4.  3.100 /  4.  3.100
  libpostproc    56.  3.100 / 56.  3.100
Input #0, video4linux2,v4l2, from '/dev/video2':B sq=    0B f=0/0   
  Duration: N/A, start: 254970.739108, bitrate: 147456 kb/s
  Stream #0:0: Video: rawvideo (YUY2 / 0x32595559), yuyv422, 640x480, 147456 kb/s, 30 fps, 30 tbr, 1000k tbn


    


    I'm running this on a thinkpad t420s, so I definitely wouldn't be surprised if my laptop just can't process video that quickly. If that is the case, suggestions for optimizations would be great !

    


  • ffmpeg Batch Replace MP4 Thumbnails

    1er juin 2022, par pglove

    Windows 10, 2022 build of ffmpeg

    


    I found this command to replace the thumbnails on mp4 files :

    


    ffmpeg -i video.mp4 -i image.png -map 1 -map 0 -c copy -disposition:0 attached_pic out.mp4


    


    here :
How do I add a custom thumbnail to a .mp4 file using ffmpeg ?

    


    I have modified it to use jpg instead of png, and have a folder full of videos and images.

    


    ffmpeg -i ###.mp4 -i ###.jpg -map 1 -map 0 -c copy -disposition:0 attached_pic ###-new.mp4


    


    Every mp4 has an alpha-numeric name with a corresponding jpg of the same name.

    


    I generated a list of commands I would need for each file, so I have 100 commands.

    


    If I copy and paste one line at a time it works, but when I copy and paste all 100 lines into the command line on windows it seems like one or two files process as expected, but the rest fail.

    


    I'm pretty sure I'm just missing a step, and any help would be much appreciated turning it into a batch process.

    


    Thanks

    


    *I just tried with 2 lines, the first processed, the second stopped.

    


    Some feedback would be nice if I've posed the question poorly, not provided enough information, or done something else wrong to deserve a downvote already. I don't use forums very often, I try to only ask when I'm stumped, so perhaps my etiquette is poor. I thought I followed correct procedure...