# 3rd Party Tracking # IAS: Campaign Tracking & Process Overview #### **Overview** **Integral Ad Science (IAS)** is an American technology company that provides solutions for the verification of digital advertising. This article provides an overview on workflow and the roles of both agencies and the Eskimi platform in the provision and implementation of IAS trackers: --- #### **Campaign Setup and Optimisation Workflow**
**Steps** **Clarification** **Responsibilities**
**Step 1:** Associate Eskimi DSP and Eskimi Media Partner with the IAS account. \*This step needs to be completed once for each agency's IAS account. If the account was already associated before, move to step 2. With Eskimi now integrated into IAS as a DSP, clients can easily request association with their IAS account for streamlined tracking and optimization. By linking Eskimi DSP and Eskimi media partner with the agency's IAS account, all future tags created for Eskimi DSP will automatically include DSP internal macros. This facilitates tracking metrics per custom segments provided by the DSP, enhancing campaign optimization. To initiate the association process, clients can reach out to[ IAS support](https://manual.eskimi.com/helpcenter.integralads.com) using the following request: **"Hello,** **We would like to associate Eskimi DSP (ID: 77) and Eskimi media partner (ID: 9688) with our team/account."** Client / Agency
**Step 2:** Create IAS Tag \*Ensure that the selected type of tag aligns with campaign goals and supports the measurement of KPIs. For further details on tags, refer to the **[provided article](https://manual.eskimi.com/books/3rd-party-tracking/page/ias-video-and-display-trackers-glossary)**. **Scenario 1:** Tags that do NOT require Eskimi AdServing or future wrapping (display monitoring tags, impression 1x1 pixel tracker video) - Follow the [Tag Manager user Guide](https://helpcenter.integralads.com/article/tag-manager-guide) to prepare the tags. **Scenario 2:** Video tag that requires Eskimi AdServing and future wrapping with IAS tags (Wrapped Video) - Provide mp4 file to Eskimi AdOps at adops@eskimi.com. - Eskimi AdOps Team will upload the mp4 file to the Ad Server. - Eskimi AdOps Team will provide the VAST URI back to you. - Agency utilise the provided VAST URI to prepare wrapped video tags following the - [Tag Manager - User Guide.](https://helpcenter.integralads.com/article/tag-manager-guide) Client / Agency
**Step 3:** Provide information about Brand's KPIs for IAS and Brand requirements To ensure that the campaign effectively meets its KPIs, alignment on KPIs and requirements is crucial. Therefore, the agency/client is responsible for providing such details, including brand safety guidelines and campaign IAS KPIs, to the Ad Ops Team in the email thread together with [other campaign details.](https://manual.eskimi.com/link/16#bkmrk-campaign-requirement)Client / Agency
**Step 4:** Provide IAS trackers to Eskimi AdOps The agency/client is responsible for providing accurate IAS trackers, ensuring their reliability and relevance for campaign KPIs measurement. Client / Agency
**Step 5:** Correct implementation of the tag Eskimi AdOps is responsible for the correct implementation of IAS trackers, maintaining consistency across diverse campaigns Eskimi DSP AdOps
**Step 6:** Setup of daily auto-reporting The agency/client will receive campaign data in IAS reports within 48 hours from the campaign start time, at which point it is possible to export the IAS report. It is the agency's responsibility to either set up auto-reporting or provide consistent reporting containing mandatory information for campaign optimization to the Eskimi AdOps team at adops@eskimi.com. The provided report should include data for the total campaign per day, as well as data per apps/sites or placement\_id macro. For more detailed report information, please refer to the instructions provided in [this article.](https://manual.eskimi.com/link/439#bkmrk-page-title) Client / Agency
**Step 7:** Check reports daily and optimise for IAS KPIs Eskimi offers the capability to optimise campaigns based on client KPIs using insights from IAS reports. Here's an outline of the optimisation process and requirements: 1. The agency receives IAS reports once tags are implemented and the campaign has been live for more than 48 hours. 2. The agency shares the report with required segments with Eskimi AdOps. 3. Eskimi proceeds to optimise the campaign by either excluding low-performing segments or including high-performing segments. These segments typically revolve around apps/sites or placement\_id. Eskimi DSP AdOps
**Step 8:** Troubleshoot \*Applied only when there are significant discrepancies between Eskimi DSP vs IAS report. Upon checking reports and identifying discrepancies, the following actions need to be taken in the established order until the root of the issue is identified: 1. Eskimi AdOps is responsible for checking if the tag was implemented correctly and/or if there's tag duplication. 2. Eskimi AdOps is responsible for exporting the daily campaign report and providing a preview page where tags are firing for future investigation. 3. The Client/Agency is responsible for double-checking and confirming that there were no mistakes in tag creation. 4. The Client/Agency is responsible for contacting IAS support for further investigation Eskimi DSP AdOps / Client / Agency

**Disclaimer: Eskimi's Accountability** - Eskimi assumes no responsibility for discrepancies or issues in measurement capabilities found in IAS reports if they originate from areas under the control of the agency/client. While Eskimi may provide support and suggestions in various scenarios, the ultimate responsibility lies with the agency/client based on designated areas of responsibility. Therefore, Eskimi cannot be held liable for compensation related to such circumstances.

--- #### **FAQ** **Does Eskimi support IAS trackers?** Yes. Eskimi supports monitoring pixel trackers, as well as monitoring creative tags. Eskimi also supports blocking tags that prevent showing the ad visuals in forbidden content. **Do you have the ability to optimise the campaign based on viewability?** Yes. We track viewability metrics in our internal reports, and with this data campaigns can be optimised accordingly. However, it's also important for us to receive IAS reports to monitor any discrepancies and optimise the viewability of IAS data, as the measurement technologies are slightly different. **Do you have the ability to optimise the campaign based on brand safety?** Yes. To optimise, we'll need a report from IAS based on which optimisation will be done. Because Eskimi isn't measuring Brand Safety KPIs internally. **How can we track viewability with IAS trackers in banner and video campaigns?** Video IAS measurement - In order to capture Viewability data when running a VAST campaign, each video must be wrapped within an IAS tag. This tag, within IAS, is referred to as Multimedia Tag Monitoring. It's important to note that employing this tracker might result in the exclusion of certain traffic, as only video traffic compatible with VPAID/OMID will qualify for viewability measurement. Display IAS measurement - Viewability data can be gathered by implementing the tracker in the form of a Javascript tag. **How Eskimi can optimise IAS KPIs?** We need daily reports from IAS, based on which we will create a black-list/ white-list and apply them to the campaign as optimisation. [Here](https://manual.eskimi.com/books/3rd-party-tracking/page/ias-report-builder-agency-account) are the instructions about expected segments in the IAS report. # 3rd Party Trackers #### **What are 3rd party trackers?** In the Eskimi platform, “3rd Party Tags” are any *externally-provided code* designed to *monitor, record, or track the performance* of Eskimi campaigns. 3rd Party Tags are typically HTML tags (*IMG pixels* or *Javascript tags*) that are implemented by Eskimi on a publisher’s page when your ad is displayed, seen, or clicked. These tags are used to transfer data to other platforms, outside of Eskimi’s proprietary dashboard. --- #### **What are the types of 3rd party trackers?** **3rd party pixels (image):** A tracking pixel is a tool used to track ad impressions. It consists of a piece of code inserted into the creative. This code causes a 1x1 transparent image to track with the ad. **How to validate that you have a 3rd party pixel (image):** - Be 1x1 pixels (they come in a URL format) - Use a clickable pixel/image tag rather than code such as JavaScript tags - Only use macros including Cachebuster, IP, User Agent (UA), Timestamp, or Episode ID. **1x1 pixel examples:** ``` https://ad.doubleclick.net/ddm/trackimp/N705418.1727343ESKIMI.COM/B28985587.353603375;dc_trk_aid=545020201 dc_trk_cid=182974786;ord= [timestamp];dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;tfua=;gdpr=${GDPR};gdpr_consent=${GDPR_CONSENT_755};ltd=? ``` ``` https://track.adform.net/adfserve/?bn=60266225;1x1inv=1;srctype=3;ord={cachebuster} ``` **Practical validation:** You can always Paste the URL into a browser to make sure it loads properly. The browser will load an all black page with a tiny dot of white in the center. If the browser loads something else you might be using a JavaScript tag, not an image pixel. [![ezgif.com-gif-maker-2 copy.gif](https://manual.eskimi.com/uploads/images/gallery/2022-12/WYlBeSXXfPbPUs4E-ezgif-com-gif-maker-2-copy.gif)](https://manual.eskimi.com/uploads/images/gallery/2022-12/WYlBeSXXfPbPUs4E-ezgif-com-gif-maker-2-copy.gif) **3rd Party JavasScript:** Javascript tags that allow advertisers to capture more information rather than only impressions. JS trackers are the backbone of 3rd party companies like IAS, MOAT, DV etc. **How to validate that you have a 3rd party JavaScript:** - The tag will be in a <script><script> - It will be a code rather than a clickable pixel/image - Allow various macros. Eskimi macros have to be implemented into the tag (ex.: {creative\_id}, {site\_id} etc.). **Any 3rd party macros will not be supported and Eskimi system will not be able to fetch the data**. *(Eskimi macros can be found in campaign setup page, under click URL parameters).* **JavaScript tag examples:** ```java ``` ```javascript ``` ``` https://z.moatads.com/heinekenkheskimidisplay418936584220/moatad.js#moatClientLevel1={campaign_id}&moatClientLevel2= {site_id}&moatClientLevel3={creative_title}&moatClientLevel4={creative_size} ``` **Practical validation:** You can always Paste the URL from the Javascript into a browser to make sure it loads properly. The browser should fetch more information from the tag. If the browser doesn't bring any information, then you might be not using a JavaScript tag. **[![ezgif.com-gif-maker-2.gif](https://manual.eskimi.com/uploads/images/gallery/2022-12/cMX39ttijNfSLgww-ezgif-com-gif-maker-2.gif)](https://manual.eskimi.com/uploads/images/gallery/2022-12/cMX39ttijNfSLgww-ezgif-com-gif-maker-2.gif)** **Keep in mind:** - The tag should be implemented exactly as you got it from the 3rd party vendor. - There are supply limitations as there are publishers that will not support JS tags on their pages. **Note:** Pixels could be implemented as pixels or as HTML/JavaScript tags. In the provided example: ```javascript ``` This code snippet is HTML/JavaScript code. However, it contains an HTML img tag, indicating that the URL within it serves as an image. There are two options for implementation: 1. Extract the URL from the tag (`https://gdeua.hit.gemius.pl/_{CACHEBUSTER}/redot.gif?id=nAE7_Yw7MDfkVxcFmlFmC2ZWDfXZJOdExNe22B4YXQz.U7/fastid=exkyeeteovzqevebeouudwxytsob/stparam=odcppjdoqy/nc=0/gdpr=0/gdpr_consent=`) and set it up as a Pixel tracker. Ensure that your tracker is secure (HTTPS). 2. Take the entire code snippet (``) and set it up as an HTML/JavaScript code tracker. **Important**: - HTTPS impression trackers must always be secure SSL (HTTPS). For click URLs, it is possible to use a non-secure tracker. - The conventional approach for handling pixel tags of this type, which are image files, is to add them as pixel tracking tags rather than HTML/JS tags. --- **How to implement & validate 3rd party trackers?** **3rd party pixels (image):** There are two ways how image pixels can be created: a) during campaign setup in the creative section; b) at the campaign approval level under **Custom impression tracking**. 1\. Choose **Pixel** in the dropdown section under *custom impression tracking*. 2\. Paste **only** the URL of the tag *1x1 pixel*. 3\. **Save** your campaign. 4\. Go to the **preview page** of the campaign. 5\. Click the right button of your mouse, navigate yourself to **Inspect** section*.* 6\. Search for your tag in the **Network** section. Paste the domain in the search bar. *The flow works the same for **display** and **video** advertising.* **3rd party JavaScript:** There are two ways how image pixels can be created: a) during campaign setup in the creative section; b) at the campaign approval level under **Custom impression tracking**. 1\. Choose **JavaScript** in the dropdown section under *custom impression tracking*. 2\. JavaScript must be pasted in a <script><script>. If the prodided JavaScript isn't in a <script><script>, contact 3rd party tag owners to understand if the tag was properly provided and how it should be implemented. 3\. **Save** your campaign. 2\. Go to the **preview page** of the campaign. 3\. Click the right button of your mouse, navigate yourself to **Inspect** section*.* 4\. Search for your tag in the **Network** *section*. Paste the domain in the search bar. *The flow works the same for **display** and **video** advertising.*

The preview page can be shared with the 3rd party platform for both 1x1 pixels and JavaScript tags. So they would be able to verify that the tags are firing properly.

--- #### **Macros** Most of the time both pixel and HTML/JS tags come with macros that allows Eskimi to send relevant parameters to another server. It is essential to make sure that all the macros in the tag are supported by Eskimi. Macros have to be changed to a corresponding Eskimi macros. For example the client shared DCM trackers which contains unsupported macros such as ${GDPR} and ${GDPR\_CONSENT\_755}: ```javascript ``` By leaving these macros unchanged we might face discrepancies between two servers as the GDPR consent will not be sent to the 3rd party provider. Some 3rd party providers will not be able to render their tracker if the consent is not their. To avoid discrepancies these macros must be changed into corresponding Eskimi macros. See example below: ```javascript ``` --- #### **Why to use 3rd party trackers?** **Ad Verification** Send live campaign data to your 3rd party tracking platform. Validate brand safety, numbers of impressions, viewable impressions and clicks. **Attribution Observe the whole user journey, not just the last click. Measure the effectiveness of Eskimi on users that have seen your ads (and have not necessarily clicked them). **Re-engagement** Identify users that have engaged with your Eskimi ads and remarket them on other platforms. --- #### **Limitations** 1\. **Majority of image pixels allow to track impressions only**. They don't provide comprehensive information about brand safety, IVT, viewability like JavaScript tags. We recommend to check with 3rd party providers about limitations and capabilities of their tracking. 2\. **VAST video support both image and JavaScript trackers**. However, the same image pixel limitations will be applied. Also, to enable JavaScript tracking for VAST video, the VAST URI will have to be wrapped into a JavaScript tag by the 3rd party provider (MOAT, IAS). 3\. Some of the device browsers may fail to properly fire 3rd party trackers. One of them is **Android WebView (Dalvik)**. Adman trackers don't track this browser, while trackers like IAS may result in 3X higher discrepancy in comparison with the regular Android WebView. To reduce the possible discrepancy we recommend removing Android WebView (Dalvik) when 3rd party trackers are being used. [![Screenshot 2023-07-13 at 13.25.29.png](https://manual.eskimi.com/uploads/images/gallery/2023-07/scaled-1680-/ZEeSZ8EzVU4lVYd7-screenshot-2023-07-13-at-13-25-29.png)](https://manual.eskimi.com/uploads/images/gallery/2023-07/ZEeSZ8EzVU4lVYd7-screenshot-2023-07-13-at-13-25-29.png) # 3rd Party Verification Platforms # Exploring Banner/IBV/Native Integrations within 3rd Party Verification Platforms ##### **Introduction** In the dynamic landscape of digital advertising, where capturing and retaining users' attention is paramount, the role of third-party verification platforms has become increasingly vital. Advertisers and publishers alike have sought ways to ensure the transparency, viewability, and brand s afety of their online campaigns. However, beyond their fundamental functions lies a lesser-known yet innovative aspect that is pois ed to revolutionise the industry - **the integration of creative wrapping**. In this article, we delve into the practical implications how Banners/IBV/Native ads executed through Eskimi should be wrapped into a 3rd party verification platform. --- ##### **Banner, IBV, Native Wrapping Process for Ad Operations Team** 1. Begin by uploading the client's creatives through the creative setup page. 2. Set up a campaign using the newly uploaded creatives. 3. Access the preview page of the campaign. 4. Right-click on the creative and select "Inspect Element", or navigate to the developer's tools. [![Untitled design-5.png](https://manual.eskimi.com/uploads/images/gallery/2021-03/scaled-1680-/untitled-design-5.png)](https://manual.eskimi.com/uploads/images/gallery/2021-03/untitled-design-5.png) 5\. Locate the `
**[![Untitled design-6.png](https://manual.eskimi.com/uploads/images/gallery/2021-03/scaled-1680-/untitled-design-6.png)](https://manual.eskimi.com/uploads/images/gallery/2021-03/untitled-design-6.png)** 6\. Replace `"dsp.eskimi.com"` in the image file URL with `"dsp-media.eskimi.com"`. This step is crucial to ensure the proper functioning of the dashboard when re-uploading the wrapped creatives. 7\. Place the modified image file into a JavaScript tag, following the format: ``` ``` 8. Adjust the **width** and **height** attributes according to the specific creative size. 9. Repeat the above steps for all the creatives associated with the campaign. 10. Review the creatives either by yourself or by seeking input from your colleagues. 11. Ensure your final file resembles the following example: [Example Link](http://bit.ly/3v1OSqd) 12. Share the completed Excel file containing the wrapped creatives with the 3rd party platform team. 13. The 3rd party support team will integrate the shared tags into their own tag, which may take between 1-3 working days depending on the platform. 14. Once you receive the wrapped tags, upload them to the creative setup and launch the campaign according to the client's requirements. # Exploring Rich Media Integrations within 3rd Party Verification Platforms ##### **Introduction** In the dynamic landscape of digital advertising, where capturing and retaining users' attention is paramount, the role of third-party verification platforms has become increasingly vital. Advertisers and publishers alike have sought ways to ensure the transparency, viewability, and brand s afety of their online campaigns. However, beyond their fundamental functions lies a lesser-known yet innovative aspect that is pois ed to revolutionise the industry - **the integration of creative wrapping**. In this article, we delve into the practical implications how Rich Media ads executed through Eskimi should be wrapped into a 3rd party verification platform. --- ##### **Rich Media Wrapping Process for Ad Operations Team** 1. Begin by uploading the Rich Media zip through the creative setup page. 2. Copy **all the JavaScript** which was updated with necessary Eskimi trackers. [![Screenshot 2023-06-07 at 15.57.07.png](https://manual.eskimi.com/uploads/images/gallery/2023-06/scaled-1680-/jRSrbnGL5OogseGS-screenshot-2023-06-07-at-15-57-07.png)](https://manual.eskimi.com/uploads/images/gallery/2023-06/jRSrbnGL5OogseGS-screenshot-2023-06-07-at-15-57-07.png) 3\. Paste the JavaScript code to and Excel or notepad. 4\. Repeat the above steps for all the creatives associated with the campaign. 5\. Review the creatives either by yourself or by seeking input from your colleagues. 6\. Share the completed Excel file containing the wrapped creatives with the 3rd party platform team. 7\. The 3rd party support team will integrate the shared tags into their own tag, which may take between 1-3 working days depending on the platform. 8\. Once you receive the wrapped tags, upload them to the creative setup and launch the campaign according to the client's requirements. # IAS: Video and Display Trackers & Glossary #### **Trackers for Video:**
**IAS Solution****Explanation****Requirements****Measure Viewability****Measure Invisible URLs****Measure Impressions** **Measure Brand Safety**
Multimedia Tag Monitoring (Wrapped Video)Video tracking tag that will work across desktop, CTV, mobile & in-app. Can measure viewability, set to not blockRequires a VPAID or OMID player/publisher support & 3rd party ad servingYesYesYesYes
Multimedia Tag Blocking (Wrapped Video)Video tracking tag that will work across desktop, CTV, mobile & in-app. Can measure viewability, set to blockRequires a VPAID or OMID player/publisher support & 3rd party ad servingYesYesYesYes
Unified Video 1x1 PixelVideo tracking tag that will work across desktop, CTV, mobile & in-app. Cannot measure viewability or blockRequires a VAST player & 3rd party ad servingNoNoYesYes
Ensuring accurate measurement of viewability and other metrics with IAS requires using **Wrapped Video Creative**. This is because certain metrics, such as those measured by JavaScript (JS), cannot be captured using the traditional 1x1 pixel. At the same time, the VAST video format also doesn't support a separate JS impression tracker, so Multimedia Tag Monitoring is necessary, wrapping the video within the Creative Tag for accurate measurement. However, in cases where the goal is to measure pure impressions to verify discrepancies, a 1x1 pixel (impression tracker) is sufficient. This tracker, known as "**Unified Video Pixel**" can be employed for such purposes. Additionally, It's essential to use VPAID/OMID-compatible video inventory to enable IAS to measure viewability effectively. However, remember that inventory compatible with VPAID/OMID may limit the overall supply available to the campaign. --- #### **Trackers for Display:**
**IAS Solution****Explanation****Measure Viewability****Measure Invisible URLs****Measure Impressions** **Measure Brand Safety**
Blocking Creative TagDisplay tags with blocking. Requires JS supportYesYesYesYes
Monitoring JS Display tags without blocking. Requires JS supportYesYesYesYes
Monitoring 1x1 pixel Display tags without blocking.NoNoYesYes
Viewability measurements are possible with JavaScript tags only. However, some publishers or exchanges might not support this format. In such cases, viewability measurement by IAS wouldn't be possible. Nevertheless, 1x1 monitoring pixels can be utilized for display creatives. By using this type of tracker, IAS would be able to measure impressions to verify the total amount of served impressions. --- #### **IAS Articles:** [**User Guide - Tag Manager** ](https://helpcenter.integralads.com/article/tag-manager-guide)- a comprehensive guide on how to create different Tags using an IAS self-service account **[Multimedia Tag](https://helpcenter.integralads.com/article/uvt-guide) -** overview of Multimedia tag capabilities, it is creation and limitations. [**IAS Tag Structure** ](https://helpcenter.integralads.com/article/tag-structures)- overview of the different structures of IAS Tags. --- #### **Glossary:**
TermDefinition
Total Tracked AdsThe number of ads IAS processed.
Eligible Ads For Viewability MeasurementThe number of all unblocked ads that are invalid traffic (IVT) free and served in a JavaScript environment where Viewability measurement is possible.
Measured AdsThe total number of ads in the campaign with all detected invalid traffic removed, where IAS was able to collect viewability data. In some ad environments, technical limitations can prevent ads from being measured for viewability or audibility by IAS.
Measured Rate (out of Ads)The percentage of Measured Ads out of Eligible Ads for Viewability or Audibility Measurement.
Viewable ImpressionsThe number of unblocked viewable impressions in the campaign with all detected invalid traffic removed, where at least 50% of the ad was in view for 1 continuous second for display (2 continuous seconds for video).
Viewable Rate (out of measured ads)The percentage of Viewable Impressions (at least 1 pixel of the creative rendered on screen; 50% in view for 1 continuous second - display; 2 continuous seconds - video; a 30% or more rule applies to large creatives that are at least 242,500 pixels.) out of unblocked Measured Ads with all detected invalid traffic removed.
Eligible Ads for Invalid Traffic Detection Excludes all ads where signals to make an IVT determination are missing. Note: This metric has been updated to no longer include test impressions, which was previously reported as GIVT and represents a trace amount of overall GIVT impressions. Test impressions will still be included in our calculation for Total Tracked Ads.
Eligible Rate For Invalid Traffic DetectionThe percentage of Eligible Ads for Invalid Traffic Detection, out of all ads IAS processed (Total Tracked Ads).
General Invalid Traffic (GIVT) AdsTraffic that failed to meet ad quality criteria filtered through and caught by known IP and bot lists (ex: Google web crawlers).
General Invalid Traffic (GIVT) RateThe percentage of ads that IAS detected as GIVT, out of all ads processed by IAS. Traffic that failed to meet ad quality criteria filtered through and caught by known IP and bot lists (ex: google web crawlers).
Sophisticated Invalid Traffic (SIVT) AdsTraffic that failed to meet proprietary and sophisticated invalid traffic detection criteria. Examples of failed traffic can include: hijacked devices, ad tags, or creative; adware; malware; and misappropriated content.
Sophisticated Invalid Traffic RatePercentage of traffic that failed to meet proprietary and sophisticated invalid traffic detection criteria out of Total Tracked Ads.
Bots (SIVT) AdsThe number of ads that IAS detected as bots. A malicious software application that runs automated tasks over the internet, usually to make a profit by falsely mimicking real human activity.
Bots (SIVT) RateThe percentage of ads that IAS detected as bots, out of all ads processed by IAS. A malicious software application that runs automated tasks over the internet, usually to make a profit by falsely mimicking real human activity.
Domain Spoofing (SIVT) AdsAds that are low quality inventory disguised as high-quality legitimate-sites, or send incorrect referrer information to hide their identity.
Domain Spoofing (SIVT) RateThe percentage of ads that are low quality inventory disguised as high-quality legitimate-sites or send incorrect referrer information to hide their identity, out of all ads processed by IAS.
Hidden Ads (SIVT)The number of ads that IAS detected as Hidden Ads (SIVT). Ads that have no chance of ever being seen by humans. Types of hidden ads include: pixel stuffing, ad stacking, ads clipped by iframes, zero opacity ads, off-page ads, ad truncation, and hidden ads embedded in ads.
Hidden Ads (SIVT) RateThe percentage of ads that IAS detected as Hidden Ads (SIVT), out of all ads processed by IAS. Ads that have no chance of ever being seen by humans. Types of hidden ads include: pixel stuffing, ad stacking, ads clipped by iframes, zero opacity ads, off-page ads, ad truncation, and hidden ads embedded in ads.
Reduced Value Inventory (RVI) AdsTraffic which IAS flagged as being generated in a way counter to the advertiser’s interests. Possible examples include the use of incentivized browsing and "proxy servers".
Reduced Value Inventory Rate The percentage of Reduced Value Inventory (RVI) Ads, out of all ads processed by IAS.
Incentivized Browsing (RVI) AdsThe act of interacting with ads for payment or benefits, usually not by an advertiser-targeted audience
Incentivized Browsing (RVI) RateThe percentage of ads that IAS detected as Incentivized Browsing (RVI), out of all ads processed by IAS. The act of generating traffic and/or engaging with ads on ad-supported sites by human users, in exchange for payment of some other, typically financial, benefit.
Proxy Server (RVI) AdsThe number of ads that IAS detected as Proxy Servers (RVI). A computer network service that uses indirect network connections to sometimes enable bots to hide their true identity and location.
Proxy Server (RVI) Rate The percentage of ads that IAS detected as Proxy Servers (RVI), out of all ads processed by IAS. A computer network service that uses indirect network connections to sometimes enable bots to hide their true identity and location.
Total Eligible Ads For Brand SafetyThe number of ads IAS processed across all publishers that have opted into brand safety measurement. This metric includes all detected invalid traffic (General Invalid Traffic and Sophisticated Invalid Traffic).
Passed AdsThe number of ads that IAS passed for invalid traffic, brand safety, custom keywords, custom URL, geo, invisible URL, or target language.
Pass RateThe percentage of ads that IAS passed for invalid traffic, brand safety, custom keywords, custom URL, geo, invisible URL, or target language, out of all ads IAS processed.
Failed AdsThe number of failed ads for invalid traffic, brand safety, custom keywords, custom URL, geo, invisible URL, target language, or your Brand suitability profile. These ads may or may not be blocked.
Fail RateThe percentage of ads that IAS failed for invalid traffic, brand safety, custom keywords, custom URL, geo, invisible URL or target language, out of all ads IAS processed. These ads may or may not be blocked.
Brand Safety Risk AdsThe number of ads that didn't meet your brand safety threshold.
Brand Safety Risk %The percentage of ads that didn't meet your brand safety thresholds, out of Total Eligible Ads for Brand Safety.
Brand Suitability Failed AdsAds marked as failed for your Brand suitability profile.
Brand Suitability Fail %Ads marked as failed for your Brand suitability profile, out of Total Eligible Ads for Brand Safety.
Custom URL/App Exclusion List AdsThe number of ads marked as failed for custom URL/App Exclusion List.
Custom URL/App Exclusion List Rate The percentage of eligible ads marked as failed for your custom URL lists, out of Total Eligible Ads for Brand Safety.
Out of Geo AdsThe number of ads marked as failed for being served outside of the target geo .
Out of Geo Rate The percentage of ads marked as failed for being served outside of the target geo, out of Total Eligible Ads for Brand Safety.
Invalid Traffic AdsThe number of ads that IAS detected as invalid traffic.
Invalid Traffic Rate The percentage of ads that IAS detected as invalid traffic, out of all ads IAS processed.
Invisible URL AdsThe number of ads marked as failed because IAS did not detect the top level page where the ad was served.
Invisible URL %The percentage of ads marked as failed because the top level URL was undetectable, out of Total Eligible Ads for Brand Safety.
Target Language Mismatch AdsThe number of ads marked as failed for language-targeting.
Target Language Mismatch % The percentage of ads marked as failed for language targeting, out of Total Eligible Ads for Brand Safety.

A whole Glossary with updated info is available in the IAS HelpCenter -[ **check here**](https://helpcenter.integralads.com/article/advertiser-metrics-glossary) for more info

# IAS: Report Builder - Agency account #### **Introduction** In this article it is described regarding auto-report set up from IAS (Integral Ad Sience) vereficator. Both reports are needed in case to be able to proceed with needed optimisation of campaign. Which is crucial for reaching good campaign KPIs and troubleshoot on data descripency that usually appears due to different methodology of measurement between DSP and 3rd party verification. [Total report per campaign](https://manual.eskimi.com/link/439#bkmrk-total-campaign-repor) - this report is needed for the evaluation of campaign performance, and troubleshoot discrepancy of measured stats. Report should include campaign or/and placement as main segment split. It also should include all important KPIs and be established for period from the start till the end day of campaign. [Report per domains/apps](https://manual.eskimi.com/link/439#bkmrk-site%2Fapps-report-ste) - this report is needed for KPIs evaluation across different sites/apps and helps to optimise campaign for reaching better KPIs by excluding site and apps with lower performance. This report should include dates, campaigns and show last 30 days stats.

Keep in mind that it is possible to prepare auto-report only when campaigns measured some ads. Otherwise, you will not able to select needed campaigns for your report. Therefore, Plan to prepare auto-report on the 3rd day after campaigns started, as it takes up to 48h for IAS to collect data on their side.

--- #### **Total campaign report step-by-step set up guide** 1\. First of all open your IAS account and go to "Build New Report" menu ## **[![Screenshot 2023-08-11 at 17.23.23.png](https://manual.eskimi.com/uploads/images/gallery/2023-08/scaled-1680-/aiuTTFs5HpvU3DCf-screenshot-2023-08-11-at-17-23-23.png)](https://manual.eskimi.com/uploads/images/gallery/2023-08/aiuTTFs5HpvU3DCf-screenshot-2023-08-11-at-17-23-23.png)** 2\. In this menu you need to establish report name (keep the name clear possible for yourself and Eskimi DSP team). For "Data Range" menu select "Campaign to Date: From Last Active Campaign" and scroll down till the "Report type" section. ## **[![Screenshot 2023-08-11 at 17.23.33.png](https://manual.eskimi.com/uploads/images/gallery/2023-08/scaled-1680-/o6R9Takg86GbU9rY-screenshot-2023-08-11-at-17-23-33.png)](https://manual.eskimi.com/uploads/images/gallery/2023-08/o6R9Takg86GbU9rY-screenshot-2023-08-11-at-17-23-33.png)** 3\. In Report Type section you will need to create 4 different sheets as it is shown on the screen below. You can name sheets accordingly "Daily Campaigns", "Total Campaigns", "Daily Placements", "Total Placements". Each sheet will be presented in same xls file which will be generated automatically. Start with one sheet creation, select "Performance Report" and scroll down till "Dimensions" section.

**Tip 1:** Create 1 sheet at first, for example "Daily Campaigns". And move to next steps. Later on the sheet might be copied so it will simplify process of creation as you will not need go from the scratch on all next steps for each separate sheet.

**Tip 2:** If you are using separate tracker per each placement, then create reports per placements as well, so it will be 4 sheets in total. However if you are measuring performance per campaign level, it would be enough to create only 2 sheets which is "Daily campaigns" and "Total campaigns"

## **![Screenshot 2023-08-11 at 17.34.25.png](https://manual.eskimi.com/uploads/images/gallery/2023-08/scaled-1680-/G9vJAQpCiuwIqthU-screenshot-2023-08-11-at-17-34-25.png)** 4\. For the sheet "Daily Campaigns" for Dimensions section you need to select "Media Partners", "Campaigns", "Dates". Select dimensions in same order. Also once dimensions are selected specify media partners (it should be Eskimi), also specify campaigns (you need to select campaigns that you want to include for reporting", and as last step select "by day" for Date dimension. In this case IAS will generate report per selected campaign with daily split. Once this done scroll down till the section "Minimum Total Tracked Ads Filter". ## **[![Screenshot 2023-08-11 at 17.25.42.png](https://manual.eskimi.com/uploads/images/gallery/2023-08/scaled-1680-/k2YQcsR1BxJuq0zF-screenshot-2023-08-11-at-17-25-42.png)](https://manual.eskimi.com/uploads/images/gallery/2023-08/k2YQcsR1BxJuq0zF-screenshot-2023-08-11-at-17-25-42.png)** 5\. In the "minimum total tracked ads filter" section you need to select "all tracked ads". In this case all measured impressions for dimensions you selected above will be presented in the report. Once selected you need scroll down till "Metric" section ## **[![Screenshot 2023-08-11 at 17.26.01.png](https://manual.eskimi.com/uploads/images/gallery/2023-08/scaled-1680-/Zzv8q3iWq0hTvzMx-screenshot-2023-08-11-at-17-26-01.png)](https://manual.eskimi.com/uploads/images/gallery/2023-08/Zzv8q3iWq0hTvzMx-screenshot-2023-08-11-at-17-26-01.png)** 6\. In "Metrics" section you need to enable metrics which are important to for campaign analysis. Below you can see our suggestions regarding metrics that should be selected. Please include them to any report you are creating for Eskimi team. In case you would like to know definition of the metrics, please refer to [article prepared by IAS: "Advertise Metrics Clossary"](https://helpcenter.integralads.com/topics/advertiser-agency/advertiser-metrics-glossary/advertiser-metrics-glossary)
[![Screenshot 2023-08-11 at 17.30.11.png](https://manual.eskimi.com/uploads/images/gallery/2023-08/scaled-1680-/OCpcynkjkRSDywKD-screenshot-2023-08-11-at-17-30-11.png)](https://manual.eskimi.com/uploads/images/gallery/2023-08/OCpcynkjkRSDywKD-screenshot-2023-08-11-at-17-30-11.png)![Screenshot 2023-08-11 at 17.30.27.png](https://manual.eskimi.com/uploads/images/gallery/2023-08/scaled-1680-/KRpvCmA4XSDckLJ9-screenshot-2023-08-11-at-17-30-27.png)[![Screenshot 2023-08-11 at 17.30.34.png](https://manual.eskimi.com/uploads/images/gallery/2023-08/scaled-1680-/oXYF5Z4KdfcDXo6M-screenshot-2023-08-11-at-17-30-34.png)](https://manual.eskimi.com/uploads/images/gallery/2023-08/oXYF5Z4KdfcDXo6M-screenshot-2023-08-11-at-17-30-34.png)
![Screenshot 2023-08-13 at 13.28.00.png](https://manual.eskimi.com/uploads/images/gallery/2023-08/scaled-1680-/hICQcPIm7OvgUIBi-screenshot-2023-08-13-at-13-28-00.png)[![Screenshot 2023-08-11 at 17.31.00.png](https://manual.eskimi.com/uploads/images/gallery/2023-08/scaled-1680-/zuIdcc4L7XxUN1ik-screenshot-2023-08-11-at-17-31-00.png)](https://manual.eskimi.com/uploads/images/gallery/2023-08/zuIdcc4L7XxUN1ik-screenshot-2023-08-11-at-17-31-00.png)
[![Screenshot 2023-08-11 at 17.30.45.png](https://manual.eskimi.com/uploads/images/gallery/2023-08/scaled-1680-/rvevlQfvASNX0yDf-screenshot-2023-08-11-at-17-30-45.png)](https://manual.eskimi.com/uploads/images/gallery/2023-08/rvevlQfvASNX0yDf-screenshot-2023-08-11-at-17-30-45.png)
7\. At this step you can move back to the[ 3rd point](https://manual.eskimi.com/link/439#bkmrk-3.-in-report-type-se) and duplicate the sheet, in this case all settings will be already preselected and will not require additional selection from scratch. Once new sheets are duplicated, you need to rename them accordingly.[![Screenshot 2023-08-11 at 17.34.29.png](https://manual.eskimi.com/uploads/images/gallery/2023-08/scaled-1680-/ksZXnEXk09ny8eup-screenshot-2023-08-11-at-17-34-29.png)](https://manual.eskimi.com/uploads/images/gallery/2023-08/ksZXnEXk09ny8eup-screenshot-2023-08-11-at-17-34-29.png) 8\. After duplicating sheets open the one you want to adjust 1 by 1. At this step you need to change dimensions per each sheet. The sheet called "Total Camapaigns" should have selected dimensions as on screen below. Once dimension selected move to another sheet. Keep in mind that you also need to select media partner, and campaigns that you want to include in the report. ## **[![Screenshot 2023-08-11 at 17.32.04.png](https://manual.eskimi.com/uploads/images/gallery/2023-08/scaled-1680-/5sCdlJQbMv729FGG-screenshot-2023-08-11-at-17-32-04.png)](https://manual.eskimi.com/uploads/images/gallery/2023-08/5sCdlJQbMv729FGG-screenshot-2023-08-11-at-17-32-04.png)** 9\. In case you set up pixel per each creative (a.k. placement) you can add additional report per placement segment. In this case the sheet called "Daily Placements" should consist dimensions as on screen below. Keep in mind that you also need to select media partner, and campaigns that you want to include in the report. ## **[![Screenshot 2023-08-11 at 17.32.26.png](https://manual.eskimi.com/uploads/images/gallery/2023-08/scaled-1680-/kasPxcEwqTe5I8Pn-screenshot-2023-08-11-at-17-32-26.png)](https://manual.eskimi.com/uploads/images/gallery/2023-08/kasPxcEwqTe5I8Pn-screenshot-2023-08-11-at-17-32-26.png)** 10\. Open sheet "Total placements" and select following dimensions. Keep in mind that you also need to select media partner, and campaigns that you want to include in the report. ## **[![Screenshot 2023-08-11 at 17.32.45.png](https://manual.eskimi.com/uploads/images/gallery/2023-08/scaled-1680-/BUztKZxrwgZvTDQO-screenshot-2023-08-11-at-17-32-45.png)](https://manual.eskimi.com/uploads/images/gallery/2023-08/BUztKZxrwgZvTDQO-screenshot-2023-08-11-at-17-32-45.png)** 11\. Once all set up is done scroll the page till the end and enter email details and frequency for the auto reporting. It is also possible to enter multiple emails who need to get the settled up report. Email Details - enter "adops@eskmi.com" Frequency - select "daily" and establish a period from the campaign first day till the end of last campaign. ## **[![Screenshot 2023-08-11 at 17.31.34.png](https://manual.eskimi.com/uploads/images/gallery/2023-08/scaled-1680-/ULLE5UBnCjALWlLp-screenshot-2023-08-11-at-17-31-34.png)](https://manual.eskimi.com/uploads/images/gallery/2023-08/ULLE5UBnCjALWlLp-screenshot-2023-08-11-at-17-31-34.png)** 12\. Once everything is done the button "save and run" will be active, so you need to press on it to activate the report. [![Screenshot 2023-08-14 at 10.23.47.png](https://manual.eskimi.com/uploads/images/gallery/2023-08/scaled-1680-/HfQEUhl8B1QRrCyi-screenshot-2023-08-14-at-10-23-47.png)](https://manual.eskimi.com/uploads/images/gallery/2023-08/HfQEUhl8B1QRrCyi-screenshot-2023-08-14-at-10-23-47.png) 13\. If everything set up correctly, the receiver(s) will start getting daily report from IAS. The example of IAS email presented below.[![Screenshot 2023-08-14 at 10.54.07.png](https://manual.eskimi.com/uploads/images/gallery/2023-08/scaled-1680-/WA4Od92o6R9aBdrR-screenshot-2023-08-14-at-10-54-07.png)](https://manual.eskimi.com/uploads/images/gallery/2023-08/WA4Od92o6R9aBdrR-screenshot-2023-08-14-at-10-54-07.png) --- #### **Site/Apps report step-by-step set up guide** 0\. If you already set up Total campaign report, you can go to Custom Report menu and duplicate the settings from previously created report. In this case most of the settings will be pre-selected and will require slight adjustments (you can follow this guide further to see the adjustment that need to be done). Otherwise you will need to create the report from scratch, where you can follow step-by-step process described below. [![Screenshot 2023-08-14 at 10.32.50.png](https://manual.eskimi.com/uploads/images/gallery/2023-08/scaled-1680-/zT4IDFGrluRAQPAG-screenshot-2023-08-14-at-10-32-50.png)](https://manual.eskimi.com/uploads/images/gallery/2023-08/zT4IDFGrluRAQPAG-screenshot-2023-08-14-at-10-32-50.png) 1\. First of all open your IAS account and go to "Build New Report" menu ## **[![Screenshot 2023-08-11 at 17.23.23.png](https://manual.eskimi.com/uploads/images/gallery/2023-08/scaled-1680-/aiuTTFs5HpvU3DCf-screenshot-2023-08-11-at-17-23-23.png)](https://manual.eskimi.com/uploads/images/gallery/2023-08/aiuTTFs5HpvU3DCf-screenshot-2023-08-11-at-17-23-23.png)** 2\. In this menu you need to establish report name (keep the name clear possible for yourself and Eskimi DSP team). For "Data Range" menu select "Last 30 Days" and scroll down till the "Report type" section. ## [![Screenshot 2023-08-14 at 10.35.21.png](https://manual.eskimi.com/uploads/images/gallery/2023-08/scaled-1680-/vZgWoc9kNYpTfxMG-screenshot-2023-08-14-at-10-35-21.png)](https://manual.eskimi.com/uploads/images/gallery/2023-08/vZgWoc9kNYpTfxMG-screenshot-2023-08-14-at-10-35-21.png) 3\. In Report Type section you will need to create 2 different sheets as it is shown on the screen below. You can name sheets accordingly "Domains" and "Apps". Each sheet will be presented in same xls file which will be generated automatically. Start with one sheet creation, select "Performance Report" and scroll down till "Dimensions" section.

**Tip 1:** Create 1 sheet at first, for example "Domains". And move to next steps. Later on the sheet might be copied so it will simplify process of creation as you will not need go from the scratch on all next steps for each separate sheet.

## [![Screenshot 2023-08-14 at 10.36.28.png](https://manual.eskimi.com/uploads/images/gallery/2023-08/scaled-1680-/TMRAS1p9HClGM4NV-screenshot-2023-08-14-at-10-36-28.png)](https://manual.eskimi.com/uploads/images/gallery/2023-08/TMRAS1p9HClGM4NV-screenshot-2023-08-14-at-10-36-28.png) 4\. For the sheet "Domains" for Dimensions section you need to select "Media Partners", "Campaigns", "Domains" and "Dates". Select dimensions in same order. Also once dimensions are selected specify media partners (it should be Eskimi), also specify campaigns (you need to select campaigns that you want to include for reporting", and as last step select "by day" for Date dimension. In this case IAS will generate report per domains that appeared for selected campaigns with a daily split. Once this done scroll down till the section "Minimum Total Tracked Ads Filter". ## [![Screenshot 2023-08-11 at 17.38.59.png](https://manual.eskimi.com/uploads/images/gallery/2023-08/scaled-1680-/z9s95mbXAvRLj08c-screenshot-2023-08-11-at-17-38-59.png)](https://manual.eskimi.com/uploads/images/gallery/2023-08/z9s95mbXAvRLj08c-screenshot-2023-08-11-at-17-38-59.png) 5\. In the "minimum total tracked ads filter" section you need to select "all tracked ads". In this case all measured impressions for dimensions you selected above will be presented in the report. Once selected you need scroll down till "Metric" section ## **[![Screenshot 2023-08-11 at 17.26.01.png](https://manual.eskimi.com/uploads/images/gallery/2023-08/scaled-1680-/Zzv8q3iWq0hTvzMx-screenshot-2023-08-11-at-17-26-01.png)](https://manual.eskimi.com/uploads/images/gallery/2023-08/Zzv8q3iWq0hTvzMx-screenshot-2023-08-11-at-17-26-01.png)** 6\. In "Metrics" section you need to enable metrics which are important to for campaign analysis. Below you can see our suggestions regarding metrics that should be selected. Please include them to any report you are creating for Eskimi team. In case you would like to know definition of the metrics, please refer to [article prepared by IAS: "Advertise Metrics Clossary"](https://helpcenter.integralads.com/topics/advertiser-agency/advertiser-metrics-glossary/advertiser-metrics-glossary)
[![Screenshot 2023-08-11 at 17.30.11.png](https://manual.eskimi.com/uploads/images/gallery/2023-08/scaled-1680-/OCpcynkjkRSDywKD-screenshot-2023-08-11-at-17-30-11.png)](https://manual.eskimi.com/uploads/images/gallery/2023-08/OCpcynkjkRSDywKD-screenshot-2023-08-11-at-17-30-11.png)![Screenshot 2023-08-11 at 17.30.27.png](https://manual.eskimi.com/uploads/images/gallery/2023-08/scaled-1680-/KRpvCmA4XSDckLJ9-screenshot-2023-08-11-at-17-30-27.png)[![Screenshot 2023-08-11 at 17.30.34.png](https://manual.eskimi.com/uploads/images/gallery/2023-08/scaled-1680-/oXYF5Z4KdfcDXo6M-screenshot-2023-08-11-at-17-30-34.png)](https://manual.eskimi.com/uploads/images/gallery/2023-08/oXYF5Z4KdfcDXo6M-screenshot-2023-08-11-at-17-30-34.png)
![Screenshot 2023-08-13 at 13.28.00.png](https://manual.eskimi.com/uploads/images/gallery/2023-08/scaled-1680-/hICQcPIm7OvgUIBi-screenshot-2023-08-13-at-13-28-00.png)[![Screenshot 2023-08-11 at 17.31.00.png](https://manual.eskimi.com/uploads/images/gallery/2023-08/scaled-1680-/zuIdcc4L7XxUN1ik-screenshot-2023-08-11-at-17-31-00.png)](https://manual.eskimi.com/uploads/images/gallery/2023-08/zuIdcc4L7XxUN1ik-screenshot-2023-08-11-at-17-31-00.png)
[![Screenshot 2023-08-11 at 17.30.45.png](https://manual.eskimi.com/uploads/images/gallery/2023-08/scaled-1680-/rvevlQfvASNX0yDf-screenshot-2023-08-11-at-17-30-45.png)](https://manual.eskimi.com/uploads/images/gallery/2023-08/rvevlQfvASNX0yDf-screenshot-2023-08-11-at-17-30-45.png)
7\. At this step you can move back to the [3rd point ](https://manual.eskimi.com/link/439#bkmrk-3.-in-report-type-se-0)and duplicate the sheet, in this case all settings will be already preselected and will not require additional selection from scratch. Once new sheets are duplicated, you need to rename them accordingly.[![Screenshot 2023-08-14 at 10.40.46.png](https://manual.eskimi.com/uploads/images/gallery/2023-08/scaled-1680-/yYEQ520vUinS3heH-screenshot-2023-08-14-at-10-40-46.png)](https://manual.eskimi.com/uploads/images/gallery/2023-08/yYEQ520vUinS3heH-screenshot-2023-08-14-at-10-40-46.png) 8\. After duplicating sheets open the one you want to adjust 1 by 1. At this step you need to change dimensions per each sheet. The sheet called "Apps" should have selected dimensions as on screen below. Basically you need to unselect "domains" and select "apps" here. Once dimension selected scroll the page down till "Dilivery" section. ## [![Screenshot 2023-08-11 at 17.39.06.png](https://manual.eskimi.com/uploads/images/gallery/2023-08/scaled-1680-/q0QmEJ2VKZYiqVAm-screenshot-2023-08-11-at-17-39-06.png)](https://manual.eskimi.com/uploads/images/gallery/2023-08/q0QmEJ2VKZYiqVAm-screenshot-2023-08-11-at-17-39-06.png) 11\. Once all set up is done scroll the page till the end and enter email details and frequency for the auto reporting. It is also possible to enter multiple emails who need to get the settled up report. Email Details - enter "adops@eskmi.com" Frequency - select "daily" and establish a period from the campaign first day till the end of last campaign. ## **[![Screenshot 2023-08-11 at 17.31.34.png](https://manual.eskimi.com/uploads/images/gallery/2023-08/scaled-1680-/ULLE5UBnCjALWlLp-screenshot-2023-08-11-at-17-31-34.png)](https://manual.eskimi.com/uploads/images/gallery/2023-08/ULLE5UBnCjALWlLp-screenshot-2023-08-11-at-17-31-34.png)** 12\. Once everything is done the button "save and run" will be active, so you need to press on it to activate the report. [![Screenshot 2023-08-14 at 10.23.47.png](https://manual.eskimi.com/uploads/images/gallery/2023-08/scaled-1680-/HfQEUhl8B1QRrCyi-screenshot-2023-08-14-at-10-23-47.png)](https://manual.eskimi.com/uploads/images/gallery/2023-08/HfQEUhl8B1QRrCyi-screenshot-2023-08-14-at-10-23-47.png) 13\. If everything set up correctly, the receiver(s) will start getting daily report from IAS. The example of IAS email presented below. [![Screenshot 2023-08-14 at 10.55.36.png](https://manual.eskimi.com/uploads/images/gallery/2023-08/scaled-1680-/yCU0FHVzoBkhCGZl-screenshot-2023-08-14-at-10-55-36.png)](https://manual.eskimi.com/uploads/images/gallery/2023-08/yCU0FHVzoBkhCGZl-screenshot-2023-08-14-at-10-55-36.png) --- #### **Future campaigns** **I**f you reached to this stage it means that your both reports are set up. The only question might remains is how to be with future campaigns. In this case there are several options: ##### **Option One** If you are planning future campaigns to be tracked in IAS as well, you can simple edit previously created report by selecting new campaigns in the "Dimension" section and adjusting the Delivery period accordingly. Keep in mind that this should be done for both reports and for each sheet separately. ##### **Option Two** You can also create new report by simple coping from previously created. For new report you need to select new campaigns that will be tracked with IAS as well. In this case, report setting require only several adjustments in "Dimension" and "Delivery" sections. Keep in mind that this should be done for both reports and for each sheep accordingly. # MOAT # Rich Media & MOAT measurement (external) Maximizing media spends and ensuring ads are displayed in a fraud-free, brand-safe environment is a priority for many advertisers. To achieve this, brands globally are turning to third-party measurement solutions like MOAT. In this article, we will explore how MOAT measurement works with an innovative ad solution called Rich Media. --- **Defining Rich Media** Rich Media refers to HTML ads created by Eskimi's in-house creative team. These ads are developed using proprietary tools and are not reliant on third-party software. --- ##### **Understanding MOAT Measurement** MOAT measurement is a third-party tool that utilizes JavaScript tags to enable brands to measure ad impressions based on various parameters such as invalid traffic (IVT), brand safety, viewability, and more. It serves the purpose of verifying supply quality and making necessary adjustments based on the gathered data. --- ##### **Integration of Rich Media Ads with MOAT Measurement** Rich Media ads created by Eskimi can be effectively utilized in conjunction with MOAT impression trackers, namely JavaScript and Pixel tags. These third-party trackers are implemented by Eskimi's ad operations team prior to the campaign launch, ensuring seamless functionality. --- ##### **Enabling Custom Ad-Finding Logic in MOAT** For optimal performance of Rich Media ads, it is essential to have MOAT's custom ad-finding logic enabled for your specific MOAT account. This customized logic, implemented by MOAT, plays a vital role in accurately measuring various ad metrics such as impressions, viewability, invalid traffic (IVT), brand safety, and other relevant parameters. With the custom ad-finding logic in place, Rich Media ads can be located with the highest degree of accuracy. --- ##### **Workflow for Implementation** If your brand intends to incorporate Rich Media ads into your media mix, it is advisable to contact our dedicated MOAT account manager and inform them of your plan to run Rich Media ads through Eskimi. The MOAT account management team will facilitate the enabling of the ad-finding logic for your MOAT account. These changes need to be implemented only once. While the implementation of an ad-finding logic for a specific account will take 2-4 working days. The client should also inform MOAT of the following: *- Are they running display and/or video activity?* *- Which environments/devices are they running activity in (Desktop, Mobile web, or mobile in-app)?* *- What is their preferred reporting hierarchy and corresponding Eskimi macros?* *[![Screenshot 2023-05-18 at 16.05.10.png](https://manual.eskimi.com/uploads/images/gallery/2023-05/scaled-1680-/kuA2LzyyFnSX26KC-screenshot-2023-05-18-at-16-05-10.png)](https://manual.eskimi.com/uploads/images/gallery/2023-05/kuA2LzyyFnSX26KC-screenshot-2023-05-18-at-16-05-10.png)* Should you require further clarification on the workflows, please feel free to reach out to your dedicated account manager, sales representative, or ad operations (adops) team at Eskimi. # Rich Media & MOAT measurement (internal) Maximizing media spends and ensuring ads are displayed in a fraud-free, brand-safe environment is a priority for many advertisers. To achieve this, brands globally are turning to third-party measurement solutions like MOAT. In this article, we will explore how MOAT measurement works with an innovative ad solution called Rich Media. --- ##### **Defining Rich Media** Rich Media refers to HTML ads created by Eskimi's in-house creative team. These ads are developed using proprietary tools and are not reliant on third-party software. --- ##### **Understanding MOAT Measurement** MOAT measurement is a third-party tool that utilizes JavaScript tags to enable brands to measure ad impressions based on various parameters such as invalid traffic (IVT), brand safety, viewability, and more. It serves the purpose of verifying supply quality and making necessary adjustments based on the gathered data. --- ##### **Integration of Rich Media Ads with MOAT Measurement** Eskimi's Rich Media ads can be seamlessly integrated with MOAT impression trackers using JavaScript and Pixel tags. Implementation of these trackers should follow the manual instructions provided at this link: [https://manual.eskimi.com/books/3rd-party-tracking/page/3rd-party-trackers](https://manual.eskimi.com/books/3rd-party-tracking/page/3rd-party-trackers). To ensure optimal performance of Rich Media ads, the MOAT account management team needs to enable custom ad-finding logic specific to the client planning to run Rich Media ads through Eskimi. --- ##### **Explaining MOAT Custom Ad-Finding Logic** MOAT has implemented custom ad-finding logic specifically for Eskimi's Rich Media ads to ensure accurate measurement of ad performance, including impressions, viewability, IVT, and brand safety. This custom logic was introduced to address tracking issues faced by MOAT when measuring Rich Media ads, which resulted in a discrepancy of over 40% between the two systems. The new logic has significantly improved tracking accuracy, reducing the discrepancy to 6%. --- ##### **Workflow Overview** The standards mentioned above are implemented on an individual client basis by a dedicated MOAT team. Therefore, Eskimi's client-facing teams must establish effective communication with the client before launching any Rich Media campaign with MOAT tags. The communication process should follow these steps: 1. **Account Management/Sales:** Confirm with the client if they intend to utilize MOAT measurement solution for Rich Media advertising. If the client plans to do so, they should contact their MOAT representatives and inform them that their Rich Media ads will be run through Eskimi's DSP. The client should also inform MOAT of the following: *- Are they running display and/or video activity?* *- Which environments/devices are they running activity in (Desktop, Mobile web, or mobile in-app)?* *- What is their preferred reporting hierarchy and corresponding Eskimi macros?* The MOAT custom ad-finding logic supports Rich Media ad formats listed in the "Approved Rich Media" section. If a specific format is not listed, it requires additional approval from the MOAT team. The approval process typically takes 1-3 working days. Share the preview link with your client and their assigned MOAT account manager. 2. **MOAT Team:** The MOAT team will enable the custom ad-finding logic at the customer level. The client only needs to reach out to MOAT once. The logic will be activated within 2-4 working days. 3. **Adops:** Adops will set up a campaign using the Rich Media ads and MOAT trackers. Adops should verify the proper firing of the trackers through the preview page, following the instructions provided in the article at this link: [https://manual.eskimi.com/books/3rd-party-tracking/page/3rd-party-trackers](https://manual.eskimi.com/books/3rd-party-tracking/page/3rd-party-trackers). Share the preview page with the client and, ideally, with the dedicated MOAT account manager for confirmation that the trackers are firing correctly and the ads are being found. 4. **Tech Support:** Any concerns related to discrepancies should be addressed through the tech support channel. [![Screenshot 2023-05-18 at 16.05.10.png](https://manual.eskimi.com/uploads/images/gallery/2023-05/scaled-1680-/kuA2LzyyFnSX26KC-screenshot-2023-05-18-at-16-05-10.png)](https://manual.eskimi.com/uploads/images/gallery/2023-05/kuA2LzyyFnSX26KC-screenshot-2023-05-18-at-16-05-10.png) --- ##### **Approved Rich Media Formats** MOAT has already enabled the custom ad-finding logic for most of Eskimi's Rich Media formats. The following list represents the Rich Media ads that do not require MOAT to create a custom ad-finding logic. If the client plans to run advertising using any of the formats listed, they only need to inform their MOAT account management that they will be utilizing Eskimi DSP. **3D Dancing:** [https://dsp.eskimi.com/campaign/FAlqlqop](https://dsp.eskimi.com/campaign/FAlqlqop) **Animated Cubes Interactive:** [https://dsp.eskimi.com/campaign/A7lqlqqr](https://dsp.eskimi.com/campaign/A7lqlqqr) **3D Cube Horizontal:** [https://dsp.eskimi.com/campaign/2Dlqlqqq](https://dsp.eskimi.com/campaign/2Dlqlqqq) **3D Cubes:** [https://dsp.eskimi.com/campaign/E2lqlqqp](https://dsp.eskimi.com/campaign/E2lqlqqp) **Parallax:** [https://dsp.eskimi.com/campaign/27lqlqqo](https://dsp.eskimi.com/campaign/27lqlqqo) **Pixel Pages:** [https://dsp.eskimi.com/campaign/5Clqlqqn](https://dsp.eskimi.com/campaign/5Clqlqqn) **Page Flip:** [https://dsp.eskimi.com/campaign/56lqlqqm](https://dsp.eskimi.com/campaign/56lqlqqm) **Blinds:** [https://dsp.eskimi.com/campaign/73lqlqql](https://dsp.eskimi.com/campaign/73lqlqql) **Card Swipe:** [https://dsp.eskimi.com/campaign/93lqlqpt](https://dsp.eskimi.com/campaign/93lqlqpt) **Carousel:** [https://dsp.eskimi.com/campaign/7Elqlqps](https://dsp.eskimi.com/campaign/7Elqlqps) **Rotating Billboard:** [https://dsp.eskimi.com/campaign/E2lqlqpr](https://dsp.eskimi.com/campaign/E2lqlqpr) **3D Rotating:** [https://dsp.eskimi.com/campaign/46lqlqpq](https://dsp.eskimi.com/campaign/46lqlqpq) **Shake & Break:** [https://dsp.eskimi.com/campaign/02lqlqpp](https://dsp.eskimi.com/campaign/02lqlqpp) **Countdown:** [https://dsp.eskimi.com/campaign/E3lqlqpo](https://dsp.eskimi.com/campaign/E3lqlqpo) **Animated 3D Cubes:** [https://dsp.eskimi.com/campaign/C6lqlqpn](https://dsp.eskimi.com/campaign/C6lqlqpn) **3D Triangle:** [https://dsp.eskimi.com/campaign/5Alqlqpm](https://dsp.eskimi.com/campaign/5Alqlqpm) **3D Cube Vertical:** [https://dsp.eskimi.com/campaign/AClqlqpl](https://dsp.eskimi.com/campaign/AClqlqpl) **Scratch to Reveal:** [https://dsp.eskimi.com/campaign/5Elqlqpk](https://dsp.eskimi.com/campaign/5Elqlqpk) **Parallax 3D Cube:** [https://dsp.eskimi.com/campaign/67lqlqot](https://dsp.eskimi.com/campaign/67lqlqot) **Parallax 3D Triangle:** [https://dsp.eskimi.com/campaign/7Elqlqos](https://dsp.eskimi.com/campaign/7Elqlqos) **Glitch:** [https://dsp.eskimi.com/campaign/F3lqlqor](https://dsp.eskimi.com/campaign/F3lqlqor) **Slider:** [https://dsp.eskimi.com/campaign/11lqlqoq](https://dsp.eskimi.com/campaign/11lqlqoq) **Screentakover:** [https://dsp.eskimi.com/campaign/0Alqlqrn](https://dsp.eskimi.com/campaign/0Alqlqrn) **Floating:** [https://dsp.eskimi.com/campaign/55lqlqro](https://dsp.eskimi.com/campaign/55lqlqro) **Blow to reveal:** [https://dsp.eskimi.com/campaign/3Blqlqrp](https://dsp.eskimi.com/campaign/3Blqlqrp) **AR:** [https://dsp.eskimi.com/campaign/C4lqlqrr](https://dsp.eskimi.com/campaign/C4lqlqrr) **Calculator:** [https://dsp.eskimi.com/campaign/A2lqlqsl](https://dsp.eskimi.com/campaign/A2lqlqsl) **Tap to reveal:** [https://dsp.eskimi.com/campaign/29lqlqsm](https://dsp.eskimi.com/campaign/29lqlqsm) **Interaction:** [https://dsp.eskimi.com/campaign/F3lqlqsq](https://dsp.eskimi.com/campaign/F3lqlqsq) **Product features:** [https://dsp.eskimi.com/campaign/E4lqlqss](https://dsp.eskimi.com/campaign/E4lqlqss) **Gamification:** [https://dsp.eskimi.com/campaign/F7lqlqst](https://dsp.eskimi.com/campaign/F7lqlqst) **Weather API:** [https://dsp.eskimi.com/campaign/44lqlqtk](https://dsp.eskimi.com/campaign/44lqlqtk) If the ad type your clients are planning to use with MOAT measurement is not found in the list of approved Rich Media formats, it is important to inform the client and their MOAT account management that a custom ad-finding logic is required for the new ad format. As mentioned earlier, the process of creating this ad-finding logic typically takes 1-3 days for the MOAT engineering team to complete. # Banners/IBV/Rich Media & IAS measurement #### **General information about IAS Display** Integral Ad Science (IAS) is the global market leader in digital ad verification, offering technologies that drive high-quality advertising media. IAS helps digital advertisers make great impressions, ensuring ads are seen by real people in safe and suitable environments. **IAS measurement** allows deeper analytics for the programmatic campaigns. With the reporting clients will know about: **Brand safety, viewability, ad environment, invalid traffic performance**. These insights give the opportunity to optimize buying and deliver better results.
**IAS Solution****Explanation**
BlockingDisplay tags with blocking. Reures JS
MonitoringDisplay tags without blocking. Can be JS or image
If the media partner does not accept Javascript or the Javascript tag is not implemented, viewability measurements cannot be collected. \*\* Please note that 1x1 trackers cannot collect viewability and cannot be wrapped for blocking. --- #### **IAS With Eskimi DSP** Eskimi DSP can offer their clients to opt in for **IAS measurement** solution. The client has to inform their Business Managers. While BMs should confirm IAS tracker implementation with the adops who will be responsible for campaign management and optimization. From the technical stand point adops need to implement **CM pixel** as a HTML/JS impression tracker. CM pixel is a small piece of code that measures performance and sends back the information to IAS dashboard. CM pixel works for Banners, IBV and Rich Media. Keep in mind that CM pixel is a universal code that doesn't require any changes. --- #### **CM Pixel** ```javascript ``` ##### **CM Pixel Implementation Example:** You need to mark check box from as it is shown on screen-below. You can see that check-box on campaign approval page for every campaign. [![Screenshot 2023-05-24 at 15.39.26.png](https://manual.eskimi.com/uploads/images/gallery/2023-05/scaled-1680-/lZAN6YD1PtIGq6vF-screenshot-2023-05-24-at-15-39-26.png)](https://manual.eskimi.com/uploads/images/gallery/2023-05/lZAN6YD1PtIGq6vF-screenshot-2023-05-24-at-15-39-26.png) When the CM pixel is implemented to the campaign you should see the results accumulating on IAS within 1 working day. --- ### Valuable Links **Dashboard link:** [https://reporting.integralplatform.com/uaa/login](https://reporting.integralplatform.com/uaa/login) **Support link:** [https://support.integralads.com/s/contactsupport](https://support.integralads.com/s/contactsupport) # Troubleshooting and Trackers Configuration Guides # Troubleshooting guide for 3rd party trackers ##### **How to check if the tracker is a pixel:**
Easiest way to check if the tracker you’re using is a 1x1 pixel or not is just to open it in a browser, for example:
``` https://pixel.adsafeprotected.com/jload?anId=931059&advId=Eskimi&campId={campaign_id_enc}&pubId= {site_domain_enc}{app_bundle_enc}&chanId={creative_id_enc}&placementId={placement_id} ```

not an impression pixel

``` https://pixel.adsafeprotected.com/?anId=931059&advId=Eskimi&campId={campaign_id_enc}&pubId= {site_domain_enc}{app_bundle_enc}&chanId={creative_id_enc}&placementId={placement_id} ```

correct impression pixel

From the first view these two trackers look almost identical, but they’re not, if you would open both of them in your browser you will see. You will always recognize the pixel if the browser window is a black screen with a small 1x1 white dot in the middle.
[![WYlBeSXXfPbPUs4E-ezgif-com-gif-maker-2-copy.gif](https://manual.eskimi.com/uploads/images/gallery/2024-02/5YNNiNH4lQodJX8V-wylbesxxfpbpus4e-ezgif-com-gif-maker-2-copy.gif)](https://manual.eskimi.com/uploads/images/gallery/2024-02/5YNNiNH4lQodJX8V-wylbesxxfpbpus4e-ezgif-com-gif-maker-2-copy.gif)
---
If you implement the pixel incorrectly (for example if you use the first URL) there might be huge discrepancies between us and the 3rd party platform (they might even not track anything), so it’s very important before you launch a campaign that uses 3rd party trackers to double check if the trackers are correctly implemented.
Other 3rd party pixel examples:
``` https://ad.doubleclick.net/ddm/trackimp/N705418.1727343ESKIMI.COM/B28985587.353603375;dc_trk_aid= 545020201;dc_trk_cid=182974786;ord=[timestamp];dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;tfua=; gdpr=${GDPR};gdpr_consent=${GDPR_CONSENT_755};ltd=? ``` ``` https://track.adform.net/adfserve/?bn=60266225;1x1inv=1;srctype=3;ord={cachebuster} ``` **Some other ways to recognize if it’s a pixel:**
```javascript ```
This is a our internal IAS JS tracker, but you can extract a pixel from this tracker. Most of the tracking pixel will be placed inside the **<img>** element:
```javascript ```
If you look closely you we will that the height and the width are set to 1x1 for this element (witch almost always indicates that it’s 1x1 pixel). So just extract the URL part from this element and use it as a tracking pixel (it’s not always possible to extract the pixel from JS trackers, keep that in mind). --- ##### **How to validate that you have a 3rd party JavaScript tracker:** - The tag will be in a ` ``` However, if you run a campaign on Gadsme exchange with this pixel, then the client might have bid data discrepancies between 3rd party platform and our impressions. To avoid that, please always edit the tracker as in the example below: ```javascript ``` The pixel below doesn't have "$" before GDRP macros and the macros themselves are written in lowercase format. Also `GDPR_CONSENT_755` is changed to `gdpr_consent` (it doesn't have the "755" number). # Adform creative tag implementation (updated) The following article presents the approach how adform tags should be implemented in Eskimi DSP. 1\. Usually the tags which you will receive from client will be placed in excel file and looks similar to example below ```javascript ``` 2\. To continue tag implementation, you need to create banner type creative set, then add creative as JS/HTML banner and copy the tag from spreadsheet manually. - *When copying tags from this spreadsheet, make sure that you click inside the cell and highlight the text that you want to copy. If you select and copy the entire cell, rather than the text within it, some applications may put an extra set of quotation marks (") around the tags, causing them to function incorrectly when they're placed on the publisher's web page.* - *Don't forget to establish weight and hight for creative in DSP system* *3. Once the code is copied, you need to adjust tag with click macro in order to track clicks in campaign.* *3.1 add `;click={click_url}` into the redirect string.* *3.2 To ensure proper cache-busting, replace **\[timestamp\]** with **{CACHEBUSTER}**.* Once all 2 steps completed the tags should look like ```javascript ``` 4\. Press save and later you can link this creative to your campaign. --- **Possible issues and troubleshooting:** According to our experience we noticed that the adform create tags might be created in multiply variations. Unfortunately, sometimes the creatives might be prepared incorrectly, not follow adform requirements. Therefore sometimes you might notice that after you followed the guide of tag adjustment the tag don't track clicks properly. In such cases suggest to client double check how the creatives were created, and if they follow all adform requirements. In that scenario client can refer to adform support team, or refer to official adform documentation: The documentation of how the creative should be created below: *[https://www.adformhelp.com/s/article/UUID-ba1da05a-285e-ade0-1165-a33481f90b35](https://www.adformhelp.com/s/article/UUID-1a343877-58f8-363d-69d3-0f81da9b9715)* Please also note that there are three important things to be taken into consideration when talking about Adform clicks to work correctly and tracker to fire well: \- Adform DHTML library; \- manifest.json file; \- Click function. # Sizmek Tags Sometimes it may happen that you will receive JS banner tags for Sizmek. But the tags may not be compatible with our DSP platform, without any additional changes. Lets take an example of a bad tag: ```javascript   ``` Upon looking at the tag there are a few things: - First of all our **{CLICK\_URL}** macro is missing. - And no use of **{CACHEBUSTER**} macro. - The URL in the **<a>** needs to be encoded. In order to fix the tag, we need to make several changes. To start let's look at the correct tag. ```javascript ``` 1\. **{CLICK\_URL}** macro is added in two places, the **<script>** part of the tag, and the **<noscript>** part of the tag. **<script>** part of the tag: to insert the **{CLICK\_URL}** macro you have to add the **"&ncu=$${CLICK\_URL}$$"** of the first URL. **<noscript>** part of the tag: insert **{CLICK\_URL}** before the **href="" url** 2\. Enable Cachebuster. Cachebuster in Sizmek is enabled, by using the **\[timestamp\]** property of the URL. To enable this from our DSP end, that has to be changed to **{CACHEBUSTER}**. 3\. Encode the **<noscript>** URL: the after the **{CLICK\_URL}** part has to be encoded. To encode the URL use this tool: [https://meyerweb.com/eric/tools/dencoder/](https://meyerweb.com/eric/tools/dencoder/). # Ad Discrepancy in CM360 ##### **What is CM360?** Google Campaign Manager 360 (CM360) is an ad server within [Google’s Marketing Platform](https://marketingplatform.google.com/about/) which allows to host and manage digital advertising all in one place and review creative performance in real-time. Marketers use CM360 to manually create tracking assets called “tags”, which are then delivered by a media partner. --- ##### **What is Ad Discrepancy?** Ad discrepancy refers to a difference in analytical data between two parties. Discrepancies arise from the use of multiple tools, formulas, and methodologies to calculate data. The most frequent metrics used by publishers and advertisers are impressions, clicks, page views, user sessions, bounce rate, and others, depending on the use case. The advertising industry is currently experiencing two types of discrepancies: 1\) between ad tech vendors; 2\) between sell-side and buy-side platforms. --- ##### **What percentage of discrepancy is considered normal by CM360?** When counting clicks and impressions, discrepancies of up to 20% are considered normal by CM360. --- ##### **What are the frequently occurring reasons of discrepancies in CM360?** 1. Reports with imprecise comparisons. For instance, do the third-party report and the Campaign Manager 360 report have the same date range? 2. The initially exported tag has been wrapped or changed. 3. Incorrectly implemented cache-busting. 4. Tag has been implemented more than once. --- ##### **What do to if discrepancy is more than 20%?** If clicks/impressions discrepancy is more than 20%, recommend to the client to contact Google Marketing Platform support and to do so while the campaign is still live. Before contacting support, client has to make sure that campaign has enough data, since according to CM360 discrepancies with limited data (less than 1,000 impressions) cannot be investigated. To receive a faster support, CM360 [recommends](https://support.google.com/campaignmanager/answer/2835377?hl=en) to have this information ready: 1. A placement report broken down by date that allows comparison between CM360 and 3rd Party platform/Site. 2. A live URL or a live app where support can view the ad tags. If that's not possible, provide a test URL or app that's implemented exactly as the live tags - creative preview page in our instance. Use CM360's [official discrepancy spreadsheet](https://storage.googleapis.com/support-kms-prod/yVJJXbFF87Am6xENmXpRtCXeSHCcvznTn0Nc) to send this information to their support. # VAST video & IAS measurement #### **What is IAS pixel for VAST video?** Eskimi supports IAS third party pixels via the piggy back method, where the Eskimi append the IAS pixel tag directly on creatives prior to platform upload. To measure performance on IAS for video, VAST video creative must be wrapped into IAS wrapper. This is a small pixel code that can be implemented directly and automatically through Eskimi platform.
**IAS Solution****Explanation****Requirements**
Multimedia Tag MonitoringVideo tracking tag that will work across desktop, CTV, mobile & in-app. Can measure viewability, set to not blockRequires a VPAID player/publisher support & 3rd party ad serving
Multimedia Tag BlockingVideo tracking tag that will work across desktop, CTV, mobile & in-app. Can measure viewability, set to blockRequires a VPAID player/publisher support & 3rd party ad serving
Unified Video PixelVideo tracking tag that will work across desktop, CTV, mobile & in-app. Cannot measure viewability or blockRequires a VAST player & 3rd party ad serving
Viewability measurements cannot be collected if it is not third party ad serving and the video inventories are not VPAID compatible. IAS alternative solution would be our Unified Video Pixel, which is essentially just the image pixel generated for various events (i.e. first quartile/ second quartile etc), you can implement the various event trackers to ensure you are able to collect **valid quartile measurements** since viewability would not be measured. --- #### **Why IAS tracker is relevant for VAST video?** IAS trackers allow advertisers to understand their VAST video performance in 3 main areas: 1\. Brand safety 2\. Viewability 3\. Invalid traffic When the a VAST video is wrapped into an IAS tag, the above mentioned mentrics will be tracked on IAS dashboard automatically. --- #### **How to wrap VAST video into IAS tracker?** Eskimi allows to wrap VAST video in highly automated manner. 1\. Go to your account's *Creatives* section. 2\. Select *Add creative set.* [![image-1665046554721.png](https://manual.eskimi.com/uploads/images/gallery/2022-10/scaled-1680-/iksjTSSxCUbr8ST9-image-1665046554721.png)](https://manual.eskimi.com/uploads/images/gallery/2022-10/iksjTSSxCUbr8ST9-image-1665046554721.png) 3\. Give your creative set a name & select creative format as *Video.* *[![Screenshot 2022-10-06 at 11.44.56.png](https://manual.eskimi.com/uploads/images/gallery/2022-10/scaled-1680-/ryp4zErqjUN8XFht-screenshot-2022-10-06-at-11-44-56.png)](https://manual.eskimi.com/uploads/images/gallery/2022-10/ryp4zErqjUN8XFht-screenshot-2022-10-06-at-11-44-56.png)* 4*.* From the *format* dropdown select **VAST video** or **VAST XML.** It will be possible to wrap VAST video even when **VAST + IBV** is selected. [![Screenshot 2022-10-06 at 11.45.20.png](https://manual.eskimi.com/uploads/images/gallery/2022-10/scaled-1680-/l0yE1k5EdEzteLW5-screenshot-2022-10-06-at-11-45-20.png)](https://manual.eskimi.com/uploads/images/gallery/2022-10/l0yE1k5EdEzteLW5-screenshot-2022-10-06-at-11-45-20.png) 5\. Upload your VAST video by selecting *Choose file*. You should see a successful video upload right below the button. Select *Enable VAST wrapper.* The VAST video or tag will be automatically wrapped into the IAS tracker. It is not needed to take the VAST tag from the preview page anymore. VAST wrapper can be enabled at any point of the campaign execution. [![Screenshot 2023-05-24 at 15.41.38.png](https://manual.eskimi.com/uploads/images/gallery/2023-05/scaled-1680-/6MKN1XJzH5RS0bUu-screenshot-2023-05-24-at-15-41-38.png)](https://manual.eskimi.com/uploads/images/gallery/2023-05/6MKN1XJzH5RS0bUu-screenshot-2023-05-24-at-15-41-38.png) The flow was tested and works as intended. However, any challenges can be directly discussed with the product team. --- #### **Limitations** 1\. Eskimi can wrap VAST videos only with Eskimi IAS tracker. If the client wants to wrap the video into their own IAS tracker it is necessary to follow[ the standard procedure](https://manual.eskimi.com/books/3rd-party-tracking/page/vast-wrapping-into-clients-ias-tag-by-eskimi) where VAST video tag is taken from the preview page. 2\. The wrapping is available for Eskimi IAS tracker. Any 3rd party trackers have to be used in the standard manner. For example, if the client wants to wrap the video into MOAT tracker it will be mandatory to setup the campaign and [take the VAST tag from the preview page](https://manual.eskimi.com/books/3rd-party-tracking/page/vast-wrapping-into-clients-ias-tag-by-eskimi). 3\. Any tracked video metrics will be reflected only on IAS dashboard. However, metrics can be exported manually or [automated reports](https://manual.eskimi.com/books/tracking/page/report-builder-ias-agency-account) can be enabled to increase transparency with the clients.