Recherche avancée

Sur d’autres sites (9196)

• A Guide to Bank Customer Segmentation

  18 juillet 2024, par Erin

  Banking customers are more diverse, complex, and demanding than ever. As a result, banks have to work harder to win their loyalty, with 75% saying they would switch to a bank that better fits their needs.

  The problem is banking customers’ demands are increasingly varied amid economic uncertainties, increased competition, and generational shifts.

  If banks want to retain their customers, they can’t treat them all the same. They need a bank customer segmentation strategy that allows them to reach specific customer groups and cater to their unique demands.

  What is customer segmentation ?

  Customer segmentation divides a customer base into distinct groups based on shared characteristics or behaviours.

  This allows companies to analyse the behaviours and needs of different customer groups. Banks can use these insights to target segments with relevant marketing throughout the customer cycle, e.g., new customers, inactive customers, loyal customers, etc.

  You combine data points from multiple segmentation categories to create a customer segment. The most common customer segmentation categories include :

  • Demographic segmentation
  • Website activity segmentation
  • Geographic segmentation
  • Purchase history segmentation
  • Product-based segmentation
  • Customer lifecycle segmentation
  • Technographic segmentation
  • Channel preference segmentation
  • Value-based segmentation

  

  By combining segmentation categories, you can create detailed customer segments. For example, high-value customers based in a particular market, using a specific product, and approaching the end of the lifecycle. This segment is ideal for customer retention campaigns, localised for their market and personalised to satisfy their needs.

  

  Matomo’s privacy-centric web analytics solution helps you capture data from the first visit. Unlike Google Analytics, Matomo doesn’t use data sampling (more on this later) or AI to fill in data gaps. You get 100% accurate data for reliable insights and customer segmentation.

  Try Matomo for Free

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

  Start for free

  No credit card required

  Why is customer segmentation important for banks ?

  Customer segmentation allows you to address the needs of specific groups instead of treating all of your customers the same. This has never been more important amid a surge in bank switching, with three in four customers ready to switch to a provider that better suits their needs.

  Younger customers are the most likely to switch, with 19% of 18-24 year olds changing their primary bank in the past year (PDF).

  Customer expectations are changing, driven by economic uncertainties, declining trust in traditional banking, and the rise of fintech. Even as economic pressures lift, banks need to catch up with the demands of maturing millennials, Gen Z, and future generations of banking customers.

  Switching is the new normal, especially for tech-savvy customers encouraged by an expanding world of digital banking options.

  To retain customers, banks need to know them better and understand how their needs change over time. Customer retention provides the insights banks need to understand these needs at a granular level and the means to target specific customer groups with relevant messages.

  At its core, customer segmentation is essential to banks for two key reasons :

  • Customer retention : Holding on to customers for longer by satisfying their personal needs.
  • Customer lifetime value : Maximising ongoing customer revenue through retention, purchase frequency, cross-selling, and upselling.

  Here are some actionable bank customer segmentation strategies that can achieve these two objectives :

  Prevent switching with segment analysis

  Use customer segmentation to prevent them from switching to rivals by knowing what they want from you. Analyse customer needs and how they change throughout the lifecycle. Third-party data reveals general trends, but what do your customers want ?

  

  Use first-party customer data and segmentation to go beyond industry trends. Know exactly what your customers want from you and how to deliver targeted messages to each segment — e.g., first-time homebuyers vs. retirement planners.

  Keep customers active with segment targeting

  Target customer segments to keep customers engaged and motivated. Create ultra-relevant marketing messages and deliver them with precision to distinct customer segments. Nurture customer motivation by continuing to address their problems and aspirations.

  Improve the quality of services and products

  Knowing your customers’ needs in greater detail allows you to adapt your products and messages to cater to the most important segments. Customers switch banks because they feel their needs are better met elsewhere. Prevent this by implementing customer segmentation insights into product development and marketing.

  Personalise customer experiences by layering segments

  Layer segments to create ultra-specific target customer groups for personalised services and marketing campaigns. For example, top-spending customers are one of your most important segments, but there’s only so much you can do with this. However, you can divide this group into even narrower target audiences by layering multiple segments.

  For example, segmenting top-spending customers by product type can create more relevant messaging. You can also segment recent activity and pinpoint specific usage segments, such as those with a recent drop in transactions.

  Now, you have a three-layered segment of high-spending customers who use specific products less often and whom you can target with re-engagement campaigns.

  Maximise customer lifetime value

  Bringing all of this together, customer segmentation helps you maximise customer lifetime value in several ways :

  • Prevent switching
  • Enhance engagement and motivation
  • Re-engage customers
  • Cross-selling, upselling
  • Personalised customer loyalty incentives

  The longer you retain customers, the more you can learn about them, and the more effective your lifetime value campaigns will be.

  Balancing bank customer segmentation with privacy and marketing regulations

  Of course, customer segmentation uses a lot of data, which raises important legal and ethical questions. First, you need to comply with data and privacy regulations, such as GDPR and CCPA. Second, you also have to consider the privacy expectations of your customers, who are increasingly aware of privacy issues and rising security threats targeting financial service providers.

  If you aim to retain and maximise customer value, respecting their privacy and protecting their data are non-negotiables.

  Regulators are clamping down on finance

  Regulatory scrutiny towards the finance industry is intensifying, largely driven by the rise of fintech and the growing threat of cyber attacks. Not only was 2023 a record-breaking year for finance security breaches but several compromises of major US providers “exposed shortcomings in the current supervisory framework and have put considerable public pressure on banking authorities to reevaluate their supervisory and examination programs” (Deloitte).

  Banks face some of the strictest consumer protections and marketing regulations, but the digital age creates new threats.

  In 2022, the Consumer Financial Protection Bureau (CFPB) warned that digital marketers must comply with finance consumer protections when targeting audiences. CFPB Director Rohit Chopra said : “When Big Tech firms use sophisticated behavioural targeting techniques to market financial products, they must adhere to federal consumer financial protection laws.”

  This couldn’t be more relevant to customer segmentation and the tools banks use to conduct it.

  Customer data in the hands of agencies and big tech

  Banks should pay attention to the words of CFPB Director Rohit Chopra when partnering with marketing agencies and choosing analytics tools. Digital marketing agencies are rarely experts in financial regulations, and tech giants like Google don’t have the best track record for adhering to them.

  Google is constantly in the EU courts over its data use. In 2022, the EU ruled that the previous version of Google Analytics violated EU privacy regulations. Google Analytics 4 was promptly released but didn’t resolve all the issues.

  Meanwhile, any company that inadvertently misuses Google Analytics is legally responsible for its compliance with data regulations.

  Banks need a privacy-centric alternative to Google Analytics

  Google’s track record with data regulation compliance is a big issue, but it’s not the only one. Google Analytics uses data sampling, which Google defines as the “practice of analysing a subset of data to uncover meaningful information from a larger data set.”

  This means Google Analytics places thresholds on how much of your data it analyses — anything after that is calculated assumptions. We’ve explained why this is such a problem before, and GA4 relies on data sampling even more than the previous version.

  In short, banks should question whether they can trust Google with their customer data and whether they can trust Google Analytics to provide accurate data in the first place. And they do. 80% of financial marketers say they’re concerned about ad tech bias from major providers like Google and Meta.

  

  Matomo is the privacy-centric alternative to Google Analytics, giving you 100% data ownership and compliant web analytics. With no data sampling, Matomo provides 20-40% more data to help you make accurate, informed decisions. Get the data you need for customer segmentation without putting their data at risk.

  Try Matomo for Free

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

  Start for free

  No credit card required

  Bank customer segmentation examples

  Now, let’s look at some customer segments you create and layer to target specific customer groups.

  Visit-based segmentation

  Visit segmentation filters audiences based on the pages they visit on your website and the behaviors they exhibit—for example, first-time visitors vs. returning visitors or landing page visitors vs. blog page visitors.

  If you look at HSBC’s website, you’ll see it is structured into several categories for key customer personas. One of its segments is international customers living in the US, so it has pages and resources expats, people working in the US, people studying in the US, etc. 

  

  By combining visit-based segmentation with ultra-relevant pages for specific target audiences, HSBC can track each group’s demand and interest and analyse their behaviours. It can determine which audiences are returning, which products they want, and which messages convert them.

  Demographic segmentation

  Demographic segmentation divides customers by attributes such as age, gender, and location. However, you can also combine these insights with other non-personal data to better understand specific audiences.

  For example, in Matomo, you can segment audiences based on the language of their browser, the country they’re visiting from, and other characteristics. So, in this case, HSBC could differentiate between visitors already residing in the US and those outside of the country looking for information on moving there.

  

  It could determine which countries they’re visiting, which languages to localise for, and which networks to run ultra-relevant social campaigns on.

  Interaction-based segmentation

  Interaction-based segmentation uses events and goals to segment users based on their actions on your website. For example, you can segment audiences who visit specific URLs, such as a loan application page, or those who don’t complete an action, such as failing to complete a form.

  

  With events and goals set up, you can track the actions visitors complete before making purchases. You can monitor topical interests, page visits, content interactions, and pathways toward conversions, which feed into their customer journey.

  From here, you can segment customers based on their path leading up to their first purchase, follow-up purchases, and other actions.

  Purchase-based segmentation

  Purchase-based segmentation allows you to analyse the customer behaviours related to their purchase history and spending habits. For example, you can track the journey of repeat customers or identify first-time buyers showing interest in other products/services.

  You can implement these insights into your cross-selling and upselling campaigns with relevant messages designed to increase retention and customer lifetime value.

  Get reliable website analytics for your bank customer segmentation needs

  With customers switching in greater numbers, banks need to prioritise customer retention and lifetime value. Customer segmentation allows you to target specific customer groups and address their unique needs — the perfect strategy to stop them from moving to another provider.

  Quality, accurate data is the key ingredient of an effective bank customer segmentation strategy. Don’t accept data sampling from Google Analytics or any other tool that limits the amount of your own data you can access. Choose a web analytics tool like Matamo that unlocks the full potential of your website analytics to get the most out of bank customer segmentation.

  Matomo is trusted by over 1 million websites globally, including many banks, for its accuracy, compliance, and reliability. Discover why financial institutions rely on Matomo to meet their web analytics needs.

  Start collecting the insights you need for granular, layered segmentation — without putting your bank customer data at risk. Request a demo of Matomo now.

  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

  

