You may run into issues with flickering, read the FAQ related to "flickering" here:https://marketing.adobe.com/resources/help/en_US/target/ov2/c_target-atjs-faq.html

Is there a use case for having more than one adapter?  I can see the need for two if you have one website using Akamai and another site using sftp?  But can one presume most orgs would only require one adapter? Is there another scenario that I might be missing?The whole notion of adapters is somewha...

You can use a data element as well and just return a function or object as another option// data element codefunction myFunction(params){...}return myFunction;var myFunction=_satellite.getVar("dataeleement)("myvalue");

Glad you got that resolved but that's not normally required as that is an optional feature, so there is something specific to your implementation there.You might be able to request they disable the timestamp feature if you don't want to pass it:https://marketing.adobe.com/resources/help/en_US/sc/imp...

It is simple as adding custom logic:if(criteria is met){s.products=";;;;event2= "+_satellite.getVar("hpelement")+""}so this might workif(_satellite.getVar("hpelement")){ s.events= "event2"; s.products=";;;;event2= "+_satellite.getVar("hpelement")+""  s.linkTrackVars="events";  s.linkTrackEvents="eve...

In cases where you need to have a custom bounce rate metric, it would be nice to hide the out of box metric (bounce rate) from Reports and Analytics and Workspace.

reference to "user/Agent" (XML/ POST):https://marketing.adobe.com/developer/documentation/data-insertion/r-supported-tags​Code examples for Java:Data Insertion Sample (Java) | Adobe Developer Connection

If you are using GET then you would likely need to make sure you are sending the user-agent http headerThe "userAgent" field can be used if you using POST / xml.  I believe this is noted in the documentation.

I believe you would pass this via the "userAgent" field or via the HTTP headers if you are sending a POST request.  Using the Android SDK instead might be a better alternative as it takes care of it for you.

I think the rationale of rounding is to make the interface easier to read and being off by a few pennies isn't going to really impact analysis.  I think serialization is more intended for counter metrics, I'm not sure if it was intended for currency metrics, you may want to do a client care request ...