Data handling information

Approval status: this technical summary is not an approved privacy notice or legal determination. The responsible legal entity, controller/processor roles, contact details, purposes, lawful bases, retention periods, and processor terms must be verified and approved before service activation.

What the tracker is designed to receive

The HTTP request includes a visible destination URL used for validation and redirect handling. The planned tracking_request event records profile and Link Master asset identifiers, revision and configuration generation, profile-derived project and campaign identifiers, validated immediate-hop host and route labels, selected Google Ads metadata and genuine click-ID fields where applicable, method, and typed warnings. It does not persist the destination URL, request body, IP address, user agent, referrer, keyword, or arbitrary query parameters. Test profiles remove all three click-ID values before persistence. Event schema version 2.0.0 is a design target; integration and deployment have not been verified.

POST bodies are discarded without being parsed or merged into the destination. The tracker is not designed to receive names, email addresses, payment data, or free-form customer content. Consent is unavailable at the tracker.

Browser storage and landing-page measurement

The static information pages contain no JavaScript, analytics SDK, cookie mechanism, local-storage code, or form. The tracker design does not use cookies or fingerprint visitors. A separate landing-page integration would require its own consent and privacy review; it must not infer consent when a consent signal is missing.

Use and limits

A tracking request records an accepted HTTP request. It does not authenticate an ad click or prove advertising attribution, a conversion, or billing. Individual matching is allowed only when the defined consent and time-window evidence is available; otherwise the outcome remains unlinked, ambiguous, or aggregate-only. Tracking-request counts are not human-click or billing counts.

Storage, retention, and location

The design selects Google Cloud region europe-west2 for Pulse runtime and data resources. This does not mean all traffic, logs, backups, control planes, infrastructure state, or external processors stay in the UK or European Economic Area. The effective resource locations, access paths, retention windows, and transfer arrangements still require a residency review and Privacy approval before activation.

The design sets separate retention windows for event data, queues, fallback recovery, and operational audit records. No production retention period or deployed storage location is asserted by this page. The owner must publish verified retention and request-handling details in an approved notice before public service activation.

Requests and contact

This page has no request form or mailbox. Use the contact in the advertiser's current approved privacy notice. The corporate legal owner and privacy contact for Pulse have not been verified in this source.

Read service terms information or return to the service overview.