Recherche avancée

Sur d’autres sites (4058)

• Revision 32884 : auteurs dans les sommaires (page d’accueil+rubriques)

  13 novembre 2009, par fil@… — Log

  auteurs dans les sommaires (page d’accueil+rubriques)

• Making Your First-Party Data Work for You and Your Customers

  11 mars, par Alex Carmona

  At last count, 162 countries had enacted data privacy policies of one kind or another. These laws or regulations, without exception, intend to eliminate the use of third-party data. That puts marketing under pressure because third-party data has been the foundation of online marketing efforts since the dawn of the Internet.

  Marketers need to future-proof their operations by switching to first-party data. This will require considerable adjustment to systems and processes, but the reward will be effective marketing campaigns that satisfy privacy compliance requirements and bring the business closer to its customers.

  To do that, you’ll need a coherent first-party data strategy. That’s what this article is all about. We’ll explain the different types of personal data and discuss how to use them in marketing without compromising or breaching data privacy regulations. We’ll also discuss how to build that strategy in your business. 

  So, let’s dive in.

  The different data types

  There are four distinct types of personal data used in marketing, each subject to different data privacy regulations.

  Before getting into the different types, it’s essential to understand that all four may comprise one or more of the following :

  Identifying data	Name, email address, phone number, etc.
  Behavioural data	Website activity, app usage, wishlist content, purchase history, etc.
  Transactional data	Orders, payments, subscription details, etc.
  Account data	Communication preferences, product interests, wish lists, etc.
  Demographic data	Age, gender, income level, education, etc.
  Geographic Data	Location-based information, such as zip codes or regional preferences.
  Psychographic Data	Interests, hobbies and lifestyle preferences.

  First-party data

  When businesses communicate directly with customers, any data they exchange is first-party. It doesn’t matter how the interaction occurs : on the telephone, a website, a chat session, or even in person.

  Of course, the parties involved aren’t necessarily individuals. They may be companies, but people within those businesses will probably share at least some of the data with colleagues. That’s fine, so long as the data : 

  • Remains confidential between the original two parties involved, and 
  • It is handled and stored following applicable data privacy regulations.

  The core characteristic of first-party data is that it’s collected directly from customer interactions. This makes it reliable, accurate and inherently compliant with privacy regulations — assuming the collecting party complies with data privacy laws.

  A great example of first-party data use is in banking. Data collected from customer interactions is used to provide personalised services, detect fraud, assess credit risk and improve customer retention.

  Zero-party data

  There’s also a subset of first-party data, sometimes called zero-party data. It’s what users intentionally and proactively share with a business. It can be preferences, intentions, personal information, survey responses, support tickets, etc.

  What makes it different is that the collection of this data depends heavily on the user’s trust. Transparency is a critical factor, too ; visitors expect to be informed about how you’ll use their data. Consumers also have the right to withdraw permission to use all or some of their information at any time.

  

  Second-party data

  This data is acquired from a separate organisation that collects it firsthand. Second-party data is someone else’s first-party data that’s later shared with or sold to other businesses. The key here is that whoever owns that data must give explicit consent and be informed of who businesses share their data with.

  A good example is the cooperation between hotel chains, car rental companies, and airlines. They share joint customers’ flight data, hotel reservations, and car rental bookings, much like travel agents did before the internet undermined that business model.

  Third-party data

  This type of data is the arch-enemy of lawmakers and regulators trying to protect the personal data of citizens and residents in their country. It’s information collected by entities that have no direct relationship with the individuals whose data it is.

  Third-party data is usually gathered, aggregated, and sold by data brokers or companies, often by using third-party cookies on popular websites. It’s an entire business model — these third-party brokers sell data for marketing, analytics, or research purposes. 

  Most of the time, third-party data subjects are unaware that their data has been gathered and sold. Hence the need for strong data privacy regulations.

  Benefits of a first-party data strategy

  First-party data is reliable, accurate, and ethically sourced. It’s an essential part of any modern digital marketing strategy.

  More personalised experiences

  The most important application of first-party data is customising and personalising customers’ interactions based on real behaviours and preferences. Personalised experiences aren’t restricted to websites and can extend to all customer communication.

  The result is company communications and marketing messages are far more relevant to customers. It allows businesses to engage more meaningfully with them, building trust and strengthening customer relationships. Inevitably, this also results in stronger customer loyalty and better customer retention.

  Greater understanding of customers

  Because first-party data is more accurate and reliable, it can be used to derive valuable insights into customer needs and wants. When all the disparate first-party data points are centralised and organised, it’s possible to uncover trends and patterns in customer behaviour that might not be apparent using other data.

  This helps businesses predict and respond to customer needs. It also allows marketing teams to be more deliberate when segmenting customers and prospects into like-minded groups. The data can also be used to create more precise personas for future campaigns or reveal how likely a customer would be to purchase in response to a campaign.

  Build trust with customers

  First-party data is unique to a business and originates from interactions with customers. It’s also data collected with consent and is “owned” by the company — if you can ever own someone else’s data. If treated like the precious resource, it can help businesses build trust with customers.

  However, developing that trust requires a transparent, step-by-step approach. This gradually strengthens relationships to the point where customers are more comfortable sharing the information they’re asked for.

  However, while building trust is a long and sometimes arduous process, it can be lost in an instant. That’s why first-party data must be protected like the Crown Jewels.

  

  Components of a first-party data strategy

  Security is essential to any first-party data strategy, and for good reason. As Gartner puts it, a business must find the optimal balance between business outcomes and data risk mitigation. Once security is baked in, attention can turn to the different aspects of the strategy.

  Data collection

  There are many ways to collect first-party data ethically, within the law and while complying with data privacy regulations, such as Europe’s General Data Protection Regulation (GDPR). Potential sources include :

  Website activity	forms and surveys, behavioural tracking, cookies, tracking pixels and chatbots
  Mobile app interactions	in-app analytics, push notifications and in-app forms
  Email marketing	newsletter sign-ups, email engagement tracking, promotions, polls and surveys
  Events	registrations, post-event surveys and virtual event analytics
  Social media interaction	polls and surveys, direct messages and social media analytics
  Previous transactions	purchase history, loyalty programmes and e-receipts
  Customer service	call centre data, live chat, chatbots and feedback forms
  In-person interactions	in-store purchases, customer feedback and Wi-Fi sign-ins
  Gated content	whitepapers, ebooks, podcasts, webinars and video downloads
  Interactive content	quizzes, assessments, calculators and free tools
  CRM platforms	customer profiles and sales data
  Consent management	privacy policies, consent forms, preference setting

  Consent management

  It may be the final item on the list above, but it’s also a key requirement of many data privacy laws and regulations. For example, the GDPR is very clear about consent : “Processing personal data is generally prohibited, unless it is expressly allowed by law, or the data subject has consented to the processing.”

  For that reason, your first-party data strategy must incorporate various transparent consent mechanisms, such as cookie banners and opt-in forms. Crucially, you must provide customers with a mechanism to manage their preferences and revoke that consent easily if they wish to.

  Data management

  Effective first-party data management, mainly its security and storage, is critical. Most data privacy regimes restrict the transfer of personal data to other jurisdictions and even prohibit it in some instances. Many even specify where residents’ data must be stored.

  Consider this cautionary tale : The single biggest fine levied for data privacy infringement so far was €1.2 billion. The Irish Data Protection Commission imposed a massive fine on Meta for transferring EU users’ data to the US without adequate data protection mechanisms.

  Data security is critical. If first-party data is compromised, it becomes third-party data, and any customer trust developed with the business will evaporate. To add insult to injury, data regulators could come knocking. That’s why the trend is to use encryption and anonymisation techniques alongside standard access controls.

  Once security is assured, the focus is on data management. Many businesses use a Customer Data Platform. This software gathers, combines and manages data from many sources to create a complete and central customer profile. Modern CRM systems can also do that job. AI tools could help find patterns and study them. But the most important thing is to keep databases clean and well-organised to make it easier to use and avoid data silos.

  Data activation

  Once first-party data has been collected and analysed, it needs to be activated, which means a business needs to use it for the intended purpose. This is the implementation phase where a well-constructed first-party strategy pays off. 

  The activation stage is where businesses use the intelligence they gather to :

  • Personalise website and app experiences
  • Adapt marketing campaigns
  • Improve conversion rates
  • Match stated preferences
  • Cater to observed behaviours
  • Customise recommendations based on purchase history
  • Create segmented email campaigns
  • Improve retargeting efforts
  • Develop more impactful content

  Measurement and optimisation

  Because first-party data is collected directly from customers or prospects, it’s far more relevant, reliable, and specific. Your analytics and campaign tracking will be more accurate. This gives you direct and actionable insights into your audience’s behaviour, empowering you to optimise your strategies and achieve better results.

  The same goes for your collection and activation efforts. An advanced web analytics platform like Matomo lets you identify key user behaviour and optimise your tracking. Heatmaps, marketing attribution tools, user behaviour analytics and custom reports allow you to segment audiences for better traction (and collect even more first-party data).

  

  How to build a first-party data strategy

  There are five important and sequential steps to building a first-party data strategy. But this isn’t a one-time process. It must be revisited regularly as operating and regulatory environments change. There are five steps : 

  1. Audit existing data

  Chances are that customers already freely provide a lot of first-party data in the normal course of business. The first step is to locate this data, and the easiest way to do that is by mapping the customer journey. This identifies all the touchpoints where first-party data might be found.

  2. Define objectives

  Then, it’s time to step back and figure out the goals of the first-party data strategy. Consider what you’re trying to achieve. For example :

  • Reduce churn 
  • Expand an existing loyalty programme
  • Unload excess inventory
  • Improve customer experiences

  Whatever the objectives are, they should be clear and measurable.

  3. Implement tools and technology

  The first two steps point to data gaps. Now, the focus turns to ethical web analytics with a tool like Matomo. 

  To further comply with data privacy regulations, it may also be appropriate to implement a Consent Management Platform (CMP) to help manage preferences and consent choices.

  4. Build trust with transparency

  With the tools in place, it’s time to engage customers. To build trust, keep them informed about how their data is used and remind them of their right to withdraw their consent. 

  Transparency is crucial in such engagement, as outlined in the 7 GDPR principles.

  5. Continuously improve

  Rinse and repeat. The one constant in business and life is change. As things change, they expose weaknesses or flaws in the logic behind systems and processes. That’s why a first-party data strategy needs to be continually reviewed, updated, and revised. It must adapt to changing trends, markets, regulations, etc. 

  Tools that can help

  Looking back at the different types of data, it’s clear that some are harder and more bothersome to get than others. But capturing behaviours and interactions can be easy — especially if you use tools that follow data privacy rules.

  But here’s a tip. Google Analytics 4 isn’t compliant by default, especially not with Europe’s GDPR. It may also struggle to comply with some of the newer data privacy regulations planned by different US states and other countries.

  Matomo Analytics is compliant with the GDPR and many other data privacy regulations worldwide. Because it’s open source, it can be integrated with any consent manager.

  Get started today by trying Matomo for free for 21 days,
  no credit card required.

  Try Matomo for free

