Story: Ability to build models in the app?

[cyberjar09]

• hi I wanted to start by thanking the team for this great piece of software
• I was wondering if there is any plan to build models in valmi, i.e., ala grouparoo/census
• intention would be to build groups/segments/audiences based off models which can be rETL'd and also shared across the org
  • eg: marketing build a segment for LTV>100, which can also be targetted by product for a different product experience
• thanks!

[rajvarkala]

Hi,
Glad to hear that you are finding the software useful.
Are you looking at the model as sql query? Or as a UI version for building segments/audiences?
I have a couple of questions about the use-case.

1. What is stopping you from building a simple 'view' with sql in the database?
2. Who in your org will find this model functionality most useful?
3. Which sources/destinations are you considering rETL for?

Best,
Raj

[cyberjar09]

HI @rajvarkala thanks for your time

Are you looking at the model as sql query? Or as a UI version for building segments/audiences?

both would be ideal IMHO, giving flexibility to users of the software to point and click or drill down to SQL if need be

What is stopping you from building a simple 'view' with sql in the database?

it is possible, but the workflow I frequently encounter is:

• marketing team want to create a new target segment
• they request BI team to create the dbt model in the DWH
• the request goes into the backlog/queue and gets done based on priority

This poses a few challenges which will be alleviated by having the features mentioned above:

• marketing team can now self serve i.e., no bottleneck on another team for building audiences
• if there is new fields required, then the old workflow can kick off but for the most part, it allows teams to operate independently

Who in your org will find this model functionality most useful?

• marketing will be able to self serve for the most part (crm, facebook audiences etc.)
• product can start leveraging segments to target specific users with new features (retl to feature toggle SaaS)
• BI wont have to be bottleneck for a lot of these types of requests if the data already exists in the warehouse and is exposed to the tool for querying/building audiences

Which sources/destinations are you considering rETL for?

• source in my case is a DWH, i.e., redshift, databricks
• destinations are going to vary
  • crm tool (emarsys, braze)
  • facebook audiences
  • configcat (feature flagging)
  • zendesk (hydrate more customer info for customer experience team)

[rajvarkala]

Thanks for the detailed answer.

I think it is the next logical step for rETL to let users (marketers/product/customer-success) to self-serve more with data. We will spec out and share the product details of this particular feature.

Thanks again.