Recherche avancée

Sur d’autres sites (5969)

• 5 Key Benefits of Using a Tag Manager

  12 décembre 2021, par erin — Analytics Tips, Marketing

  Websites today have become very complex to manage, and as you continue to look for ways to optimise your website, you’ll want to consider using a Tag Manager. 

  A Tag Manager will help your marketing team seamlessly track how your visitors are engaging with your website’s elements. Without a Tag Manager, you are missing out on business-altering insights.

  In this blog, we’ll cover :

  Tag Manager overview 

  A Tag Manager (AKA Tag Management System or TMS) is a centralised system for implementing, managing and tracking events. A tag is just another word for a piece of code on a website that tracks a specific event. 

  An example of a tag tracking code might be Facebook pixels, ad conversions and other website activities such as signing up to a newsletter or PDF download. 

  Triggers are the actual actions that website visitors take that activate the tag. Examples of triggers are things like : 

  • A thank you page view to show that a visitor has completed a conversion action
  • Clicking a download or sign up button 
  • Scroll depth or how far down users are scrolling on your webpage 

  Each of these will give you insights into how your website is performing and how your users are engaging with your content. Going back to the scroll depth trigger example, this would be particularly helpful for validating bounce rate and finding out where users are dropping off on a page. Discover other ways to take advantage of tags and event tracking. 

  

  5 key benefits of a Tag Manager

  1. Removes the risks of website downtime 

  Tags are powerful for in-depth web analytics. However, tagging opens up the potential for non-technical team members to break the front-end of your website in a couple of clicks. 

  A Tag Manager reduces that risk. For example, Matomo Tag Manager lets you preview tags to see if they are firing before pushing them live. You can also give specific users restricted access so you can approve any tagging before it goes live. 

  Tag Managers protect the functionality of your website and ensure that there is no downtime.

  2. Your website will load faster 

  When it comes to the success of your website, page speed is one of the most important factors. 

  Each time you add a tag to your site, you run the risk of slowing down the page speed. This can quickly build up to a poor performing site and frustrate your visitors.

  You can’t track tags if visitors won’t even stay long enough for your site to load. In fact, 1 in 4 visitors would abandon a website that takes more than 4 seconds to load. According to Deloitte, just a 0.1 second difference in loading speed can affect every step of your customer journey. 

  A Tag Manager, on the other hand, is a lightweight option only requiring one single tag. Using a Tag Manager to track events can make all the difference to your website’s performance and user experience.

  3. Greater efficiency for marketing

  Time is critical in marketing. The longer it takes for a campaign to launch, the greater the chances are that you’re missing out on sales opportunities.

  Waiting for the IT team to tag a thank you page before setting an ad live is inefficient and impacts your bottom line.

  Equipping marketing with a Tag Manager means that they’ll be able to launch campaigns faster and more effectively.

  Check out our Marketer’s Guide to Successful Website Event Tracking for more.

  4. Control all of your tracking and marketing tags in one place 

  Keeping track of what tags are on your site and where they’re located is a complicated task if you aren’t using a Tag Manager. Unmanaged tags can quickly pile up and result in errors with your analytics, like counting conversions twice. 

  Using a Tag Manager to centralise your tags in one easy to manage place reduces the chances of human errors. Instead, your team will be able to quickly see what tags are already in place so they aren’t doubling up on tracking.

  5. Reduce work for the IT team 

  Let’s face it, the IT team has more critical tasks at hand than adding tags to the website. Freeing up your IT team to focus on higher priority tasks should always be a goal.

  Tagging, while crucial for marketing, has the potential to create a lot of extra work for your website developers. Inserting code for each individual tag is time-consuming and means you aren’t collecting data in the meantime.

  Rather than overloading your IT team, empower your marketing team with the ability to add tags with a few clicks. 

  How to choose a Tag Management System

  There are many tools to choose from and the default option tends to be Google Tag Manager (GTM). But before you implement GTM or any other Tag Management Solution, we highly recommend asking these questions :

  1. What are my goals for a Tag Manager ? Before purchasing a Tag Manager, or any tool for that matter, understanding your goals upfront is best practice.
  2. Does the solution offer Tag Manager training resources ? If online Tag Manager training and educational resources are available for the tool, then you’ll be able to hit the ground running and start to see an ROI instantly.
  3. Can I get online support ? In case you need any help with the tool, having access to online support is a big bonus. 
  4. Is it compliant with privacy regulations ? If your business is already compliant, in the process of becoming compliant or future-proofing your tech stack for looming privacy regulations, then researching this is crucial. 
  5. How much does it cost ? If it’s “free”, find out how and why. In most cases, free solutions are just vehicles for collecting data to advertise to your users. 
  6. What do others think about the Tag Manager ? Check out reviews on sites like Capterra or G2 to find out how other businesses rate the tool. 

  Google Tag Manager alternative

  As privacy becomes a greater concern globally for end-users and governments, many businesses are looking for alternatives to the world’s largest advertising company – Google.

  Matomo Tag Manager is more than a Google Tag Manager alternative. With Matomo Tag Manager, you get a GDPR, HIPAA, CCPA and PECR compliant, open source Tag Manager and your data is 100% yours to own.

  Plus, with Matomo Tag Manager you only need one single tracking code for all of your website and tag analytics. No matter what you are tracking (scrolls, clicks, downloads, Heatmaps, visits, etc.), you will only ever need one piece of code on your website and one tool to manage it all. 

  The takeaway 

  Tagging is powerful but can quickly become complicated, risky and time-consuming. Tag Managers reduce these obstacles allowing you to set tags and triggers effortlessly. It empowers marketing teams, streamlines processes and removes the reliance on IT.

  Ready to try Matomo Tag Manager ? Start your 21-day free trial now – no credit card required. 

