For each Audiohook account, a unique 1x1 transparent pixel is generated which we refer to as the Audiohook Pixel. Contained in the pixel is a unique account specific id.

<img src="https://listen.audiohook.com/account-specific-id/pixel.png" style="display: none;">

Here's an example of an Audiohook Pixel with than account specific id populated.

<img src="https://listen.audiohook.com/abcdefgh-ijkl-mnop-qrst-uvwxyzabcdef/pixel.png" style="display: none;">

While this pixel can be installed anywhere on a webpage such as in the header, the body, or the footer; we recommend that the pixel be installed at the bottom of the webpage just above the body close tag.

<body>
...
<Audiohook Pixel>
</body>

The Audiohook Pixel collects anonymous data to inform insights on the audience which are ultimately used to power audio campaigns. With that said, the Audiohook Pixel can be executed either client-side or server-side. For client-side installations, any tag management software or integration related software such as Google Tag Manager and Segment can be used as long as the Audiohook Pixel is ultimately executed client-side. For marketers that prefer a server-side integration, we have a simple RESTful api which uses a POST method to send the same anonymous data which is documented here.

Did this answer your question?