Recherche avancée

Sur d’autres sites (6076)

• Integrating FFMpeg in Native Android Application with C++ results in bunch of errors [closed]

  13 décembre 2024, par BraveEvidence

  I need to integrate ffmpeg in my android app, i don't want to usee ffmpegkit as that is not properly maintained, i cloned ffmpeg-android-maker and then ran ./ffmpeg-android-maker.sh it created build folder and output folder,
The output folder looks like this

  


  

  


  I have created a kotlin android project using android studio, so i have written all the code to pick the video and i have the video uri with me in kotlin, i also added a C++ module with help of Android studio and it did all the configuration in build.gradle and also created CMake file for me.

  


  For now I just want to concentrate on building the android project so forget about writing any C++ code, I then created jniLibs in main folder and in jniLibs I copied arm64-v8a,armeabi-v7a, x86,x86_64 from the output folder of ffmpeg-android-maker and then I want to cpp folder of my android project which is also in main folder and in cpp folder I created include folder and copied libavcodec, libavdevice, libavfilter etc then I updated my CmakeLists.txt to following

  


  cmake_minimum_required(VERSION 3.22.1)

project("myandroidapp")

#set(FFMPEG_LIBS_DIR ${CMAKE_SOURCE_DIR}/src/main/jniLibs)

include_directories(${CMAKE_SOURCE_DIR}/src/main/cpp/include)

set_target_properties(${CMAKE_PROJECT_NAME} PROPERTIES
        LIBRARY_OUTPUT_DIRECTORY ${CMAKE_SOURCE_DIR}/src/main/jniLibs/${ANDROID_ABI}
)

add_library(${CMAKE_PROJECT_NAME} SHARED
    # List C/C++ source files with relative paths to this CMakeLists.txt.
    myandroidapp.cpp)


# Specifies libraries CMake should link to your target library. You
# can link libraries from various origins, such as libraries defined in this
# build script, prebuilt third-party libraries, or Android system libraries.
target_link_libraries(${CMAKE_PROJECT_NAME}
    # List libraries link to the target library
    android
    log
        avcodec
        avdevice
        avfilter
        avformat
        avutil
        swresample
        swscale)


  


  Then in build.gradle I did following

  


  externalNativeBuild {
        cmake {
            path = file("src/main/cpp/CMakeLists.txt")
            version = "3.22.1"
        }
    }

    sourceSets {
        getByName("main") {
            jniLibs.srcDirs("src/main/jniLibs")
        }
    }

    packaging {
        jniLibs.pickFirsts.add("lib/arm64-v8a/libavcodec.so")
        jniLibs.pickFirsts.add("lib/arm64-v8a/libavformat.so")
        jniLibs.pickFirsts.add("lib/arm64-v8a/libavutil.so")
        jniLibs.pickFirsts.add("lib/arm64-v8a/libswscale.so")
        jniLibs.pickFirsts.add("lib/armeabi-v7a/libavcodec.so")
        jniLibs.pickFirsts.add("lib/armeabi-v7a/libavformat.so")
        jniLibs.pickFirsts.add("lib/armeabi-v7a/libavutil.so")
        jniLibs.pickFirsts.add("lib/armeabi-v7a/libswscale.so")
        jniLibs.pickFirsts.add("lib/x86/libavcodec.so")
        jniLibs.pickFirsts.add("lib/x86/libavformat.so")
        jniLibs.pickFirsts.add("lib/x86/libavutil.so")
        jniLibs.pickFirsts.add("lib/x86/libswscale.so")
        jniLibs.pickFirsts.add("lib/x86_64/libavcodec.so")
        jniLibs.pickFirsts.add("lib/x86_64/libavformat.so")
        jniLibs.pickFirsts.add("lib/x86_64/libavutil.so")
        jniLibs.pickFirsts.add("lib/x86_64/libswscale.so")
    }


  


  when I try to build my project I get following error

  


  [CXX1429] error when building with cmake using /Users/transformhub/Downloads/mycam/ffmpeg/MyAndroidapp/app/src/main/cpp/CMakeLists.txt: -- Configuring incomplete, errors occurred!
See also "/Users/transformhub/Downloads/mycam/ffmpeg/MyAndroidapp/app/.cxx/Debug/406wr1e2/arm64-v8a/CMakeFiles/CMakeOutput.log".

C++ build system [configure] failed while executing:
    /Users/transformhub/Library/Android/sdk/cmake/3.22.1/bin/cmake \
      -H/Users/transformhub/Downloads/mycam/ffmpeg/MyAndroidapp/app/src/main/cpp \
      -DCMAKE_SYSTEM_NAME=Android \
      -DCMAKE_EXPORT_COMPILE_COMMANDS=ON \
      -DCMAKE_SYSTEM_VERSION=24 \
      -DANDROID_PLATFORM=android-24 \
      -DANDROID_ABI=arm64-v8a \
      -DCMAKE_ANDROID_ARCH_ABI=arm64-v8a \
      -DANDROID_NDK=/Users/transformhub/Library/Android/sdk/ndk/26.1.10909125 \
      -DCMAKE_ANDROID_NDK=/Users/transformhub/Library/Android/sdk/ndk/26.1.10909125 \
      -DCMAKE_TOOLCHAIN_FILE=/Users/transformhub/Library/Android/sdk/ndk/26.1.10909125/build/cmake/android.toolchain.cmake \
      -DCMAKE_MAKE_PROGRAM=/Users/transformhub/Library/Android/sdk/cmake/3.22.1/bin/ninja \
      -DCMAKE_LIBRARY_OUTPUT_DIRECTORY=/Users/transformhub/Downloads/mycam/ffmpeg/MyAndroidapp/app/build/intermediates/cxx/Debug/406wr1e2/obj/arm64-v8a \
      -DCMAKE_RUNTIME_OUTPUT_DIRECTORY=/Users/transformhub/Downloads/mycam/ffmpeg/MyAndroidapp/app/build/intermediates/cxx/Debug/406wr1e2/obj/arm64-v8a \
      -DCMAKE_BUILD_TYPE=Debug \
      -B/Users/transformhub/Downloads/mycam/ffmpeg/MyAndroidapp/app/.cxx/Debug/406wr1e2/arm64-v8a \
      -GNinja
  from /Users/transformhub/Downloads/mycam/ffmpeg/MyAndroidapp/app
