ContributionsMost RecentMost LikesSolutionsRe: Whats the exact difference between user_id and target_user_id? HiSyedSa, I am simply trying to understand the logic that is used to propagate these two columns in the Bulk Data API because not all of the action types are following the logic defined in the Bulk data API documentation. In terms of metric, lets say I want to investigate a community user journey and determine how quickly does a user earn certain badges. If I run my command based on user_id, I would not be getting badges.award events in my output. I hope this clarifies the question for you. Whats the exact difference between user_id and target_user_id? Hi everyone, There might be a very straight forward answer to this but what is the exact difference between user_id and target_user_id? I understand the context when the events are message related like user A replying to user B will generate message.publish event where user_id will be A and target_user_id will be B or similarly for kudos.give event. But I also encountered other events where this definition fails such as badges.award event orsolutions.first_solution. where user_id is either null or its of the user the action is taken upon. e.g. user B accepts user A answer as the solution. This triggerssolutions.first_solution The data has both user_id and target_user_id as user A whereas user B triggered this event. Is there a clear definition for all the action types what each of these columns would represent? multiple visits.visit-summary events generated for the same visit_id Hi everyone, During our recent data quality check we encountered the issue of multiple visits.visit-summary events generated for the same visit_ids and created_at timestamp. Upon comparison while some of these events only had event_id as a differentiating factor some also had other features differentiating these two events? visit duration not available for visits.visit-summary events in Bulk Data API v2 Hi there, Does anyone know the reason why some of the 'visits.visit-summary' events might not be propagating anything in the visit_duration? According to the Bulk Data API v2 documentationthat is the sole purpose of this action_type. Also, does anyone know how is the visit_duration generated for single action_type visits such as view? Can someone please help our team figure this out? Duplicated document_id/event_id in the bulk data extraction Hi Everyone, I was working with bulk data extraction and as per documentation, my assumption was document_id (event_id) is unique but our 3-day sample extraction had multiple ids(not rows) that were duplicated. All records(rows) per repeated id were created at the same time and had same action_type (messages.delete in my case) but different message_ids. Is anyone aware of this issue or know what might be causing such a critical issue? Re: Image attachment is a message_type = message with unique conversation_id Thanks Cladius for looking into this. Yeah, the only way I was able to establish the relationship was due to timestamp and action taken and check that across multiple users/posts/messages to validate it. As I understand, since each media file is a message.publish event with its own unique and completely different message and conversation ids I don't think the LIQL query you wrote would be able to establish the one-one relationship because we would not know the message id in the images table. Please let me know if I am missing something here. Image attachment is a message_type = message with unique conversation_id Hi, I came across how events are recorded and reported through Khoros API and was wondering if someone can help me answer couple of questions based on my exploratory work: 1) Why are images recorded as a separate event with their own stand alone unique conversation_id even when they are part of the same reply or initial post to start the thread (attached pics reflect it as an example) 2) How can we connect these image events back to original conversation_id or message_id they are actually linked with? Looking forward to your feedback! Any help understanding this will be highly appreciated. CC:tyw