The Tractn Pixel records website page-view observations after installation. Business events such as a signup, lead submission or purchase require separate configuration. A browser event does not by itself verify a person's identity, a unique customer or accounting revenue.
Install in the correct company context
Open the tracking setup for the intended company and copy the snippet shown there. Add it through your website's deployment or approved tag-management workflow. Avoid installing duplicate copies through both the site code and a tag manager.
Apply your site's consent and privacy setup before collecting data. Do not include passwords, authentication links or unnecessary personal information in event fields. Review the actual values being sent, not only the variable names in an example snippet.
Define a successful business event
Choose the action and the exact point where it succeeds. A button click is not the same as a completed signup, and a form validation error should not create a lead conversion. Use the Event & Goal Builder where available, replacing example variables with real confirmed values.
For money events, include the actual amount and three-letter currency code. Keep tests distinguishable from production outcomes, and verify how duplicate submissions or repeated page loads are handled.
Illustration: results chart beside a marketer. Product screens may differ.
Verify the installation end to end
- Open a known public page after the deployment is ready.
- Make the appropriate consent choice and verify expected collection behavior.
- Complete one controlled successful action.
- Confirm the event appears in the intended company with the expected name and time.
- Where lead creation is configured, confirm the lead record and its consent state separately.
If the page-view check passes but the conversion is absent, inspect the business-event implementation. The base snippet does not automatically make every form or signup flow observable.
How does this relate to Google Analytics?
Tractn tracking and GA4 are separate destinations. A connection used to read Analytics data does not automatically send Tractn events to Google. Google's recommended event documentation describes events such as generate_lead, sign_up and purchase and how to verify them.
Use the data within its limits
Consent choices, blocked scripts and incomplete identity links can leave gaps. Use the attribution guide before equating recorded events with unique customers or causal revenue. For email follow-up, finish the separate lead and sequence handoff; a page view is not marketing-email consent.
Frequently asked questions
Does the page-view snippet track confirmed signups?
A page view is not a confirmed signup. Configure successful business events separately and verify that each reaches the correct company and measurement destination.
Should a form button click count as a conversion?
Only if a click itself is the defined goal. For leads or signups, record the successful completion instead, so validation failures and abandoned submissions are not counted as completed outcomes.
How do I verify the tracking setup?
Run a controlled successful action, inspect the resulting record and test duplicate handling and consent behaviour. Check external destinations separately from Tractn’s own records.
Sources
External references
These references support the linked guidance in the article. Product-specific instructions are documented separately below.
- recommended event documentation — support.google.com.
Tractn documentation
Related first-party guides for the Tractn workflows discussed here; these are product documentation, not independent research.