Google Ads Tracking

Web3App supports transparent click measurement using an explicit next-hop destination supplied in the tracking request.

Tracking Template

Copy your tracker's template from its details page in your account. Replace the example identifier below with your actual Tracking ID; 5932832 is illustrative.

Campaign measurement

Place the template in Google Ads' Tracking template field and set your HTTPS landing page as the Final URL. Google Ads expands its ValueTrack placeholders when forming the request. Use Google Ads' Test action before publishing.

Explicit next-hop routing

The redirect parameter specifies the immediate next-hop destination for transparent tracking requests.

Public tracking requests require the redirect parameter. Web3App uses only this explicit next-hop after validation and never substitutes a saved destination.

Web3App records supported campaign parameters and then redirects the request directly to the supplied destination.

The response is an HTTP 302 with the validated next-hop in the Location header. Web3App inserts no intermediate page, tracking domain, JavaScript, iframe or meta refresh. Visitor identity, IP, country, device, User-Agent, referrer and advertising-platform or reviewer detection do not change the destination.

Encoding and validation

Supply exactly one redirect value. URL-encode a literal destination as a single query value so its own query string is preserved:

The request query is decoded once. The tracker accepts validated HTTP(S) URLs; use HTTPS throughout Google Ads tracking. Credentials in URLs, loopback/private or reserved IP literals, local hostnames and direct loops into this tracker are rejected. Missing, empty, repeated and invalid redirect values return HTTP 400, with no fallback redirect or click event. A missing parameter displays “Missing transparency parameter”. Paused trackers return HTTP 410; unknown trackers return HTTP 404.

Recorded campaign data

Supported fields include keyword, creative, matchtype, network, campaignid, adgroupid, device, placement, target, UTM parameters, gclid, gbraid and wbraid. Other query parameters are retained subject to sensitive-field redaction and storage limits. The redirect value is separate technical metadata. Click events also include the resolved destination and destination_source=next_hop.

Outer campaign parameters are not appended to the next-hop URL. Parameters required by the landing page must already be inside the supplied destination. Accepted GET requests record clicks; HEAD requests return the same redirect without recording a click.

Technical verification

A persistent public verification tracker is available at CERTTEST01 with an explicit next-hop. It returns HTTP 302 to the certification test page. The same tracker without redirect returns HTTP 400. It uses the same validation and routing as every other tracker.

Platform requirements

This documentation describes the implemented template. It does not assert certification or approval by Google. Use of third-party click trackers in Google Ads remains subject to Google's current requirements.

Google's click-tracking guidelines · About tracking in Google Ads

Support: support@web3app.online