then when you report all revenue will go equally to each offer in the list variable but and you would also be able to tell how many times each one is shown. Then when someone clicks on the offer on the target page put (assuming offer1)
s.events=eventyy // offer clicked event
then you can run a report on list1 with those 2 events and a calculated event called 'offer click thru' eventyy/eventxx shown as a percent with 2 decimal places. and you have a nice report of impressions, clicks and click thru
then as a suggestion also put the offer1 into it's own evar so with a visit expiration and use that evar to do any conversion reports on offer clicks (since you set the evar and eventyy at the same time the conversions click will get credited to that evar also.
This works nicely AS LONG AS your target pages for your offers don't have offers on them also. If so you need to suppress the offer impression list1 and eventxx when this happens or all the offers impressed will get a click event because you will set eventyy. In the overall scheme of things this causes under reporting of the offer impressions but your click thru rates are probably going to be under 10% so it's not a huge issue. And you shouldn't have an offer take a customer to another offer because they could click those offers and bounce out of the first offer you worked so hard to get them to click on.
If you don't want to loose the impressions then you can use list1 for the offers and the evar for the clicks (forget about setting list1 on the target page). Then you can use report builder to mix the 2 reports together and use excel to do the click-thru calculation.
one more thing. list1 with eventxx is 'view through' so you can do conversions based on customers SEEING an offer but not necessarily clicking on it. Sometimes this is important especially if an offer is tied in a targeting platform to specific individuals/traits etc
[if you are using target then you can actually see a lot of this in the target reporting interface]