CMake Error at CMakeLists.txt:15 (set_target_properties):
  set_target_properties Can not find target to add properties to:
  myandroidapp : com.android.ide.common.process.ProcessException: -- Configuring incomplete, errors occurred!
See also "/Users/transformhub/Downloads/mycam/ffmpeg/MyAndroidapp/app/.cxx/Debug/406wr1e2/arm64-v8a/CMakeFiles/CMakeOutput.log".

C++ build system [configure] failed while executing:
    /Users/transformhub/Library/Android/sdk/cmake/3.22.1/bin/cmake \
      -H/Users/transformhub/Downloads/mycam/ffmpeg/MyAndroidapp/app/src/main/cpp \
      -DCMAKE_SYSTEM_NAME=Android \
      -DCMAKE_EXPORT_COMPILE_COMMANDS=ON \
      -DCMAKE_SYSTEM_VERSION=24 \
      -DANDROID_PLATFORM=android-24 \
      -DANDROID_ABI=arm64-v8a \
      -DCMAKE_ANDROID_ARCH_ABI=arm64-v8a \
      -DANDROID_NDK=/Users/transformhub/Library/Android/sdk/ndk/26.1.10909125 \
      -DCMAKE_ANDROID_NDK=/Users/transformhub/Library/Android/sdk/ndk/26.1.10909125 \
      -DCMAKE_TOOLCHAIN_FILE=/Users/transformhub/Library/Android/sdk/ndk/26.1.10909125/build/cmake/android.toolchain.cmake \
      -DCMAKE_MAKE_PROGRAM=/Users/transformhub/Library/Android/sdk/cmake/3.22.1/bin/ninja \
      -DCMAKE_LIBRARY_OUTPUT_DIRECTORY=/Users/transformhub/Downloads/mycam/ffmpeg/MyAndroidapp/app/build/intermediates/cxx/Debug/406wr1e2/obj/arm64-v8a \
      -DCMAKE_RUNTIME_OUTPUT_DIRECTORY=/Users/transformhub/Downloads/mycam/ffmpeg/MyAndroidapp/app/build/intermediates/cxx/Debug/406wr1e2/obj/arm64-v8a \
      -DCMAKE_BUILD_TYPE=Debug \
      -B/Users/transformhub/Downloads/mycam/ffmpeg/MyAndroidapp/app/.cxx/Debug/406wr1e2/arm64-v8a \
      -GNinja
  from /Users/transformhub/Downloads/mycam/ffmpeg/MyAndroidapp/app
