If Target's "auto CSS Element Selector" ambiguity is the main cause for concern, you could also consider using the Insert Before/After but then changing the "CSS Element Selector" to your specific #myElementID instead.   

I'm assuming you don't have Adobe Analytics but just to mention that with Adobe Analytics this would be very simple as you could create your own Calculated Metric based on "clicked element & viewed page" and then use that as your Primary Goal.  Without Adobe Analytics, one option would be to trigger...

At a basic level you'll get an array of objects in the offer parameter that's available on success. If it's activities created via VEC, this could contain multiple different modifications (i.e. change button colour, add custom code etc etc) from one or more Target activities. So you'd need logic to ...

It is technically possible to do this but the general recommendation would be to add triggerView() calls via the tag manager or as part of web application code

The easiest way to achieve this would be to set profile attributes (either directly as mbox params or via profile scripts) based on the combination of the user seeing the Target experience and then either dismissing it or logging in again. You could then apply an audience to the activity that exclud...

Yes, the A/B tests would run fine for customers who already provided consent.You could choose to load the library after consent is given, without triggering a page refresh, but that will introduce "flicker" when the default content is replaced by the variant content. So some customers choose to refr...

I've highlighted what can be added to the html template part of the code, in order to close the lightbox based on "Close" button click instead of background click. Note: the original "No Thanks" button is also removed

There isn't any way to do this with an acceptable amount of cross-browser compatibility - more details in this MDN doc

Yes, the updated segment definition will be shared with Target

You can continue to use Customer Attributes with Web SDK data collection, you just need to ensure two things:i) You pass your customerID as part of the XDM identityMap object, more details hereii) You configure your datastream with reference to that same Third Party ID, more details here