• C# .net mvc Process return encoding progress (FFMpeg) to client initiated with ajax

  19 décembre 2014, par user1585895

  I am using FFMpeg to encode wav to mp3s, and on completion download the final .zip to the client.

  All works great, and I can Debug.WriteLine the progress of the encoding, but I would like to return _percentage back to the client to do some UI updates based on the value of _percentage and if all encoding is done, Im not sure how to approach this.

  My thinking is as follows :

  • ajax post to CreateAndDownloadAlbum(List trackIds, int productId)
  • loop through List and create a new Process, run
    — parse StdError to get encoding percentage in myProcess_ErrorData(object source, DataReceivedEventArgs e)
    — send _percentage value at timed intervals back to CreateAndDownloadAlbum
    — update UI based on value of _percentage, when all is complete break and call public ActionResult SendFileDownload()

  Any input would be great.

  Thanks !

  front end AJAX call to post list of file Ids to download

  var data = $('#downloadAlbum').serialize();
  
  $.ajax({
  
      url: "/Admin/CreateAndDownloadAlbum",
  
      method: "POST",
  
      data: data,
  
      dataType: 'json',
  
      success: function(result) {
  
           // wait here for _percentage
  
           // if not 100, call again to get new _percentage value
  
           // if 100, update UI, move to next file being encoded
  
           // if all encoding is complete, call SendFileDownload() in controller
  
      }
  
  });

  then the controller code

  [HttpPost]
  
      public void CreateAndDownloadAlbum(List<trackstodownload> trackIds, int productId)
  
      {
  
          _numTracksToDownload = trackIds.Count;
  
          var product = _productRepository.GetProductById(productId);
  
          var artist = _artistRepository.GetArtistById(product.ArtistId);
  
  
  
          var folderGuid = Guid.NewGuid();
  
          _zipFolder = string.Concat(artist.ArtistName.ToUpper().Replace(" ", "_"), "[", product.ProductName.ToUpper().Replace(" ", "_"), "].zip");
  
          _mp3FolderPath = Server.MapPath("/Files/" + productId + "/" + folderGuid);
  
          _zipDownloadPath = Server.MapPath("/Delivery/" + _zipFolder);
  
  
  
          if (!Directory.Exists(Server.MapPath("/Files/" + productId + "/" + folderGuid)))
  
          {
  
              Directory.CreateDirectory(Server.MapPath("/Files/" + productId + "/" + folderGuid));
  
          }
  
  
  
          foreach (var z in trackIds)
  
          {
  
              var track = _trackRepository.GetTrackById(z.TrackId);
  
              var process = new Process();
  
              var startInfo = new ProcessStartInfo
  
              {
  
                  WindowStyle = System.Diagnostics.ProcessWindowStyle.Hidden,
  
                  FileName = "F:\\Development\\ffmpeg\\ffmpeg.exe",
  
                  RedirectStandardOutput = true,
  
                  RedirectStandardError = true,
  
                  UseShellExecute = false
  
              };
  
              var startFile = Path.Combine("F:\\Development","Files", track.ProductId.ToString(), track.TrackFileName);
  
              var endFile = Path.Combine("F:\\Development", "Files", track.ProductId.ToString(), folderGuid.ToString(), track.TrackFileName.Replace(".wav", ".mp3"));
  
  
  
              startInfo.Arguments = "-i " + startFile + " -b:a 320k " + endFile + " -stats";
  
              process.StartInfo = startInfo;
  
              process.EnableRaisingEvents = true;
  
              process.Exited += myProcess_exited;
  
              process.OutputDataReceived += myProcess_OutputData;
  
              process.ErrorDataReceived += myProcess_ErrorData;
  
  
  
              try
  
              {
  
                  process.Start();
  
                  process.BeginOutputReadLine();
  
                  process.BeginErrorReadLine();
  
  
  
                  if (process.HasExited == false)
  
                  {
  
                      process.WaitForExit();
  
                  }
  
              }
  
              catch (Exception)
  
              {
  
  
  
                  throw;
  
              }
  
          }
  
  
  
          SendFileDownload();
  
  
  
      }
  
  
  
      public ActionResult SendFileDownload()
  
      {
  
          // zip and move to delivery folder
  
          using (var zip = new ZipFile())
  
          {
  
              zip.AddDirectory(_mp3FolderPath, _zipFolder);
  
              zip.Save(_zipDownloadPath);
  
          }
  
  
  
          // delete items in temp guid folder
  
          var downloadedMessageInfo = new DirectoryInfo(_mp3FolderPath);
  
          foreach (var f in downloadedMessageInfo.GetFiles())
  
          {
  
              f.Delete();
  
          }
  
  
  
          // delete temp folder
  
          Directory.Delete(_mp3FolderPath);
  
  
  
          // download file
  
          string file = _zipDownloadPath;
  
          return File(file, "application/force-download", Path.GetFileName(file));
  
  
  
      }
  
  
  
      public void myProcess_exited(Object source, EventArgs e)
  
      {
  
          Debug.WriteLine("myProcess_exited ===================================");
  
          _duration = new TimeSpan(0, 0, 0);
  
          _frameTime = new TimeSpan(0, 0, 0);
  
          _percentage = 0;
  
          _numEncodedTracks++; // using this to tell me if all tracks have been encoded
  
      }
  
  
  
      public void myProcess_OutputData(object source, DataReceivedEventArgs e)
  
      {
  
      }
  
  
  
      public void myProcess_ErrorData(object source, DataReceivedEventArgs e)
  
      {
  
          string strMessage = e.Data;
  
  
  
          if (!string.IsNullOrEmpty(strMessage) &amp;&amp; (strMessage.Contains("Duration: ") || strMessage.Contains("size=")))
  
          {
  
              if (_duration != null)
  
              {
  
                  if (strMessage.Contains("Duration: "))
  
                  {
  
                      _strDuration = strMessage.Substring(strMessage.IndexOf("Duration: ") + ("Duration: ").Length,
  
                          ("00:00:00.00").Length);
  
  
  
                      char[] d_delHrMn = new char[] { ':' };
  
                      string[] d_tempHrMn = _strDuration.Split(d_delHrMn, StringSplitOptions.RemoveEmptyEntries);
  
  
  
                      char[] d_delSec = new char[] { '.' };
  
                      string[] d_tempSec = d_tempHrMn[2].Split(d_delSec, StringSplitOptions.RemoveEmptyEntries);
  
  
  
                      var d_hour = d_tempHrMn[0] == "0" ? 0 : Convert.ToInt32(d_tempHrMn[0]);
  
                      var d_min = d_tempHrMn[1] == "0" ? 0 : Convert.ToInt32(d_tempHrMn[1]);
  
                      var d_sec = d_tempSec[0] == "0" ? 0 : Convert.ToInt32(d_tempSec[0]);
  
  
  
                      _duration = new TimeSpan(d_hour, d_min, d_sec);
  
                  }
  
              }
  
  
  
              if (strMessage.Contains("size="))
  
              {
  
                  _strFrameTime = strMessage.Substring(strMessage.IndexOf("time=") + ("time=").Length,
  
                      ("00:00:00.00").Length);
  
  
  
                  char[] f_delHrMn = new char[] { ':' };
  
                  string[] f_tempHrMn = _strFrameTime.Split(f_delHrMn, StringSplitOptions.RemoveEmptyEntries);
  
  
  
                  char[] f_delSec = new char[] { '.' };
  
                  string[] f_tempSec = f_tempHrMn[2].Split(f_delSec, StringSplitOptions.RemoveEmptyEntries);
  
  
  
                  var f_hour = f_tempHrMn[0] == "0" ? 0 : Convert.ToInt32(f_tempHrMn[0]);
  
                  var f_min = f_tempHrMn[1] == "0" ? 0 : Convert.ToInt32(f_tempHrMn[1]);
  
                  var f_sec = f_tempSec[0] == "0" ? 0 : Convert.ToInt32(f_tempSec[0]);
  
  
  
                  _frameTime = new TimeSpan(f_hour, f_min, f_sec);
  
  
  
              }
  
  
  
              if (_strDuration != "00:00:00.00" &amp;&amp; _strFrameTime != "00:00:00.00" &amp;&amp; _percentage &lt; 100)
  
              {
  
                  _percentage = _frameTime.TotalMilliseconds / _duration.TotalMilliseconds * 100;
  
                  Debug.WriteLine(_percentage + " || " + _frameTime + " " + _duration);
  
              }
  
          }
  
      }
  
  </trackstodownload>

