Recherche avancée
Autres articles (37)
-
Les autorisations surchargées par les plugins
27 avril 2010, parMediaspip core
autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs -
Support de tous types de médias
10 avril 2011Contrairement à beaucoup de logiciels et autres plate-formes modernes de partage de documents, MediaSPIP a l’ambition de gérer un maximum de formats de documents différents qu’ils soient de type : images (png, gif, jpg, bmp et autres...) ; audio (MP3, Ogg, Wav et autres...) ; vidéo (Avi, MP4, Ogv, mpg, mov, wmv et autres...) ; contenu textuel, code ou autres (open office, microsoft office (tableur, présentation), web (html, css), LaTeX, Google Earth) (...)
-
L’utiliser, en parler, le critiquer
10 avril 2011La première attitude à adopter est d’en parler, soit directement avec les personnes impliquées dans son développement, soit autour de vous pour convaincre de nouvelles personnes à l’utiliser.
Plus la communauté sera nombreuse et plus les évolutions seront rapides ...
Une liste de discussion est disponible pour tout échange entre utilisateurs.
Sur d’autres sites (6727)
-
Discard data stream from container using ffmpeg
10 décembre 2020, par A.BeI am trying to get rid of a data (subtitle) stream within a Mp4 container, using ffmpeg.



Here's the screenshot from ffprobe :



Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'test.m4v':
Metadata:
major_brand : isom
minor_version : 2
compatible_brands: isomiso2avc1mp41
creation_time : 2018-01-19T15:10:48.000000Z
Duration: 00:00:42.17, start: 0.000000, bitrate: 6260 kb/s
Chapter #0:0: start 0.000000, end 42.166000
Metadata:
 title : Chapter 1
Stream #0:0(eng): Data: bin_data (text / 0x74786574), 0 kb/s (default)
Metadata:
 creation_time : 2018-01-19T15:10:48.000000Z
 handler_name : Apple Alias Data Handler
Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, 
fltp, 317 kb/s (default)
Metadata:
 creation_time : 2018-01-19T15:10:48.000000Z
 handler_name : AAC audio
Stream #0:2(eng): Video: h264 (High) (avc1 / 0x31637661), yuvj420p(pc), 
1920x1080, 5926 kb/s, 30 fps, 30 tbr, 30k tbn, 60k tbc (default)
Metadata:
 creation_time : 2018-01-19T15:10:48.000000Z
 handler_name : H264 video
 **Unsupported codec with id 100359 for input stream 0**



I tried :



ffmpeg -i test.m4v -acodec copy -vcodec copy -sn nodata.mp4



Data track still there, just moved from stream 0 to stream 2



I tried also :



ffmpeg -i test.m4v -acodec copy -vcodec copy -map 0:1 -map 0:2 no2.mp4



Same result, track still there, just jumped to stream 0:2 no luck.



Any hint ?
Thanks in advance


