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 users who entered a specific journey, or the profile IDs of users who received email or web push messages from that journey. You can use two different methods to export the data:
Export Raw User Data API
The Export Raw User Data API prepares the raw user data for all users for all attributes of those requested and for a list of events and the event parameters of these events, including the journey events, exports it into Insider's AWS S3 Bucket, and returns a link to your webhook endpoint as a response.
You can use this API to export raw user data based on the journey events of the respective users.
Use 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 the Filters 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 the 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 the 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, or reply.
| Action Code | Name | Description |
|---|---|---|
| 1 | SEND | Email sent to the user. Email request sent to the Email product by Architect. This might not mean the email has been succesfully sent to the user. |
| 2 | CLICK | User clicked on the email. |
| 3 | CLOSE | User closed the in-app. |
| 4 | VIEW | User opened the application and viewed the in-app. This can be seen as "Delivered" metric in the panel as well. |
| 13 | ELIGIBLE_PROCEED | When user did not see the InApp campaign, the users are proceeded to the next element due to Engagement Timeout. |
| 14 | ELIGIBLE_COUPON_PROCEED | There is an email channel that includes a coupon in it. If user receives that email, this action code is sent. If the channel is configured as "Stop journey when coupons are expired", as the user did not receive the coupon, this action code is not sent. |
| 16 | REPLY | User replied to the WhatsApp message. |
| 18 | CAPPED | User did not receive the message due to frequency capping. |
| 19 | CALL_API_SUCCESS | When a Call an API element is used and when a request is sent successfully to that endpoint, this action code is sent. |
| 20 | CALL_API_FAILED | When a Call an API element is used and the request cannot be sent to that endpoint, this action code is sent. |
| 21 | CALL_API_SENT | For Call an API Performance Monitoring, customer needs to send "send" data to Insider. This action code is sent when customer sends a "send" action to Insider from their outsource endpoints. |
| 22 | CALL_API_OPEN | For Call an API Performance Monitoring, customer needs to send "open" data to Insider. This action code is sent when customer sends an "open" action to Insider from their outsource endpoints. |
| 23 | CALL_API_THROTTLED | If the request is throttled via Request Throttling in Architect > Settings > API Preferences, this action code is sent. |
| 24 | CALL_API_PROCEED | When all requests catch up to the rate limits and fail in all their retries (default retry limit is 5), this action code is sent and users are proceeded to the next element. |
| 25 | GCM_DROPPED | If the Google Ads channel is used and the user drops on the Google Customer Match side, this action code is sent. |
| 26 | CALL_API_SAVED_ACTION_CODE | When the sent request returns a response and that response is saved to the Insider database, this action code is sent. |
| 27 | PRIORITY_EXIT | If the user exits the journey due to Journey Prioritization, this action code is sent. |
| 28 | SMS_DROPPED | When the SMS message could not be transferred to the service provider to be addressed to recipients, this action code is sent. |
| 29 | SMS_UNDELIVERED | When the SMS message cannot be addressed to recipients by the service provider, this action code is sent. |
| 30 | WHATSAPP_OPEN | If the user enabled the Open feature for the WhatsApp messages, this action code is sent when the user opens a WhatsApp message. |
| 32 | SMS_UNSUBSCRIBE | When the user unsubscribes from SMS messaging from Architect communications, this action code is sent. |
| 33 | WHATS_APP_UNSUBSCRIBE | When the user unsubscribes from WhatsApp messaging from Architect communications, this action code is sent. |
| 34 | SKIPPED | When the user is skipped to the next element, this action code is sent. |
| 35 | LIVE_ACTION_PROCEED | When the user arrives at an element which requires a live action, user is kept "On Hold" until that live action is made. If the user does not make that live action within 30 days period, we proceed that user to the next element in the journey. When that user is proceeded to the next element in this case, this action code is sent. |
| 36 | CALL_API_EMPTY_RESPONSE_ACTION_CODE | When the sent request returns a response, but the response is empty, this action code is sent. Being empty means response.data.length === 0. |
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 ent from a journey. For example, the user activities on a bulk web push message are not included in the journey_product_action event.
The Channel Code event parameter describes the type of channel. You can use this to determine which channel this event is performed on.
| Channel Code | Channel Name |
|---|---|
| EM | |
| WP | Web Push |
| SMS | SMS |
| WAB | |
| APP | App Push |
| IA | InApp |
| WC | On-Site |
| AC | Call an API |
| GCM | Google Ads Customer Match |
| FB | Facebook Custom Audiences |