As part of the platform, Audiohook automatically calculates and reports on website sessions, including any associated UTMs as well as any events (if they are being supplied) that occurred during said website session.

Unfortunately because web browsers such as Chrome, Firefox, Edge, and Safari implement different standards as well as differences in implementations of web analytic software, it is not uncommon to see differences in reporting between two providers. To minimize these discrepancies, advertisers can append an anonymous customer id onto the Audiohook Pixel url via the aci parameter as shown below. Note that double curly brackets are to denote variables and should not be included.

<img src="https://listen.audiohook.com/e5c2bdf9-46ff-466d-a210-8678ceaf420a/pixel.png?aci={{anonymous-customer-id}}" style="display: none;">

This anonymous customer id can be the id associated with your website cookie, the anonymous client id value that Google Analytics assigns, or even the MD5 hashed value of the user's email address for marketers who's users are required to login.

Moreover, the aci parameter should ideally be appended anytime the Audiohook Pixel is being called.

For example, when the Audiohook Pixel is being called on a website visit it would look like this.

<img src="https://listen.audiohook.com/e5c2bdf9-46ff-466d-a210-8678ceaf420a/pixel.png?aci=a1b2c3d4" style="display: none;">

If that same user, then made a purchase the event tracking call would look like this. Note, this also works for marketers using the retired order and value parameters.

<img src="https://listen.audiohook.com/abcdefgh-ijkl-mnop-qrst-uvwxyzabcdef/pixel.png?event_name=purchase&event_id=182&event_value=107.12&aci=a1b2c3d4" style="display: none;">

Did this answer your question?