Recherche avancée

Sur d’autres sites (9208)

• [Aug-Sept 2013] Piwik 2.0 Development Update !

  3 octobre 2013, par Fabian Becker — Development

  This Development Update is the first in a new series of posts we’ll be writing to keep you, our loyal users, informed of our efforts. We hope these updates keep you excited about Piwik’s future, and if you’re a developer, we hope they inspire and challenge you to accomplish more yourself !

  Despite this being our first update, it will probably be one of our biggest. We’ve gotten a lot done as we race towards the Piwik 2.0 release ! Just see for yourself :

  What we’ve accomplished

  Theming

  Piwik now supports theming, a feature that was requested often in the past. Because of our switch to the Twig template engine and other major code changes it is now possible to change the way Piwik looks. Additionally, developers can use the dynamic stylesheet language LESS, instead of CSS. Piwik will automatically transform the LESS code into CSS.

  Piwik 2.0 will ship with a new dark theme called PleineLune (french for Full Moon) that makes use of the new theming feature. Another theme with a left-aligned menu was created during the Piwik Meetup in Paris. Both of these themes were created by Thomas Zilliox, a very talented designer and CSS expert.

  

  PHP 5.3 Namespaces

  For Piwik 2.0 we decided to make use of namespaces, a feature introduced in PHP 5.3. The usage of namespaces makes our code more readable and allows us to better modularize the platform. This is in part why we are raising the required minimum PHP version to 5.3 for Piwik 2.0. (Remember to update your server !)

  Translations in JSON

  All translations are now stored in JSON files which makes storing translations in Piwik a lot cleaner that the giant PHP array we previously used.

  Side note : if you’d like to make Piwik available to more languages, please sign up at translations.piwik.org. We’d love to have your help !

  UI Tests

  We now use UI tests to make sure that changes to the code don’t break the UI. UI tests use PhantomJS and CutyCapt and are automatically executed on Travis CI. Whenever an integration test fails the script produces a screenshot diff that shows the difference. Learn more.

  

  AnonymizeIP supports IPv6

  The AnonymizeIP plugin now masks IPv6 addresses. The concept of the config option ‘ip_address_mask_length’ has now changed to reflect the level of masking that should be applied to the IP. With a masking level of 1 Piwik will mask the last octet of an IPv4 address and the last 80 bits of an IPv6 address.

  All Websites Dashboard usable with 20,000+ Websites

  The All Websites Dashboard is now usable even if you track many thousands of websites in your Piwik instance. We rewrote parts of the archiving process in order to make this possible. Making Piwik fast and memory efficient is a constant concern for core developers.

  Plugins can now add new Visualizations

  Piwik Plugins and Themes can now create new visualizations for your report data. They can also specify their own ViewDataTable footer icons or modify existing ones. This will allow plugin developers to create new ways for you to view your data, customize existing reports so they look great in new visualizations and provide extra analytics functionality accessible in each of your reports.

  The new TreemapVisualization plugin makes use of this feature to let you view your reports as treemaps. It serves as an example of this new functionality.

  Piwik Marketplace

  The Piwik Marketplace is a new platform developers can use to publish their plugins and themes so all Piwik users can easily access them. The marketplace is hosted at plugins.piwik.org and is currently in an early development state, but we’re already able to host plugins !

  Developers can easily publish their plugins by adding a commit hook to their Github repositories. Every time you push a new tag, the marketplace will make a new version of your plugin available. The marketplace will provide a centralized platform to search for plugins and also provide statistics on plugin usage.

  Install Plugins and Themes in one click from within Piwik

  Piwik has offered since the beginning the much-loved “one click update” feature. We are bringing the same functionnality to the Marketplace : you will be able to install Plugins and Themes in one click directly within the Piwik interface ! Similarly to WordPress or Firefox, Piwik will let you extend the functionnality of your analytics platform.

  Conclusion

  In Piwik 2.0 you will be able to install plugins and themes from the marketplace. And, if you’re so inclined, you will be able to create and host your own plugins/themes on the marketplace so everyone can use them. This is by far the accomplishment we are most excited by… the possibilities it opens up for Piwik’s future are truly unlimited. We hope you share our excitement !

  Au revoir, until next time !

  PS : our mission is to liberate web analytics ; thank you for sharing the word about Piwik 2.0 !

