What the snippet you add to your site actually does, what it costs your page, and how it behaves when things go wrong.
What you install
To use Converly, you need to install a script tag in the <head> of every page. You will be given it when you create a flow in your account (or you can access it in the Settings section of your account). It looks a bit like this:
<script src="https://js.converly.io/v1/loader.js?key=site_XXXXXXXX"></script>The site key travels in the URL rather than a data- attribute deliberately. This is because popular WordPress optimization plugins strip data- attributes when they defer scripts, and this breaks the tracking as the code snippet wouldn't know which Converly account to associate conversions with.
What it does
When placed on your website, the Converly tracking code does the following:
- Sends a heartbeat back to Converly's servers so we know it's installed and running.
- Reads any ad click identifiers and campaign parameters from the URL when the visitor first arrives and stores them in first-party cookies on your domain.
- Records the landing page and referrer once, so the original source survives later navigation.
- Loads the detection module for whichever form tools your published flows use
- The detection module then listens for a successful conversion (i.e. the Gravity Forms detection module listens for the specific signal Gravity Forms sends on submission success) and reports it back to the main Converly tracking code
- The Converly tracking code then generates a conversion ID and sends everything to our servers as a conversion, where it is processed and sent on to your ad platforms and analytics tools.
What it costs your page
The Converly tracking code is small and served to your visitors from the nearest of 750+ data centers around the world, so it won't affect your page load speed and the normal operation of your website.
| Attribute | Value | Notes |
|---|---|---|
| Transfer size | ~41 KB | Gzipped, which is what actually crosses the network. Around 136 KB uncompressed. |
| Delivery | 750+ edge locations | Converly's tracking code is stored and served to a visitor from the nearest of 750+ data centers around the world, so load time does not depend on where in the world they are. |
| Loading | asynchronous | Does not block rendering or delay your page becoming interactive. |
| Detection code | loaded on demand | Only the detection needed for the tools you actually use is fetched, rather than every supported integration. |
| Failure mode | silent and safe | If the script fails to load, your page and your forms work exactly as they did before. It never sits between a visitor and your form submitting. |
When it refuses to run
If the browser sends the Global Privacy Control signal, the script stops immediately and completely. No cookies, no storage, no network request. If a consent platform is connected and consent for advertising is absent or unknown, it holds off rather than assuming permission.
When the network is unreliable
A conversion that cannot be sent to Converly's servers is queued locally and retried on the next page load, using the same conversion identifier so it cannot double count. Personal data is stripped before anything is written to local storage, so a queued conversion carries the identifiers needed to attribute it and nothing sensitive.
Sends also survive the visitor navigating away mid-submission, which is required for a form that redirects to a thank-you page.
Guardrails
- Two copies of the script on one page do not double fire. The second stands down.
- Conversions are only accepted from the domains on your account, so a copied snippet on another site records nothing. See Security and access.
- Oversized field values are capped, so a visitor pasting something enormous into a textarea cannot break the submission.
- Sensitive fields are skipped before their value is read. See What happens to personal data.