How do you build customer journeys with data?

What are some of the ways people have built customer journeys using internal data?
eg: Understanding user signup/onboarding flow, key actions people take in the first couple of sessions post signup, etc. Thinking mainly from a data engineering standpoint here on how to build something like this internally.


Would you be able to explain how information designing angles and building client ventures utilizing information cross with regards to your inquiry? I’m not really clear on the thing you are searching for.


At my latest organization, we constructed an onboarding stream and afterward utilized UI occasion information and logical programming to do the channel examination. We searched for simple successes to lessen drop-off and afterward did straightforward investigations to check whether we could make it work (we could, here and there). The “information designing” was that occasion information was produced by the UI, shipped off Segment, and afterward Mixpanel to check out partners and the funnel(s). We likewise sent that occasion information into an information distribution center to have for recorded purposes and some announcing.


Intriguing - how does Data Engineering end up with this being their obligation versus say Growth, UX, Product, or in any event, Marketing? Does it seem like one of those positions would diagram the information needs then, at that point, go to Data Engineering to assist them with building it?

1 Like

I consider Data Engineering groups being liable for giving the right structures to examination partners to find solutions with negligible code. Going with an off-the-rack instrument is certainly one approach. I’m moving toward it from the point where you fabricate something inside where you approach every one of the information and aren’t limited to just the information you have ingested into an outer device. With the right structure set up, finding a solution to the inquiry “What does a client do post-information exchange?” turns out to be only one of the inquiries that the system can help you reply to. A more conventional answer can open up the chance of addressing comparable inquiries including client experience through the item without a significant lift.

1 Like

Ok. So would you say you are utilizing this as a utilization case by which to fabricate your information designing as an assistant stage, that empowers partners, for example, Growth, UX, Product, Marketing to get to that information without requesting you to make another structure for each from their oddball use cases?

From an information angle – you can glance at the way of this information stack. One supposition – it’s not real-time, yet you can make it close ongoing in the event that you work on explicit advances.

Snowplow – occasion information definition and assortment. It’s open-source and you gain admittance to crude information. I’ve seen individuals additionally utilize top-notch logs rather than occasion information.

Stockroom – a solitary spot for every one of the information, pick whatever you like, for example, Snowflake.

Overseen ELT device – to stack information from different frameworks into the distribution center, for example, Fivetran/join.

DBT – occasion information change, there are a few bundles for Snowplow. An incredible advantage of having every one of the information in one stockroom is that you can interface client touchpoints from different frameworks into one excursion. Likewise gives information on newness/quality testing.

BI device/SQL/Custom UI – to get to experiences. This can be the trickiest, relies upon how SQL-accommodating is your organization, your information shoppers, and on the off chance that you have designing assets to fabricate some self-serve UI on top of stockroom information.

Extra advantage – on the off chance that you have every one of the information in one stockroom (controlled by DBT) – your information becomes code, fabricating downstream use cases (for example Computer-based intelligence/ML, information operationalization) additionally turns out to be a lot simpler.

Expectation this makes a difference.

1 Like

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.