Moat

Moat is reaching end-of-life on September 30, 2024. See Oracle Advertising for any questions.

Moat is an analytics and measurement company that offers viewability, attention, and brand safety solutions across display, video, mobile, and more.

If you are a brand or media agency already using Moat, this integration will help you measure Moat viewability and attention signals on all your Celtra campaigns. As Moat has integrated the Celtra Viewability Observee API, measurement is can be ensured across all Celtra display formats.

You can enable Moat through account-level integrations from the add-ons section of your account.

After enabling, you'll see metrics in Moat broken down by your Celtra campaign, supplier, placement, and creative.

If the Rule-based feed is used in your creative, MOAT will also receive information on which creative variant was shown by feed ID and report label matched at serving time (and additional feed IDs/report labels if used). By default, this is not visible and “creative variant” information must be requested from Moat.

If the 3rd party ad server already reports data to Moat, enabling Celtra will not interfere with the current configuration. Data from the perspective of both systems and their hierarchies will both be available.

You can also append Moat tags to Celtra tags and authorize an agency to access Moat reports for their slice of impressions from your Celtra account. If the tag generated by Celtra contains macros, any edits to the tag will result in Moat data collection issue upon trafficking. These macros are critical for Moat to collect data effectively. Macro enabled tags must be trafficked through external servers exactly as they are generated.

Note: Events will be reported to Moat for all Javascript-based tags, including display and VPAID, but not for VAST.

Granting access to Moat reports to your agencies

To authorize an agency to access Moat reports for their slice of impressions from your Celtra account:

1. Look up the Celtra Media Agency ID by going to Account > Partners (you must be an admin to access this page)

2. Send an email to moat-celtra-adcreator_ww@oracle.com providing the Moat team with the ID and authorizing access:

   I authorize to access Moat reports for Celtra impressions with Media Agency ID .

The agency will have access to reports for all campaigns on which they are set as the media agency in Celtra.

Data sent to Moat

The following data will be sent to Moat:

1. Celtra data:

   • Campaign ID & Name

   • Placement ID & Name

   • Creative ID & Name

   • Supplier ID & Name

   • Brand ID & Name

   • Media Agency ID & Name

   • Creative Format

   • External Ad Server

2. Data obtained from the external ad server:

   • Advertiser ID (Google Ad Manager)

   • Campaign ID (DCM, Sizmek, The Trade Desk, MediaMath, Google Display & Video 360, Google Ad Manager, AppNexus)

   • Campaign name (Sizmek)

   • Placement ID (DCM, Sizmek, The Trade Desk, MediaMath, Google Ad Manager, AppNexus)

   • Placement Name (Sizmek, MediaMath)

   • Creative ID (Sizmek, DCM, The Trade Desk, MediaMath, Google Display & Video 360, Google Ad Manager, AppNexus)

   • Creative Name (Sizmek)

   • Site ID (DCM, Sizmek, The Trade Desk, MediaMath, Google Display & Video 360, Google Ad Manager, AppNexus)

   • Site Name (Sizmek, MediaMath, Google Display & Video 360, Google Ad Manager, AppNexus)

   • External Line Item ID (DCM, Sizmek, MediaMath, Google Ad Manager)

Display

If you are e.g. a network or a publisher, and have received a Moat tag from an advertiser looking to measure Moat viewability and attention signals on their campaign, you should append the Moat tag to the Celtra tag when inserting them into your 1st party ad server.

In this case, a Moat tag will typically not contain any ad server macros. Instead, the parameters are already filled with the advertiser's own values.

When inserted into a page side-by-side, the Moat script automatically detects the neighboring Celtra tag and a Celtra-Moat integration ensures the correct HTML elements are measured for viewability across all creative formats.

The Celtra / Moat integration requires proper tag placement. To ensure the Moat script automatically detects the neighboring Celtra tag, the Moat tag, and Celtra tag must be implemented side-by-side. This ensures the correct HTML elements are measured for viewability across creative formats. Failure to do so will impact Moat’s ability to track and can result in data collection issues and reporting delays.

If you have included the Moat SDK into your apps, the Moat script will also automatically communicate with it to measure viewability.

Video

To measure video with viewability for an advertiser, your video player must be integrated with Moat, or the advertiser must use the Celtra-Moat account-level integration described above.

Please note that firing off the MOAT script through execute JS action will not work properly.

Celtra now supports passing custom parameters to Moat. To do so, click on Accounts -> General and scroll down to the Custom Attributes area to review account-level Texts and Lists custom attribute types.

This means that you can set up custom attributes for your campaigns, creatives, or placements, you can prefix each parameter like the following: zMoatCustomYourAttribute

Example: zMoatCustomAttr1 to send zMoatCustomAttr1 param in the URL - e.g. zMoatCustomAttr1=

Texts: The value entered will be sent as the value of the attribute.

Lists: The item selected from the list will be the value of the attribute.

zMoatCustom attribute values support macro replacement of all Celtra provided macros described on the Using Macros page. Macro replacement is supported both for Text and List values.

Please follow the guidelines in this section if you are experiencing problems using an external 3rd party ad server alongside the Moat + Celtra integration.

Why am I not seeing data?

Issues with this integration primarily arise due to adjustments made to the macro-enabled tags generated by the Celtra platform.

• Check that the correct ad server was selected when generating the tag.

• Check for errors in the tag format. Most common issues are missing quotes or other characters.

• Confirm you are not trafficking tags containing hardcoded parameters as they will break the integration.

• Ensure trafficked tag has not been edited or adjusted in any way. Adding or removing macros might break the integration.

Further Support

Please reach out to your Moat and Celtra dedicated account & support leads with detailed notes about the issue.

1. Summary

   • Provide a detailed summary of the issue.

2. Reporting

   • Compile reporting from multiple parties over the same time frame, for the same campaign, which confirms the issue at hand.

3. Workflow

   • Provide a description of the full workflow and parties involved.

   • What agency is trafficking the tag through what DSP and any 3rd Party Ad Servers involved.

4. Test Page

   • Include relevant test page(s) in your support request.

5. Contact

   • Email support@celtra.com, moat-celtra-adcreator_ww@oracle.com, along with the point person from the other parties defined in the workflow.

   • Make sure to include all information from the above steps to prevent delays in addressing your request.

After we receive your email, support personnel from Moat / Celtra will confirm once it is under review (usually within 12-24 hours) and reach back out with feedback or additional questions. We appreciate your patience and we’re happy to work together to help solve any issue at hand.