CMake Error at CMakeLists.txt:15 (set_target_properties):
  set_target_properties Can not find target to add properties to:
  myandroidapp
    at com.android.build.gradle.internal.cxx.process.ExecuteProcessKt.execute(ExecuteProcess.kt:288)
    at com.android.build.gradle.internal.cxx.process.ExecuteProcessKt$executeProcess$1.invoke(ExecuteProcess.kt:108)
    at com.android.build.gradle.internal.cxx.process.ExecuteProcessKt$executeProcess$1.invoke(ExecuteProcess.kt:106)
    at com.android.build.gradle.internal.cxx.timing.TimingEnvironmentKt.time(TimingEnvironment.kt:32)
    at com.android.build.gradle.internal.cxx.process.ExecuteProcessKt.executeProcess(ExecuteProcess.kt:106)
    at com.android.build.gradle.internal.cxx.process.ExecuteProcessKt.executeProcess$default(ExecuteProcess.kt:85)
    at com.android.build.gradle.tasks.CmakeQueryMetadataGenerator.executeProcess(CmakeFileApiMetadataGenerator.kt:59)
    at com.android.build.gradle.tasks.ExternalNativeJsonGenerator$configureOneAbi$1$1$3.invoke(ExternalNativeJsonGenerator.kt:247)
    at com.android.build.gradle.tasks.ExternalNativeJsonGenerator$configureOneAbi$1$1$3.invoke(ExternalNativeJsonGenerator.kt:247)
    at com.android.build.gradle.internal.cxx.timing.TimingEnvironmentKt.time(TimingEnvironment.kt:32)
    at com.android.build.gradle.tasks.ExternalNativeJsonGenerator.configureOneAbi(ExternalNativeJsonGenerator.kt:247)
    at com.android.build.gradle.tasks.ExternalNativeJsonGenerator.configure(ExternalNativeJsonGenerator.kt:113)
    at com.android.build.gradle.tasks.ExternalNativeBuildJsonTask.doTaskAction(ExternalNativeBuildJsonTask.kt:89)
    at com.android.build.gradle.internal.tasks.UnsafeOutputsTask$taskAction$$inlined$recordTaskAction$1.invoke(BaseTask.kt:66)
    at com.android.build.gradle.internal.tasks.Blocks.recordSpan(Blocks.java:51)
    at com.android.build.gradle.internal.tasks.UnsafeOutputsTask.taskAction(UnsafeOutputsTask.kt:81)
    at jdk.internal.reflect.GeneratedMethodAccessor172.invoke(Unknown Source)
    at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.base/java.lang.reflect.Method.invoke(Unknown Source)
    at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:125)
    at org.gradle.api.internal.project.taskfactory.StandardTaskAction.doExecute(StandardTaskAction.java:58)
    at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:51)
    at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:29)
    at org.gradle.api.internal.tasks.execution.TaskExecution$3.run(TaskExecution.java:244)
    at org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:29)
    at org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:26)
    at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:66)
    at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:59)
    at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:157)
    at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:59)
    at org.gradle.internal.operations.DefaultBuildOperationRunner.run(DefaultBuildOperationRunner.java:47)
    at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:68)
    at org.gradle.api.internal.tasks.execution.TaskExecution.executeAction(TaskExecution.java:229)
    at org.gradle.api.internal.tasks.execution.TaskExecution.executeActions(TaskExecution.java:212)
    at org.gradle.api.internal.tasks.execution.TaskExecution.executeWithPreviousOutputFiles(TaskExecution.java:195)
    at org.gradle.api.internal.tasks.execution.TaskExecution.execute(TaskExecution.java:162)
    at org.gradle.internal.execution.steps.ExecuteStep.executeInternal(ExecuteStep.java:105)
    at org.gradle.internal.execution.steps.ExecuteStep.access$000(ExecuteStep.java:44)
    at org.gradle.internal.execution.steps.ExecuteStep$1.call(ExecuteStep.java:59)
    at org.gradle.internal.execution.steps.ExecuteStep$1.call(ExecuteStep.java:56)
    at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:200)
    at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:195)
    at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:66)
    at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:59)
    at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:157)
    at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:59)
    at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:53)
    at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:73)
    at org.gradle.internal.execution.steps.ExecuteStep.execute(ExecuteStep.java:56)
    at org.gradle.internal.execution.steps.ExecuteStep.execute(ExecuteStep.java:44)
    at org.gradle.internal.execution.steps.CancelExecutionStep.execute(CancelExecutionStep.java:41)
    at org.gradle.internal.execution.steps.TimeoutStep.executeWithoutTimeout(TimeoutStep.java:74)
    at org.gradle.internal.execution.steps.TimeoutStep.execute(TimeoutStep.java:55)
    at org.gradle.internal.execution.steps.PreCreateOutputParentsStep.execute(PreCreateOutputParentsStep.java:50)
    at org.gradle.internal.execution.steps.PreCreateOutputParentsStep.execute(PreCreateOutputParentsStep.java:28)
    at org.gradle.internal.execution.steps.RemovePreviousOutputsStep.execute(RemovePreviousOutputsStep.java:67)
    at org.gradle.internal.execution.steps.RemovePreviousOutputsStep.execute(RemovePreviousOutputsStep.java:37)
    at org.gradle.internal.execution.steps.BroadcastChangingOutputsStep.execute(BroadcastChangingOutputsStep.java:61)
    at org.gradle.internal.execution.steps.BroadcastChangingOutputsStep.execute(BroadcastChangingOutputsStep.java:26)
    at org.gradle.internal.execution.steps.CaptureOutputsAfterExecutionStep.execute(CaptureOutputsAfterExecutionStep.java:67)
    at org.gradle.internal.execution.steps.CaptureOutputsAfterExecutionStep.execute(CaptureOutputsAfterExecutionStep.java:45)
    at org.gradle.internal.execution.steps.ResolveInputChangesStep.execute(ResolveInputChangesStep.java:40)
    at org.gradle.internal.execution.steps.ResolveInputChangesStep.execute(ResolveInputChangesStep.java:29)
    at org.gradle.internal.execution.steps.BuildCacheStep.executeWithoutCache(BuildCacheStep.java:189)
    at org.gradle.internal.execution.steps.BuildCacheStep.lambda$execute$1(BuildCacheStep.java:75)
    at org.gradle.internal.Either$Right.fold(Either.java:175)
    at org.gradle.internal.execution.caching.CachingState.fold(CachingState.java:62)
    at org.gradle.internal.execution.steps.BuildCacheStep.execute(BuildCacheStep.java:73)
    at org.gradle.internal.execution.steps.BuildCacheStep.execute(BuildCacheStep.java:48)
    at org.gradle.internal.execution.steps.StoreExecutionStateStep.execute(StoreExecutionStateStep.java:46)
    at org.gradle.internal.execution.steps.StoreExecutionStateStep.execute(StoreExecutionStateStep.java:35)
    at org.gradle.internal.execution.steps.SkipUpToDateStep.executeBecause(SkipUpToDateStep.java:76)
    at org.gradle.internal.execution.steps.SkipUpToDateStep.lambda$execute$2(SkipUpToDateStep.java:54)
    at java.base/java.util.Optional.orElseGet(Unknown Source)
    at org.gradle.internal.execution.steps.SkipUpToDateStep.execute(SkipUpToDateStep.java:54)
    at org.gradle.internal.execution.steps.SkipUpToDateStep.execute(SkipUpToDateStep.java:36)
    at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsFinishedStep.execute(MarkSnapshottingInputsFinishedStep.java:37)
    at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsFinishedStep.execute(MarkSnapshottingInputsFinishedStep.java:27)
    at org.gradle.internal.execution.steps.ResolveIncrementalCachingStateStep.executeDelegate(ResolveIncrementalCachingStateStep.java:49)
    at org.gradle.internal.execution.steps.ResolveIncrementalCachingStateStep.executeDelegate(ResolveIncrementalCachingStateStep.java:27)
    at org.gradle.internal.execution.steps.AbstractResolveCachingStateStep.execute(AbstractResolveCachingStateStep.java:71)
    at org.gradle.internal.execution.steps.AbstractResolveCachingStateStep.execute(AbstractResolveCachingStateStep.java:39)
    at org.gradle.internal.execution.steps.ResolveChangesStep.execute(ResolveChangesStep.java:65)
    at org.gradle.internal.execution.steps.ResolveChangesStep.execute(ResolveChangesStep.java:36)
    at org.gradle.internal.execution.steps.ValidateStep.execute(ValidateStep.java:106)
    at org.gradle.internal.execution.steps.ValidateStep.execute(ValidateStep.java:55)
    at org.gradle.internal.execution.steps.AbstractCaptureStateBeforeExecutionStep.execute(AbstractCaptureStateBeforeExecutionStep.java:64)
    at org.gradle.internal.execution.steps.AbstractCaptureStateBeforeExecutionStep.execute(AbstractCaptureStateBeforeExecutionStep.java:43)
    at org.gradle.internal.execution.steps.AbstractSkipEmptyWorkStep.executeWithNonEmptySources(AbstractSkipEmptyWorkStep.java:125)
    at org.gradle.internal.execution.steps.AbstractSkipEmptyWorkStep.execute(AbstractSkipEmptyWorkStep.java:56)
    at org.gradle.internal.execution.steps.AbstractSkipEmptyWorkStep.execute(AbstractSkipEmptyWorkStep.java:36)
    at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsStartedStep.execute(MarkSnapshottingInputsStartedStep.java:38)
    at org.gradle.internal.execution.steps.LoadPreviousExecutionStateStep.execute(LoadPreviousExecutionStateStep.java:36)
    at org.gradle.internal.execution.steps.LoadPreviousExecutionStateStep.execute(LoadPreviousExecutionStateStep.java:23)
    at org.gradle.internal.execution.steps.HandleStaleOutputsStep.execute(HandleStaleOutputsStep.java:75)
    at org.gradle.internal.execution.steps.HandleStaleOutputsStep.execute(HandleStaleOutputsStep.java:41)
    at org.gradle.internal.execution.steps.AssignMutableWorkspaceStep.lambda$execute$0(AssignMutableWorkspaceStep.java:35)
    at org.gradle.api.internal.tasks.execution.TaskExecution$4.withWorkspace(TaskExecution.java:289)
    at org.gradle.internal.execution.steps.AssignMutableWorkspaceStep.execute(AssignMutableWorkspaceStep.java:31)
    at org.gradle.internal.execution.steps.AssignMutableWorkspaceStep.execute(AssignMutableWorkspaceStep.java:22)
    at org.gradle.internal.execution.steps.ChoosePipelineStep.execute(ChoosePipelineStep.java:40)
    at org.gradle.internal.execution.steps.ChoosePipelineStep.execute(ChoosePipelineStep.java:23)
    at org.gradle.internal.execution.steps.ExecuteWorkBuildOperationFiringStep.lambda$execute$2(ExecuteWorkBuildOperationFiringStep.java:67)
    at java.base/java.util.Optional.orElseGet(Unknown Source)
    at org.gradle.internal.execution.steps.ExecuteWorkBuildOperationFiringStep.execute(ExecuteWorkBuildOperationFiringStep.java:67)
    at org.gradle.internal.execution.steps.ExecuteWorkBuildOperationFiringStep.execute(ExecuteWorkBuildOperationFiringStep.java:39)
    at org.gradle.internal.execution.steps.IdentityCacheStep.execute(IdentityCacheStep.java:46)
    at org.gradle.internal.execution.steps.IdentityCacheStep.execute(IdentityCacheStep.java:34)
    at org.gradle.internal.execution.steps.IdentifyStep.execute(IdentifyStep.java:48)
    at org.gradle.internal.execution.steps.IdentifyStep.execute(IdentifyStep.java:35)
    at org.gradle.internal.execution.impl.DefaultExecutionEngine$1.execute(DefaultExecutionEngine.java:61)
    at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeIfValid(ExecuteActionsTaskExecuter.java:127)
    at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:116)
    at org.gradle.api.internal.tasks.execution.FinalizePropertiesTaskExecuter.execute(FinalizePropertiesTaskExecuter.java:46)
    at org.gradle.api.internal.tasks.execution.ResolveTaskExecutionModeExecuter.execute(ResolveTaskExecutionModeExecuter.java:51)
    at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:57)
    at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:74)
    at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:36)
    at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.executeTask(EventFiringTaskExecuter.java:77)
    at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:55)
    at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:52)
    at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:200)
    at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:195)
    at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:66)
    at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:59)
    at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:157)
    at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:59)
    at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:53)
    at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:73)
    at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter.execute(EventFiringTaskExecuter.java:52)
    at org.gradle.execution.plan.LocalTaskNodeExecutor.execute(LocalTaskNodeExecutor.java:42)
    at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:331)
    at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:318)
    at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.lambda$execute$0(DefaultTaskExecutionGraph.java:314)
    at org.gradle.internal.operations.CurrentBuildOperationRef.with(CurrentBuildOperationRef.java:80)
    at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:314)
    at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:303)
    at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.execute(DefaultPlanExecutor.java:463)
    at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.run(DefaultPlanExecutor.java:380)
    at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
    at org.gradle.internal.concurrent.AbstractManagedExecutor$1.run(AbstractManagedExecutor.java:47)
    at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
    at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
    at java.base/java.lang.Thread.run(Unknown Source)
