
Recherche avancée
Médias (1)
-
Bug de détection d’ogg
22 mars 2013, par
Mis à jour : Avril 2013
Langue : français
Type : Video
Autres articles (100)
-
Publier sur MédiaSpip
13 juin 2013Puis-je poster des contenus à partir d’une tablette Ipad ?
Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir -
Création définitive du canal
12 mars 2010, parLorsque votre demande est validée, vous pouvez alors procéder à la création proprement dite du canal. Chaque canal est un site à part entière placé sous votre responsabilité. Les administrateurs de la plateforme n’y ont aucun accès.
A la validation, vous recevez un email vous invitant donc à créer votre canal.
Pour ce faire il vous suffit de vous rendre à son adresse, dans notre exemple "http://votre_sous_domaine.mediaspip.net".
A ce moment là un mot de passe vous est demandé, il vous suffit d’y (...) -
Les tâches Cron régulières de la ferme
1er décembre 2010, parLa gestion de la ferme passe par l’exécution à intervalle régulier de plusieurs tâches répétitives dites Cron.
Le super Cron (gestion_mutu_super_cron)
Cette tâche, planifiée chaque minute, a pour simple effet d’appeler le Cron de l’ensemble des instances de la mutualisation régulièrement. Couplée avec un Cron système sur le site central de la mutualisation, cela permet de simplement générer des visites régulières sur les différents sites et éviter que les tâches des sites peu visités soient trop (...)
Sur d’autres sites (9123)
-
avcodec_find_decoder for FFMpeg 2.1 is not working with Android
18 mars 2014, par Fabien HenonI ported FFMpeg 2.1 to Android with NDK and I wrote a JNI function to initialize a video.
Here is the code of this C function :
JNIEXPORT int JNICALL Java_com_media_ffmpeg_FFMpeg_naInit(JNIEnv *pEnv, jobject pObj, jstring pfilename) {
gVideoFileName = (char *) (*pEnv)->GetStringUTFChars(pEnv, pfilename, NULL);
__android_log_print(ANDROID_LOG_INFO, TAG, "Init %s\n", gVideoFileName);
avcodec_register_all();
__android_log_print(ANDROID_LOG_INFO, TAG, "avcodec_register_all\n");
av_register_all();
__android_log_print(ANDROID_LOG_INFO, TAG, "av_register_all\n");
VideoState *vs;
__android_log_print(ANDROID_LOG_INFO, TAG, "VideoState var\n");
vs = malloc(sizeof (VideoState));
memset(vs, 0, sizeof(VideoState));
__android_log_print(ANDROID_LOG_INFO, TAG, "malloc\n");
gvs = vs;
__android_log_print(ANDROID_LOG_INFO, TAG, "VideoState\n");
//open the video file
avformat_open_input(&vs->pFormatCtx, gVideoFileName, NULL, NULL);
__android_log_print(ANDROID_LOG_INFO, TAG, "open_input\n");
//retrieve stream info
avformat_find_stream_info(vs->pFormatCtx, NULL);
__android_log_print(ANDROID_LOG_INFO, TAG, "find_stream_info\n");
//find the video stream
AVCodecContext *pcodecctx;
//find the first video stream
vs->videoStreamIdx = -1;
__android_log_print(ANDROID_LOG_INFO, TAG, "before loop\n");
AVCodec *pcodec;
vs->videoStreamIdx = av_find_best_stream(vs->pFormatCtx, AVMEDIA_TYPE_VIDEO, -1, -1, &pcodec, 0);
__android_log_print(ANDROID_LOG_INFO, TAG, "after loop. %d\n", vs->videoStreamIdx);
//get the decoder from the video stream
pcodecctx = vs->pFormatCtx->streams[vs->videoStreamIdx]->codec;
__android_log_print(ANDROID_LOG_INFO, TAG, "stream selected %d, %d\n", pcodecctx != NULL ? 1 : 0, pcodecctx->codec_id);
pcodec = avcodec_find_decoder(pcodecctx->codec_id);
__android_log_print(ANDROID_LOG_INFO, TAG, "find_decoder\n");
//open the codec
avcodec_open2(pcodecctx, pcodec, NULL);
__android_log_print(ANDROID_LOG_INFO, TAG, "open2\n");
return 0;
}When I execute this function from my Java code the log
find_decoder
(after the call to the functionavcodec_find_decoder
) is never displayed.Everything is correct : pointers have correct values and
pcodecctx->codec_id
has a value equal to 28.
But whenavcodec_find_decoder
there is nothing more, like a crash and I have no more log.Did I do something wrong when using and initializing FFMpeg ?
PS : before that instead of a call to
malloc
, thenmemset
I had a call toav_mallocz
but I also had a crash at this point, and replacing this call bymalloc
andmemset
fixed the crash.EDIT
I built
FFMpeg
using this script :#!/bin/bash
NDK=/Users/me/android-ndk
SYSROOT=$NDK/platforms/android-8/arch-arm/
TOOLCHAIN=$NDK/toolchains/arm-linux-androideabi-4.6/prebuilt/darwin-x86_64
function build_one
{
./configure \
--prefix=$PREFIX \
--disable-shared \
--enable-static \
--disable-doc \
--disable-ffmpeg \
--disable-ffplay \
--disable-ffprobe \
--disable-ffserver \
--disable-avdevice \
--disable-doc \
--disable-symver \
--cross-prefix=$TOOLCHAIN/bin/arm-linux-androideabi- \
--target-os=linux \
--arch=arm \
--enable-cross-compile \
--sysroot=$SYSROOT \
--extra-cflags="-Os -fpic $ADDI_CFLAGS" \
--extra-ldflags="$ADDI_LDFLAGS" \
$ADDITIONAL_CONFIGURE_FLAG
make clean
make
make install
}
CPU=arm
PREFIX=$(pwd)/android/$CPU
ADDI_CFLAGS="-marm"
build_oneEDIT 2
Here is the output for the configuration of the build of the library
Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk/usr/include/c++/4.2.1
Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk/usr/include/c++/4.2.1
install prefix /Users/fabienhenon/android-ndk/sources/ffmpeg/android/arm
source path .
C compiler /Users/fabienhenon/android-ndk/toolchains/arm-linux-androideabi-4.6/prebuilt/darwin-x86_64/bin/arm-linux-androideabi-gcc
C library bionic
host C compiler gcc
host C library
ARCH arm (armv5te)
big-endian no
runtime cpu detection yes
ARMv5TE enabled yes
ARMv6 enabled yes
ARMv6T2 enabled yes
VFP enabled yes
NEON enabled yes
THUMB enabled no
debug symbols yes
strip symbols yes
optimize for size no
optimizations yes
static yes
shared no
postprocessing support no
new filter support yes
network support yes
threading support pthreads
safe bitstream reader yes
SDL support no
opencl enabled no
libzvbi enabled no
texi2html enabled no
perl enabled yes
pod2man enabled yes
makeinfo enabled yes
External libraries:
zlib
Enabled decoders:
aac bmp iac
aac_latm bmv_audio idcin
aasc bmv_video idf
ac3 brender_pix iff_byterun1
adpcm_4xm c93 iff_ilbm
adpcm_adx cavs imc
adpcm_afc cdgraphics indeo2
adpcm_ct cdxl indeo3
adpcm_dtk cinepak indeo4
adpcm_ea cljr indeo5
adpcm_ea_maxis_xa cllc interplay_dpcm
adpcm_ea_r1 comfortnoise interplay_video
adpcm_ea_r2 cook jacosub
adpcm_ea_r3 cpia jpeg2000
adpcm_ea_xas cscd jpegls
adpcm_g722 cyuv jv
adpcm_g726 dca kgv1
adpcm_g726le dfa kmvc
adpcm_ima_amv dirac lagarith
adpcm_ima_apc dnxhd loco
adpcm_ima_dk3 dpx mace3
adpcm_ima_dk4 dsicinaudio mace6
adpcm_ima_ea_eacs dsicinvideo mdec
adpcm_ima_ea_sead dvbsub metasound
adpcm_ima_iss dvdsub microdvd
adpcm_ima_oki dvvideo mimic
adpcm_ima_qt dxa mjpeg
adpcm_ima_rad dxtory mjpegb
adpcm_ima_smjpeg eac3 mlp
adpcm_ima_wav eacmv mmvideo
adpcm_ima_ws eamad motionpixels
adpcm_ms eatgq movtext
adpcm_sbpro_2 eatgv mp1
adpcm_sbpro_3 eatqi mp1float
adpcm_sbpro_4 eightbps mp2
adpcm_swf eightsvx_exp mp2float
adpcm_thp eightsvx_fib mp3
adpcm_xa escape124 mp3adu
adpcm_yamaha escape130 mp3adufloat
aic evrc mp3float
alac exr mp3on4
als ffv1 mp3on4float
amrnb ffvhuff mpc7
amrwb ffwavesynth mpc8
amv flac mpeg1video
anm flashsv mpeg2video
ansi flashsv2 mpeg4
ape flic mpegvideo
ass flv mpl2
asv1 fourxm msa1
asv2 fraps msmpeg4v1
atrac1 frwu msmpeg4v2
atrac3 g2m msmpeg4v3
aura g723_1 msrle
aura2 g729 mss1
avrn gif mss2
avrp gsm msvideo1
avs gsm_ms mszh
avui h261 mts2
ayuv h263 mvc1
bethsoftvid h263i mvc2
bfi h263p mxpeg
bink h264 nellymoser
binkaudio_dct hevc nuv
binkaudio_rdft hnm4_video paf_audio
bintext huffyuv paf_video
pam realtext v308
pbm rl2 v408
pcm_alaw roq v410
pcm_bluray roq_dpcm vb
pcm_dvd rpza vble
pcm_f32be rv10 vc1
pcm_f32le rv20 vc1image
pcm_f64be rv30 vcr1
pcm_f64le rv40 vima
pcm_lxf s302m vmdaudio
pcm_mulaw sami vmdvideo
pcm_s16be sanm vmnc
pcm_s16be_planar sgi vorbis
pcm_s16le sgirle vp3
pcm_s16le_planar shorten vp5
pcm_s24be sipr vp6
pcm_s24daud smackaud vp6a
pcm_s24le smacker vp6f
pcm_s24le_planar smc vp8
pcm_s32be smvjpeg vp9
pcm_s32le snow vplayer
pcm_s32le_planar sol_dpcm vqa
pcm_s8 sonic wavpack
pcm_s8_planar sp5x webp
pcm_u16be srt webvtt
pcm_u16le ssa wmalossless
pcm_u24be subrip wmapro
pcm_u24le subviewer wmav1
pcm_u32be subviewer1 wmav2
pcm_u32le sunrast wmavoice
pcm_u8 svq1 wmv1
pcm_zork svq3 wmv2
pcx tak wmv3
pgm targa wmv3image
pgmyuv targa_y216 wnv1
pgssub text ws_snd1
pictor theora xan_dpcm
pjs thp xan_wc3
png tiertexseqvideo xan_wc4
ppm tiff xbin
prores tmv xbm
prores_lgpl truehd xface
ptx truemotion1 xl
qcelp truemotion2 xsub
qdm2 truespeech xwd
qdraw tscc y41p
qpeg tscc2 yop
qtrle tta yuv4
r10k twinvq zero12v
r210 txd zerocodec
ra_144 ulti zlib
ra_288 utvideo zmbv
ralf v210
rawvideo v210x
Enabled encoders:
a64multi ljpeg prores
a64multi5 mjpeg prores_aw
aac movtext prores_ks
ac3 mp2 qtrle
ac3_fixed mp2fixed r10k
adpcm_adx mpeg1video r210
adpcm_g722 mpeg2video ra_144
adpcm_g726 mpeg4 rawvideo
adpcm_ima_qt msmpeg4v2 roq
adpcm_ima_wav msmpeg4v3 roq_dpcm
adpcm_ms msvideo1 rv10
adpcm_swf nellymoser rv20
adpcm_yamaha pam s302m
alac pbm sgi
amv pcm_alaw snow
ass pcm_f32be sonic
asv1 pcm_f32le sonic_ls
asv2 pcm_f64be srt
avrp pcm_f64le ssa
avui pcm_mulaw subrip
ayuv pcm_s16be sunrast
bmp pcm_s16be_planar svq1
cljr pcm_s16le targa
comfortnoise pcm_s16le_planar tiff
dca pcm_s24be tta
dnxhd pcm_s24daud utvideo
dpx pcm_s24le v210
dvbsub pcm_s24le_planar v308
dvdsub pcm_s32be v408
dvvideo pcm_s32le v410
eac3 pcm_s32le_planar vorbis
ffv1 pcm_s8 wavpack
ffvhuff pcm_s8_planar wmav1
flac pcm_u16be wmav2
flashsv pcm_u16le wmv1
flashsv2 pcm_u24be wmv2
flv pcm_u24le xbm
g723_1 pcm_u32be xface
gif pcm_u32le xsub
h261 pcm_u8 xwd
h263 pcx y41p
h263p pgm yuv4
huffyuv pgmyuv zlib
jpeg2000 png zmbv
jpegls ppm
Enabled hwaccels:
Enabled parsers:
aac dvd_nav mpegvideo
aac_latm dvdsub png
ac3 flac pnm
adx gsm rv30
bmp h261 rv40
cavsvideo h263 tak
cook h264 vc1
dca hevc vorbis
dirac mjpeg vp3
dnxhd mlp vp8
dpx mpeg4video vp9
dvbsub mpegaudio
Enabled demuxers:
aac hevc pcm_s32le
ac3 hls pcm_s8
act hnm pcm_u16be
adf ico pcm_u16le
adp idcin pcm_u24be
adx idf pcm_u24le
aea iff pcm_u32be
afc ilbc pcm_u32le
aiff image2 pcm_u8
amr image2pipe pjs
anm ingenient pmp
apc ipmovie pva
ape ircam pvf
aqtitle iss qcp
asf iv8 r3d
ass ivf rawvideo
ast jacosub realtext
au jv redspark
avi latm rl2
avr lmlm4 rm
avs loas roq
bethsoftvid lvf rpl
bfi lxf rsd
bink m4v rso
bintext matroska rtp
bit mgsts rtsp
bmv microdvd sami
boa mjpeg sap
brstm mlp sbg
c93 mm sdp
caf mmf segafilm
cavsvideo mov shorten
cdg mp3 siff
cdxl mpc smacker
concat mpc8 smjpeg
data mpegps smush
daud mpegts sol
dfa mpegtsraw sox
dirac mpegvideo spdif
dnxhd mpl2 srt
dsicin mpsub str
dts msnwc_tcp subviewer
dtshd mtv subviewer1
dv mv swf
dxa mvi tak
ea mxf tedcaptions
ea_cdata mxg thp
eac3 nc tiertexseq
epaf nistsphere tmv
ffm nsv truehd
ffmetadata nut tta
filmstrip nuv tty
flac ogg txd
flic oma vc1
flv paf vc1t
fourxm pcm_alaw vivo
frm pcm_f32be vmd
g722 pcm_f32le vobsub
g723_1 pcm_f64be voc
g729 pcm_f64le vplayer
gif pcm_mulaw vqf
gsm pcm_s16be w64
gxf pcm_s16le wav
h261 pcm_s24be wc3
h263 pcm_s24le webvtt
h264 pcm_s32be wsaud
wsvqa xa xwma
wtv xbin yop
wv xmv yuv4mpegpipe
Enabled muxers:
a64 image2pipe pcm_s24be
ac3 ipod pcm_s24le
adts ircam pcm_s32be
adx ismv pcm_s32le
aiff ivf pcm_s8
amr jacosub pcm_u16be
asf latm pcm_u16le
asf_stream m4v pcm_u24be
ass matroska pcm_u24le
ast matroska_audio pcm_u32be
au md5 pcm_u32le
avi microdvd pcm_u8
avm2 mjpeg psp
bit mkvtimestamp_v2 rawvideo
caf mlp rm
cavsvideo mmf roq
crc mov rso
data mp2 rtp
daud mp3 rtsp
dirac mp4 sap
dnxhd mpeg1system segment
dts mpeg1vcd smjpeg
dv mpeg1video smoothstreaming
eac3 mpeg2dvd sox
f4v mpeg2svcd spdif
ffm mpeg2video speex
ffmetadata mpeg2vob srt
filmstrip mpegts stream_segment
flac mpjpeg swf
flv mxf tee
framecrc mxf_d10 tg2
framemd5 null tgp
g722 nut truehd
g723_1 ogg vc1
gif oma vc1t
gxf opus voc
h261 pcm_alaw w64
h263 pcm_f32be wav
h264 pcm_f32le webm
hds pcm_f64be webvtt
hls pcm_f64le wtv
ico pcm_mulaw wv
ilbc pcm_s16be yuv4mpegpipe
image2 pcm_s16le
Enabled protocols:
cache hls rtmpt
concat http rtp
crypto httpproxy srtp
data md5 tcp
ffrtmphttp mmsh udp
file mmst unix
ftp pipe
gopher rtmp
Enabled filters:
aconvert colorchannelmixer null
adelay compand nullsink
aecho concat nullsrc
aeval copy overlay
aevalsrc crop pad
afade curves pan
aformat dctdnoiz perms
ainterleave decimate pixdesctest
allpass deshake psnr
alphaextract drawbox removelogo
alphamerge drawgrid replaygain
amerge earwax rgbtestsrc
amix edgedetect rotate
amovie elbg scale
anull equalizer select
anullsink extractplanes sendcmd
anullsrc fade separatefields
apad field setdar
aperms fieldmatch setfield
aphaser fieldorder setpts
aresample format setsar
aselect fps settb
asendcmd framestep showinfo
asetnsamples gradfun showspectrum
asetpts haldclut showwaves
asetrate haldclutsrc silencedetect
asettb hflip sine
ashowinfo highpass smptebars
asplit histogram smptehdbars
astats hue split
astreamsync idet swapuv
atempo il telecine
atrim interleave testsrc
avectorscope join thumbnail
bandpass life tile
bandreject lowpass transpose
bass lut treble
bbox lut3d trim
biquad lutrgb unsharp
blackdetect lutyuv vflip
blend mandelbrot vignette
cellauto mergeplanes volume
channelmap movie volumedetect
channelsplit negate w3fdif
color noformat
colorbalance noise
Enabled bsfs:
aac_adtstoasc imx_dump_header mp3_header_decompress
chomp mjpeg2jpeg noise
dump_extradata mjpega_dump_header remove_extradata
h264_mp4toannexb mov2textsub text2movsub
Enabled indevs:
dv1394 lavfi
fbdev v4l2
Enabled outdevs:
fbdev v4l2
License: LGPL version 2.1 or later -
Making Your First-Party Data Work for You and Your Customers
11 mars, par Alex CarmonaAt last count, 162 countries had enacted data privacy policies of one kind or another. These laws or regulations, without exception, intend to eliminate the use of third-party data. That puts marketing under pressure because third-party data has been the foundation of online marketing efforts since the dawn of the Internet.
Marketers need to future-proof their operations by switching to first-party data. This will require considerable adjustment to systems and processes, but the reward will be effective marketing campaigns that satisfy privacy compliance requirements and bring the business closer to its customers.
To do that, you’ll need a coherent first-party data strategy. That’s what this article is all about. We’ll explain the different types of personal data and discuss how to use them in marketing without compromising or breaching data privacy regulations. We’ll also discuss how to build that strategy in your business.
So, let’s dive in.
The different data types
There are four distinct types of personal data used in marketing, each subject to different data privacy regulations.
Before getting into the different types, it’s essential to understand that all four may comprise one or more of the following :
Identifying data Name, email address, phone number, etc. Behavioural data Website activity, app usage, wishlist content, purchase history, etc. Transactional data Orders, payments, subscription details, etc. Account data Communication preferences, product interests, wish lists, etc. Demographic data Age, gender, income level, education, etc. Geographic Data Location-based information, such as zip codes or regional preferences. Psychographic Data Interests, hobbies and lifestyle preferences. First-party data
When businesses communicate directly with customers, any data they exchange is first-party. It doesn’t matter how the interaction occurs : on the telephone, a website, a chat session, or even in person.
Of course, the parties involved aren’t necessarily individuals. They may be companies, but people within those businesses will probably share at least some of the data with colleagues. That’s fine, so long as the data :
- Remains confidential between the original two parties involved, and
- It is handled and stored following applicable data privacy regulations.
The core characteristic of first-party data is that it’s collected directly from customer interactions. This makes it reliable, accurate and inherently compliant with privacy regulations — assuming the collecting party complies with data privacy laws.
A great example of first-party data use is in banking. Data collected from customer interactions is used to provide personalised services, detect fraud, assess credit risk and improve customer retention.
Zero-party data
There’s also a subset of first-party data, sometimes called zero-party data. It’s what users intentionally and proactively share with a business. It can be preferences, intentions, personal information, survey responses, support tickets, etc.
What makes it different is that the collection of this data depends heavily on the user’s trust. Transparency is a critical factor, too ; visitors expect to be informed about how you’ll use their data. Consumers also have the right to withdraw permission to use all or some of their information at any time.
Second-party data
This data is acquired from a separate organisation that collects it firsthand. Second-party data is someone else’s first-party data that’s later shared with or sold to other businesses. The key here is that whoever owns that data must give explicit consent and be informed of who businesses share their data with.
A good example is the cooperation between hotel chains, car rental companies, and airlines. They share joint customers’ flight data, hotel reservations, and car rental bookings, much like travel agents did before the internet undermined that business model.
Third-party data
This type of data is the arch-enemy of lawmakers and regulators trying to protect the personal data of citizens and residents in their country. It’s information collected by entities that have no direct relationship with the individuals whose data it is.
Third-party data is usually gathered, aggregated, and sold by data brokers or companies, often by using third-party cookies on popular websites. It’s an entire business model — these third-party brokers sell data for marketing, analytics, or research purposes.
Most of the time, third-party data subjects are unaware that their data has been gathered and sold. Hence the need for strong data privacy regulations.
Benefits of a first-party data strategy
First-party data is reliable, accurate, and ethically sourced. It’s an essential part of any modern digital marketing strategy.
More personalised experiences
The most important application of first-party data is customising and personalising customers’ interactions based on real behaviours and preferences. Personalised experiences aren’t restricted to websites and can extend to all customer communication.
The result is company communications and marketing messages are far more relevant to customers. It allows businesses to engage more meaningfully with them, building trust and strengthening customer relationships. Inevitably, this also results in stronger customer loyalty and better customer retention.
Greater understanding of customers
Because first-party data is more accurate and reliable, it can be used to derive valuable insights into customer needs and wants. When all the disparate first-party data points are centralised and organised, it’s possible to uncover trends and patterns in customer behaviour that might not be apparent using other data.
This helps businesses predict and respond to customer needs. It also allows marketing teams to be more deliberate when segmenting customers and prospects into like-minded groups. The data can also be used to create more precise personas for future campaigns or reveal how likely a customer would be to purchase in response to a campaign.
Build trust with customers
First-party data is unique to a business and originates from interactions with customers. It’s also data collected with consent and is “owned” by the company — if you can ever own someone else’s data. If treated like the precious resource, it can help businesses build trust with customers.
However, developing that trust requires a transparent, step-by-step approach. This gradually strengthens relationships to the point where customers are more comfortable sharing the information they’re asked for.
However, while building trust is a long and sometimes arduous process, it can be lost in an instant. That’s why first-party data must be protected like the Crown Jewels.
Components of a first-party data strategy
Security is essential to any first-party data strategy, and for good reason. As Gartner puts it, a business must find the optimal balance between business outcomes and data risk mitigation. Once security is baked in, attention can turn to the different aspects of the strategy.
Data collection
There are many ways to collect first-party data ethically, within the law and while complying with data privacy regulations, such as Europe’s General Data Protection Regulation (GDPR). Potential sources include :
Website activity forms and surveys, behavioural tracking, cookies, tracking pixels and chatbots Mobile app interactions in-app analytics, push notifications and in-app forms Email marketing newsletter sign-ups, email engagement tracking, promotions, polls and surveys Events registrations, post-event surveys and virtual event analytics Social media interaction polls and surveys, direct messages and social media analytics Previous transactions purchase history, loyalty programmes and e-receipts Customer service call centre data, live chat, chatbots and feedback forms In-person interactions in-store purchases, customer feedback and Wi-Fi sign-ins Gated content whitepapers, ebooks, podcasts, webinars and video downloads Interactive content quizzes, assessments, calculators and free tools CRM platforms customer profiles and sales data Consent management privacy policies, consent forms, preference setting Consent management
It may be the final item on the list above, but it’s also a key requirement of many data privacy laws and regulations. For example, the GDPR is very clear about consent : “Processing personal data is generally prohibited, unless it is expressly allowed by law, or the data subject has consented to the processing.”
For that reason, your first-party data strategy must incorporate various transparent consent mechanisms, such as cookie banners and opt-in forms. Crucially, you must provide customers with a mechanism to manage their preferences and revoke that consent easily if they wish to.
Data management
Effective first-party data management, mainly its security and storage, is critical. Most data privacy regimes restrict the transfer of personal data to other jurisdictions and even prohibit it in some instances. Many even specify where residents’ data must be stored.
Consider this cautionary tale : The single biggest fine levied for data privacy infringement so far was €1.2 billion. The Irish Data Protection Commission imposed a massive fine on Meta for transferring EU users’ data to the US without adequate data protection mechanisms.
Data security is critical. If first-party data is compromised, it becomes third-party data, and any customer trust developed with the business will evaporate. To add insult to injury, data regulators could come knocking. That’s why the trend is to use encryption and anonymisation techniques alongside standard access controls.
Once security is assured, the focus is on data management. Many businesses use a Customer Data Platform. This software gathers, combines and manages data from many sources to create a complete and central customer profile. Modern CRM systems can also do that job. AI tools could help find patterns and study them. But the most important thing is to keep databases clean and well-organised to make it easier to use and avoid data silos.
Data activation
Once first-party data has been collected and analysed, it needs to be activated, which means a business needs to use it for the intended purpose. This is the implementation phase where a well-constructed first-party strategy pays off.
The activation stage is where businesses use the intelligence they gather to :
- Personalise website and app experiences
- Adapt marketing campaigns
- Improve conversion rates
- Match stated preferences
- Cater to observed behaviours
- Customise recommendations based on purchase history
- Create segmented email campaigns
- Improve retargeting efforts
- Develop more impactful content
Measurement and optimisation
Because first-party data is collected directly from customers or prospects, it’s far more relevant, reliable, and specific. Your analytics and campaign tracking will be more accurate. This gives you direct and actionable insights into your audience’s behaviour, empowering you to optimise your strategies and achieve better results.
The same goes for your collection and activation efforts. An advanced web analytics platform like Matomo lets you identify key user behaviour and optimise your tracking. Heatmaps, marketing attribution tools, user behaviour analytics and custom reports allow you to segment audiences for better traction (and collect even more first-party data).
How to build a first-party data strategy
There are five important and sequential steps to building a first-party data strategy. But this isn’t a one-time process. It must be revisited regularly as operating and regulatory environments change. There are five steps :
- Audit existing data
Chances are that customers already freely provide a lot of first-party data in the normal course of business. The first step is to locate this data, and the easiest way to do that is by mapping the customer journey. This identifies all the touchpoints where first-party data might be found.
- Define objectives
Then, it’s time to step back and figure out the goals of the first-party data strategy. Consider what you’re trying to achieve. For example :
- Reduce churn
- Expand an existing loyalty programme
- Unload excess inventory
- Improve customer experiences
Whatever the objectives are, they should be clear and measurable.
- Implement tools and technology
The first two steps point to data gaps. Now, the focus turns to ethical web analytics with a tool like Matomo.
To further comply with data privacy regulations, it may also be appropriate to implement a Consent Management Platform (CMP) to help manage preferences and consent choices.
- Build trust with transparency
With the tools in place, it’s time to engage customers. To build trust, keep them informed about how their data is used and remind them of their right to withdraw their consent.
Transparency is crucial in such engagement, as outlined in the 7 GDPR principles.
- Continuously improve
Rinse and repeat. The one constant in business and life is change. As things change, they expose weaknesses or flaws in the logic behind systems and processes. That’s why a first-party data strategy needs to be continually reviewed, updated, and revised. It must adapt to changing trends, markets, regulations, etc.
Tools that can help
Looking back at the different types of data, it’s clear that some are harder and more bothersome to get than others. But capturing behaviours and interactions can be easy — especially if you use tools that follow data privacy rules.
But here’s a tip. Google Analytics 4 isn’t compliant by default, especially not with Europe’s GDPR. It may also struggle to comply with some of the newer data privacy regulations planned by different US states and other countries.
Matomo Analytics is compliant with the GDPR and many other data privacy regulations worldwide. Because it’s open source, it can be integrated with any consent manager.
Get started today by trying Matomo for free for 21 days,
no credit card required. -
Six Best Amplitude Alternatives
10 décembre 2024, par Daniel Crough