• B2B Marketing Attribution Guide : How to Master It in 2024

  21 mai 2024, par Erin

  The last thing you want is to invest your advertising dollars in channels, campaigns and ads that don’t work. But B2B marketing attribution — figuring out which marketing efforts drive revenue — is far from easy.

  With longer sales funnels and multiple people from the same company involved in the same sales process, B2B (business-to-business) is a different ballgame from B2C (business-to-consumer) marketing.

  In this guide, we break down what B2B marketing attribution is, how it’s different, which tools you can use to set it up and the best practices.

  What is B2B marketing attribution ?

  Marketing attribution in B2B companies is about figuring out where your high-value leads come from — nailing down long customer journeys across many different touchpoints.

  

  The goal is to determine which campaigns and content contributed to various parts of the customer journey. It’s a complex process that needs a reliable, privacy-focused web analytics tool and a CRM that integrates with it.

  This process significantly differs from traditional marketing attribution, where you focus more on short sales cycles from individual customers. With multiple contributing decision makers, B2B attribution requires more robust systems.

  What makes marketing attribution different for B2B ?

  The key differences between B2B and B2C marketing attribution are a longer sales funnel and more people involved in the sales process.

  The B2B sales funnel is significantly longer and more complex

  The typical B2C sales funnel is often broken down into four simple stages :

  1. Awareness : when a prospect first finds out about your product or brand
  2. Interest : where a prospect starts to learn about the benefits of your product
  3. Desire : when a prospect understands that they need your product
  4. Action : the actual process of closing the sale

  Even the most simplified B2B sales funnel includes several key stages.

  

  Here’s a brief overview of each :

  1. Awareness : Buyers recognise they have a problem and start looking for solutions. Stand out with blog posts, social media updates, ebooks and whitepapers.
  2. Consideration : Buyers are aware of your company and are comparing options. Provide product demos, webinars and case studies to address their concerns and build trust.
  3. Conversion : Buyers have chosen your product or company. Offer live demos, customer service, case studies and testimonials to finalise the purchase.
  4. Loyalty : Buyers have made a purchase and are now customers. Nurture relationships with thank you emails, follow-ups, how-tos, reward programs and surveys to encourage repeat business.
  5. Advocacy : Loyal customers become advocates, promoting your brand to others. Encourage this with surveys, testimonial requests and a referral program.

  A longer sales cycle typically involves not only more touchpoints but also extended decision-making processes.

  More teams are involved in the marketing and sales process

  The last differentiation in B2B attribution is the number of people involved. Instead of clear-cut sales and marketing teams, revenue teams are becoming more common.

  They include all go-to-market teams like sales, marketing, customer success and customer support. In B2B sales, long-term customer relationships can be incredibly valuable. As such, the focus shifts away from new customer acquisition alone.

  For example, you can also track and optimise your onboarding process. Marketing gets involved in post-sale efforts to boost loyalty. Sales reps follow up with customer success to get new sales angles and insights. Customer support insights drive future product development.

  Everyone works together to meet high-level company goals.

  The next section will explore how to set up an attribution system.

  How to find the right mix of B2B marketing attribution tools

  For most B2B marketing teams, the main struggle with attribution is not with the strategy but with creating a reliable system that gives them the data points they need to implement that strategy.

  We’ll outline one approach you can take to achieve this without a million-dollar budget or internal data science team.

  Use website analytics to track touchpoints

  The first thing you want to do is install a reliable website analytics solution on your website. 

  Once you’ve got your analytics in place, use campaign tracking parameters to track touchpoints from external campaigns like email newsletters, social media ads, review sites (like Capterra) and third-party partner campaigns.

  This way, you get a clear picture of which sources are driving traffic and conversions, helping you improve your marketing strategies.

  With analytics installed, you can track the referring sources of visits, engagement and conversion events. A robust solution like Matomo tracks everything from traffic sources, marketing attribution and visitor counts to behavioural analytics, like clicks, scrolling patterns and form interactions on your site.

  Marketing attribution will give you a cohesive view of which traffic sources and campaigns drive conversions and revenue over long periods. With Matomo’s marketing attribution feature, you can even use different marketing attribution models to compare results :

  

  For example, in a single report, you can compare the last interaction, first interaction and linear (three common marketing attribution models). 

  In total, Matomo has 6 available attribution models to choose from :

  1. First interaction
  2. Last interaction
  3. Last non-direct 
  4. Linear
  5. Position based
  6. Time decay 

  These additional attribution models are crucial for B2B sites. While other web analytics solutions often limit to last-click attribution, this model isn’t optimal for B2B with extended sales cycles.

  Try Matomo for Free

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

  Start for free

  No credit card required

  Use a CRM to integrate customer data from multiple sources

  Use your CRM software to integrate customer data from multiple sources. This will give you the ability to get meaningful B2B marketing insights. For example, you can get company-level insights so you can view conversion information by company, not just by person.

  Done effectively, you can close the loop back to analytics data by integrating data from multiple teams and platforms. 

  Implement self-reported attribution

  To further enhance the data, add qualifying questions in the lead signup process to create a hybrid attribution model. This is also known as self-reported attribution.

  

  Your web analytics platform won’t always be able to track the source of certain visits — for instance, “dark social” or peer-to-peer sharing, where links are shared privately and are not easily traceable by analytics tools.

  Doing self-reported attribution is crucial for getting a holistic image of your customer journey. 

  However, self-reported attribution isn’t foolproof ; users may click randomly or inaccurately recall where they first heard about you. So it’s essential to blend this data with your analytics to gain a more accurate understanding.

  Best practices for handling B2B prospect data in a privacy-sensitive world 

  Lastly, it’s important to respect your prospects’ privacy and comply with privacy regulations when conducting B2B marketing attribution.

  Privacy regulations and their enforcement are rapidly gaining momentum around the globe. Meta recently received a record GDPR fine of €1.2 billion for insufficient privacy measures when handling user data by the Irish Data Protection Agency.

  If you don’t want to risk major fines (or customers feeling betrayed), you shouldn’t follow in the same footsteps.

  Switch to a privacy-friendly web analytics

  Instead of using a controversial solution like Google Analytics, use a privacy-friendly web analytics solution like Matomo, Fathom or Plausible. 

  These alternatives not only ensure compliance with regulations like GDPR but also provide peace of mind amid the uncertain relationship between Google and GDPR. Google Analytics has faced bans in recent years, raising concerns about the future of the solution.

  While organisations governed by GDPR can currently use Google Analytics, there’s no guarantee of its continued availability.

  Make the switch to privacy-friendly web analytics to avoid potential fines and disruptive rulings that could force you to change platforms urgently. Such disruptions can be catastrophic for marketing teams heavily reliant on web analytics for tracking campaigns, business goals and marketing efforts.

  Improve your B2B marketing attribution with Matomo

  Matomo’s privacy-by-design architecture makes it the perfect analytics platform for the modern B2B marketer. Matomo enables you to meet even the strictest privacy regulations.

  At the same time, through campaign tracking URLs, marketing attribution, integrations and our API, you can track the results of various marketing channels and campaigns effectively. We help you understand the impact of each dollar of your marketing budget. 

  If you want a competitive edge over other B2B companies, try Matomo for free for 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

  