Caused by: com.android.ide.common.process.ProcessException: Error while executing process /Users/transformhub/Library/Android/sdk/cmake/3.22.1/bin/cmake with arguments {-H/Users/transformhub/Downloads/mycam/ffmpeg/MyAndroidapp/app/src/main/cpp -DCMAKE_SYSTEM_NAME=Android -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DCMAKE_SYSTEM_VERSION=24 -DANDROID_PLATFORM=android-24 -DANDROID_ABI=arm64-v8a -DCMAKE_ANDROID_ARCH_ABI=arm64-v8a -DANDROID_NDK=/Users/transformhub/Library/Android/sdk/ndk/26.1.10909125 -DCMAKE_ANDROID_NDK=/Users/transformhub/Library/Android/sdk/ndk/26.1.10909125 -DCMAKE_TOOLCHAIN_FILE=/Users/transformhub/Library/Android/sdk/ndk/26.1.10909125/build/cmake/android.toolchain.cmake -DCMAKE_MAKE_PROGRAM=/Users/transformhub/Library/Android/sdk/cmake/3.22.1/bin/ninja -DCMAKE_LIBRARY_OUTPUT_DIRECTORY=/Users/transformhub/Downloads/mycam/ffmpeg/MyAndroidapp/app/build/intermediates/cxx/Debug/406wr1e2/obj/arm64-v8a -DCMAKE_RUNTIME_OUTPUT_DIRECTORY=/Users/transformhub/Downloads/mycam/ffmpeg/MyAndroidapp/app/build/intermediates/cxx/Debug/406wr1e2/obj/arm64-v8a -DCMAKE_BUILD_TYPE=Debug -B/Users/transformhub/Downloads/mycam/ffmpeg/MyAndroidapp/app/.cxx/Debug/406wr1e2/arm64-v8a -GNinja}
    at com.android.build.gradle.internal.process.GradleProcessResult.buildProcessException(GradleProcessResult.java:73)
    at com.android.build.gradle.internal.process.GradleProcessResult.assertNormalExitValue(GradleProcessResult.java:48)
    at com.android.build.gradle.internal.cxx.process.ExecuteProcessKt.execute(ExecuteProcess.kt:277)
    ... 143 more