• How to write UI tests for your plugin – Introducing the Piwik Platform

  18 février 2015, par Thomas Steur — Development

  This is the next post of our blog series where we introduce the capabilities of the Piwik platform (our previous post was How to write unit tests for your plugin). This time you’ll learn how to write UI tests in Piwik. For this tutorial you will need to have basic knowledge of JavaScript and the Piwik platform.

  What is a UI test ?

  Some might know a UI test under the term ‘CSS test’ or ‘screenshot test’. When we speak of UI tests we mean automated tests that capture a screenshot of a URL and then compare the result with an expected image. If the images are not exactly the same the test will fail. For more information read our blog post about UI Testing.

  What is a UI test good for ?

  We use them to test our PHP Controllers, Twig templates, CSS, and indirectly test our JavaScript. We do usually not write Unit or Integration tests for our controllers. For example we use UI tests to ensure that the installation, the login and the update process works as expected. We also have tests for most pages, reports, settings, etc. This increases the quality of our product and saves us a lot of time as it is easy to write and maintain such tests. All UI tests are executed on Travis after each commit and compared with our expected screenshots.

  Getting started

  In this post, we assume that you have already installed Piwik 2.11.0 or later via git, set up your development environment and created a plugin. If not, visit the Piwik Developer Zone where you’ll find the tutorial Setting up Piwik and other Guides that help you to develop a plugin.

  Next you need to install the needed packages to execute UI tests.

  Let’s create a UI test

  We start by using the Piwik Console to create a new UI test :

  ./console generate:test --testtype ui

  The command will ask you to enter the name of the plugin the created test should belong to. I will use the plugin name “Widgetize”. Next it will ask you for the name of the test. Here you usually enter the name of the page or report you want to test. I will use the name “WidgetizePage” in this example. There should now be a file plugins/Widgetize/tests/UI/WidgetizePage_spec.js which contains already an example to get you started easily :

  describe("WidgetizePage", function () {
  
      var generalParams = 'idSite=1&period=day&date=2010-01-03';
  
  
  
      it('should load a simple page by its module and action', function (done) {
  
          var screenshotName = 'simplePage';
  
          // will save image in "processed-ui-screenshots/WidgetizePageTest_simplePage.png"
  
  
  
          expect.screenshot(screenshotName).to.be.capture(function (page) {
  
              var urlToTest = "?" + generalParams + "&module=Widgetize&action=index";
  
              page.load(urlToTest);
  
          }, done);
  
      });
  
  });

  What is happening here ?

  This example declares a new set of specs by calling the method describe(name, callback) and within that a new spec by calling the method it(description, func). Within the spec we load a URL and once loaded capture a screenshot of the whole page. The captured screenshot will be saved under the defined screenshotName. You might have noticed we write our UI tests in BDD style.

  Capturing only a part of the page

  It is good practice to not always capture the full page. For example many pages contain a menu and if you change that menu, all your screenshot tests would fail. To avoid this you would instead have a separate test for your menu. To capture only a part of the page simply specify a jQuery selector and call the method captureSelector instead of capture :

  var contentSelector = '#selector1, .selector2 .selector3';
  
  // Only the content of both selectors will be in visible in the captured screenshot
  
  expect.screenshot('page_partial').to.be.captureSelector(contentSelector, function (page) {
  
      page.load(urlToTest);
  
  }, done);

  Hiding content

  There is a known issue with sparklines that can fail tests randomly. Also version numbers or a date that changes from time to time can fail tests without actually having an error. To avoid this you can prevent elements from being visible in the captured screenshot via CSS as we add a CSS class called uiTest to the HTML element while tests are running.

  .uiTest .version { visibility:hidden }

  Running a test

  To run the previously generated tests we will use the command tests:run-ui :

  ./console tests:run-ui WidgetizePage

  After running the tests for the first time you will notice a new folder plugins/PLUGINNAME/tests/UI/processed-ui-screenshots in your plugin. If everything worked, there will be an image for every captured screenshot. If you’re happy with the result it is time to copy the file over to the expected-ui-screenshots folder, otherwise you have to adjust your test until you get the result you want. From now on, the newly captured screenshots will be compared with the expected images whenever you execute the tests.

  Fixing a test

  At some point your UI test will fail, for example due to expected CSS changes. To fix a test all you have to do is to copy the captured screenshot from the folder processed-ui-screenshots to the folder expected-ui-screenshots.

  Executing the UI tests on Travis

  In case you have not generated a .travis.yml file for your plugin yet you can do this by executing the following command :

  ./console generate:travis-yml --plugin PLUGINNAME

  Next you have to activate Travis for your repository.

  Advanced features

  Isn’t it easy to create a UI test ? We never even created a file ! Of course you can accomplish even more if you want. For example you can specify a fixture to be inserted before running the tests which is useful when your plugin requires custom data. You can also control the browser as it was a human by clicking, moving the mouse, typing text, etc. If you want to discover more features have a look at our existing test cases.

  If you have any feedback regarding our APIs or our guides in the Developer Zone feel free to send it to us.