Technical research - how yesware and email tracking work on technical level

i would like to hire someone to outline the details for how yesware and similar email tracking work. I know the premise at a high level is that they embed a image in the email body and then track when the email is opened by way of knowing the pixel is requested. But I would like to get more granular on the code level. Lets see specifically in the email object what the code looks like. Lets see what the http traffic looks like. Lets figure out if there are any cookies or other things left on the client machines. I am centering this around MS outlook and not gmail so i would want you to install the trial of yesware and then begin the analysis from there. I think to get network traffic you can use things like Charles or Wireshark. my end goal from you is a report on how something like this works from end to end. Starting with the pixel, the location in the email and method used for injecting the pixel, and then the http traffic to and from the server with regard to tracking the email. Want to see how it handles things like replies and forwards and if it leaves its original pixel in place or generates and embeds a new one etc.. Basically I want the entire lifecycle outlined