How to Add Jewelry Try On to Squarespace: A Step‑by‑Step Guide to Jewelry Try On Squarespace
Give shoppers confidence by adding a virtual try‑on (VTO) experience to your product pages using link‑based tools like tryitonme.com.
Start with a no‑code Button Block on your Squarespace PDPs, then scale with Code Injection or template edits for site‑wide placement.
Map one try‑on URL per SKU/variant, QA across devices, and track clicks via UTMs and GTM events to measure impact.
Introduction — jewelry try on Squarespace made simple
You want shoppers to feel confident buying jewelry online. A virtual try‑on solution closes the gap between static photos and how a piece looks on a real person. This guide shows how to add a link‑based VTO using tryitonme.com, a zero‑code platform that delivers shareable try‑on links for web, mobile, and social (see a writeup at cermin.id).
Read on for prerequisites, SKU mapping, no‑code button embeds, optional theme edits, QA checks, tracking tips, troubleshooting, and a rollout plan so you can launch quickly.
Quick overview — why virtual try‑on matters for jewelry e‑commerce
Jewelry is an intensely visual purchase. A good try‑on experience helps shoppers:
visualize scale and how a piece sits on them,
compare styles and finishes with less uncertainty,
feel more confident at checkout, and
reduce post‑purchase disappointment and returns.
For rings, earrings, necklaces, bracelets, and watches, previewing a product on yourself closes the gap between curiosity and conversion.
Why tryitonme.com is the Right Fit for Your Business
tryitonme.com is built for retailers who want fast, low‑effort VTO:
Zero‑code, link‑based deployment — no SDK or API work required (tryitonme.com).
Shareable product URLs for product pages, social, and campaigns.
Fast onboarding: purchase a package, send standard product photos, and the tryitonme team/AI handles AR processing — links returned in ~3 business days.
Links work across mobile browsers and social in‑app browsers; contact tryitonme for embed/modal options.
Want a demo or sample links? Book a demo or see the accessory pricing page via cermin.id.
Prerequisites — what you need before starting on Squarespace
Checklist before you start:
Active Squarespace site (Squarespace 7.1 recommended; 7.0 works with selector differences). See a related example at cermin.id.
A tryitonme account with generated try‑on URLs for each product/variant — contact tryitonme.
Optional: Google Analytics / Google Tag Manager for tracking and CRO.
Map products to tryitonme links (inventory & organization)
Create one try‑on URL per SKU or per variant if assets differ. Keep a master CSV or spreadsheet with:
SKU / Product ID
Product name
Variant (if applicable)
tryitonme link (full URL)
Status (Ready / In Progress)
Notes (campaign, image set)
Best practices: use SKUs for reliable mapping, store try‑on URLs in a custom product field in Squarespace for future automation, and version your sheet. For link generation help, contact tryitonme or review pricing notes at cermin.id.
Simple embed — add a Try On button with Squarespace Blocks (no code)
In the product description or product page area, add a Button Block.
Paste the product’s tryitonme URL into the button link and set “Open in new window” (recommended).
Save and publish.
Suggested labels: “Try On”, “See It On You”, “Try It Virtually”.
PDP placement — where to put the try on button for max impact
Placement affects usage and conversions. UX research from the Nielsen Norman Group shows clear, prominent CTAs perform best.
Next to Add to Cart (best: proximity to purchase actions).
Under the main product image or carousel (ties visuals to the try‑on).
Sticky mobile CTA (keeps Try On available as users scroll).
A/B test button color, label, and position to find what converts best for your store.
Advanced embed — persistent/site‑wide button via theme edits or Code Injection
Two scalable paths:
A. Low‑code (Code Injection)
Add a small script to Settings > Advanced > Code Injection. The script can read a SKU or custom field and inject the correct try‑on button into the PDP (see Squarespace Code Injection docs here).
B. Template / Developer (Developer Platform)
Edit product templates to render a shared button partial that pulls try‑on links from a custom field for robust automation. See the Squarespace developer docs.
Version note: selectors and template HTML vary between Squarespace 7.1 and 7.0 — test selectors in the browser console before publishing.
Sample JS snippet (illustrative)
<script>
document.addEventListener("DOMContentLoaded", function () {
var productDetails = document.querySelector(".ProductItem-details"); // adjust selector
var tryOnUrl = "https://tryitonme.com/try/abc123"; // replace per SKU or inject dynamically
if (!productDetails || document.querySelector(".tryon-button")) return;
var button = document.createElement("a");
button.href = tryOnUrl;
button.target = "_blank";
button.rel = "noopener noreferrer";
button.className = "tryon-button";
button.textContent = "Try On";
button.setAttribute("aria-label", "Try this jewelry item on virtually");
productDetails.appendChild(button);
});
</script>
Modal vs new tab behavior — UX tradeoffs and recommendation
New tab:
Pros: simplest, most reliable across browsers and in‑app browsers.
Cons: temporarily leaves the PDP.
Modal/overlay:
Pros: seamless, keeps shoppers on the page.
Cons: needs extra JS and may be fragile across templates and mobile in‑app browsers.
Recommendation: launch using new tab behavior for speed and reliability. If you want a modal later, contact tryitonme to confirm embed options.
Styling & UX considerations for the Try On CTA
Design for clarity and accessibility:
Size: large enough for mobile tap targets (minimum 44×44 px).
<script>
document.addEventListener("click", function (e) {
var link = e.target.closest(".tryon-button");
if (!link) return;
window.dataLayer = window.dataLayer || [];
window.dataLayer.push({
event: "try_on_click",
tryon_url: link.href
});
});
</script>
KPIs to monitor: Try‑on CTR, add‑to‑cart and conversion lift for users who used try‑on, and return rate differences for enabled vs non‑enabled SKUs. For a measurement plan, see an analytics example at cermin.id.
Troubleshooting common issues & quick fixes
Button missing? Check your selector in the script, clear Squarespace cache, and ensure Code Injection is in the correct area.
Wrong product opens? Verify SKU → try‑on URL mapping and custom field usage.
Analytics not firing? Ensure GTM loads before your click listener or push events into the dataLayer manually.
Layout shifts on mobile? Reduce button padding, use a sticky CTA, or adjust CSS to avoid reflow.
Launch checklist & rollout plan
Pick 5–10 top SKUs (rings, earrings, watches) for a pilot (see ROI notes at cermin.id).
Map links and add the Try On button.
Run internal beta and device/browser QA.
Launch to a small live audience.
Review KPIs 1–2 weeks after launch and iterate.
Scale to more products when confident.
Examples, screenshots and copy templates to include when publishing
Prepare these assets for the post: before/after PDP screenshots (desktop + mobile), code blocks (HTML/CSS/JS + GTM snippets), sample button copy variations, alt text suggestions, and product structured data reference at Google Developers. Add captions calling out CSS selectors and where code should be placed.
SEO & content optimization notes
Place “jewelry try on squarespace” in the title/H1 and opening paragraph.
Use “virtual try on squarespace” naturally in the intro and relevant sections.
Avoid keyword stuffing; write for merchants and conversions.
FAQ
Do I need a developer to embed try‑on?
No. You can start with a Button Block and a link. Code is optional for site‑wide automation; developer help is useful for large catalogs or template edits. See a no‑code case study at cermin.id.
Will it slow my site?
A simple link/button has minimal impact. If you add scripts, keep them lightweight and test performance.
Does it work on social?
Yes — shareable try‑on links are designed to work across social and email clients. Test in in‑app browsers to confirm behavior.
How do I track try‑on usage?
Use UTMs on the try‑on links and push click events to your dataLayer or GA via GTM. Example event push is included above.
What if variant assets differ (e.g., size or color)?
Create a separate try‑on URL per variant and store it by SKU in your spreadsheet or a custom product field so the correct link is used for each option.
Call to action — next steps
Ready to try it? Generate demo links and see how a try‑on experience performs on your best‑selling pieces. Visit tryitonme.com to request a demo or start onboarding. For pricing and accessory examples, see cermin.id.