Tracking flow
For Google Ads transparent click tracking, the production intent is:
Strict transparent Google modes redirect only to the declared redirection_url. They do not apply Split routing, offer rotation, cloaking destination changes, device/geo rules, or fallback destinations.
How the redirect works
When a user clicks an advertising link configured through FourLook, the request is received by the FourLook tracking endpoint. FourLook records the applicable tracking and attribution information and then redirects the user to the destination URL specified by the tracking request.
Immediate next-hop destination
Google’s transparent click tracker guidance emphasizes clarity around the immediate next-hop destination. In FourLook’s strict transparent Google modes, that next hop is the value of the redirection_url parameter.
Example using redirection_url
https://click.fourlook.com/gads-click?redirection_url=https%3A%2F%2Fadvertiser.com%2Flanding
In this example:
- The tracker receives the click at
/gads-click. - The declared destination is
https://advertiser.com/landing. - After validation and logging, FourLook redirects to that declared destination.
- FourLook may append its own click correlation parameter
fl_click_id.
FourLook /gads-click endpoint
FourLook provides a dedicated transparent click tracker endpoint:
https://click.fourlook.com/gads-click
Template shape:
https://click.fourlook.com/gads-click?redirection_url={lpurl}&gclid={gclid}&gbraid={gbraid}&wbraid={wbraid}&campaignid={campaignid}&adgroupid={adgroupid}&creative={creative}&device={device}&matchtype={matchtype}&keyword={keyword}
Validation behavior
redirection_urlis required.- It must be an absolute HTTPS URL.
- Double-encoded absolute URLs are rejected.
- Localhost, IP hosts, unsafe characters, and invalid hosts are rejected.
- Accepted clicks are logged for reporting.
- The redirect target remains the declared
redirection_url.
Google must still review and approve the tracker domain and path. FourLook does not claim automatic certification or guaranteed approval.
First-party GGADS bridge
Customers can also upload a FourLook-generated index.php file to an advertiser-controlled HTTPS path such as:
https://brand.com/GGADS/
Google Ads template example:
https://brand.com/GGADS/?redirection_url={lpurl}&gclid={gclid}&gbraid={gbraid}&wbraid={wbraid}&campaignid={campaignid}&adgroupid={adgroupid}&creative={creative}&device={device}&matchtype={matchtype}&keyword={keyword}
The uploaded GGADS file:
- Validates
redirection_urllocally - Sends the click to FourLook server-to-server with a per-campaign token
- Receives the destination from FourLook
- Redirects the visitor using HTTP 302
GGADS is also configured for strict transparent Google use: FourLook logs the click and returns the declared redirection_url with fl_click_id. Split, rotation, cloaking, device/geo redirects, and fallback destinations are not applied to this Google bridge click.
What information is recorded
Depending on the request and campaign configuration, FourLook may record:
- Click ID / FourLook click identifier
- Timestamp
- IP address
- User agent / device / browser information
- Referrer
- Destination URL /
redirection_url - Campaign and tracking parameters
- Google identifiers such as
gclid,gbraid, andwbraidwhen present
See the Privacy Policy for retention, rights, and customer responsibilities.
Policy and abuse controls
FourLook’s Acceptable Use Policy prohibits malicious redirects, phishing, malware, deceptive landing pages, circumvention of advertising-platform policies, fraudulent traffic, unauthorized tracking, and illegal activities. Accounts, domains, or campaigns that appear abusive may be suspended or restricted.
Related pages: