| 00:00 - 00:03 | We've received the CHEQ implementation guide |
| 00:04 - 00:05 | it can be implemented via GTM |
| 00:05 - 00:07 | or directly on the website |
| 00:08 - 00:12 | but the problem is that bots don't consent |
| 00:12 - 00:15 | and CHEQ must fire pre-consent as "Strictly Necessary" |
| 00:17 - 00:19 | the CHEQ solution is "Strictly Necessary" |
| 00:19 - 00:21 | so the web team just needs to update the cookie banner? |
| 00:24 - 00:26 | my CMO |
| 00:27 - 00:28 | unfortunately IT said... |
| 00:31 - 00:33 | that will take over 6 months... |
| 00:34 - 00:36 | it will require a DPA, DPO and InfoSec Approval... |
| 00:53 - 00:58 | can Affiliate Marketing, Paid and Paid Social leave the room? |
| 01:13 - 01:15 | Bot's don't consent! |
| 01:15 - 01:17 | the CHEQ team assured me Since CHEQ is a Cyber Security Solution |
| 01:18 - 01:23 | it can be categorized as an "essential tool" for our website security |
| 01:25 - 01:28 | that means invalid visitors are only being evaluated if they opt in |
| 01:29 - 01:31 | fraudsters do not provide consent by nature |
| 01:31 - 01:34 | this defeats the whole purpose of a POC |
| 01:34 - 01:37 | it would be like asking a burglar to consent to you recording them on CCTV cameras |
| 01:37 - 01:40 | the tag ought to be fired up regardless |
| 01:40 - 01:42 | If the CHEQ tag only fires after cookie consent, then that delays the whole detection |
| 01:42 - 01:46 | but Lunio fires post consent, why can't CHEQ? |
| 01:46 - 01:48 | the consequence is that we will miss "hit and run" bots which come for very short periods of time |
| 01:48 - 01:52 | well then tell CHEQ they've no deal for their Q4! |
| 01:53 - 01:54 | use GTM they said! |
| 01:56 - 01:57 | it was meant to be an easy POC |
| 01:57 - 02:00 | to demonstrate how much wasted Paid Spend we have |
| 02:00 - 02:03 | to see which LLMs are scraping our site |
| 02:04 - 02:08 | and to cleanse our Adobe Analytics. |
| 02:08 - 02:13 | I just want a single source of truth |
| 02:14 - 02:16 | how hard is it to have a clean set of website analytics |
| 02:17 - 02:21 | why can't we just set it as "strictly necessary"? |
| 02:27 - 02:29 | Rory from CHEQ told me |
| 02:30 - 02:34 | they had legal credentials to fire pre-consent |
| 02:34 - 02:36 | it was acknowledged by a law firm |
| 02:41 - 02:42 | by the EU judicial bodies of Cooley LLP in 2023 |
| 02:43 - 02:47 | Therefore, CHEQ Cookies are "strictly necessary" |
| 02:48 - 02:53 | we have a legitimate business interest in ensuring the prevention of malicious actors on-site |
| 02:54 - 02:56 | but now you're telling me |
| 02:56 - 02:59 | Bots have rights! |
| 03:00 - 03:02 | the fraudsters scraping my content... |
| 03:04 - 03:07 | don't worry your paid marketing budget will be safe |
| 03:14 - 03:16 | and IT's server costs are growing |
| 03:19 - 03:23 | from non human traffic that wont ever convert |
| 03:25 - 03:26 | tell CHEQ |
| 03:31 - 03:33 | the POC must go on |
| 03:40 - 03:46 | let's get CHEQ to send over whatever documentation they have |
| 03:46 - 03:49 | our DPO will review their terms of service |
| 03:53 - 03:56 | otherwise we miss our peak |
