In this article
We will review how to set up access to Google Ad Manager logs for SlotClicked events.
Our platform has the functionality to read data from GAM log files, processing the click events, and feeding these into the Permutive API. Once ingested, these events can be used in custom cohorts, allowing customers to target audiences based on their clicks on ads.
Google Ad Manager logs
Google Ad Manager (GAM) is a tool used to serve adverts on publisher properties. One of its features allows access to the raw logs for events involving these adverts (see Ad Manager Data Transfer reports). We refer to these log files as GAM logs in this document and our platform.
Note that log access is a premium feature of GAM that not all customers have access to.
Ad click events
A certain type of event in GAM log files represents a user clicking on an advert. These events contain information about the advert that was clicked, in particular the identifiers that link the event back to a particular ad campaign and creative in GAM.
The log files containing click events are known as "NetworkClicks" and "NetworkBackfillClicks" in GAM.
By reading these events from log files, we have much stronger guarantees of accuracy and support events from any type of device that uses the GAM SDK.
For a customer to start using GAM log click events in their cohorts, they must enable the GAM log integration in the dashboard and follow the instructions shown on the page.
These instructions are also included below for reference.
Using GAM log events in cohorts
Once the integration is enabled, a new event type named "GamLogSlotClicked", representing a click on an ad ingested from a log file, will be available for inclusion in cohorts.
Please note the "Gam" prefix here, in comparison to the event without the prefix ("SlotClicked"), which are generated from SDKs rather than ingested from log files and have limited device support.