Verification and Constraints

Prove both phone controls from the actual click through GTM and GA4. Verify Ads configuration and attributed receipt where legitimately available.

COMPLETE · Paid attribution pendingPrior evidence retained15 / 15 evidence criteria proved

The previous screenshots showed GTM Summary, not event-specific results. This retry closes that proof gap with selected events and matching Analytics parameters.

23 September, mandatory verification complete. Parent inspected original screenshots and accepted the defined verification scope. All 63 evidence-file hashes and decoded image dimensions passed. Honest QA traffic, no paid click ID. A temporary local UI flag exposes the paid-only reveal handler. No live call or provider configuration change.

End goal system

Complete means all mandatory screenshot and coverage checks pass. Paid Ads attribution alone may remain pending.

ConfirmedAssumptionOpen
flowchart TD A["Controlled phone click
Reveal and widget, no call"]:::confirmed --> B["GTM event details
Selected events verified"]:::confirmed B --> C["Matching GA4 events
Session, time and page verified"]:::confirmed C --> D["Ads configuration
Roles and link verified"]:::confirmed D --> E["Attributed Ads conversion
Only legitimate paid activity"]:::open C --> F["Verified interaction delivery
Does not prove calls or jobs"]:::confirmed classDef confirmed fill:#e8f6ed,stroke:#147a3d,color:#173b25 classDef assumption fill:#fce8f0,stroke:#c2185b,color:#5b1430 classDef open fill:#fff,stroke:#94a3b8,color:#475569,stroke-dasharray:5 5

Route to the end state

flowchart LR A["Existing captures
Useful but incomplete"]:::confirmed --> C["Controlled session
Native browser recovery available"]:::confirmed B["Coverage completed
Mobile and consent checked"]:::confirmed --> C C --> D["Capture actual panels
GTM event and GA4 event details"]:::confirmed D --> E["Check measurement scope
Consent, templates and Ads routes"]:::confirmed E --> F["Independent acceptance
Inspect originals and ledger"]:::confirmed classDef confirmed fill:#e8f6ed,stroke:#147a3d,color:#173b25 classDef assumption fill:#fce8f0,stroke:#c2185b,color:#5b1430 classDef open fill:#fff,stroke:#94a3b8,color:#475569,stroke-dasharray:5 5
GTM event panels/Users/agency/Documents/Agty/csupi/deliverables/ads-tracking-verification-20260923-retryActual controlled reveal and widget clicks

Trace phone clicks through GTM

Capture each selected event header, its identifying click variables and the tags fired for that event.

3 / 3
Verification and Constraints
  • No recreated screenshots or claims beyond the evidence.
  • No live ad clicks, real calls, fabricated paid attribution or production settings changes.
  • No private visitor data or authentication details on the public board.

Selected events 17 and 18 show successful GA4 and Ads tags separately. Variables distinguish hero reveal and floating_widget. Original captures are private.

Original screenshots remain private. See the local parent report and evidence-manifest.json for exact paths and hashes.
GA4 event screenshots/Users/agency/Documents/Agty/csupi/deliverables/ads-tracking-verification-20260923-retryKnown controlled QA session

Match each event inside GA4

Prove the two events in GA4 with session or page parameters and timestamps that match the click ledger.

3 / 3
Verification and Constraints
  • No recreated screenshots or claims beyond the evidence.
  • No live ad clicks, real calls, fabricated paid attribution or production settings changes.
  • No private visitor data or authentication details on the public board.

GA4 DebugView shows both phone events at 09:54:19 and 09:55:41 with the unique QA page URL, matching placement and the same session ID. Original parameter captures saved privately.

Original screenshots remain private. See the local parent report and evidence-manifest.json for exact paths and hashes.
Coverage matrix/Users/agency/Documents/Agty/csupi/deliverables/ads-tracking-verification-20260923-retryLive homepage, location and service templates

Verify mobile and consent behavior

Check the actual mobile controls and expected granted or denied consent behavior without changing production configuration.

3 / 3
Verification and Constraints
  • No recreated screenshots or claims beyond the evidence.
  • No live ad clicks, real calls, fabricated paid attribution or production settings changes.
  • No private visitor data or authentication details on the public board.

Actual 390 × 844 mobile homepage, Buda location and furgonmentes service controls delivered one GA4 event per click. All 21 active ad destinations passed bootstrap inventory. Denied consent sends expected cookieless pings. Clean live repeat clicks and header CTA passed.

Original screenshots remain private. See the local parent report and evidence-manifest.json for exact paths and hashes.
Ads screenshot and readback/Users/agency/Documents/Agty/csupi/deliverables/ads-tracking-verification-20260923-retryPrimary GA4 import, secondary direct Ads tag

Confirm Ads measurement configuration

Show how Ads receives phone interactions while keeping genuine paid attribution separate from test delivery.

3 / 3
Verification and Constraints
  • No recreated screenshots or claims beyond the evidence.
  • No live ad clicks, real calls, fabricated paid attribution or production settings changes.
  • No private visitor data or authentication details on the public board.

UI and API confirm action 6509672057 is Primary despite its Secondary label. Direct Ads action is secondary. GA4 link and active campaign goals verified. Genuine attributed Ads conversion remains PENDING.

Original screenshots remain private. See the local parent report and evidence-manifest.json for exact paths and hashes.
Report, manifest, screenshots/Users/agency/Documents/Agty/csupi/deliverables/ads-tracking-verification-20260923-retryProvider captures and chronological test ledger

Publish evidence for independent review

Make every verification claim traceable to an original screenshot and same-session evidence.

3 / 3
Verification and Constraints
  • No recreated screenshots or claims beyond the evidence.
  • No live ad clicks, real calls, fabricated paid attribution or production settings changes.
  • No private visitor data or authentication details on the public board.

Private original captures, SHA-256 manifest, chronological request ledger and parent report are complete. Parent copied the files, verified hashes and accepted the evidence. A private screenshot walkthrough accompanies this board. No private screenshot or telemetry is embedded here.

Original screenshots remain private. See the local parent report and evidence-manifest.json for exact paths and hashes.

Review handoff

Review the private screenshot walkthrough in the Codex file panel: Reveal → Floating button → Mobile and consent → Ads → Limits and next check. The public page intentionally contains no private account screenshots.

Inputs: original captures + provider receipts → output: verified report for understanding tracking → parent acceptance.