• FFMPEG code not generating thumbnail, but it was working before [closed]

  25 mars 2020, par Shijil

  I want to save thumbnails in my website using this simple FFMPEG code.
  I tried to run it, but it shows error

      <?php
  
  
  
  
  
  $file="Videos/bloodshot.mp4";
  
  $vname="bloodshot";
  
  
  
  $W = intval($_GET['file']);
  
  $H = intval($_GET['file']);
  
  
  
  if(substr($file,0,1) != '.'){
  
  
  
  $mov = new ffmpeg_movie($file);
  
  $wn = $mov->GetFrameWidth();
  
  $hn = $mov->GetFrameHeight();
  
  
  
  $frame = $mov->getFrame(32);
  
  
  
  $gd = $frame->toGDImage();
  
  
  
  if(!$W and !$H)
  
  {
  
  
  
  $W = $neww; // width of the image
  
  $H = $newh; // height image
  
  }
  
  
  
  
  
  $new = imageCreateTrueColor($W, $H);
  
  imageCopyResized($new, $gd, 0, 0, 0, 0, $neww, $newh, $wn, $hn);
  
  $black = imagecolorallocate($new, 255, 255, 255);
  
  imagegif($new);
  
  imagegif ($new, './thumb/success.gif', 100);
  
  }
  
  ?>

  error log is

  [25-Mar-2020 14:52:31 UTC] PHP Fatal error:  Uncaught Error: Class 'ffmpeg_movie' not found in /home/xxxxxxx/public_html/Videos/ffmpeg.php:12
  
  Stack trace:
  
  #0 {main}
  
    thrown in /home/xxxxxxx/public_html/Videos/ffmpeg.php on line 12

  I was able to run it without error in a mobile site few years ago. But it seems to be not working now.
  Server has FFMPEG support.
  I am not an expert in php, please fix this code for me.