• FFmpeg Concatenation Command Fails in Flutter App

  18 février 2024, par Petro

  I'm developing a Flutter application where I need to concatenate several images into a single video file using FFmpeg. Despite following the recommended practices and trying multiple variations of the FFmpeg command, all my attempts result in failure with an exit code of 1.

  


  FFMPEG Version : ffmpeg_kit_flutter: ^6.0.3-LTS

  


  All of the files are present when this happens...


  


  Environment :
Flutter app targeting Android
Using ffmpeg-kit-flutter for FFmpeg operations

  


  Objective :
To concatenate multiple images stored in the app's file system into a video.

  


  Code Snippet :
I'm generating a list of image paths, writing them to a file (ffmpeg_list.txt), and using that file with FFmpeg's concat demuxer. Here's a simplified version of my code :

  


  Future<void> _createVideoFromImages() async {&#xA;  final Directory appDir = await getApplicationDocumentsDirectory();&#xA;  final Uuid uuid = Uuid();&#xA;  final String videoFileName = uuid.v4();&#xA;  final String outputPath = &#x27;${appDir.path}/$videoFileName.mp4&#x27;;&#xA;  &#xA;  final Directory tempImageDir = await Directory(&#x27;${appDir.path}/tempImages&#x27;).create();&#xA;  final StringBuffer ffmpegInput = StringBuffer();&#xA;  int index = 0;&#xA;&#xA;  for (var image in _images) {&#xA;    String newFileName = &#x27;img${index&#x2B;&#x2B;}${Path.extension(image.path)}&#x27;.replaceAll(&#x27; &#x27;, &#x27;_&#x27;);&#xA;    final String newPath = &#x27;${tempImageDir.path}/$newFileName&#x27;;&#xA;    await image.copy(newPath);&#xA;    ffmpegInput.writeln("file &#x27;$newPath&#x27;");&#xA;  }&#xA;&#xA;  final String listFilePath = &#x27;${appDir.path}/ffmpeg_list.txt&#x27;;&#xA;  await File(listFilePath).writeAsString(ffmpegInput.toString());&#xA;&#xA;  if(await File(listFilePath).exists()) {&#xA;    String ffmpegCommand = "-v verbose -f concat -safe 0 -i $listFilePath -vsync vfr -pix_fmt yuv420p -c:v libx264 -r 30 $outputPath";&#xA;    // Additional commands tried here...&#xA;    await FFmpegKit.execute(ffmpegCommand).then((session) async {&#xA;      // Error handling code...&#xA;    });&#xA;  }&#xA;}&#xA;&#xA;Result Logs:&#xA;I/flutter: file exists at /data/user/0/com.example.app/app_flutter/ffmpeg_list.txt&#xA;I/flutter: FFmpeg command: -v verbose -f concat -safe 0 -i /data/user/0/com.example.app/app_flutter/ffmpeg_list.txt -vsync vfr -pix_fmt yuv420p -c:v libx264 -r 30 /data/user/0/com.example.app/app_flutter/58fdf92b-47b0-49d1-be93-d9c95870c733.mp4&#xA;I/flutter: Failed to create video&#xA;I/flutter: FFmpeg process exited with:1&#xA;I/flutter: FFmpeg command failed with logs: ffmpeg version n6.0 Copyright (c) 2000-2023 the FFmpeg developers...&#xA;</void>

  


  Attempts :
-Simplified the FFmpeg command by removing -vsync vfr, -pix_fmt yuv420p, and adjusting -r 30 parameters.
-Tried using the -c copy option to avoid re-encoding.
-Tested with a single image to ensure basic functionality works.
-Checked file permissions and ensured all images and the list file are accessible.

  


  Despite these attempts, the command fails without providing specific error messages related to the command's execution. The verbose logs do not offer insights beyond the FFmpeg version and configuration.

  


  Questions :
Are there known issues with FFmpeg's concat that might lead to such failures ?
Are there alternative approaches ?

  


  I appreciate any insights or suggestions the community might have. Thank you !

  


  Full code :

  


  Future<void> _createVideoFromImages() async {&#xA;    final Directory appDir = await getApplicationDocumentsDirectory();&#xA;    final Uuid uuid = Uuid();&#xA;    final String videoFileName = uuid.v4();&#xA;    final String outputPath = &#x27;${appDir.path}/$videoFileName.mp4&#x27;;&#xA;    final String singleImagePath = _images[0]!.path;&#xA;&#xA;// Create a directory to store renamed images to avoid any naming conflict&#xA;    final Directory tempImageDir = await Directory(&#x27;${appDir.path}/tempImages&#x27;).create();&#xA;&#xA;    final StringBuffer ffmpegInput = StringBuffer();&#xA;    int index = 0; // To ensure unique filenames&#xA;&#xA;    for (var image in _images) {&#xA;      // Generate a new filename by replacing spaces with underscores and adding an index&#xA;      String newFileName = &#x27;img${index&#x2B;&#x2B;}${p.extension(image!.path)}&#x27;.replaceAll(&#x27; &#x27;, &#x27;_&#x27;);&#xA;      final String newPath = &#x27;${tempImageDir.path}/$newFileName&#x27;;&#xA;&#xA;      // Copy and rename the original file to the new path&#xA;      await image!.copy(newPath);&#xA;&#xA;      // Add the new, safely named file path to the ffmpegInput&#xA;      ffmpegInput.writeln("file &#x27;$newPath&#x27;");&#xA;    }&#xA;&#xA;// Write the paths to a temporary text file for FFmpeg&#x27;s concat demuxer&#xA;    final String listFilePath = &#x27;${appDir.path}/ffmpeg_list.txt&#x27;;&#xA;    await File(listFilePath).writeAsString(ffmpegInput.toString());&#xA;&#xA;    //check if file exists&#xA;    if(await File(listFilePath).exists()) {&#xA;      print("file exists at $listFilePath");&#xA;&#xA;// Use the generated list file in the concat command&#xA;      String ffmpegCommand = "-v verbose -f concat -safe 0 -i $listFilePath -vsync vfr -pix_fmt yuv420p -c:v libx264 -r 30 $outputPath";&#xA;      String ffmpegCommand2 = "-v verbose -f concat -safe 0 -i $listFilePath -c:v libx264 $outputPath";&#xA;      String ffmpegCommand3 = "-v verbose -i $singleImagePath -frames:v 1 $outputPath";&#xA;      //print command&#xA;      print("FFmpeg command: $ffmpegCommand");&#xA;&#xA;&#xA;      await FFmpegKit.execute(ffmpegCommand).then((session) async {&#xA;        // Check the session for success or failure&#xA;        final returnCode = await session.getReturnCode();&#xA;        if (returnCode!.isValueSuccess()) {&#xA;          print("Video created successfully: $outputPath");&#xA;          //okay all set, now set the video to be this:&#xA;          _actual_video_file_ready_to_upload = File(outputPath);&#xA;          print ("video path is: ${outputPath}");&#xA;        } else {&#xA;          print("Failed to create video");&#xA;          print("FFmpeg process exited with:" &#x2B; returnCode.toString());&#xA;          // Command failed; capture and log error details&#xA;          await session.getLogsAsString().then((logs) {&#xA;            print("FFmpeg command failed with logs: $logs");&#xA;          });&#xA;          // Handle failure, e.g., by showing an error message&#xA;          showSnackBarHelperERRORWrapLongString(context, "Failed to create video");&#xA;        }&#xA;      });&#xA;&#xA;      //try command 2&#xA;      if(_actual_video_file_ready_to_upload == null) {&#xA;        await FFmpegKit.execute(ffmpegCommand2).then((session) async {&#xA;          // Check the session for success or failure&#xA;          final returnCode = await session.getReturnCode();&#xA;          if (returnCode!.isValueSuccess()) {&#xA;            print("Video created successfully: $outputPath");&#xA;            //okay all set, now set the video to be this:&#xA;            _actual_video_file_ready_to_upload = File(outputPath);&#xA;            print ("video path is: ${outputPath}");&#xA;          } else {&#xA;            print("Failed to create video");&#xA;            print("FFmpeg process exited with:" &#x2B; returnCode.toString());&#xA;            // Command failed; capture and log error details&#xA;            await session.getLogsAsString().then((logs) {&#xA;              print("FFmpeg command failed with logs: $logs");&#xA;            });&#xA;            // Handle failure, e.g., by showing an error message&#xA;            showSnackBarHelperERRORWrapLongString(context, "Failed to create video");&#xA;          }&#xA;        });&#xA;      }&#xA;      //try command 3&#xA;      if(_actual_video_file_ready_to_upload == null) {&#xA;        await FFmpegKit.execute(ffmpegCommand3).then((session) async {&#xA;          // Check the session for success or failure&#xA;          final returnCode = await session.getReturnCode();&#xA;          if (returnCode!.isValueSuccess()) {&#xA;            print("Video created successfully: $outputPath");&#xA;            //okay all set, now set the video to be this:&#xA;            _actual_video_file_ready_to_upload = File(outputPath);&#xA;            print ("video path is: ${outputPath}");&#xA;          } else {&#xA;            print("Failed to create video");&#xA;            print("FFmpeg process exited with:" &#x2B; returnCode.toString());&#xA;            // Command failed; capture and log error details&#xA;            await session.getLogsAsString().then((logs) {&#xA;              print("FFmpeg command failed with logs: $logs");&#xA;            });&#xA;            // Handle failure, e.g., by showing an error message&#xA;            showSnackBarHelperERRORWrapLongString(context, "Failed to create video");&#xA;          }&#xA;        });&#xA;      }&#xA;    }else{&#xA;      print("file does not exist at $listFilePath");&#xA;    }&#xA;  }&#xA;</void>