• Discord.js Music bot TypeError [ERR_INVALID_ARG_TYPE] : The "file" argument must be of type string. Received type object

  21 février 2020, par Cole Perry

  I’m new to Discord.js and I’m trying to have the bot join a voice channel and play an audio file on my computer. I have been following this guide : https://discord.js.org/#/docs/main/stable/topics/voice . Here is the Index.js page :

  const Discord = require('discord.js');
  
  const Colesbot = new Discord.Client();
  
  
  
  const token = '***********************************************';
  
  
  
  
  
  
  
  Colesbot.on('ready', () =>{
  
      console.log('Slamsbot is online.');
  
  })
  
  
  
  Colesbot.on('message', msg=>{
  
     if(msg.content == "What up bot?"){
  
         msg.reply("Whats good pimp?")
  
     }
  
  });
  
  
  
  Colesbot.on('message', message=>{
  
      if (message.content === '/join') {
  
          // Only try to join the sender's voice channel if they are in one themselves
  
          if (message.member.voiceChannel) {
  
              message.member.voiceChannel.join().then(connection => {
  
                  message.reply('I have successfully connected to the channel!');
  
  
  
                  // To play a file, we need to give an absolute path to it
  
                  const dispatcher = connection.playFile('C:\Users\bobal\Documents\GitHub\Spotify-Playlist-Discord-bot\Assets\Glory.mp3');
  
  
  
                  dispatcher.on('end', () => {
  
                      // The song has finished
  
                      console.log('Finished playing!');
  
                    });
  
  
  
                  dispatcher.on('error', e => {
  
                      // Catch any errors that may arise
  
                      console.log(e);
  
                    });
  
  
  
                    dispatcher.setVolume(0.5); // Set the volume to 50%
  
              }).catch(console.log);
  
      } else {
  
          message.reply('You need to join a voice channel first!');
  
        }
  
      }
  
   });
  
  
  
  
  
  
  
  //Event listener for new guild members
  
  Colesbot.on('guildMemberAdd', member =>{
  
      // Send the message to a designated channel on a server:
  
      const channel = member.guild.channels.find(ch => ch.name === 'general');
  
      // Do nothing if the channel wasn't found on this server
  
      if (!channel) return;
  
      // Send the message, mentioning the member
  
      channel.send(`Welcome to the server, ${member}. Please use the bot-commands channel to assign yourself a role.`);
  
  })
  
  
  
  Colesbot.login(token);
  
  
  
  
  
  
  
  exports.run = (client, message, args) => {
  
  
  
      let user = message.mentions.users.first || message.author;
  
  
  
  
  
  }

  FFMPEG is installed and I have set the environment path for it. When I type FFMPEG in the command line I get the proper response.

  Some have said I need to install the ffmpeg binaries but when I run npm install ffmpeg-binaries I get this error message :

  npm WARN deprecated ffmpeg-binaries@4.0.0: ffmpeg-binaries is no longer being maintained. use ffmpeg-static, or just install ffmpeg
  
  
  
  > lzma-native@3.0.8 install C:\Users\bobal\Documents\GitHub\Spotify-Playlist-Discord-bot\node_modules\lzma-native
  
  > node-pre-gyp install --fallback-to-build && node node_modules/rimraf/bin.js build
  
  
  
  node-pre-gyp ERR! Tried to download(404): https://node-pre-gyp.addaleax.net/lzma-native/lzma_native-v3.0.8-node-v72-win32-x64.tar.gz
  
  node-pre-gyp ERR! Pre-built binaries not found for lzma-native@3.0.8 and node@12.14.1 (node-v72 ABI, unknown) (falling back to source compile with node-gyp)
  
  node-pre-gyp ERR! Tried to download(undefined): https://node-pre-gyp.addaleax.net/lzma-native/lzma_native-v3.0.8-node-v72-win32-x64.tar.gz
  
  node-pre-gyp ERR! Pre-built binaries not found for lzma-native@3.0.8 and node@12.14.1 (node-v72 ABI, unknown) (falling back to source compile with node-gyp)
  
  gyp ERR! find Python
  
  gyp ERR! find Python Python is not set from command line or npm configuration
  
  gyp ERR! find Python Python is not set from environment variable PYTHON
  
  gyp ERR! find Python checking if "python" can be used
  
  gyp ERR! find Python - "python" is not in PATH or produced an error
  
  gyp ERR! find Python checking if "python2" can be used
  
  gyp ERR! find Python - "python2" is not in PATH or produced an error
  
  gyp ERR! find Python checking if "python3" can be used
  
  gyp ERR! find Python - "python3" is not in PATH or produced an error
  
  gyp ERR! find Python checking if the py launcher can be used to find Python 2
  
  gyp ERR! find Python - "py.exe" is not in PATH or produced an error
  
  gyp ERR! find Python checking if Python is C:\Python27\python.exe
  
  gyp ERR! find Python - "C:\Python27\python.exe" could not be run
  
  gyp ERR! find Python checking if Python is C:\Python37\python.exe
  
  gyp ERR! find Python - "C:\Python37\python.exe" could not be run
  
  gypgyp ERR!  find PythonERR!
  
  find Pythongyp
  
   gyp ERR!ERR!  find Pythonfind Python Python is not set from command line or npm configuration
  
   **********************************************************
  
  gypgyp  ERR!ERR!  find Pythonfind Python Python is not set from environment variable PYTHON
  
   You need to install the latest version of Python.
  
  gypgyp  ERR!ERR!  find Pythonfind Python checking if "python" can be used
  
   Node-gyp should be able to find and use Python. If not,
  
  gypgyp  ERR!ERR!  find Pythonfind Python - "python" is not in PATH or produced an error
  
   you can try one of the following options:
  
  gypgyp  ERR!ERR!  find Pythonfind Python checking if "python2" can be used
  
   - Use the switch --python="C:\Path\To\python.exe"
  
  gypgyp ERR!  ERR!find Python  - "python2" is not in PATH or produced an error
  
  find Pythongyp   (accepted by both node-gyp and npm)
  
   gypERR!  ERR!find Python  checking if "python3" can be used
  
  find Pythongyp - Set the environment variable PYTHON
  
   gypERR!  ERR!find Python  - "python3" is not in PATH or produced an error
  
  find Pythongyp - Set the npm configuration variable python:
  
   gypERR!  ERR!find Python  checking if the py launcher can be used to find Python 2
  
  find Pythongyp   npm config set python "C:\Path\To\python.exe"
  
   gypERR!  ERR!find Python  - "py.exe" is not in PATH or produced an error
  
  find Pythongyp For more information consult the documentation at:
  
   gypERR!  ERR!find Python  checking if Python is C:\Python27\python.exe
  
  gypfind Python  https://github.com/nodejs/node-gyp#installation
  
  ERR!gyp  find PythonERR! - "C:\Python27\python.exe" could not be run
  
   gypfind Python  **********************************************************
  
  ERR!gyp  find PythonERR! checking if Python is C:\Python37\python.exe
  
   gypfind Python
  
  ERR! find Python - "C:\Python37\python.exe" could not be run
  
  gypgyp  ERR!ERR!  configure errorfind Python
  
  
  
  gypgyp  ERR!ERR!  stackfind Python Error: Could not find any Python installation to use
  
   **********************************************************
  
  gyp gypERR!  ERR!stack      at PythonFinder.fail (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-python.js:307:47)
  
  find Pythongyp  You need to install the latest version of Python.
  
  ERR!gyp stack      at PythonFinder.runChecks (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-python.js:136:21)
  
  ERR!gyp  ERR!find Python  Node-gyp should be able to find and use Python. If not,
  
  stack     at PythonFinder.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-python.js:225:16)
  
  gypgyp  ERR!ERR!  find Pythonstack you can try one of the following options:
  
       at PythonFinder.execFileCallback (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-python.js:271:16)
  
  gypgyp  ERR!ERR!  stackfind Python     at exithandler (child_process.js:302:5)
  
  gyp - Use the switch --python="C:\Path\To\python.exe"
  
   gypERR!  stackERR!     at ChildProcess.errorhandler (child_process.js:314:5)
  
   gyp find PythonERR!    (accepted by both node-gyp and npm)
  
  stack     at ChildProcess.emit (events.js:223:5)
  
  gypgyp  ERR!ERR!  stackfind Python     at Process.ChildProcess._handle.onexit (internal/child_process.js:270:12)
  
   - Set the environment variable PYTHON
  
  gypgyp  ERR!ERR! stack      at onErrorNT (internal/child_process.js:456:16)
  
  find Pythongyp - Set the npm configuration variable python:
  
   gypERR!  ERR!stack      at processTicksAndRejections (internal/process/task_queues.js:81:21)
  
  find Python   npm config set python "C:\Path\To\python.exe"
  
  gypgyp  ERR!ERR!  find PythonSystem For more information consult the documentation at:
  
   Windows_NT 10.0.17763
  
  gypgyp  ERR!ERR!  find Pythoncommand https://github.com/nodejs/node-gyp#installation
  
   "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "configure" "--fallback-to-build" "--module=C:\\Users\\bobal\\Documents\\GitHub\\Spotify-Playlist-Discord-bot\\node_modules\\lzma-native\\binding-v3.0.8-node-v72-win32-x64\\lzma_native.node" "--module_name=lzma_native" "--module_path=C:\\Users\\bobal\\Documents\\GitHub\\Spotify-Playlist-Discord-bot\\node_modules\\lzma-native\\binding-v3.0.8-node-v72-win32-x64"
  
  gypgyp  ERR!ERR!  find Pythoncwd **********************************************************
  
   C:\Users\bobal\Documents\GitHub\Spotify-Playlist-Discord-bot\node_modules\lzma-native
  
  gypgyp  ERR!ERR!  find Pythonnode -v
  
   v12.14.1
  
  gyp ERR! node-gyp -vgyp v5.0.5
  
   gyp ERR!ERR!  configure errornot ok
  
  
  
  gyp ERR! stack Error: Could not find any Python installation to use
  
  gyp ERR! stack     at PythonFinder.fail (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-python.js:307:47)
  
  gyp ERR! stack     at PythonFinder.runChecks (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-python.js:136:21)
  
  gyp ERR! stack     at PythonFinder.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-python.js:225:16)
  
  gyp ERR! stack     at PythonFinder.execFileCallback (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-python.js:271:16)
  
  gyp ERR! stack     at exithandler (child_process.js:302:5)
  
  gyp ERR! stacknode-pre-gyp     at ChildProcess.errorhandler (child_process.js:314:5)
  
   gypERR!  ERR!build error
  
  stack     at ChildProcess.emit (events.js:223:5)
  
  node-pre-gypgyp  ERR!ERR!  stackstack     at Process.ChildProcess._handle.onexit (internal/child_process.js:270:12)
  
   Error: Failed to execute 'C:\Program Files\nodejs\node.exe C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js configure --fallback-to-build --module=C:\Users\bobal\Documents\GitHub\Spotify-Playlist-Discord-bot\node_modules\lzma-native\binding-v3.0.8-node-v72-win32-x64\lzma_native.node --module_name=lzma_native --module_path=C:\Users\bobal\Documents\GitHub\Spotify-Playlist-Discord-bot\node_modules\lzma-native\binding-v3.0.8-node-v72-win32-x64' (1)
  
  node-pre-gypgyp  ERR! ERR!stack      at ChildProcess.<anonymous> (C:\Users\bobal\Documents\GitHub\Spotify-Playlist-Discord-bot\node_modules\lzma-native\node_modules\node-pre-gyp\lib\util\compile.js:83:29)
  
  stacknode-pre-gyp     at onErrorNT (internal/child_process.js:456:16)
  
   gypERR!  ERR!stack      at ChildProcess.emit (events.js:223:5)
  
  stacknode-pre-gyp     at processTicksAndRejections (internal/process/task_queues.js:81:21)
  
   ERR! stackgyp     at maybeClose (internal/child_process.js:1021:16)
  
   node-pre-gypERR!  ERR!System stack Windows_NT 10.0.17763
  
       at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)
  
  gyp ERR! node-pre-gypcommand  "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "configure" "--fallback-to-build" "--module=C:\\Users\\bobal\\Documents\\GitHub\\Spotify-Playlist-Discord-bot\\node_modules\\lzma-native\\binding-v3.0.8-node-v72-win32-x64\\lzma_native.node" "--module_name=lzma_native" "--module_path=C:\\Users\\bobal\\Documents\\GitHub\\Spotify-Playlist-Discord-bot\\node_modules\\lzma-native\\binding-v3.0.8-node-v72-win32-x64"
  
  ERR!gyp  SystemERR! Windows_NT 10.0.17763
  
   node-pre-gypcwd  C:\Users\bobal\Documents\GitHub\Spotify-Playlist-Discord-bot\node_modules\lzma-native
  
  ERR!gyp  commandERR! "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\bobal\\Documents\\GitHub\\Spotify-Playlist-Discord-bot\\node_modules\\lzma-native\\node_modules\\node-pre-gyp\\bin\\node-pre-gyp" "install" "--fallback-to-build"
  
   node-pre-gypnode -v  v12.14.1
  
  ERR!gyp  cwdERR! C:\Users\bobal\Documents\GitHub\Spotify-Playlist-Discord-bot\node_modules\lzma-native
  
   node-pre-gypnode-gyp -v  v5.0.5
  
  ERR!gyp  ERR!node -v  v12.14.1
  
  not ok
  
  node-pre-gyp ERR! node-pre-gyp -v v0.6.39
  
  node-pre-gyp ERR! not ok
  
  Failed to execute 'C:\Program Files\nodejs\node.exe C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js configure --fallback-to-build --module=C:\Users\bobal\Documents\GitHub\Spotify-Playlist-Discord-bot\node_modules\lzma-native\binding-v3.0.8-node-v72-win32-x64\lzma_native.node --module_name=lzma_native --module_path=C:\Users\bobal\Documents\GitHub\Spotify-Playlist-Discord-bot\node_modules\lzma-native\binding-v3.0.8-node-v72-win32-x64' (1)
  
  npm WARN discord.js@11.5.1 requires a peer of @discordjs/uws@^10.149.0 but none is installed. You must install peer dependencies yourself.
  
  npm WARN spotifybot@1.0.0 No description
  
  npm WARN spotifybot@1.0.0 No repository field.
  
  
  
  npm ERR! code ELIFECYCLE
  
  npm ERR! errno 1
  
  npm ERR! lzma-native@3.0.8 install: `node-pre-gyp install --fallback-to-build &amp;&amp; node node_modules/rimraf/bin.js build`
  
  npm ERR! Exit status 1
  
  npm ERR!
  
  npm ERR! Failed at the lzma-native@3.0.8 install script.
  
  npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
  
  
  
  npm ERR! A complete log of this run can be found in:
  
  npm ERR!     C:\Users\bobal\AppData\Roaming\npm-cache\_logs\2020-02-21T19_25_47_323Z-debug.log
  
  </anonymous></anonymous></anonymous>

  So then I tried installing an older version and I’m now using ffmpeg-binaries@3.2.2-3 but when I type /join I get this : [ERR_INVALID_ARG_TYPE] : The "file" argument must be of type string. Received type object