How to export journey user data

You can export user activities or user information related to a specific journey. For example, you can export the profile IDs or email addresses of the users who entered a specific journey, or the profile IDs of the users who received email or web push messages from a specific journey. You can use two different methods to export the data:

• Export Raw User Data API
• Using User Profiles

Export Raw User Data API

This API helps you get a download link to export the requested user filters, attributes, and event details. Read more on Export Raw User Data API.

Using User Profiles

You can filter users on User Profiles with the desired Journey-related events. Then, you can export those users with up to 20 attributes.

Journey Enter and Exit Activities

1. Navigate to Audience > User Profiles.

2. Click Filter Contacts button on the listing page.3. Select the Events box under the Standard segments.4. Select the "journey_enter" or "journey_exit" based on your needs.

5. Define the Times, Time Range, and Unit values.

6. Specify the journey you want to export user data from. 

You can also use other event parameters such as Journey Exit Reason, Journey Enter Reason, Journey Name or Event Code of the element user exited from.

7. Click the Apply button to apply the filters.

8. You can see the number of users who fit in this segment next to the Filter button together with the number of filters applied.

9. Click the Export button to download your user data.

10. You can include the user attributes in your export file.

11. You will receive an email to download your CSV file in your inbox.

User's Channel Activities

A journey includes different messaging channels and users can receive messages from them. You can export the user activities on a specified channel(s).

You can use the Channel Interactions box under Predefined Segments in the filtering section. 

If you select Architect from the Product dropdown, you can also select Journey Name and Channel Name.

The Journey specific Channel activities under the users' Events tab

Architect generates Journey Product Action event for all the messaging channels Architect has. The action (user activity) and the channel are defined with event parameters. 

Action Code event parameter describes the activity such as click, view, reply.

Campaign ID has a unique value. This way, you can consider each channel separately. For example, you can have 10 web push channels in the same journey but you can specifically export one of the web push activities.

You can use the journey ID event parameter to select a specific journey. The journey_product_action event considers only the messages that are sent from a journey. For example, the user activities on a bulk web push message are not included in the journey_product_action event.

Channel Code event parameter describes the type of the channel. You can use this to understand from which channel this event is performed.