• FFMPEG x264 (fourcc=0x21) codec is not working with OpenCV

  6 mars 2020, par dkac

  I’m trying to use mp4 format coding (fourcc=0x21) on OpenCV 3.2 without success. Probably I have a problem with my Ubuntu 18.04 setup but currently I’m running out of ideas how to fix it. First, I recompiled FFMPEG with x264 support. Than, recompiled OpenCV (with contrib and OPENCV_ENABLE_NONFREE=ON, WITH_FFMPEG=ON). It is still not working.

  I cannot use fourcc different than 0x21. I mean.. I cannot use another codec.

  Example :

  >>> import cv2
  
  >>> out = cv2.VideoWriter('output.mp4', 0x21, 20.0, (640,480))
  
  OpenCV: FFMPEG: tag 0x00000021/'!???' is not found (format 'mp4 / (null)')'

  However, this is working fine (other fourcc, codec) :

  >>> out = cv2.VideoWriter('output.mp4',0x31637661 , 20.0, (640,480))

  OpenCV compiled with FFMPEG support (version 3.2), cmake config :

  Video I/O:
  
  DC1394 1.x:                  NO
  
  DC1394 2.x:                  YES (ver 2.2.5)
  
  FFMPEG:                      YES
  
    avcodec:                   YES (ver 57.107.100)
  
    avformat:                  YES (ver 57.83.100)
  
    avutil:                    YES (ver 55.78.100)
  
    swscale:                   YES (ver 4.8.100)
  
    avresample:                YES (ver 3.7.0)

  FFMPEG build with x264 support :

  ffmpeg -version
  
  ffmpeg version N-96891-g60b1f85 Copyright (c) 2000-2020 the FFmpeg developers
  
  built with gcc 7 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
  
  configuration: --prefix=/home/user/ffmpeg_build --pkg-config-flags=--static --extra-cflags=-I/home/user/ffmpeg_build/include --extra-ldflags=-L/home/user/ffmpeg_build/lib --extra-libs='-lpthread -lm' --bindir=/home/user/bin --enable-gpl --enable-libass --enable-libfdk-aac --enable-libfreetype --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-nonfree
  
  libavutil      56. 42.100 / 56. 42.100
  
  libavcodec     58. 73.102 / 58. 73.102
  
  libavformat    58. 39.101 / 58. 39.101
  
  libavdevice    58.  9.103 / 58.  9.103
  
  libavfilter     7. 77.100 /  7. 77.100
  
  libswscale      5.  6.100 /  5.  6.100
  
  libswresample   3.  6.100 /  3.  6.100
  
  libpostproc    55.  6.100 / 55.  6.100

  FFMPEG x264 simple conversion test is working :

  ffmpeg -i in.mp4 -vcodec libx264 -f mp4 out.mp4y
  
  ffmpeg version N-96891-g60b1f85 Copyright (c) 2000-2020 the FFmpeg developers
  
  built with gcc 7 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
  
  configuration: --prefix=/home/user/ffmpeg_build --pkg-config-flags=--static --extra-cflags=-I/home/user/ffmpeg_build/include --extra-ldflags=-L/home/user/ffmpeg_build/lib --extra-libs='-lpthread -lm' --bindir=/home/user/bin --enable-gpl --enable-libass --enable-libfdk-aac --enable-libfreetype --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-nonfree
  
  libavutil      56. 42.100 / 56. 42.100
  
  libavcodec     58. 73.102 / 58. 73.102
  
  libavformat    58. 39.101 / 58. 39.101
  
  libavdevice    58.  9.103 / 58.  9.103
  
  libavfilter     7. 77.100 /  7. 77.100
  
  libswscale      5.  6.100 /  5.  6.100
  
  libswresample   3.  6.100 /  3.  6.100
  
  libpostproc    55.  6.100 / 55.  6.100
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'in.mp4':
  
  Metadata:
  
     major_brand     : isom
  
     minor_version   : 512
  
     compatible_brands: isomiso2avc1mp41
  
     encoder         : Lavf57.83.100
  
  Duration: 00:00:10.00, start: 0.000000, bitrate: 3826 kb/s
  
   Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 1280x960, 3825 kb/s, 10 fps, 10 tbr, 10240 tbn, 20 tbc (default)
  
  Metadata:
  
    handler_name    : VideoHandler
  
  File 'out.mp4y' already exists. Overwrite? [y/N] y
  
  Stream mapping:
  
    Stream #0:0 -> #0:0 (h264 (native) -> h264 (libx264))