# Install on ClickFunnels Source: https://www.luriart.com/docs/install/clickfunnels Plain text: https://www.luriart.com/docs/install/clickfunnels.txt Add the Luria tag to a funnel's head tracking code, then count the conversion on your order confirmation step. Time needed: about 6 minutes. ## What you'll need * Your Luria tag, with your site ID already in it. You get it during onboarding, or email [hello@luriart.com](mailto:hello@luriart.com) and we will send it to you. The dashboard does not show the site ID yet. * Edit access to the funnel. * To know which version you are on. ClickFunnels 2.0 and Classic put tracking code in different places, and both are covered below. ### Step 1: Open the funnel's tracking code In ClickFunnels 2.0, open the funnel, go to Settings, then Tracking Codes, and find the head box. In Classic, open the funnel, go to Settings, then Tracking Code, and find the Header Code box. [Screenshot: ClickFunnels funnel settings screen with the head tracking code box open and empty] ### Step 2: Paste the tag Paste this into the head box, with your own site ID in place of `YOUR_SITE_ID`, then save: ```html ``` Funnel-level head code runs on every step of that funnel, which is what you want: Luria needs to see the landing step and the confirmation step to tie a conversion back to the version that was live. **Warning:** Luria reads your site ID off the tag itself. If you retype the ID, wrap the tag in other markup, or split it across two boxes, nothing loads and your funnel is untouched. ### Step 3: Count the conversion on the confirmation step Open your order confirmation or thank-you step, open that step's own tracking code, and paste this into its head or footer box: ```html ``` Change the goal name and value to match the offer. Use `window.luria.convert("purchase", 97.00)` for a sale, or `window.luria.convert("lead")` for an opt-in step with no value. The short retry loop is there because the tag loads asynchronously, so `window.luria` can appear a moment after the page does. Luria also counts a conversion on its own when the path is `/thank-you`, `/thank_you`, or `/orders/` plus an order token. Add the call anyway. The automatic one is recorded, but split test results only count conversions you name yourself. **Note:** Put the call on one step only, normally the final confirmation. Calling it on both an upsell page and the confirmation page counts the same buyer twice. ## Verify it worked 1. Publish the funnel and open the live URL in a private window with ad blockers off. 2. View the page source. The tag should sit inside ``. 3. Open DevTools, go to Network, filter for `luriart.com`. You should see calls to `/api/patches` and `/api/events`, and `/api/consent` the first time. 4. In the Console, type `window.luria`. It should return an object, not `undefined`. 5. Run one real test purchase or opt-in, then open the Customers tab in your dashboard. The converted session appears there. [Screenshot: Luria dashboard Customers tab listing converted sessions with source, first seen and value] Full checklist: [Verify your install](/install/verify). ## Common failures **The tag works on the landing step but not the confirmation step** You pasted it into a single step instead of the funnel's tracking code. Move it up to funnel level so every step loads it. **Console says window.luria is undefined** The tag is missing its site ID, so the snippet stops immediately. Or Global Privacy Control or Do Not Track is on in your test browser, in which case Luria collects nothing at all by design. Or you are in a region where Luria shows its own small consent banner and you declined; clear the site data and choose Accept to test again. **Conversions land but no test results move** The conversion is being auto detected rather than named. Add the explicit `window.luria.convert(...)` call to the confirmation step. **One order counted as two conversions** `window.luria.convert` ran twice, usually because it is on two steps. Call it once. **A second copy of the tag** Harmless. Luria ignores the duplicate rather than counting twice. Remove the spare anyway. ## Next steps * [Verify your install](/install/verify) * [JavaScript events reference](/reference/javascript-events) * [Snippet not firing](/troubleshooting/snippet-not-firing) * [Reading your results](/tests/reading-results)