Partial evidence
3 steps · 2 hosts · 6 recognized event calls from GA4, Meta Pixel, HubSpot · 32.7 s in one browser session
Funnel browser observations
Finding and next validation
Requires internal validation
GA4 event calls were observed at “Pricing”, but not at “App signup entry”.
Events on this page may depend on clicks or form submissions, which this public page check does not complete. Requires internal validation.
If the destination also lacks this event, conversion reporting and ad optimization for this step may be incomplete. Browser silence alone does not establish that.
Check the expected GA4 event for “App signup entry” in the destination debugger. If neither browser nor server delivery appears there, correct the event trigger.
- Navigation
- Direct URL comparison; CTA journey not tested
- Event-call presence
- Homepage: no recognized event calls · Pricing: GA4 2, Meta Pixel 2, HubSpot 2 · App signup entry: no recognized event calls. Requests do not prove destination receipt.
- Visitor continuity
- No attribution-related cookie or storage values matched across handoffs. Visitor identity requires internal validation.
- Signal changes
- GA4 event calls: 0 → 2; Meta Pixel event calls: 0 → 2; 6 more below.
- Campaign attribution
- Requires internal validation. Landing URL tags and payload page URLs do not prove campaign assignment.
- Conversion verification
- No forms or purchases completed. Conversion receipt requires internal validation.
Scope and remaining uncertainty2 limits
3 public URLs across 2 hosts, opened directly in one browser session. No clicks, logins, or form submissions.
- No supported analytics request signatures were observed at “Homepage”, “App signup entry”. Custom collectors, deferred scripts, or browser restrictions may explain this; it does not establish missing tracking.
- Events that fire on clicks or form submissions were not tested, and server-side delivery, CRM records, and destination receipt are outside browser evidence.
Signal coverage overview
Every step in order · scroll table on narrow screens
| Browser signal | Final URL: https://ramp.com/ | Final URL: https://ramp.com/pricing | Final URL: https://app.ramp.com/sign-upFinal URL changed |
|---|---|---|---|
| Page URL campaign tags | Not observed in page URL | Not observed in page URL | Not observed in page URL |
| Total event calls | 0 event calls · not observed | 6 event calls | 0 event calls · not observed |
| GA4 | Not observed | 2 event calls | Not observed · seen earlier |
| Meta Pixel | Not observed | 2 event calls | Not observed · seen earlier |
| HubSpot | Not observed | 2 event calls | Not observed · seen earlier |
| Click-ID: _ttp | Not observed | Cookie observed | Cookie observed |
| Campaign in event payload | Not observed | Not observed | Not observed |
| Conversion evidence | Not designated as a conversion URL. | Not designated as a conversion URL. | Not designated as a conversion URL. |
| Storage keys | 1 keys · 0 click-ID-like | 9 keys · 5 click-ID-like | 2 keys · 0 click-ID-like |
| Consent | CMP not detected | CMP not detected | CMP not detected |
“Not observed” means not observed in browser evidence. Differences do not prove backend tracking failed. SDK loading alone does not establish event delivery.
Funnel path checked
Per-step details · browser observations from one session
Final URL: https://ramp.com/
Submitted: https://ramp.com
- Events / SDK-only
- 0 event calls
Not observed in browser evidence
- Click-ID cookies
- Not observed in browser evidence
- Campaign in event payload
Not observed in browser evidence · no event calls to inspect
- Conversion evidence
- Not designated as a conversion URL.
Final URL: https://ramp.com/pricing
- Events / SDK-only
- 6 event calls
GA4: page_view, Meta Pixel: PageView, HubSpot: Event call
- Click-ID cookies
- _ttpDomain not retained
- _ttpDomain not retained
- Campaign in event payload
Not observed in browser evidence in retained event payloads
- Conversion evidence
- Not designated as a conversion URL.
5 signal changes since step 1. Review cross-step observations ↓
Final URL: https://app.ramp.com/sign-up
Submitted: https://ramp.com/sign-up
- Events / SDK-only
- 0 event calls
Not observed in browser evidence
- Click-ID cookies
- _ttpDomain not retained
- _ttpDomain not retained
- Campaign in event payload
Not observed in browser evidence · no event calls to inspect
- Conversion evidence
- Not designated as a conversion URL.
3 signal changes since step 2. Review cross-step observations ↓
Counts refer to intercepted event requests, not confirmed destination receipt. Cookie availability depends on domain scope; later GA4 hits can omit UTMs while session attribution remains intact.
Cross-step observations
2 observations · 0 supported · 2 need validation
- Pricing: GA4 event calls: 0 → 2
- Pricing: Meta Pixel event calls: 0 → 2
- Pricing: HubSpot event calls: 0 → 2
- Pricing: _ttp cookie: not observed previously → observed at this step
- Pricing: _ttp cookie: not observed previously → observed at this step
- App signup entry: GA4 event calls: 2 → 0 (not observed at this step)
- App signup entry: Meta Pixel event calls: 2 → 0 (not observed at this step)
- App signup entry: HubSpot event calls: 2 → 0 (not observed at this step)
Event counts can vary by page. UTMs on later GA4 page views are not required for session attribution; these changes do not prove attribution loss.
- Requires internal validation
GA4 event calls were observed at “Pricing”, but not at “App signup entry”.
Events on this page may depend on clicks or form submissions, which this public page check does not complete. Requires internal validation.
PrimaryP2 · Can't determine from outsideOwner: Engineering + AnalyticsEffort M
- Requires internal validation
Meta Pixel event calls were observed at “Pricing”, but not at “App signup entry”.
Events on this page may depend on clicks or form submissions, which this public page check does not complete. Requires internal validation.
P2 · Can't determine from outsideOwner: Engineering + AnalyticsEffort M
Browser evidence
Retained requests, cookies, storage, and conditions for each step
Inspect retained events, cookies, storage and navigation by step
Step 03 of 03 · Page view
App signup entry
https://ramp.com/sign-up
- Loaded
- https://app.ramp.com/sign-up
- Navigation
- Direct URL, same browser session
- Consent
- No consent platform detected
- Observed
- 6.7 s · 0 platform requests
Conclusion evidence. GA4 event calls at this step: 0, not observed in browser evidence.
Event calls0
No event calls were observed in this step’s browser evidence. Events may need a click, form submission, or consent, or may be sent server-side.
Script loads0
No supported analytics scripts were loaded at this step. Cached scripts may not appear as new requests.
Storage and forms2
2 storage keys · 0 forms with attribution fields · inspect names
- ajs_anonymous_idSegmentlocalStorage
- ajs_user_idSegmentlocalStorage
Collection and linking0
No first-party collection endpoint or _gl link decoration was observed.
Consent0
No consent platform detected. The scanner does not click consent banners.
Navigation
- Fromramp.comHost changed to app.ramp.com
Session and method
Run-level evidence and the limits of a browser scan
3 public URLs across 2 hosts, opened directly in one browser session. No clicks, logins, or form submissions.
Browser evidence cannot verify visitor identity, campaign assignment, server-side enrichment or conversion receipt. Full request, storage and handoff diagnostics remain available in the interactive report.
- No supported analytics request signatures were observed at “Homepage”, “App signup entry”. Custom collectors, deferred scripts, or browser restrictions may explain this; it does not establish missing tracking.
- Events that fire on clicks or form submissions were not tested, and server-side delivery, CRM records, and destination receipt are outside browser evidence.
Browser evidence summary6 measures
Structured browser evidence from the live funnel scan. GA4 / GTM, Meta Pixel, HubSpot.
Engineering handoffOwner: Engineering + Analytics
Events to add or fix
- Validate conversion and server-side/CAPI events in each destination before sign-off.
Required properties
- utm_source
- utm_medium
- utm_campaign
- gclid/fbclid or destination click ID
- lifecycle_stage
- conversion_step
QA checklist
- Re-run the same public path with a tagged URL.
- Confirm browser-visible event payloads in GA4, Segment, Meta, HubSpot, or the active destination.
- Check whether server-side tagging, CAPI, CRM enrichment, or warehouse joins explain any browser absence.
- Document cannot-determine cases instead of asserting them as proven losses.
Acceptance criteria
- Conversion-step events include campaign context or a validated server-side enrichment path.
- Click IDs persist through the handoff by cookie, localStorage, linker, or server-side forwarding.
- Analytics owner can reproduce the result in the destination debugger.
# Revenue Signal QA Packet Path: Homepage -> Pricing -> App signup entry Steps: 3 Runtime: 32.7s ## Executive Summary Status: Partial evidence (Requires internal validation) Direct URL comparison; CTA journey not tested GA4 event calls were observed at “Pricing”, but not at “App signup entry”. Confidence detail: Events on this page may depend on clicks or form submissions, which this public page check does not complete. Requires internal validation. Scope: 3 public URLs across 2 hosts, opened directly in one browser session. No clicks, logins, or form submissions. Why it matters: If the destination also lacks this event, conversion reporting and ad optimization for this step may be incomplete. Browser silence alone does not establish that. Next action: Check the expected GA4 event for “App signup entry” in the destination debugger. If neither browser nor server delivery appears there, correct the event trigger. ## What Remains Uncertain - No supported analytics request signatures were observed at “Homepage”, “App signup entry”. Custom collectors, deferred scripts, or browser restrictions may explain this; it does not establish missing tracking. - Events that fire on clicks or form submissions were not tested, and server-side delivery, CRM records, and destination receipt are outside browser evidence. ## Recommended Fixes - [ ] P3 Validate: GA4 event calls were observed at “Pricing”, but not at “App signup entry”. - Confidence: Requires internal validation - GA4 event calls were observed at “Pricing”, but not at “App signup entry”. Events on this page may depend on clicks or form submissions, which this public page check does not complete. Requires internal validation. - Owner: Engineering + Analytics - [ ] P3 Validate: Meta Pixel event calls were observed at “Pricing”, but not at “App signup entry”. - Confidence: Requires internal validation - Meta Pixel event calls were observed at “Pricing”, but not at “App signup entry”. Events on this page may depend on clicks or form submissions, which this public page check does not complete. Requires internal validation. - Owner: Engineering + Analytics ## Cross-step observations - Pricing: GA4 event calls: 0 → 2 - Pricing: Meta Pixel event calls: 0 → 2 - Pricing: HubSpot event calls: 0 → 2 - Pricing: _ttp cookie: not observed previously → observed at this step - Pricing: _ttp cookie: not observed previously → observed at this step - App signup entry: GA4 event calls: 2 → 0 (not observed at this step) - App signup entry: Meta Pixel event calls: 2 → 0 (not observed at this step) - App signup entry: HubSpot event calls: 2 → 0 (not observed at this step) Campaign parameters embedded in a payload page URL are distinct from campaign fields. Later GA4 page views can omit UTMs without losing session attribution. ## Funnel Path Checked - Homepage (ramp.com): 0 event calls - Pricing (ramp.com): 6 event calls; events: GA4, Meta Pixel, HubSpot; click cookies: _ttp, _ttp; localStorage: _uetvid_exp, _gcl_ls, _uetsid, _uetsid_exp, _uetvid - App signup entry (app.ramp.com): 0 event calls; click cookies: _ttp, _ttp ## Acceptance Criteria - Conversion-step events include campaign context or a validated server-side enrichment path. - Click IDs persist through the handoff by cookie, localStorage, linker, or server-side forwarding. - Analytics owner can reproduce the result in the destination debugger. - Ambiguous browser absence is documented as requires-internal-validation, not asserted as a proven loss. ## Methodology Caveats - Direct URL navigation only; no form filling, login, cart state, or click automation between steps. - All steps share one browser context, so cookies and localStorage can persist naturally. - Click-ID-like values appeared in localStorage; cookie absence alone is not enough to show attribution loss. - Ad-platform differences reflect browser-visible signal only; this scan cannot detect server-side-only delivery (Meta CAPI, Google Enhanced Conversions) that leaves no client-side trace. - HubSpot activity confirms a browser request or form submission occurred; it does not confirm a CRM record was created, lead score updated, or workflow triggered. - Browser-visible signals only; backend-only CAPI, offline conversions, CRM enrichment, warehouse joins, and server-side transformations require separate validation.
Method and limits8 notes
- Direct URL navigation only; no form filling, login, cart state, or click automation between steps.
- All steps share one browser context, so cookies and localStorage can persist naturally.
- Click-ID-like values appeared in localStorage; cookie absence alone is not enough to show attribution loss.
- Ad-platform differences reflect browser-visible signal only; this scan cannot detect server-side-only delivery (Meta CAPI, Google Enhanced Conversions) that leaves no client-side trace.
- HubSpot activity confirms a browser request or form submission occurred; it does not confirm a CRM record was created, lead score updated, or workflow triggered.
- Public pages only. No login, private account access, unsafe form submission, or account creation.
- Browser-visible signals only. Backend-only Meta CAPI, Google Enhanced Conversions, offline conversions, CRM record creation, warehouse joins, browser/server event deduplication, and other server-side transformations require separate validation.
- Use observed, likely, partially visible, not visible in browser evidence, and requires backend validation language when sharing the result.