Note: The Update a Customer Session is the endpoint you will use the most once you finish the integration.
Randomize profileIDs and sessionIDs for each request.
Due to data integrity safety, we always process one session update per profileID at the time. Under normal usage of the API, it's also not expected behaviour that multiple session update API calls for 1 customer enter the system in parallel. If you are sending concurrent sessions with the same profileID they will stack up and the results of the load test will interfere.