What Conversion Tracking Includes
A button click, form start or browser return is not authoritative lead creation. Goal completion must come from ERP acceptance or another approved server-side confirmation.
OreLynx Tracking Technologies and Measurement Disclosure
Last reviewed: 15 July 2026.
The release site loads Google Tag Manager container GTM-NVJGDB9Q on every page without an analytics-choice popup. Tags configured in that container may create analytics requests or browser storage. Essential hosting and security logs may also be created by the origin and CDN.
| Surface | Current design | Operating evidence |
|---|---|---|
| Google Tag Manager | The shared release layout loads container GTM-NVJGDB9Q asynchronously and provides its no-JavaScript fallback. Preview output omits live tags. | Rendered release scan confirms one loader and one fallback per page, with no analytics popup or consent storage key. |
| Assessment conversion | The thank-you page emits lead_form_returned only after its one-time browser token matches. This remains return-path evidence, not ERP creation proof. | ERP readback and confirmation delivery remain the authoritative lead-completion evidence; GTM may use the controlled return event for a separate goal. |
| Page and campaign measurement | UTM values and the source content identifier are held in session storage and included in the submitted CRM message. GTM/GA measurement depends on the published container configuration. | Container trigger and parameter audit, CRM field readback, field-length checks and confirmation that no contact or qualification value enters analytics. |
| Origin and CDN records | Deployed infrastructure may create request and security logs independently of browser storage. | Provider inventory, data locations, access controls, redaction, retention and deletion verification |
| Authenticated application | The web.orelynx.com application is a separate surface and is outside this marketing disclosure. | Separate cookie, session, telemetry and privacy review for the authenticated application |
Prohibited Measurement Data
Do not send names, email addresses, phone numbers, message content, free text, precise coordinates, confidential records, customer data or identifiers that expose an individual or operation through the data layer or tags.
Release Verification
- Confirm one approved GTM loader and fallback appear, with no analytics popup.
- Record every first- and third-party request, cookie and storage key on representative pages.
- Verify that a failed or abandoned form does not emit the success event.
- Confirm that measurement fields contain no submitted contact or qualification data.
- Repeat the audit after deployment through the selected CDN and after every container or measurement-provider change.