WebAR settings & the launcher

AR is enabled by default on published projects — these settings control how it is offered.

Yayınlanan projelerde AR varsayılan olarak açıktır — WebAR Settings nasıl sunulacağını belirler.

Adım 1/7

Yayınlanan projelerde AR varsayılan olarak açıktır — WebAR Settings nasıl sunulacağını belirler.

WebAR ayarları

Adım 1 / 7

1. Yayınlanan projelerde AR varsayılan olarak açıktır — WebAR Settings nasıl sunulacağını belirler.
2. Launcher’ın nasıl sunulacağını seçin — açık tutun, AR-öncelikli bağlantılar paylaşın veya istemediğiniz yüzeylerde butonu gizleyin.
3. AR Placement: varsayılan zemin veya tezgâh; duvar seçeneği tablo, panel ve duvara monte aydınlatma içindir.
4. AR animation: sistem AR görüntüleyicilerinde buton yoktur; bu ayar AR dosyasının ne taşıyacağını belirler — döngüdeki ilk klip ya da kontrolle hareket eden parçalar için hareketsiz ürün.
5. AR Add to Cart: müşteri AR’dan çıkmadan yapılandırdığı ürünü sepete ekler. Açtığınızda buton metni için bir alan belirir.
6. Sağdaki canlı önizleme her değişikliği kaydetmeden önce gösterir.
7. Kaydedin — ayarlar bu projenin public yüzeylerine uygulanır.

WebAR settings

Per project, with a live settings preview:

• Keep WebAR launcher experiences available — the launcher stays on for published projects, giving phones a straight-into-AR path.
• Share AR launcher links without removing the main viewer flow — launcher links coexist with the normal viewer; offering AR-first entry doesn’t cost you the interactive 3D page.
• Disable launcher button — hide launcher entry on surfaces where AR-first isn’t wanted.

The launcher itself — what it is, launcher URLs and iframes — is covered in Links, QR & the launcher.

AR placement

Per project, under WebAR settings:

• Floor or tabletop (default) — the product places on horizontal surfaces.
• Wall — the product places on vertical surfaces: art, panels, wall-mounted shelving, lighting and screens.

Switching a project to Wall rebuilds its AR asset the next time AR is requested.

Walls take longer to find than floors on both platforms — a plain, evenly lit wall gives the camera little to track. Placing on the floor and dragging up onto the wall works too.

AR animation

Per project, under WebAR settings:

• First clip loops (default) — the AR asset carries the model’s first moving clip. Quick Look and Scene Viewer play it on a loop from the moment the product appears; neither has a play button or a way to pick another clip.
• Still, no animation — the AR asset ships without animation. The product stands in its rest pose. Use this for parts that move on a control, such as doors, drawers and dials.

Switching the setting rebuilds the project’s AR assets the next time AR is requested. The 3D viewer on the page is not affected; clips there play by their own triggers.

Scale in AR

The shopper can resize the model, and both platforms show the size as a percentage of the product’s real size with a stop at 100%. That makes your source units part of what the shopper is told: a model authored in centimetres reports “100%” at a size that was never real. Conversion refuses implausible world sizes rather than shipping them, so a unit error surfaces against the export instead of on a customer’s floor.

AR Add to Cart

A shopper inside native AR is invisible to you: it is an OS app, and it reports nothing back. This is the one exception — the shopper adds the configured product to your cart without leaving AR, and it is the only conversion native AR lets you measure.

Turn it on per project. The one thing you type is the button text, which defaults to Add to cart — it changes what the button says, not what it does: the add always lands in your cart and is always counted as an add-to-cart.

The tap reaches your page as a single togenar:ar-add-to-cart event on the embed — same event, same payload, both platforms. Wire it to your cart: see Add to cart. It also counts as a conversion in Analytics.

Requires the AR Add to Cart feature (Professional and Enterprise).

iOS gets a button. Android gets attribution.

	What happens
iOS (Quick Look)	The button appears inside the AR session, and the tap reaches your page as togenar:ar-add-to-cart.
Android, on your page (Scene Viewer)	No button of ours — your own “Add to cart” is already on screen, and the AR session it followed is credited through addedToCart().
Android, on a share link or the launcher	The button is drawn on return — there is no page of yours, so it is the only button there is.

Android needs one line from you

Call addedToCart() from your own cart handler, right after your store confirms the add — without it, an AR-driven conversion on Android is not attributed.

tg.addEventListener('togenar:ar-add-to-cart', () => addToCart(tg.getSkus()));  // iOS: fires from inside AR
addBtn.addEventListener('click', async () => {
  await addToCart(tg.getSkus());
  tg.addedToCart();                                                         // Android: credits AR
});

What iOS needs

Quick Look draws its call-to-action only when both a subtitle and a price are available, and both are read live, never typed:

• Subtitle — the shopper’s current selection (“Anthracite · With table”).
• Price — your store’s own total, pushed with the SDK’s setPrices().

No price, no iOS banner

A page that never calls setPrices() gets the Android button and nothing on iOS. It fails silently, so check the tap count in Analytics after you turn it on.

The desktop shopper, who finishes on a phone

Scan a QR code and the phone opens the viewer directly, with no page of yours to push a price or receive an event. The QR link carries the configuration and the price across, and the tap comes back to your product page as a navigation — the wiring is one if on page load, in Add to cart from AR.

Both halves require your product page’s domain on the workspace allowlist. Until it is listed, the banner points back at the Togenar viewer.

It costs the iOS photo button

Apple’s banner takes the slot Quick Look uses for its photo button, so iOS shoppers can no longer screenshot or share the model from inside AR. You are trading organic reach for a measurable conversion — which is why it is off by default. Android loses nothing.

iOS Safari only. Chrome, Firefox and Edge on iOS ignore the banner — AR still opens, it just cannot be measured there.

Plan entitlement

AR Support is a plan feature: launcher links and launcher embeds require it, while direct viewer sharing keeps working on every plan. The panel states this exactly where it applies (see Plans & billing).

Pre-launch checklist

• Scale: the model was exported in meters at true size — AR renders it 1:1 in the room (Preparing models).
• Configured products: multi-part selections merge server-side per selection and are cached — first entry per new combination warms the cache, repeats are instant.
• Your own AR button: call enterAR() from a real click handler (Localization & AR).
• Desktop: offer the QR handoff (getQr()), don’t hide AR entirely.
• Something still off? Troubleshooting lists the device-specific causes.