-
FFMPEG scale and crop in single command
26 mars 2016, par The Hungry AndroiderI’m using FFMPEG on Android using the following lib : http://writingminds.github.io/ffmpeg-android-java/
This is the command I’m using :
"-i " + path + " -vf scale=480:360,crop=360:360:0:00 -strict -2 -preset ultrafast " + fileOutPathMy goal of this is to scale the image down to 480x360, then crop it to 360x360 from (0,0) (top left corner). HOWEVER, what ends up happening is that it crops from the vertical-center. So for example if you were to take a vide of three blocks on top of each other filling the entire screen, the crop would eventually show just the middle block, whereas I desire the top block.
Any ideas as to what I’m doing wrong ?
My ultimate goal from all of this is to get a square video of size 360x360.
Output log :
03-26 12:10:16.816 17198-17198/com.noq D/FFMPEG: FFMPEG onStart
03-26 12:10:16.900 17198-17385/com.noq D/FFmpeg: Running publishing updates method
03-26 12:10:16.914 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: WARNING: linker: /data/user/0/com.noq/files/ffmpeg has text relocations. This is wasting memory and prevents security hardening. Please fix.
03-26 12:10:17.004 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: ffmpeg version n2.4.2 Copyright (c) 2000-2014 the FFmpeg developers
03-26 12:10:17.004 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: built on Oct 7 2014 15:08:46 with gcc 4.8 (GCC)
03-26 12:10:17.007 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: configuration: --target-os=linux --cross-prefix=/home/sb/Source-Code/ffmpeg-android/toolchain-android/bin/arm-linux-androideabi- --arch=arm --cpu=cortex-a8 --enable-runtime-cpudetect --sysroot=/home/sb/Source-Code/ffmpeg-android/toolchain-android/sysroot --enable-pic --enable-libx264 --enable-libass --enable-libfreetype --enable-libfribidi --enable-fontconfig --enable-pthreads --disable-debug --disable-ffserver --enable-version3 --enable-hardcoded-tables --disable-ffplay --disable-ffprobe --enable-gpl --enable-yasm --disable-doc --disable-shared --enable-static --pkg-config=/home/sb/Source-Code/ffmpeg-android/ffmpeg-pkg-config --prefix=/home/sb/Source-Code/ffmpeg-android/build/armeabi-v7a-neon --extra-cflags='-I/home/sb/Source-Code/ffmpeg-android/toolchain-android/include -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fno-strict-overflow -fstack-protector-all -mfpu=neon' --extra-ldflags='-L/home/sb/Source-Code/ffmpeg-android/toolchain-android/lib -Wl,-z,relro -Wl,-z,now -pie' --extra-libs='-lpng -lexpat -lm' --extra-cxxflags=
03-26 12:10:17.021 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: libavutil 54. 7.100 / 54. 7.100
03-26 12:10:17.022 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: libavcodec 56. 1.100 / 56. 1.100
03-26 12:10:17.022 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: libavformat 56. 4.101 / 56. 4.101
03-26 12:10:17.022 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: libavdevice 56. 0.100 / 56. 0.100
03-26 12:10:17.022 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: libavfilter 5. 1.100 / 5. 1.100
03-26 12:10:17.022 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: libswscale 3. 0.100 / 3. 0.100
03-26 12:10:17.022 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: libswresample 1. 1.100 / 1. 1.100
03-26 12:10:17.022 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: libpostproc 53. 0.100 / 53. 0.100
03-26 12:10:17.201 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/storage/emulated/0/Android/data/com.noq/files/Pictures/noq/1459008610063.mp4':
03-26 12:10:17.201 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: Metadata:
03-26 12:10:17.201 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: major_brand : mp42
03-26 12:10:17.201 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: minor_version : 0
03-26 12:10:17.201 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: compatible_brands: isommp42
03-26 12:10:17.201 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: creation_time : 2016-03-26 16:10:16
03-26 12:10:17.202 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: Duration: 00:00:02.02, start: 0.000000, bitrate: 6131 kb/s
03-26 12:10:17.202 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: Stream #0:0(eng): Video: h264 (Baseline) (avc1 / 0x31637661), yuv420p, 640x480, 5926 kb/s, SAR 65536:65536 DAR 4:3, 29.87 fps, 30.17 tbr, 90k tbn, 180k tbc (default)
03-26 12:10:17.202 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: Metadata:
03-26 12:10:17.202 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: rotate : 270
03-26 12:10:17.202 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: creation_time : 2016-03-26 16:10:16
03-26 12:10:17.202 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: handler_name : VideoHandle
03-26 12:10:17.202 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: encoder : MOTO
03-26 12:10:17.202 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: Side data:
03-26 12:10:17.202 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: displaymatrix: rotation of 90.00 degrees
03-26 12:10:17.202 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: Stream #0:1(eng): Audio: aac (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 130 kb/s (default)
03-26 12:10:17.202 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: Metadata:
03-26 12:10:17.202 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: creation_time : 2016-03-26 16:10:16
03-26 12:10:17.202 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: handler_name : SoundHandle
03-26 12:10:17.263 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: [libx264 @ 0xb78cde30] using SAR=1/1
03-26 12:10:17.297 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: [libx264 @ 0xb78cde30] using cpu capabilities: none!
03-26 12:10:17.411 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: [libx264 @ 0xb78cde30] profile Constrained Baseline, level 2.1
03-26 12:10:17.417 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: [libx264 @ 0xb78cde30] 264 - core 142 - H.264/MPEG-4 AVC codec - Copyleft 2003-2014 - http://www.videolan.org/x264.html - options: cabac=0 ref=1 deblock=0:0:0 analyse=0:0 me=dia subme=0 psy=1 psy_rd=1.00:0.00 mixed_ref=0 me_range=16 chroma_me=1 trellis=0 8x8dct=0 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=0 threads=12 lookahead_threads=2 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=0 weightp=0 keyint=250 keyint_min=25 scenecut=0 intra_refresh=0 rc=crf mbtree=0 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=0
03-26 12:10:17.464 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: Output #0, mp4, to '/storage/emulated/0/Android/data/com.noq/files/Pictures/noq/14590086100631459008616802_square.mp4':
03-26 12:10:17.464 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: Metadata:
03-26 12:10:17.464 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: major_brand : mp42
03-26 12:10:17.464 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: minor_version : 0
03-26 12:10:17.464 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: compatible_brands: isommp42
03-26 12:10:17.464 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: encoder : Lavf56.4.101
03-26 12:10:17.465 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: Stream #0:0(eng): Video: h264 (libx264) ([33][0][0][0] / 0x0021), yuv420p, 360x360 [SAR 1:1 DAR 1:1], q=-1--1, 30.17 fps, 11584 tbn, 30.17 tbc (default)
03-26 12:10:17.465 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: Metadata:
03-26 12:10:17.465 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: rotate : 270
03-26 12:10:17.465 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: creation_time : 2016-03-26 16:10:16
03-26 12:10:17.465 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: handler_name : VideoHandle
03-26 12:10:17.465 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: encoder : Lavc56.1.100 libx264
03-26 12:10:17.465 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: Stream #0:1(eng): Audio: aac ([64][0][0][0] / 0x0040), 48000 Hz, stereo, fltp, 128 kb/s (default)
03-26 12:10:17.466 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: Metadata:
03-26 12:10:17.466 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: creation_time : 2016-03-26 16:10:16
03-26 12:10:17.466 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: handler_name : SoundHandle
03-26 12:10:17.467 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: encoder : Lavc56.1.100 aac
03-26 12:10:17.467 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: Stream mapping:
03-26 12:10:17.467 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: Stream #0:0 -> #0:0 (h264 (native) -> h264 (libx264))
03-26 12:10:17.467 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: Stream #0:1 -> #0:1 (aac (native) -> aac (native))
03-26 12:10:17.468 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: Press [q] to stop, [?] for help
03-26 12:10:18.035 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: frame= 3 fps=0.0 q=0.0 size= 0kB time=00:00:01.00 bitrate= 0.4kbits/s dup=1 drop=0
03-26 12:10:18.526 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: frame= 21 fps= 20 q=24.0 size= 48kB time=00:00:01.00 bitrate= 390.3kbits/s dup=1 drop=0
03-26 12:10:19.008 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: frame= 26 fps= 17 q=25.0 size= 68kB time=00:00:01.85 bitrate= 301.1kbits/s dup=1 drop=0
03-26 12:10:19.533 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: frame= 47 fps= 23 q=23.0 size= 165kB time=00:00:01.87 bitrate= 719.7kbits/s dup=1 drop=0
03-26 12:10:19.956 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: frame= 62 fps= 25 q=-1.0 Lsize= 297kB time=00:00:02.05 bitrate=1184.9kbits/s dup=1 drop=0
03-26 12:10:19.956 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: video:262kB audio:33kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.992648%
03-26 12:10:19.984 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: [libx264 @ 0xb78cde30] frame I:1 Avg QP:20.00 size: 18507
03-26 12:10:19.984 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: [libx264 @ 0xb78cde30] frame P:61 Avg QP:23.52 size: 4079
03-26 12:10:19.984 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: [libx264 @ 0xb78cde30] mb I I16..4: 100.0% 0.0% 0.0%
03-26 12:10:19.984 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: [libx264 @ 0xb78cde30] mb P I16..4: 4.4% 0.0% 0.0% P16..4: 70.9% 0.0% 0.0% 0.0% 0.0% skip:24.7%
03-26 12:10:19.985 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: [libx264 @ 0xb78cde30] coded y,uvDC,uvAC intra: 44.6% 40.1% 14.8% inter: 39.1% 32.7% 0.6%
03-26 12:10:19.985 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: [libx264 @ 0xb78cde30] i16 v,h,dc,p: 42% 24% 21% 13%
03-26 12:10:19.986 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: [libx264 @ 0xb78cde30] i8c dc,h,v,p: 44% 24% 25% 8%
03-26 12:10:19.987 17198-17198/com.noq D/FFMPEG: FFMPEG onProgress: [libx264 @ 0xb78cde30] kb/s:1040.60
03-26 12:10:20.002 17198-17198/com.noq D/FFMPEG: FFMPEG onSuccess: WARNING: linker: /data/user/0/com.noq/files/ffmpeg has text relocations. This is wasting memory and prevents security hardening. Please fix.
ffmpeg version n2.4.2 Copyright (c) 2000-2014 the FFmpeg developers
built on Oct 7 2014 15:08:46 with gcc 4.8 (GCC)
configuration: --target-os=linux --cross-prefix=/home/sb/Source-Code/ffmpeg-android/toolchain-android/bin/arm-linux-androideabi- --arch=arm --cpu=cortex-a8 --enable-runtime-cpudetect --sysroot=/home/sb/Source-Code/ffmpeg-android/toolchain-android/sysroot --enable-pic --enable-libx264 --enable-libass --enable-libfreetype --enable-libfribidi --enable-fontconfig --enable-pthreads --disable-debug --disable-ffserver --enable-version3 --enable-hardcoded-tables --disable-ffplay --disable-ffprobe --enable-gpl --enable-yasm --disable-doc --disable-shared --enable-static --pkg-config=/home/sb/Source-Code/ffmpeg-android/ffmpeg-pkg-config --prefix=/home/sb/Source-Code/ffmpeg-android/build/armeabi-v7a-neon --extra-cflags='-I/home/sb/Source-Code/ffmpeg-android/toolchain-android/include -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fno-strict-overflow -fstack-protector-all -mfpu=neon' --extra-ldflags='-L/home/sb/Source-Code/ffmpeg-android/toolchain-android/lib -Wl,-z,relro -Wl,-z,now -pie' --extra-libs='-lpng -lexpat -lm' --extra-cxxflags=
libavutil 54. 7.100 / 54. 7.100
libavcodec 56. 1.100 / 56. 1.100
libavformat 56. 4.101 / 56. 4.101
libavdevice 56. 0.100 / 56. 0.100
libavfilter 5. 1.100 / 5. 1.100
libswscale 3. 0.100 / 3. 0.100
libswresample 1. 1.100 / 1. 1.100
libpostproc 53. 0.100 / 53. 0.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/storage/emulated/0/Android/data/com.noq/files/Pictures/noq/1459008610063.mp4':
Metadata:
major_brand : mp42
minor_version : 0
compatible_brands: isommp42
creation_time : 2016-03-26 16:10:16
Duration: 00:00:02.02, start: 0.000000, bitrate: 6131 kb/s
Stream #0:0(eng): Video: h264 (Baseline) (avc1 / 0x31637661), yuv420p, 640x480, 5926 kb/s, SAR 65536:65536 DAR 4:3, 29.87 fps, 30.17 tbr, 90k tbn, 180k tbc (default)
Metadata:
rotate : 270
creation_time : 2016-03-26 16:10:16
handler_name : VideoHandle
encoder : MOTO
Side data:
displaymatrix: rotation of 90.00 degrees
Stream #0:1(eng): Audio: aac (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 130 kb/s (default)
Metadata:
creation_time : 2016-03-26 16:10:16
handler_name : SoundHandle
[libx264 @ 0xb78cde30] using SAR=1/1
[libx264 @ 0xb78cde30] using cpu capabilities: none!
[libx264 @ 0xb78cde30] profile Constrained Baseline, level 2.1
[libx264 @ 0xb78cde30] 264 - core 142 - H.264/MPEG-4 AVC codec - Copyleft 2003-2014 - http://www.videolan.org/x264.html - options: cabac=0 ref=1 deblock=0:0:0 analyse=0:0 me=dia subme=0 psy=1 psy_rd=1.00:0.00 mixed_ref=0 me_range=16 chroma_me=1 trellis=0 8x8dct=0 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=0 threads=12 lookahead_threads=2 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=0 weightp=0 keyint=250 keyint_min=25 scenecut=0 intra_refresh=0 rc=crf mbtree=0 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=0
Output #0, mp4, to '/storage/emulated/0/Android/data/com.noq/files/Pictures/noq/14590086100631459008616802_square.mp4':
Metadata:
major_brand : mp42
minor_version : 0
compatible_brands: isommp42
encoder : Lavf56.4.101
Stream #0:0(eng): Video: h264 (libx264) ([33][0][0][0] / 0x0021), yuv420p, 360x360 [SAR 1:1 DAR 1:1], q=-1--1, 30.17 fps, 11584 tbn, 30.17 tbc (default)
Metadata:
rotate : 270
creation_time : 2016-03-26 16:10:16
handler_name : VideoHandle
encoder : Lavc56.1.100 libx264
Stream #0:1(eng): Audio: aac ([64][0][0][0] / 0x0040), 48000 Hz, stereo, fltp, 128 kb/s (default)
Metadata:
creation_time : 2016-03-26 16:10:16
handler_name : SoundHandle
encoder : La
03-26 12:10:20.037 17198-17198/com.noq D/FFMPEG: FFMPEG onFinish -
7 Fintech Marketing Strategies to Maximise Profits in 2024
24 juillet 2024, par ErinFintech investment skyrocketed in 2021, but funding tanked in the following two years. A -63% decline in fintech investment in 2023 saw the worst year in funding since 2017. Luckily, the correction quickly floored, and the fintech industry will recover in 2024, but companies will have to work much harder to secure funds.
F-Prime’s The 2024 State of Fintech Report called 2023 the year of “regulation on, risk off” amid market pressures and regulatory scrutiny. Funding is rising again, but investors want regulatory compliance and stronger growth performance from fintech ventures.
Here are seven fintech marketing strategies to generate the growth investors seek in 2024.
Top fintech marketing challenges in 2024
Following the worst global investment run since 2017 in 2023, fintech marketers need to readjust their goals to adapt to the current market challenges. The fintech honeymoon is over for Wall Street with regulator scrutiny, closures, and a distinct lack of profitability giving investors cold feet.
Here are the biggest challenges fintech marketers face in 2024 :
- Market correction : With fewer rounds and longer times between them, securing funds is a major challenge for fintech businesses. F-Prime’s The 2024 State of Fintech Report warns of “a high probability of significant shutdowns in 2024 and 2025,” highlighting the importance of allocating resources and budgets effectively.
- Contraction : Aside from VC funding decreasing by 64% in 2023, the payments category now attracts a large majority of fintech investment, meaning there’s a smaller share from a smaller pot to go around for everyone else.
- Competition : The biggest names in finance have navigated heavy disruption from startups and, for the most part, emerged stronger than ever. Meanwhile, fintech is no longer Wall Street’s hottest commodity as investors turn their attention to AI.
- Regulations : Regulatory scrutiny of fintech intensified in 2023 – particularly in the US – contributing to the “regulation on, risk off” summary of F-Prime’s report.
- Investor scrutiny : With market and industry challenges intensifying, investors are putting their money behind “safer” ventures that demonstrate real, sustainable profitability, not short-term growth.
- Customer loyalty : Even in traditional baking and finance, switching is surging as customers seek providers who better meet their needs. To achieve the sustainable growth investors are looking for, fintech startups need to know their ideal customer profile (ICP), tailor their products/services and fintech marketing campaigns to them, and retain them throughout the customer lifecycle.
(Source) The good news for fintech marketers is that the market correction is leveling out in 2024. In The 2024 State of Fintech Report, F-Prime says that “heading into 2024, we see the fintech market amid a rebound,” while McKinsey expects fintech revenue to grow “almost three times faster than those in the traditional banking sector between 2023 and 2028.”
Winning back investor confidence won’t be easy, though. F-Prime acknowledges that investors are prioritising high-performance fintech ventures, particularly those with high gross margins. Fintech marketers need to abandon the growth-at-all-costs mindset and switch to a data-driven optimisation, growth and revenue system.
7 fintech marketing strategies
Given the current state of the fintech industry and relatively low levels of investor confidence, fintech marketers’ priority is building a new culture of sustainable profit. This starts with rethinking priorities and switching up the marketing goals to reflect longer-term ambitions.
So, here are the fintech marketing strategies that matter most in 2024.
1. Optimise for profitability over growth at all costs
To progress from the growth-at-all-cost mindset, fintech marketers need to optimise for different KPIs. Instead of flexing metrics like customer growth rate, fintech companies need to take a more balanced approach to measuring sustainable profitability.
This means holding on to existing customers – and maximising their value – while they acquire new customers. It also means that, instead of trying to make everyone a target customer, you concentrate on targeting the most valuable prospects, even if it results in a smaller overall user base.
Optimising for profitability starts with putting vanity metrics in their place and pinpointing the KPIs that represent valuable business growth :
- Gross profit margin
- Revenue growth rate
- Cash flow
- Monthly active user growth (qualify “active” as completing a transaction)
- Customer acquisition cost
- Customer retention rate
- Customer lifetime value
- Avg. revenue per user
- Avg. transactions per month
- Avg. transaction value
With a more focused acquisition strategy, you can feed these insights into every company level. For example, you can prioritise customer engagement, revenue, retention, and customer service in product development and customer experience (CX).
To ensure all marketing efforts are pulling towards these KPIs, you need an attribution system that accurately measures the contribution of each channel.
Marketing attribution (aka multi-touch attribution) should be used to measure every touchpoint in the customer journey and accurately credit them for driving revenue. This helps you allocate the correct budget to the channels and campaigns, adding real value to the business (e.g., social media marketing vs content marketing).
Example : Mastercard helps a digital bank acquire 10 million high-value customers
For example, Mastercard helped a digital bank in Latin America achieve sustainable growth beyond customer acquisition. The fintech company wanted to increase revenue through targeted acquisition and profitable engagement metrics.
Strategies included :
- A more targeted acquisition strategy for high-value customers
- Increasing avg. spend per customer
- Reducing acquisition cost
- Customer retention
As a result, Mastercard’s advisors helped this fintech company acquire 10 million new customers in two years. More importantly, they increased customer spending by 28% while reducing acquisition costs by 13%, creating a more sustainable and profitable growth model.
2. Use web and app analytics to remotivate users before they disengage
Engagement is the key to customer retention and lifetime value. To prevent valuable customers from disengaging, you need to intervene when they show early signs of losing interest, but they’re still receptive to your incentivisation tactics (promotions, rewards, milestones, etc.).
By integrating web and app analytics, you can identify churn patterns and pinpoint the sequences of actions that lead to disengaging. For example, you might determine that customers who only log in once a month, engage with one dashboard, or drop below a certain transaction rate are at high risk for churn.
Using a tool like Matomo for web and app analytics, you can detect these early signs of disengagement. Once you identify your churn risks, you can create triggers to automatically fire re-engagement campaigns. You can also use CRM and session data to personalize campaigns to directly address the cause of disengagement, e.g., valuable content or incentives to increase transaction rates.
Example : Dynamic Yield fintech re-engagement case study
In this Dynamic Yield case study, one leading fintech company uses customer spending patterns to identify those most likely to disengage. The company set up automated campaigns with personalised in-app messaging, offering time-bound incentives to increase transaction rates.
With fully automated re-engagement campaigns, this fintech company increased customer retention through valuable engagement and revenue-driving actions.
3. Identify the path your most valuable customers take
Why optimise web experiences for everyone when you can tailor the online journey for your most valuable customers ? Use customer segmentation to identify the shared interests and habits of your most valuable customers. You can learn a lot about customers based on where the pages they visit and the content they engage with before taking action.
Use these insights to optimise funnels that motivate prospects displaying the same customer behaviours as your most valuable customers.
Get 20-40% more data with Matomo
One of the biggest issues with Google Analytics and many similar tools is that they produce inaccurate data due to data sampling. Once you collect a certain amount of data, Google reports estimates instead of giving you complete, accurate insights.
This means you could be basing important business decisions on inaccurate data. Furthermore, when investors are nervous about the uncertainty surrounding fintech, the last thing they want is inaccurate data.
Matomo is the reliable, accurate alternative to Google Analytics that uses no data sampling whatsoever. You get 100% access to your web analytics data, so you can base every decision on reliable insights. With Matomo, you can access between 20% and 40% more data compared to Google Analytics.
With Matomo, you can confidently unlock the full picture of your marketing efforts and give potential investors insights they can trust.
Try Matomo for Free
Get the web insights you need, without compromising data accuracy.
4. Reduce onboarding dropouts with marketing automation
Onboarding dropouts kill your chance of getting any return on your customer acquisition cost. You also miss out on developing a long-term relationship with users who fail to complete the onboarding process – a hit on immediate ROI and, potentially, long-term profits.
The onboarding process also defines the first impression for customers and sets a precedent for their ongoing experience.
An engaging onboarding experience converts more potential customers into active users and sets them up for repeat engagement and valuable actions.
Example : Maxio reduces onboarding time by 30% with GUIDEcx
Onboarding optimisation specialists, GUIDEcx helped Maxio cut six weeks off their onboarding times – a 30% reduction.
With a shorter onboarding schedule, more customers are committing to close the deal during kick-off calls. Meanwhile, by increasing automated tasks by 20%, the company has unlocked a 40% increase in capacity, allowing it to handle more customers at any given time and multiplying its capacity to generate revenue.
5. Increase the value in TTFV with personalisation
Time to first value (TTFV) is a key metric for onboarding optimisation, but some actions are more valuable than others. By personalising the experience for new users, you can increase the value of their first action, increasing motivation to continue using your fintech product/service.
The onboarding process is an opportunity to learn more about new customers and deliver the most rewarding user experience for their particular needs.
Example : Betterment helps users put their money to work right away
Betterment has implemented a quick, personalised onboarding system instead of the typical email signup process. The app wants to help new customers put their money to work right away, optimising for the first transaction during onboarding itself.
It personalises the experience by prompting new users to choose their goals, set up the right account for them, and select the best portfolio to achieve their goals. They can complete their first investment within a matter of minutes and professional financial advice is only ever a click away.
Optimise account signups with Matomo
If you want to create and optimise a signup process like Betterment, you need an analytics system with a complete conversion rate optimisation (CRO) toolkit.
Matomo includes all the CRO features you need to optimise user experience and increase signups. With heatmaps, session recordings, form analytics, and A/B testing, you can make data-driven decisions with confidence.
Try Matomo for Free
Get the web insights you need, without compromising data accuracy.
6. Use gamification to drive product engagement
Gamification can create a more engaging experience and increase motivation for customers to continue using a product. The key is to reward valuable actions, engagement time, goal completions, and the small objectives that build up to bigger achievements.
Gamification is most effective when used to help individuals achieve goals they’ve set for themselves, rather than the goals of others (e.g., an employer). This helps explain why it’s so valuable to fintech experience and how to implement effective gamification into products and services.
Example : Credit Karma gamifies personal finance
Credit Karma helps users improve their credit and build their net worth, subtly gamifying the entire experience.
Users can set their financial goals and link all of their accounts to keep track of their assets in one place. The app helps users “see your wealth grow” with assets, debts, and investments all contributing to their next wealth as one easy-to-track figure.
7. Personalise loyalty programs for retention and CLV
Loyalty programs tap into similar psychology as gamification to motivate and reward engagement. Typically, the key difference is that – rather than earning rewards for themselves – you directly reward customers for their long-term loyalty.
That being said, you can implement elements of gamification and personalisation into loyalty programs, too.
Example : Bank of America’s Preferred Rewards
Bank of America’s Preferred Rewards program implements a tiered rewards system that rewards customers for their combined spending, saving, and borrowing activity.
The program incentivises all customer activity with the bank and amplifies the rewards for its most active customers. Customers can also set personal finance goals (e.g., saving for retirement) to see which rewards benefit them the most.
Conclusion
Fintech marketing needs to catch up with the new priorities of investors in 2024. The pre-pandemic buzz is over, and investors remain cautious as regulatory scrutiny intensifies, security breaches mount up, and the market limps back into recovery.
To win investor and consumer trust, fintech companies need to drop the growth-at-all-costs mindset and switch to a marketing philosophy of long-term profitability. This is what investors want in an unstable market, and it’s certainly what customers want from a company that handles their money.
Unlock the full picture of your marketing efforts with Matomo’s robust features and accurate reporting. Trusted by over 1 million websites, Matomo is chosen for its compliance, accuracy, and powerful features that drive actionable insights and improve decision-making.
Start your free 21-day trial now. No credit card required.
Syndiquer tout le site
