Data aggregation functionality in Mautic

Ideas and Feature Requests
1

My idea is Mautic INGEST:

In some proprietary marketing automation tools (like Adobe Campaign manager), You have the possibility to gather a bunch of data from different sources to create/enrich contacts and send segment emails. An important requirement is that the marketeers are able to use these tools:

  • No queries (only if they want it
  • No code (but possibly)
  • Easy to use

Wat they want to do is combin data from different data sources (like bigquery and OracleSQL) , do ssome transformations on them (sort/ unique / filter / join / lookup / …) and then load them into Mautic as a segment.

We are now looking at using Apache HOP or other tools to do this combination of ETL in a Gui friendly way into Mautic but the question rose: should we perhaps have this in Mautic?

ingest.drawio
ingest.drawio881Ă—431 30.3 KB

I think these groups of people would benefit from this idea:

  • Enterprises with many data sources
  • Existing users of Adobe Campaign manager

Why I think they would benefit from this idea:

  • Easy migration from propietary tools to Open souce (feature parity)
  • Very powerfull plugin to create and enrich your contacts.

Are you willing to work on this idea?: Possibly

What skills and resources do you need to explore this further?
Feedback!

1 Like
2

I’m curious, which problem are you trying to solve here?
I’ve learned so far that Mautic isn’t the tooling (yet) for database warehousing.

3

Hi @woutersf,

very interested. Does Mautic - via Hop - import the data or use it with “zero data movement/copying” (to quote that industry marketing term) t create the respective segment and add that segment information to the contact? So that it would be even more viable from a data privacy standpoint, as data never leaves the source systems to be stored/copied somewhere else?

4

Someone could think of cases where people want to make queries (from mautic) on Oracle systems or mssql systems to pull in some of those rows to target them.
Yea just keeping the row in the source system might be usefull but not always ideal as it might be a combination of different tables and the result of a pipeline?
In my example it is HOP pushing it into Mautic, using the API (creating the segment + contacts).