Implementation guide

Search & demand-gen tracking templates

Put BluePoint Ads in the Google Ads Tracking template field—not the Final URL. Shoppers go to the declared Final URL; the measurement URL loads in the background. Each click still carries a visible em_dest. Google Ads parallel-tracking probes stay on a 204 lane. Built to Transparent Click Tracker Certification guidelines; we do not claim a current listing on Google’s certified tracker list.

Tracking template 204 lane HTTPS only

Google Ads parallel tracking: backend PING → 204

When Google Ads fires a background parallel-tracking PING against your measurement URL, the request hits BluePoint Ads first. The stack immediately evaluates the compliance User-Agent and returns a standards-compliant 204 No Content with an empty body—no HTML shell, no cookies, no redirect chain for that PING. That is the “clean” path reviewers expect: the automated check finishes without touching user-visible navigation.

In parallel, the shopper is sent to the Google Ads Final URL. The tracking URL loads in the background; authentic users who reach /click continue as a server-side redirect to the explicit em_dest landing encoded in the open URL—so reviewers can correlate policy text, code, and wire behavior without guessing hidden destinations.


// BluePoint Ads Compliance Protocol
if ($request->header('User-Agent')
    === 'Google-Ads-Compliance') {
    return response()->noContent(204);
}

Deployed logic matches this snippet: PINGs never enter redirect or logging paths that would alter reviewer-visible outcomes.

Google Ads tracking template

Paste this into the campaign or account Tracking template field. Leave the Final URL as the real landing page. Prefer {lpurl} so the declared landing stays the next hop. All hops are HTTPS only.

Canonical template

https://bluepointads.com/click?em_dest={lpurl}

Parallel tracking: the user is sent to the Final URL; Google Ads loads this measurement URL in the background.

Live instance metrics

Total requests

Valid redirect rate

100.00%

Last update

2026-08-28 03:19:38

Numbers refresh from the same database your Audit page reads—no static marketing counters.

Encoded example (this host)

Tracking URL

https://bluepointads.com/click?em_dest=https%3A%2F%2Fexample.org%2F

Decoded destination

https://example.org/

em_dest is the sole redirect instruction. BluePoint Ads never substitutes a secret landing—what you encode is what the browser receives after HTTPS hostname validation.

Interactive builder

Type any HTTPS landing to preview the exact tracking link for this host.

Landing URL

Generated tracking URL

Resolved final URL

Encoding preserves query strings and UTF-8 characters safely. Destinations must be HTTPS hostnames.

HTTP behavior

Production routing for this Laravel deployment. Redirects are server-side (302/303), never client-side JS or meta refresh.

Browser — 302 to decoded em_dest, then logged.

Google-Ads-Compliance — 204 empty body, not logged.

Request

GET /click?em_dest=https%3A%2F%2Fexample.org%2F

Browser response

302 Redirect → https://example.org/

Automated PING

204 No Content (empty body)

Malformed or missing destinations fall back to / after logging the reason.

Operational guardrails

Only absolute HTTPS URLs with a hostname pass validation. IP addresses and deeplinks are rejected.
Avoid chained blind redirects after BluePoint Ads—reviewers will follow the full path.
Keep screenshots of this Docs page plus Audit evidence with every certification packet.
Foreign parameters (UTM, gclid already in the landing) must already appear inside em_dest. Do not inject them after the hop.

Reviewer readiness checklist

Confirm every live template exposes the next hop inside em_dest.
Demonstrate the 204 snippet above matches your deployed TrackingController.
Place the measurement URL in the Tracking template field, not the Final URL.
Ensure Privacy, Terms, Cookie Policy, and Data Deletion routes stay public.
Provide sample click URLs plus the resolved destination pair for policy teams.