company logo

Help center

Need help? Book a call
See our website
Powered by
All collectionsTroubleshooting & referenceGlossary

Glossary

Plain-language definitions of every Antla term.

Claude Code (gleap) for Aaron From Antla·September 30, 2026

Quick definitions of Antla terms used across the Help Center. Linked articles go deeper where useful.

Funnel

A try-on configuration in Antla: generation style (template or prompt), generation model, and the products that are eligible. Shoppers only see Try On on products that belong to an active Funnel.

See Create your first Funnel.

Funnel product

A Shopify product (or product rule match) linked to a Funnel. Funnel products determine where the Try On button can appear and which looks can be generated.

See Add products: manual vs automated rules.

Try-on

The act of generating an AI look of a shopper (or Studio model) wearing a product. Also used for the storefront / app Try On button and modal experience.

See How shoppers try products on.

Credits (trial / monthly / purchased)

Units consumed when a try-on is generated. Antla draws from pools in order: trial, then monthly plan allotment, then purchased packs. When all pools are empty, Try On is hidden until you add credits or renew.

See How try-on credits work and Plans, upgrades & credit packs.

On Site Design

The Antla admin area where you customize storefront try-on UI: button copy, colors, consent text, email prompts, and related messaging—without editing theme Liquid for day-to-day changes.

See Customize On Site Design.

Try-On Feed

The in-app gallery of completed shopper try-ons for your store. Used for review and merchandising insight; older entries are cleaned on a retention schedule.

See Try-On Feed and Privacy, photos & data retention.

Generation model (Pro / Fast / Light)

The AI route used to create a look:

  • Antla Pro — highest quality emphasis

  • Antla Fast — quicker results

  • Antla Light — lighter / efficient option

Set per Funnel (and selectable in Studio). See Choose a generation model (Pro / Fast / Light).

Discount code

A code Antla can create or attach after a try-on (or in a Klaviyo flow) so the shopper receives a percentage or fixed incentive. Timing and friend-invite behavior depend on your discount settings.

See Discount settings & friend invites.

Customer request

The record created when a shopper submits their email (and related details) after a try-on—used to send follow-up email, attach discounts, and sync toward lists / Shopify as configured.

See Sharing looks & collecting emails and When customers receive emails.

Klaviyo snippet

A reusable Antla link or embed asset for Klaviyo campaigns so recipients land on a product with try-on tracking. Distinct from automated flows.

See Klaviyo snippets & campaign links.

Klaviyo flow

An Antla-built Klaviyo automation that emails shoppers after a try-on—either showing their look or recommending new products on the same photo. Audience can target products, collections, or tags; optional discount; checkout attribution via antla_flow_id.

See Klaviyo flows (show try-on / recommend) and Connect Klaviyo.

Studio

Merchant-only generation inside Antla admin for creating looks with your own model and garment photos. History lives in Studio Feed, separate from the shopper Try-On Feed.

See Antla Studio.

App embed

The Shopify theme app embed that injects Antla’s Try On experience on the online store. Must be enabled in the theme editor for the web button to appear.

See Enable the Try On button (theme embed).

Headless SDK

A script plus <antla-block> for custom Shopify storefronts that want Antla’s Try On UI. Connecting it requires Storefront public and private access tokens. Setup is Integrations → Headless SDK integration.

See Connect Headless SDK.

Headless API

HTTP endpoints for uploads, generation, and results. You build the UI. Connecting it does not require Storefront tokens. Setup is Integrations → Headless API integration. GET /context is not available on API-only shops.

See Connect Headless API.

Headless key

The shared credential for Headless SDK and Headless API. The SDK page labels it Antla SDK key. The API page labels it Antla Headless key. Clients send it as X-Antla-SDK-Key. Refreshing it invalidates both integrations.

See Choose where Try On appears.

Draggable block

Antla has two draggable blocks, one for each surface. They are set up separately, but the shopper experience is similar.

  • Shopify theme — antla-draggable-block is an optional block you place on a product template in the theme editor to add an extra Try On control. It works alongside the app embed, which still needs to be on. See Enable the Try On button (theme embed).

  • Tapcart — a custom block you place on an app screen in Tapcart Studio to show Antla Try On in your mobile app. Tapcart is not a card on Antla’s Integrations page. See Tapcart setup.

More looks consent

Shopper permission to reuse their try-on photo for additional personalized looks—especially for marketing recommendation emails. Configurable copy lives in On Site Design.

See Privacy, photos & data retention and Klaviyo flows (show try-on / recommend).

Related articles

  • What is Antla?

  • Choose where Try On appears

  • Analytics dashboard explained

  • Troubleshooting common issues

Did this answer your question?
😞
😐
😁