Everything the OCT script does, what it captures, and how to control its behaviour.
Copy the snippet from your project's Settings page and paste it into the <head> of every page on your site.
On every form submission, OCT reads and sends the following data:
A visitor rarely converts on the first page they land on. OCT stores the Google click ID in localStorage when detected in the landing page URL. On subsequent pages, the script reads it from storage — so even if the visitor navigates to a contact page before submitting a form, the gclid is still attached to the lead.
OCT uses a 30-second per-form deduplication window based on sessionStorage. A second submission from the same form on the same page within 30 seconds is silently ignored. This prevents double-counting from accidental double-clicks or form retries.
After 30 seconds, or on a new browser tab, the same form can be submitted again and will create a new lead. Your dashboard marks these as potential duplicates when the email or phone matches an existing lead within the same project.
Enabled in Project Settings → Tracking behaviour → Google Ads clicks only. When on, the script will only send a lead to OCT if the visitor arrived with a valid gclid in their session. Organic and direct visitors are silently skipped.
Use this if you only care about ad-attributed conversions and don't want to fill your lead list with organic enquiries.
By default OCT captures submissions from every <form> element on the page. To restrict it to specific forms, go to Project Settings → Tracking behaviour → Form targeting and enter the name or id attribute of the forms, comma-separated.
The script matches against both the id and name attributes of each form element. Matching is case-sensitive.