Is there anyone who can explain how pattern for sessionID is supposed to work with the delivery API?
https://developers.adobetarget.com/api/delivery-api/
The documentation states that a sessionID is required, but where is this sessionID supposed to come from and how is it generated?
Hi @rrrrrraul
I found similar query thread in forum where it answered. Please check the below links.
On the last point on sessionId generation - sessionId is generated and maintained by the client only.
Let me know if any further question you have.
So it seems the reality is that there is no existing pattern (provided by Adobe) for sessionID instantiation/maintenance for a purely server side solution.
This feels like a bit of a disappointment. There's a requirement for a sessionID, but that sessionID is only provided by the VisitorID service, which only runs in the client. How is this supposed to work for scenarios that are purely server side or IoT, etc. type systems? Does Adobe really not offer any sort of recommended pattern on how to set this up?
You can use any GUID generator and save the value in cookie for 30min
Only update the expiry when you have interaction
After 30 min GUID will be deleted automatically from cookie and you generate another one