Reporting for Canvas steps

Question

Hi all,We’re currently exploring how to build a reporting pipeline from Braze to our data warehouse and would like your input.Specifically, we’re trying to track the journey a contact takes through a Braze Canvas: from entry to any conversion or exit, and export this data for analysis.Our objectives:Understand which steps a contact entered, converted on, or exited from.Capture timestamped events (ie. entry, conversion, exit, etc.) in a way that allows us to reconstruct the user’s path.Push this data into our data warehouse for reporting.We believe the following Currents event tables might be useful:USERS_CANVAS_ENTRY_SHAREDUSERS_CANVAS_CONVERSION_SHAREDUSERS_CANVAS_EXIT_MATCHEDAUDIENCE_SHAREDUSERS_CANVAS_EXIT_PERFORMEDEVENT_SHAREDPossibly: USERS_CANVAS_EXPERIMENTSTEP_* for A/B pathsWe’d like to confirm:Are these the correct tables for capturing the step-by-step journey through a Canvas?Are there best practices for joining or correlating this data in our data warehouse?Should we stream this via Braze Currents, or is there a better approach for deeper Canvas-level reporting?Any advice, sample schemas, or learnings from similar setups would be hugely appreciated!Thanks,Coralie

manoj__ · Answer

CoralieVngt​ &nbsp;Using Braze currents is the best way to share event-level data with data warehouses.For joining the data, I would use the user_id or external_user_id based on the data availability.Also, if you are interested in tracking whether users entered or skipped actions like emails or pushes, the ABORT_SHARED tables are important.Link of tables are available here: https://www.braze.com/docs/user_guide/engagement_tools/segments/sql_segments/sql_segments_tables/#table-of-contents