BluePoint Ads

Blue Point Advertising Limited · Search & demand-gen measurement

Click measurement for search and demand-gen accounts.

Blue Point Advertising Limited is a Hong Kong–registered click tracker for agencies and B2B advertisers running Google Ads. Place the measurement URL in the Tracking template field—not the Final URL. Shoppers go to the declared Final URL; Google Ads loads the tracking URL in the background. Automated Google-Ads-Compliance PINGs receive 204 No Content. Authentic hops follow the visible em_dest parameter after HTTPS hostname validation. This site is hop measurement for Search and demand-gen—not an ABM or intent platform.

Open tracking docs Talk to accounts

1

Measured clicks (this instance)

1

HTTPS em_dest hops

100.0%

Valid share (rolling)

Account-level hops that stay reviewer-legible.

Search and demand-gen campaigns share one measurement URL while each click still carries its own explicit landing. Telemetry, screenshots, and policy Q&A map to the same rows—including the 204 lane that keeps Google Ads backend PINGs off the user navigation path. Built to the published Transparent Click Tracker Certification guidelines; we do not claim a listing on Google’s certified tracker list.

Tracking template

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

Shopper path

User → Google Ads Final URL

Measurement path

Tracking URL loaded in the background

Measurement pipeline

From tracking template to declared landing—no shadow hops.

Browser

GET /click?em_dest=… → 302 to the decoded HTTPS hostname. Logged in Audit.

Google-Ads-Compliance

Same URL, User-Agent match → 204 No Content, empty body, not written to click_events.

1

Template

Agencies place https://bluepointads.com/click?em_dest={lpurl} in the Google Ads Tracking template field. The Final URL stays the declared landing.

2

Validate

Only absolute HTTPS URLs with a hostname pass. IP addresses and deeplinks fail closed and are logged before any redirect.

3

Parallel lane

Background Google Ads requests that identify as Google-Ads-Compliance receive 204 No Content immediately—empty payload, no navigation, no cookie theatre.

4

Human hop

Authentic users continue with a single server-side away redirect to the decoded em_dest so reviewers can line up the address bar with policy.

5

Ledger

Non-PING outcomes land in click_events so Audit exports match production hops for every search or demand-gen account.

Who it is for

Built for how agencies and B2B paid media actually operate.

Search agencies

Standardize measurement across client accounts. Every hop stays tied to the visible query string buyers and reviewers can audit.

  • · Shared tracking template
  • · Fast invalid URL detection
  • · Evidence-first troubleshooting

B2B demand-gen teams

Keep Search, Display, and Performance Max hops aligned with policy: reviewers read the same Audit rows your media team uses in account reviews.

  • · Parallel-tracking 204 path
  • · Landing-level transparency
  • · Live metrics from this deployment

In-house Google Ads operators

One documentation surface, one evidence model, less bespoke slide-deck archaeology when compliance asks how the hop works.

  • · Repeatable certification story
  • · Shared legal entry points
  • · Console-ready operator access

Under the hood

Wire-level clarity for reviewers—not dashboard theatre.

The contract is small on purpose: validate the open HTTPS destination, branch the Google Ads background PING into a 204 fast path, then issue the human redirect. That is how you show auditors both halves of parallel tracking—automated silence plus a clean user hop—without inventing a second hidden destination graph.

Sample request

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

Browser

302 → https://example.org/offer

Google Ads backend PING

User-Agent: Google-Ads-Compliance

→ 204 No Content · empty body (immediate)

Traffic shape · last 7 days

Normalized from click_events · last refresh 2026-08-28 03:19:38

Open full audit →
Sat
Sun
Mon
Tue
Wed
Thu
Fri

Reviewer packet

Live hop evidence, not a mocked screenshot.

Rows below are the latest non-PING records from click_events. Google-Ads-Compliance PINGs receive 204 and are not written here. Pair this table with Docs and the full Audit ledger.

Open full audit →
Time Status Reason Target
2026-08-28 03:19:38 valid redirected https://example.org/

Reviewer proof: backend PING vs live redirect

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.

Show the whole redirect story—not a fragment.

Pair Docs (tracking template + 204 snippet) with Audit rows so certification teams see search and demand-gen measurement, transparent hops, and Google Ads PING handling in one narrative.

Open docs View audit