This page focuses on two methods of integrating with Lunio.
โ
1. Tracking Template (Google Platforms)
The Lunio tracking template is used to integrate with Google Ads
The template routes traffic through a redirect, which allows us to collect data at the point of click, in parallel to it going to your landing page.
The redirect is loaded in parallel, meaning there is no impact on page load speed. You can find more information on parallel tracking here.
2. On site Tag (Javascript)
The Lunio client side script measures clicks once they hit your landing page using a javascript snippet.
It determines the channel the clicks came from based on URL parameters (Lunio will detect utm_source=platformname as default, but we can provide a custom parameter to be used if you use alternative tracking).
The script loads asynchronously so as not to impact page load speed.
The script is also used to enable audience based protection.
What click data is collected?
Using these two sources, Lunio collects and stores the following data server side:
Data Collected | Source | Example |
User Agent | Default HTTP request field | Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.0.0 Safari/537.36 |
Client IP | Default HTTP request field | 123.123.1.1 |
Timestamp | Lunio server access time | 2024-01-01 09:30:35 BST |
Lunio Account ID | Embedded in Lunio script | 7890 |
Landing page URL | Browser current URL. For Tracking template it will include ValueTrack parameters in the URL. |
Lunio also receives, but does not necessarily store, the visiting users default http headers (as the user and the users browser decides to disclose). You can find out more about http headers here.
Lunio Audience Protection
When a customer is onboarded to a new platform in Lunio, their script is regenerated to add logic that will be activated upon a decision of an invalid click. This actions differ between platforms, but can be defined as audience addition of the impacted user to create an invalid audience, which will be excluded by the relevant ad platform. This process does not collect any additional data and does not invoke any information generation or sending to Lunio's server which Lunio didn't have from the initial request described in the table above.
โ
Lunio Conversion Tracking Script
Lunio also utilises an optional conversion tracking script, an asychronous javascript snippet which sits on your conversion page, collecting and storing the following information:
Data Collected | Source | Example |
User Agent | Default HTTP request field | Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.0.0 Safari/537.36 |
Client IP | Default HTTP request field | 123.123.1.1 |
Timestamp | Lunio server access time | 2024-01-01 09:30:35 BST |
Lunio Account ID | Embedded in Lunio script | 7890 |
Landing page URL | Browser current URL. For Tracking template it will include ValueTrack parameters in the URL. |
This data is used to identify legitimate converting traffic sources and report on Lunio's performance.
Does Lunio use cookies as part of data collection?
No, Lunio do not use cookies as part of our data collection process.
Lunio Privacy Policy
Lunio privacy policy and detailed purpose of collection is available here:
Concerns
In case of concerns please contact [email protected], or Lunio's Data Protection Officer which details are available in the privacy policy linked above.