AGT-721: Doc for size, pos, region (#18)

* AGT-721: Doc for size, pos, region

* Afix analytics example

Author: dmytro-po

dev-docs/analytics/intentiq.md

@@ -46,11 +46,8 @@ pbjs.enableAnalytics({
     provider: 'iiqAnalytics',
     options: {
         partner: 1177538,
-        manualWinReportEnabled: false,
-        reportMethod: "GET",
-        adUnitConfig: 1,
+        ABTestingConfigurationSource: 'IIQServer',
         domainName: "currentDomain.com",
-        gamPredictReporting: false
     }
 });
 ```
@@ -91,7 +88,9 @@ originalCpm: 1.5, // Original CPM value.
 originalCurrency: 'USD', // Original currency.
 status: 'rendered', // Auction status, e.g., 'rendered'.
 placementId: 'div-1' // ID of the ad placement.
-adType: 'banner' // Specifies the type of ad served
+adType: 'banner', // Specifies the type of ad served
+size: '320x250', // Size of adUnit item,
+pos: 0 // The following values are defined in the ORTB 2.5 spec
 }
 ```
 
@@ -109,6 +108,8 @@ adType: 'banner' // Specifies the type of ad served
 | status              | String    | Status of the impression. Leave empty or undefined if Prebid is not the bidding platform                                                          | rendered                      | No        |
 | placementId         | String    | Unique identifier of the ad unit on the webpage that showed this ad                                                                               | div-1                         | No        |
 | adType              | String    | Specifies the type of ad served. Possible values: “banner“, “video“, “native“, “audio“.                                                           | banner                        | No        |
+| size              | String    | Size of adUnit item                                                           | 320x250                       | No        |
+| pos              | number    | The pos field specifies the position of the adUnit on the page according to the OpenRTB 2.5 specification                                                           | 0                        | No        |
 
 To report the auction win, call the function as follows:
 

dev-docs/modules/userid-submodules/intentiq.md

@@ -58,6 +58,7 @@ Please find below list of parameters that could be used in configuring Intent IQ
 | params. ABTestingConfigurationSource| Optional | String | Determines how AB group will be defined. Possible values: `"IIQServer"` – group defined by IIQ server, `"percentage"` – generated group based on abPercentage, `"group"` – define group based on value provided by partner. | `IIQServer` |
 | params.abPercentage | Optional | Number | Percentage for A/B testing group. Default value is `95` | `95` |
 | params.group | Optional | String | Define group provided by partner, possible values: `"A"`, `"B"` | `"A"` |
+| params.region  | Optional | String | Optional region identifier used to automatically build server endpoints. When specified, region-specific endpoints will be used. (`gdpr`,`emea`, `apac`) | `"gdpr"` |
 | params.additionalParams | Optional | Array | This parameter allows sending additional custom key-value parameters with specific destination logic (sync, VR, winreport). Each custom parameter is defined as an object in the array. | `[ { parameterName: “abc”, parameterValue: 123, destination: [1,1,0] } ]` |
 | params.additionalParams [0].parameterName | Required | String | Name of the custom parameter. This will be sent as a query parameter. | `"abc"` |
 | params.additionalParams [0].parameterValue | Required | String / Number | Value to assign to the parameter. | `123` |
@@ -83,6 +84,7 @@ pbjs.setConfig({
                 sourceMetaDataExternal: 123456, // Optional parameter
                 chTimeout: 10, // Optional parameter
                 abPercentage: 95, // Optional parameter
+                region: "gdpr", // Optional parameter
                 additionalParams: [ // Optional parameter
                     {
                       parameterName: "abc",