Can we transfer our journey data to our database?

Prev Next

Yes, Architect allows you to transfer your analytics data to your own internal systems via the Architect Analytics Export API.

Through this API, you can export all analytics available in the Analytics Dashboard and Single Journey Analytics pages, including overall analytics, journey-level metrics, element-level metrics, and conversion goal performance.

The API provides multiple endpoints for exporting data depending on your needs. For example:

  • The overall analytics endpoint returns consolidated metrics for all journeys that match your filters, such as status, channels, or conversion goal.
  • The journey analytics endpoint retrieves detailed performance metrics for a specific journey, including user metrics, channel performance, and exit criteria.
  • The element analytics endpoint provides analytics for individual channel elements inside a journey.
  • The conversion goals endpoints allow exporting all goal definitions and goal-based metrics.
  • The journey list endpoint allows exporting metadata for all journeys, including tags, statuses, conversion goals, starter types, and exit criteria.

All endpoints return data in JSON format, which you can consume directly by your internal reporting systems or store in your own database. Requests require an API key generated from the panel under Settings > Security > API Keys, with the Campaign Analytics > Architect permission enabled.

With these API endpoints, you can schedule automated exports or integrate Architect analytics with your existing BI tools, data warehouses, or dashboards.