There are several non-browsing actions I would like to add as events, and possibly evars/props. These actions would occur before and after natural human product usage behavior, but would be automated and sent to Analytics directly from a server with a timestamp and possibly other metadata. Any server calls firing prior to product usage would not have any cookie based information available to them by default - they would obviously lack a native Experience Cloud ID and other default metadata. These automated server calls would only pertain to return visitors, so I suppose I could try to store cookie-based-data on the server to then populate the server call with that data?
Would any of this cause issues? Are there best practices for something like this - server calls fully outside of web browsing behavior? I imagine it would be tough to add this data to any sort of visit or visitor segment due to the lack of Experience Cloud ID