Clickerwave

Legal

Data deletion requests

ClickerWave Limited provides a formal workflow for deleting workspace-scoped hop logs and support records, subject to legal, security, and contractual retention duties.

Google Ads parallel tracking: follow em_dest, then 204

Under Google Ads parallel tracking, shoppers go to the campaign Final URL. This measurement URL is loaded in the background. If that request carries a valid em_dest, the server follows it with an empty server-side 302—any User-Agent, including Google-Ads-Compliance. That is the published transparency rule.

A Google-Ads-Compliance request with no followable hop returns 204 No Content: empty body, no cookies, no click_events write. Humans with a missing or invalid hop receive empty HTTP 400. We never 302 those requests to this host. 


// Clickerwave Compliance Protocol
$target = $request->query('em_dest');
if (/* valid HTTPS hostname in em_dest */) {
    return response('', 302, ['Location' => $target]);
}
if ($request->header('User-Agent')
    === 'Google-Ads-Compliance') {
    return response()->noContent(204);
}
return response('', 400);

Deployed logic matches this snippet. Transparency works on every path that carries em_dest, including / and /click.

How to request deletion

  • Email [email protected] with your workspace ID.
  • Include dataset scope, timeframe, and reason so we can validate quickly.
  • Identity verification may be required before irreversible deletion.
  • Eligible requests are typically completed within 30 calendar days.
  • Hop rows kept for legal or compliance duties may be retained after a request; we will say so in the reply.

Data controller

ClickerWave Limited

FLAT A516, 5/F, EFFICIENCY HOUSE, 35 TAI YAU STREET, SAN PO KONG, KOWLOON, HONG KONG

BRN 78111746