Wix is popular in Israel — service sites, brochures, and Wix Stores. Insytix connects via **OAuth app** from the Embed page (recommended) or manual Custom Code. You must **Publish** after every change.

Before you start

Insytix account, registered site with Wix domain, editor/manager access. For stores — choose Wix Store when creating the site. Only the **site owner** can install the OAuth app; collaborators view data only.

Method 1: Automatic install (recommended)

Dashboard → **Embed** → «Automatic Wix connection» card → **Install on Wix**. Wix app installer opens; approve install. Insytix receives OAuth, saves connection, and embeds tf.js via Wix APIs (Custom Embed or Embedded Script). After install — **Publish** your Wix site. If tracking isn't live — **Activate tracking automatically** then refresh status on Embed.

  • Embed → Install on Wix → approve in app
  • Publish required after install
  • «Connected to Wix» status on Embed
  • If embed fails — manual paste (method 2)

Method 2: Manual Custom Code

Copy the full block from the «Manual setup» accordion on Embed. In Wix: site editor → **Settings → Advanced → Custom Code** → **+ Add Code** → paste before `</head>` → all pages → **Publish**. Use when OAuth app isn't available on your plan.

Wix Stores

Choose Wix Store site type in Insytix for orders, abandoned carts, and commerce metrics. Ensure tf.js loads on Checkout and Thank You pages. After OAuth connect, store sites are marked ecommerce automatically.

What Insytix tracks on Wix

page_view, phone_click, Wix Forms (form_submit), WhatsApp. Stores — orders and carts. Push. Google/Meta — under **Features**, not Embed.

Verify and troubleshoot

Publish, browse site, check real-time and refresh on Embed. View Source: tf.js and ins_. If OAuth succeeded but embed pending — use manual paste. Custom domain: code on main template.

Wix separates the editor from the published site — Custom Code or OAuth app changes do not go live until you **Publish**. Insytix supports two paths: app connect from **Embed** that embeds tf.js via Wix APIs, or pasting the full block from **Custom Code** before `</head>` on all pages. In both cases the snippet must include `__INSYTIX_CONFIG__`, meta tags, and tf.js with defer and optimizer bypass attributes.

OAuth path vs Custom Code

**Install on Wix** opens the official app installer; after approval Insytix stores OAuth and attempts automatic tag embed. Good for owners who prefer not to edit code. If status stays «embed pending» or the plan blocks apps — switch to manual Custom Code from the «Manual setup» accordion on Embed. Custom Code needs publish after every change; OAuth needs publish after first install. Only the **site owner** can install the app; Wix collaborators can paste code if their role allows.

Custom domain and templates

On a custom domain, put code on the main template served to visitors — not only a single editor page. For Wix Stores explicitly check product, cart, Checkout, and Thank You pages: if tf.js does not load on Checkout, orders may not appear in Insytix. After OAuth connect, store sites are marked ecommerce when site type is **Wix Store**. Run a small test purchase and check the **Orders** tab and real time.

What gets measured on Wix

tf.js sends `page_view` on each published page load, `phone_click` on `tel:` links, `form_submit` from Wix Forms (HTML submit — not external iframe forms), and WhatsApp clicks when detected. On stores — order and cart events when site type and tf.js are active on purchase pages. **Session recordings** (if enabled on your plan) are a separate layer — they do not replace stat events. Push alerts are configured in dashboard → Notifications, separate from embed.

Common Wix troubleshooting

No visitors after install: did you publish? Check View Source on the live site (not the editor). OAuth OK but no embed: paste manual Custom Code. Forms not counted: use built-in Wix Form, not embedded Google Form. Missing orders: **Wix Store** site type + tf.js on Checkout. Google/Meta integrations: **Features**, not embed. Refresh on Embed probes the live site for tf.js, tracking ID, and endpoint.

Wix FAQ

Is Velo required?

No. Head Custom Code or the Insytix app is enough for tf.js tracking.

Wix staging / preview?

Register the public domain in Insytix; unpublished preview does not send events to production.

Working with an agency

An agency can have view access in Insytix and see real time, leads, and sources — but only the Wix owner can approve the OAuth app. If the agency pastes Custom Code, the owner must publish after each change. Share the **Embed** page with the full code block; do not send only a tf.js URL.

Security and privacy

tf.js is a public script on the site — like Google Analytics. It sends tracking events to your account endpoint; it does not access Wix Stores card data. Show a privacy policy suited to form collection. You can disconnect the Wix app in Wix or remove Custom Code — tracking stops until you reconnect from Insytix.

Day-to-day Wix scenarios

Brochure site: after adding a Wix page you do not need to paste again if Custom Code applies to «all pages» and you published. Blog — page_view fires per post. Store: check product and thank-you pages after purchase; if the order is missing in Insytix, the script is likely not on Checkout or site type is not **Wix Store**. Insytix app + immediate publish is the fastest path for owners who avoid code.

Keep an internal note with a screenshot of **Embed** when status is green, last publish date on Wix or WordPress, and active cache plugins. When switching agency or developer, this saves hours: no guessing whether the issue is Insytix account, domain, or an optimization plugin hiding tf.js. A quarterly re-check — form, tel, and test purchase on stores — confirms tracking stayed live after platform updates.

On long funnels, traffic source stays in session when visitors return in the same browser — tag first-touch links with UTM.

On long funnels, traffic source stays in session when visitors return in the same browser — tag first-touch links with UTM.

Still stuck? Request team assistance

Try the steps above first. If tracking still isn't active — dashboard → **Embed** → at the bottom, **Request team assistance**. We need **site admin access only** (WordPress Admin, Wix collaborator, etc.) — not hosting panel or site migration. Application Password or temporary user recommended; passwords are not stored in the app.