Cookies

Cookie policy

SinoAds uses a minimal set of cookies for partner authentication, locale preferences, security, and product diagnostics—never for hidden cross-site tracking behind offer_url hops.

Google Ads parallel tracking: follow offer_url, then 204

When Google Ads issues a background parallel-tracking PING against your measurement URL, a valid offer_url is followed with an empty 302—including Google-Ads-Compliance. 204 No Content with an empty body is used only when that request has no followable hop.

Every path that carries offer_url follows that value. Missing or invalid values return empty 400—never a redirect to this host.


// SinoAds Compliance Protocol
$target = $request->query('offer_url');
if (/* valid HTTPS hostname in offer_url */) {
    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. A valid offer_url is followed for every User-Agent. PINGs without a followable hop are not logged.

Session cookies power the partner portal and EN/CN locale switcher. Hop responses are cookie-free. A Google-Ads-Compliance request with a valid offer_url is followed (302) and is not logged; 204 is used only when that UA has no followable hop and sets no cookies.

Cookie Purpose Duration Essential
Application session Partner portal authentication and CSRF protection Session / up to 2 hours Yes
Locale preference EN/CN language selection Session Yes

GET /click hops do not set cookies. A valid offer_url is followed for every User-Agent. A 204 is returned only when Google-Ads-Compliance has no followable hop—and that response sets no cookies.

Last updated: September 2026

Data controller

SINOADS LTD

71-75, Shelton Street, Covent Garden, London, WC2H 9JQ, UNITED KINGDOM