Trigger a Page Analysis Request

Publishers can trigger a Verity analysis request whenever a page in their content network is visited. Callback functions can be implemented to use the Verity result analysis data. For example, a callback could publish targeting keywords using Verity data, then fetch new ads using Google Publisher Tag refresh functionality. The page can be configured to disable the initial loading of ads until Verity returns analysis data.

This convenient way to integrate with Verity involves specifying the Verity JS (JavaScript) tag on the publisher’s web pages. This section explains how to use the Verity JS tag.

Before Using the Verity Tag

Before using the Verity JS tag, publishers need to set up one or more unique Zone IDs with GumGum. A Zone ID enables Verity to authenticate requests from publishers. A Zone ID comprises a UUID assigned to a set of publisher domains. For example:

Zone ID	Domains
`46b12cfd-9b63-40bf-a632-2710ec8e31bf`	client.host.one.com client.host.two.com

Note: Requests to Verity from domains not assigned to the Zone ID are denied.

The steps to get a new Zone ID are as follows:

The publisher gathers the list of hosts where the Verity JS tag will be used, for example:
client.host.one.com
client.host.two.com
The publisher emails verity-support@gumgum.com with the list of host names. At least one host name must be specified.
Verity Support responds with a unique UUID value to be used as the Zone ID, for example:

zoneId = 46b12cfd-9b63-40bf-a632-2710ec8e31bf

If the list of hosts changes, the publisher must contact Verity Support to update the Zone ID.

*Please note, API Keys and Zone IDs will be provided by Verity Team.

Using the Verity JS Tag

To use the Verity JS page tag, the publisher will specify the Verity JS tag in a client-side HTML <script> tag on the pages in their content network and configure their Zone ID and API authentication key.

Follow these steps to implement the Verity JS tag:

Include the following <script> tag, preferably within the web page <head> tag:
<script async src="https://js.verity.gumgum.com/vpt.min.js"></script>
Initialize the following configuration object to the window object:

window.verityConfig = { apiKey: ‘<API Key supplied by GumGum>’, zoneId: ‘<Zone Id supplied by GumGum>’ }

Note: The page URL is extracted by vpt.min.js using window.location.href.
Optionally, callback functions may be passed to Verity to execute once Verity API returns a response.
Note: The response may be for a page classification with any status, so the callback should handle each possible status message. See Page Application Status Codes for details about status messages that Verity may return.

window.verity.cmd.push(function(data, error) { // do something }); }
Callback functions can be implemented to use the Verity result data. For example, a callback could publish targeting keywords using Verity data, then fetch new ads using the Google Publisher Tag googletag.pubads().refresh(). For example:

window.verity.cmd.push(function(data, error) { console.log(‘Verity done’, window.verity.getKeywords(), data, error); google tag.cmd.push(function() { googletag.pubads().setTargeting(‘keywords’, window.verity.getKeywords().concat([‘VERITY’])); googletag.pubads().refresh(); }); }

Example Verity JS Implementation

The following web page shows an example Verity JS tag implementation, where the page disables the initial loading of ads until Verity returns analysis data.