Personalization for your T-Soft store
Installed with one script tag on your T-Soft storefront. The basket total is read from the theme’s own variables, with no request.
What the ready integration gives you
Selwise campaigns, recommendations, onsite search and A/B tests run on your T-Soft store. Setup is one script tag in the theme code field that runs on every page. Product views are read from the product code on the page and page type from URL patterns. T-Soft has no ready dataLayer mapping, but Selwise reads the basket total and count from the CART_COUNT and CART_TOTAL variables the theme uses in its header; the goal bar and the “complete free shipping” strip rely on them.
- Basket total and count come from the theme’s window.CART_TOTAL and window.CART_COUNT; a formatted amount like “1.234,56” is parsed
- Product views by themselves: the product code is read from JSON-LD or data-stock-code, data-product-code, data-product-id
- “Add to cart” on recommendation and search cards clicks the button in that product’s own tile on the page
- Campaign, recommendation, search and experiment surfaces all run on the same script; no plugin is installed
On T-Soft, add/remove-from-cart events do not arrive by themselves; the theme sends them with window.selwiseLayer.push. The basket read works only with the T-Soft preset chosen explicitly and the variables present in your theme; the panel’s “Cart value” row shows its state.
- 1Create the channelOpen a web channel for your store in the panel and get your site key.
- 2Add the scriptIn the T-Soft panel, add it to the theme or custom code field so it runs on every page before the closing body tag.
- 3Choose the T-Soft presetIn the Data Layer settings turn the data layer on and choose T-Soft explicitly; the basket read depends on it. Enter page type patterns for Turkish URLs.
- 4Cart events and ordersSend add and remove from cart from the theme code, and the order with trackOrder on the confirmation page.
- 5Connect the feedEnter the feed URL and map its fields; the product code must match orders and the list price is needed for the discount rate.
Where each signal comes from
What is read by itself on your T-Soft store and what the theme code has to send.
| Signal | Source |
|---|---|
| Page viewAutomatic | By itself, on every page the script loads on. |
| Product viewAutomatic | From the product code on the page: Product JSON-LD or data-stock-code, data-product-code, data-product-id. |
| Page typeAutomatic | From URL patterns and page markers; Turkish paths need patterns. |
| Basket total and countAutomatic | From the theme’s CART_TOTAL and CART_COUNT; currency from CURRENCY, “TL” read as TRY. |
| Add and remove from cartYou send it | Not by itself; sent with window.selwiseLayer.push. |
| OrderYou send it | A trackOrder call on the order confirmation page. |
| User identityYou send it | A Selwise.identify call. |
| Search termYou send it | With Selwise search on, the search records it; for the store’s own search a search_query event is sent. |
T-Soft questions
With no request, from the window.CART_COUNT and window.CART_TOTAL variables the theme shows in its header. A formatted amount like “1.234,56” is parsed and the currency comes from the CURRENCY variable. The preset must be set to T-Soft explicitly; if the variables are missing from your theme the cart is not measured and the goal bar is not drawn.
No. The basket total is read, but add and remove from cart do not arrive by themselves; the theme’s cart code sends them with window.selwiseLayer.push. Product views and page type are read by themselves.
Selwise does not call the T-Soft cart API; it clicks the add button or form in that product’s own tile on the page. Without the product’s tile on the page nothing is added; a generic button unrelated to the product code is never clicked.
Two fields: the product code must equal the code you send in orders, and the list price must be mapped for the discount rate to be computed. The feed URL is entered on the panel’s Product Feed screen.
No. One script tag goes into the theme or custom code field and runs on every page; the verification step reads the raw HTML, so the tag must be printed by the server.
