## Overview  
**NOTE: Oracle has deprecated Moat tags. This page is hidden, but still exists for historical information.**  
Moat tags are used for marketing analytics.

## Setting Up Moat Tags in Creative  
If you are serving a third-party creative, you should append the Moat tags after the Javascript or HTML5 tags **in the same Kevel creative**.

If you are serving a first-party image, you should [host the image with Kevel](https://dev.kevel.co/v1.0/docs/misc-creative-features#section-hosting-an-image-with-kevel-and-locating-image-url) and append the Moat tags afterwards **in the same Kevel creative**.

## Inserting Macros for Levels and Slicers  
Moat will send you instructions for which macros to attach to the tag's Levels and Slicers. These will correspond to different units in Kevel, but how you want to map these is up to you and Moat. A typical Kevel integration looks like this:

- **Level1**: Advertiser ID
- **Level2**: Ad ID
- **Level3**: (N/A)
- **Level4**: (N/A)
- **Slicer1**: Site ID
- **Slicer2**: Zone ID

Using this example, here are Moat tags with the macros included:

`<noscript class="MOAT-account207343723525?moatClientLevel1={{ad.flight.AdvertiserId}}&amp;moatClientLevel2={{ad.id}}&amp;moatClientLevel3=_LINEITEM_&amp;moatClientLevel4=_CREATIVE_&amp;moatClientSlicer1={{site.id}}&amp;moatClientSlicer2={{placement.zoneIds[0]}}"></noscript><script src="https://z.moatads.com/account207343723525/moatad.js#moatClientLevel1={{ad.flight.AdvertiserId}}&amp;moatClientLevel2={{ad.id}}&amp;moatClientLevel3=_LINEITEM_&amp;moatClientLevel4=_CREATIVE_&amp;moatClientSlicer1={{site.id}}&amp;moatClientSlicer2={{placement.zoneIds[0]}}" type="text/javascript"></script>`