Caused by: org.gradle.process.internal.ExecException: Process 'command '/Users/transformhub/Library/Android/sdk/cmake/3.22.1/bin/cmake'' finished with non-zero exit value 1
    at org.gradle.process.internal.DefaultExecHandle$ExecResultImpl.assertNormalExitValue(DefaultExecHandle.java:442)
    at com.android.build.gradle.internal.process.GradleProcessResult.assertNormalExitValue(GradleProcessResult.java:46)
    ... 144 more


  


  Here is the complete source code

  


• Fintech Content Marketing : 10 Best Practices & Growth Strategies

  24 juillet 2024, par Erin

  Content marketing is an effective strategy for growth and building trust. This is especially true in the fintech industry, where competition is intense and trust is crucial. Content marketing helps you strengthen customer relationships, engage your audience, and differentiate yourself from competitors.

  To get the most out of your fintech content marketing, you need to develop the right strategy.

  In this guide, we’ll cover everything you need to know about content marketing for fintech companies so you can expand your reach and grow your business.

  What is fintech content marketing ?

  Fintech content marketing is creating content around financial topics on the internet to attract, engage, and convert audiences.

  Fintech companies can use a content strategy to drive leads by creating educational content.

  

  While financial content is important, it’s easy for it to feel boring, unrelatable, or confusing. But, when done right, fintech companies can educate their audiences with great content marketing that helps their audience understand financial topics in-depth.

  Fintech companies can create written, audio, or video content to inform their audiences about financial topics they’re interested in.

  From there, each piece of content can then be distributed to different mediums :

  • Blogs
  • Website
  • Facebook
  • YouTube
  • Instagram
  • Other websites
  • Apps
  • And more

  Once content is distributed, fintech companies can then analyse how effective the content is by tracking web analytics data like search engine traffic, social media engagement, and new customers.

  7 reasons fintech companies need content marketing

  Before we dive into fintech content marketing best practices, let’s recap why fintech companies need to lean into content to grow their business.

  Here are seven reasons your financial company needs to deploy a robust content strategy :

  

  1. Reach new audiences

  If you want to grow your fintech company, you need to find new customers. Creating content is a proven path to marketing yourself online and attracting a larger audience.

  By using search engine optimisation (SEO), social media marketing, and YouTube, you can expand your audience and grow your customer base.

  With content marketing, you can find new audiences without needing a massive budget, making scaling easier.

  2. Engage current audience

  While content can be a powerful method to reach new customers, it isn’t the only thing it’s good for.

  If you want to grow your business, another way to leverage your content is to keep your current audience engaged.

  You can create financial content to educate, inform, and add value to your current audience who already knows you. Repurposing content between the different platforms your audience is on keeps them engaged with you and your brand.

  It’s a simple way to capture and keep the attention of your audience, build trust, and convert more prospects into customers.

  3. Build relationships with customers

  You should leverage content marketing in various spaces, such as social media, your website, a blog, or even YouTube. Creating content on different channels allows you to build relationships with your customers on autopilot.

  The general rule in marketing is that the more touch points you have with your customers, the more you’ll sell. Creating more content means you always have new opportunities to increase those touchpoints, build deeper relationships, and sell more.

  4. Grow authority in a space

  If you want people to trust you and your financial tech, you need to be seen as an authority. How can someone trust that your app or web platform will help them with their finances if they don’t trust you’re a financial expert ?

  You should use informative content to become a thought leader in your space. You can post content on social media or your own platforms.

  You can also spread your authority by leveraging other brands’ or influencers’ audiences through guest blog posting and guest podcasting.

  5. Drive new leads

  Content marketing isn’t just a fun hobby for businesses. It’s one of the smartest ways to drive new leads.

  You should be crafting content for your top-of-funnel marketing strategy to attract potential customers.

  Creating content consistently is a great way to bring in new audience members into your funnel.

  Once you grow your top-of-funnel audience, you can convert them into leads by getting them to join your email list or trial your financial software.

  One tip to get more out of your content strategy is creating evergreen content to continually drive leads. For example, create “set-it-and-forget it” blog posts or YouTube videos that will continue working for you daily to attract new audience members searching for helpful financial information. Then, provide a call to action on that content to join your email list (by leveraging a lead magnet).

  6. Convert prospects to customers

  When you have a continual flow of new top-of-funnel prospects, you always have a fresh cycle of prospects you can convert into customers.

  Content is primarily used to attract new audience members and engage your current audience at the top of your funnel. But it can also be used to convert your audience into customers.

  Try mixing up your content types to drive conversions :

  • Educational
  • Entertaining
  • Promotional

  Don’t just show off educational content.

  You should also mix in “authority” content by displaying case studies of user success stories and calling to action to sign up for a free trial or request a demo.

  7. Lower Customer Acquisition Cost (CAC)

  On the business side, if you want a marketing strategy that will keep expenses low long term, you’ll want to invest more in content.

  Content marketing has a great return on investment (ROI) for your time and effort.

  Why ?

  Because the customer acquisition costs (CAC) are so low.

  You can create content that can bring in leads for months if not years.

  If you only use Google or Facebook ads to drive new leads, you always have to “pay-to-play.” When you turn the advertising tap off, your leads dry up.

  But, with blogs and videos, you can create content that can bring in organic customers on repeat. It’s like a snowball effect that keeps going long after you’ve completed the initial work.

  10 fintech content marketing best practices

  Here are ten best practices to establish a strong content marketing strategy as a fintech company :

  

  1. Set SMART goals

  A good content strategy starts with goal-setting. You’ll never get there if you don’t know where you’re going.

  To make sure your fintech content marketing strategy is a success, you need to set SMART goals :

  • Specific
  • Measurable
  • Achievable
  • Relevant
  • Time-bound

  For example, you might set a goal to reach 20,000 blog visits in one year and convert blog visits at a rate of 3%.

  Setting clear content goals will streamline operations, so you stay consistent and get the most out of your efforts.

  3. Be transparent

  Transparency is crucial for fintech companies, as they handle sensitive financial data and, in many cases, monetary transactions.

  It’s essential for you to be open and clear about your products, services, and data practices. By being honest about privacy and security measures, fintechs can build and maintain trust with their customers.

  This transparency not only helps in establishing credibility but also ensures customers feel confident about how their financial information is managed and protected.

  

  4. Take an education-first approach

  Content isn’t just about “hooking” or entertaining your audience. That’s just one aspect of a content strategy.

  The best approach to building authority and converting leads from your content is to take an education-first approach.

  Remember above, when we touched on understanding your ICP ? You need to know your ICP’s interests and pain points inside and out and then map your product’s strengths to those that are relevant.

  Always start with your ICP, then build the content strategy around them based on your product.

  Find connections and identify how your product can address the ICP’s interests and pain points.

  For example, let’s say your ICPs are Gen Z consumers. They’re interested in independence and saving for future goals. Their pain points might include lack of investment knowledge and managing student debts and other loans.

  Let’s say your product is a personal finance app. Some of your benefits might be budget tracking and beginner-friendly investment options. You could create a content strategy around budgeting in your 20s and investing for beginners.

  Content strategies will vary widely based on your ICP. For instance, content for a fintech company targeting those approaching retirement will need a different focus compared to that aimed at younger consumers.

  Remember : practical, step-by-step, value-driven content performs best regarding conversions.

  5. Leverage the right tools

  If you’re going to succeed with content, you need to lean on the right tools.

  Here are a few types of tools you should consider (and recommendations) :

  • Project management (i.e., Asana)
  • Content management system (i.e., WordPress)
  • Content scheduling (i.e., Hootsuite)
  • Design (i.e., Canva)
  • SEO (i.e., Ahrefs)
  • Web analytics (i.e., Matomo)

  Try Matomo for Free

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

  Start for free

  No credit card required

  6. Promote your content on different platforms

  You’ll want to promote your fintech content marketing strategy on different channels and platforms to get the most out of your fintech content marketing strategy.

  Start with one core platform before you pick a few platforms to promote your content. You should leverage at least one social media platform.

  Then, create a blog and an email newsletter to ensure you create multiple touchpoints.

  Here are some tips on how to pick the right platform :

  • Consider age range (i.e. TikTok for a younger audience, Facebook for an older audience)
  • Consider your preferred content type (YouTube for long-form video, X for short-form written content
  • Consider your competition (i.e. go where competitive fintech companies already are)

  7. Track results 

  How do you know if you’re on pace to reach the SMART goals you set earlier ?

  By tracking your results. 

  You should dive into your data regularly to ensure your content is working. Make sure to track social media, email marketing, and web results.

  Keep a close eye on your website KPIs and track your conversions to ensure a return on investment (ROI). For more detailed guidance on monitoring your website’s performance, check out our blog on how to check website traffic as accurately as possible.

  Remember, a data-driven approach is the best way to stay on track with your content goals.

  8. Establish a content leader

  Your content marketing needs a leader. You should establish someone on your marketing team to oversee your content plan. 

  They should ensure they collaborate well with different teams, understand social media and SEO, and know how to manage projects.

  Most of all, don’t forget that they’re in charge of tracking your data and reporting to higher-ups, so they should be comfortable with web analytics and know how to track performance well.

  9. Optimise for SEO

  It’s not enough to create a weekly blog post. You could craft the most valuable content on your website, but nobody will find it online if it isn’t optimised for SEO.

  Your content leader should analyse SEO data using a tool like Ahrefs or SEMrush to analyse different keywords to target in your content. 

  A web analytics tool like Matomo can then be used to track results. Matomo offers traditional web analytics, including pageviews, bounce rate, and sources of traffic, alongside features like heatmaps, session recordings, and A/B testing.

  These advanced features provide deeper insights into how users interact with your site and content, helping you pinpoint areas for improvement. Improving the user experience based on these insights can then positively impact your Google rankings.

  Try Matomo for Free

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

  Start for free

  No credit card required

  10. Stay compliant

  Fintech is a highly regulated industry. Keeping this in mind, you need to ensure you take the necessary steps to ensure you remain compliant with all applicable laws and regulations.

  Non-compliance can result in severe penalties.

  Given these high standards, it’s crucial to ensure that user data remains private and secure. Matomo helps with this by providing a compliant web analytics solution that respects user privacy. With Matomo, you can confidently manage compliance and build trust with your customers while also reliably tracking the performance of your content marketing.

  

  Drive your content marketing strategy with Matomo

  Leaning into content marketing can be one of the best ways your fintech company can attract, engage, convert, and retain your audience.

  By creating high-quality content for your audience on social media, YouTube, and your website, you can establish your brand as an authority to grow your business for years to come.

  But remember, you need to make sure you’re only using privacy-friendly, compliant tools to protect your audience’s data.

  Thankfully, Matomo has you covered.

  As a privacy-friendly web analytics tool, Matomo ensures that your website data is tracked and stored in compliance with privacy laws.

  Trusted by over 1 million websites, it offers reliable data without sampling, guaranteeing accuracy. Matomo is designed to be fully compliant with privacy regulations such as GDPR and CCPA, while also providing advanced features like heatmaps, session recordings, and A/B testing to help you track and enhance your website’s performance.

  Request a demo to see how Matomo can benefit your fintech business 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

  

• Multi-Site Management (Quick-Start Guide)

  18 juillet 2024, par Erin

  Do you run multiple websites ?

  Or, you’re expanding from one to two sites ?

  Multi-site management isn’t an easy task.

  While there are dozens of reasons why you may need to operate several sites, like brick and mortar stores opening new locations in different regions, you need to ensure you’re following the right strategies so you remain successful.

  So, how do you actually manage multiple websites at the same time without spreading yourself thin ?

  Using a single dashboard.

  In this guide, we’ll cover everything you need to know about managing multiple sites in a single location at once so you can lead a successful digital strategy.

  What is multi-site management ?

  Multi-site management is the process of organising and operating multiple websites from a single location. It helps with congruent branding and improved productivity.

  Enterprise businesses that use multiple, language-specific versions of their site to target their audience in specific countries or regions can also benefit from managing their multiple sites from a single location. 

  

  By analysing a few websites at once, marketers and analysts can oversee a few different business websites without having to switch between multiple platforms and technologies.

  Whatever the reason is for managing multiple sites, multi-site management helps marketers and analysts establish a consistent brand presence, improve workflow efficiencies and scale operations.

  7 Benefits of multi-site management

  Multi-site management allows you to navigate and control a few websites all in one centralised location.

  

  Here are a few of the main benefits of multi-site management :

  1. Save time by reusing code between websites

  Saving time is the main benefit of multi-site management. Rather than managing websites from multiple platforms, logins and infrastructures, you can manage everything from one place.

  Multi-site management allows you to easily reuse core code, infrastructure and other digital assets from other sites all within one dashboard.

  So, when you need to update all of your websites, you can do it all at once in a fraction of the time.

  2. Improve productivity by having everything in one place

  How many tools do you currently use for your job on a daily basis ?

  Five ? Ten ?

  Now, imagine adding on another handful of tools, logins and technology for every site you manage.

  It’s a lot, especially if you’re managing dozens of logins, usernames and passwords.

  With multi-site management, you don’t need to have multiple login credentials. Everything’s all in one place and within one system.

  You don’t need to switch between multiple tools and platforms to get things done.

  The same strategy applies to your web analytics. If you want to streamline your productivity, make sure you’re tracking all of the data from your different websites in one place. Matomo lets you track multiple sites, domains and subdomains in one centralised location with the ‘All Websites’ dashboard which is a roll-up report. This is ideal for enterprises managing and analysing numerous sites.

  Try Matomo for Free

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

  Start for free

  No credit card required

  3. Maintain brand image with consistent design across sites

  If you have multiple websites, subsidiaries or sister companies, it can take a great deal of effort to maintain branding consistency.

  But, if you’re leveraging a multi-site content management system, you can update your branding and design between all sites at the same time.

  If you need to make a change with your design, you don’t need to update each individual site with your new initiative. Instead, you can update multiple sites at once, allowing your visual branding to stay congruent, giving you uniformity in messaging.

  The result is an optimised user experience, which helps you increase trust with your audience, improve engagement and keep them coming back for years to come.

  4. Increase security through centralised management

  The greater your digital presence is, the more you can reach a wider range of people.

  But, there’s one downside : you expose yourself to more risk.

  Keeping multiple websites secure isn’t as easy to do if you’re leveraging dozens of different platforms and logins. 

  Instead, when you have all of your websites in one location, it can help you easily track every document. You can also control site versions for easy updates to prevent malicious attacks.

  5. Optimise scalability and flexibility

  If you plan on scaling your companies and digital presence, you need to ensure you’re able to do so without having to tear down your entire infrastructure or spend a ton of money upfront.

  For enterprise companies, multi-site management allows you to easily launch new regional sites as your company expands.

  Plus, if you have new product or marketing campaigns, you can simply add on microsites as needed by simply adding it to your current website lineup.

  This allows you to stay flexible in your marketing and growth strategies without adding extra risk or financial burden.

  6. Improve targeting and personalisation in marketing

  If you want to reach your audience better, but you’re managing multiple websites, it can be hard to not spread yourself too thin.

  But, if you’re managing a few websites in one place, it’s easier to track your audience’s interests, behaviour, wants and needs.

  By using a web analytics tool like Matomo to track the performance of multiple websites, you can see what’s resonating with your audience so you’re able to improve your targeting and offer personalised campaigns.

  Try Matomo for Free

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

  Start for free

  No credit card required

  7. Streamline collaboration between team members

  Making your team juggle multiple platforms, websites and tools is a surefire way to give them a headache.

  Multi-site management is one of the best ways to bring your entire team into one centralised location so you can foster seamless collaboration without leaving your team confused or frustrated.

  By placing your entire website management in one place, markters, designers, developers, writers and other team members can collaborate effectively so you can get more done in less time.

  With multi-site management, you bring your entire team into a single location to work on your websites so you can speed up your content creation process, speed up problem solving and streamline communication.

  6 Best practices of multi-site management

  When you have multiple websites, you can expand your brand presence. But, one main problem arises : it becomes overwhelming for anyone managing them.

  Since each website comes with its own platform, login credentials and assets, it becomes incredibly difficult for developers, marketers and others to maintain the sites. And, if your sites aren’t looked after properly, you could end up with technical issues and branding inconsistencies, causing you to lose conversions and negatively impact the user experience.

  Thankfully, multi-site management can help you streamline your efforts, improve productivity and scale your business.

  But, before you dive into your multi-site management process, you need to ensure you implement the right strategy.

  

  Here are a few best practices to follow to succeed with multi-site management :

  1. Use a multi-site CMS

  If you want to manage multiple websites, you need to make sure you’re leveraging a CMS that offers multi-site management capabilities.

  A multi-site CMS allows you to make simple content, design or management changes simultaneously without having to switch between different systems.

  Here are a few examples of CMS’ that offer multi-site management :

  • WordPress
  • Sanity
  • Drupal

  2. Integrate a headless CMS

  One of the most versatile types of content management systems is what’s known as a “headless CMS.”

  This is a CMS that lets you disconnect the front end from the back end of your website management.

  Here are a few examples of headless (and open source) CMS’ :

  • Strapi
  • Directus
  • Ghost

  A headless CMS can help you add versatility in the way you present content across multiple sites. It uses an API to give you more flexibility so you can push content to websites as well as apps, etc.

  Using a headless CMS can help you improve page load times, website performance and user experience by simplifying your tech stack.

  3. Implement cross-domain and mult-isite Matomo analytics tracking

  If you want to track the website analytics data of multiple sites, you need to implement cross-domain tracking.

  The best way to do this is by leveraging a web analytics solution like Matomo. It lets you track the performance of multiple subdomains or websites.

  With Matomo, you get easy data grouping and data roll-up reporting for streamlined tracking.

  

  This means you can track the individual performance of each site or group them together to see the shared performance.

  4. Enable multiuser management

  If you’re working with different team members who need access to your CMS, then you should consider enabling multiuser management.

  This allows several people to work within your multi-site CMS and also gives you the ability to grant or restrict access to certain abilities within the platform.

  This is handy if you have a few different stakeholders working in your CMS.

  By enabling different user permissions and access, you can improve the security of your website and protect sensitive company information.

  5. Leverage composable content

  Creating a few different websites is a great way to increase your brand reach. But, it can be time-consuming having to continuously create and update content within multiple sites.

  That’s where composable content comes in.

  It allows you to create similar content between sites using pre-made “blocks.” Content blocks act as templates so you can quickly add similar content pieces to each site without having to start over from scratch each time.

  This speeds up productivity for your designers, writers and editors and keeps brand image consistent across different sites.

  6. Use version control

  What happens if you update all of your websites with a redesign, but it flops ?

  Well, rather than having to tear it all down and redesign your site infrastructure, you can leverage version control to restore your website to a previous version.

  Version control is especially handy when you’re managing multiple sites at once and you have multiple team members working in your CMS.

  Version control is also helpful if you’re A/B testing different content. By saving previous versions of your websites, you can run tests to help you optimise your web performance. 

  For example, if you use Matomo’s A/B testing feature to experiment with different landing page designs for a lead magnet, but find that your previous version performed better, you can simply restore your websites to a previous version in seconds.

  Track web analytics for multiple websites with Matomo

  If you’re looking to expand your digital presence, then creating new websites is one of the best ways to grow your brand.

  Multi-site management can help you save time, improve productivity and maintain a consistent brand image across your empire.

  One challenge of multi-site management is tracking the performance of your websites.

  That’s where Matomo has you covered.

  Matomo is a privacy-friendly web analytics tool that collects, stores, and tracks data across multiple websites and subdomains, allowing you to improve your performance. 

  With over 1 million websites using Matomo, you can rely on it for accurate data without sampling, ensuring compliance with privacy regulations like GDPR and CCPA. 

  Matomo is especially beneficial for enterprises. It offers advanced roll-up reporting, enabling you to see the performance of multiple websites in one centralised dashboard. This feature, along with heatmaps, session recordings, and A/B testing, provides deeper insights into your website performance.

  Discover how Matomo can transform your web analytics with a demo. Request your demo 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