touchtry

<p>Touchtry JwelAR is a powerful WordPress plugin that seamlessly integrates Augmented Reality (AR) try-on functionality into your WooCommerce store. This plugin allows your customers to virtually try on jewelry products in real-time using their device’s camera, enhancing their shopping experience and reducing return rates.</p>
<p><strong>Key Features:</strong></p>
<ul>
<li><strong>Virtual Try-On:</strong> Let customers see how jewelry looks on them from anywhere.</li>
<li><strong>Easy Integration:</strong> Simple setup with your WooCommerce products.</li>
<li><strong>Dedicated AR Link Field:</strong> Add a unique AR try-on link per product.</li>
<li><strong>Shop Page Hover Button:</strong> Display a “Try On” button on product images when hovered.</li>
<li><strong>Single Product Page Button:</strong> Prominent “Virtual Try On” button on product pages.</li>
<li><strong>Customizable Styling:</strong> Easily control button appearance via CSS.</li>
<li><strong>User-Friendly Dashboard:</strong> Includes guidance on GLB uploads, API integration, and pricing.</li>
</ul>
<p><strong>How it Works:</strong></p>
<ol>
<li><strong>Install & Activate:</strong> Upload and activate the plugin on your WordPress website.</li>
<li><strong>Add AR Links:</strong> Use the new “AR Try-On Link” field in the WooCommerce product editor.</li>
<li><strong>Upload GLB Models:</strong> Upload your 3D GLB files and matching transparent images to your Touchtry Dashboard.</li>
<li><strong>Customer Experience:</strong>
<ul>
<li>On shop pages, a “Try On” button appears on hover.</li>
<li>On single product pages, a “Virtual Try On” button is displayed near the Add to Cart section.</li>
<li>Clicking the button launches the live AR try-on view.</li>
</ul>
</li>
</ol>
<p><strong>Requirements:</strong></p>
<ul>
<li>WooCommerce Plugin (active).</li>
<li>A Touchtry account and your product-specific AR links.</li>
</ul>


Touchtry JwelAR

good

Augmented Reality (AR) Try-On Plugin for WooCommerce by Touchtry. Empower your customers to virtually try on jewelry before they buy.

GemFind Digital Solutions

<p><strong>GemFind Diamond Link</strong> brings GemFind’s diamond search experience to WordPress. Jewelers can let visitors browse natural and fancy-color diamonds, view details, print or export PDFs, and use engagement tools such as Drop a Hint, Email a Friend, Schedule a Viewing, and Request More Info.</p>
<h4>Features</h4>
<ul>
<li>React-powered storefront (classic v1 or modern v2 UI)</li>
<li>Shortcode: <code>[gemfindDL_diamond_link]</code> with optional <code>version="1"</code> or <code>version="2"</code></li>
<li>WordPress admin: settings, CSS configurator, and onboarding help</li>
<li>REST API for the storefront and admin UI</li>
<li>Server-side proxy to JewelCloud APIs (avoids browser CORS issues)</li>
<li>Optional <strong>WooCommerce</strong> add-to-cart integration</li>
<li>PDF print export (Dompdf)</li>
<li>Full-width page template for a clean storefront layout</li>
<li>SEO-friendly path routing under your Diamond Link page</li>
</ul>
<h4>Requirements</h4>
<ul>
<li>WordPress 6.3+</li>
<li>PHP 8.1+</li>
<li>A <strong>GemFind / JewelCloud dealer account</strong> and Dealer ID (contact GemFind support)</li>
<li>WooCommerce is optional (only needed for cart checkout flows)</li>
</ul>
<h4>Shortcode</h4>
<p>Place on any page or use the page created on activation:</p>
<pre><code>[gemfindDL_diamond_link]
</code></pre>
<p>Force a specific UI version:</p>
<pre><code>[gemfindDL_diamond_link version="2"]
[gemfindDL_diamond_link version="1"]
</code></pre>
<h4>Support</h4>
<p>For dealer setup and JewelCloud Account ID, contact GemFind at <a href="mailto:support@gemfind.com" rel="nofollow ugc">support@gemfind.com</a> or visit <a href="https://gemfind.com" rel="nofollow ugc">gemfind.com</a>.</p>
<h3>Source code and build instructions</h3>
<p>This plugin includes compiled build artifacts for performance (<code>assets/build/admin.js</code>, <code>public/frontpublic/build/assets/frontend.js</code>, <code>public/static/js/frontend-v1.js</code>).</p>
<p>To comply with WordPress.org Guideline 4 (human‑readable code), the full unminified source and build tooling are maintained in a public repository:</p>
<p>Development Repository: https://github.com/GemFind-Application/New-DL-Wordpress-Plugin</p>
<h4>Build steps</h4>
<ol>
<li><code>composer install --no-dev</code></li>
<li><code>npm install</code> and <code>npm run install:all</code></li>
<li><code>npm run build</code> (admin, v2, then v1)</li>
</ol>
<h3>External services</h3>
<p>This plugin connects to third-party and external services. JewelCloud is <strong>required</strong> for live diamond inventory. Other services below are optional or only used when a merchant enables the related feature. The policy links below were verified at the time of this release.</p>
<h4>1. JewelCloud API (api.jewelcloud.com)</h4>
<ul>
<li><strong>What it is and what it’s used for.</strong> JewelCloud is GemFind Digital Solutions’ diamond inventory platform. The plugin loads live catalog data: filters, search results, detail pages, navigation, dealer authentication, video URLs, and JC options. Browser requests are proxied through the WordPress REST API (<code>gemfind-diamond-link/v1/jcProxy/*</code> and <code>/jcVideoProxy</code>) to avoid CORS issues. PHP also calls <code>https://api.jewelcloud.com</code> directly for activation defaults, init tool, email detail lookups, and server-side diamond resolution. Endpoints used include: <code>AccountAuthentication</code>, <code>GetNavigation</code>, <code>GetDiamondFilter</code>, <code>GetColorDiamondFilter</code>, <code>GetDiamond</code>, <code>GetColorDiamond</code>, <code>GetShapeByColorFilter</code>, <code>GetDiamondDetail</code>, <code>GetStyleSetting</code>, <code>GetDiamondsJCOptions</code>, <code>GetInitialFilter</code>, and <code>api/jewelry/GetVideoUrl</code>.</li>
<li><strong>What data is sent and when.</strong> The merchant’s JewelCloud Dealer ID (saved in plugin settings) is sent on every call. Filter and search query parameters (shape, carat range, colour, clarity, etc.) are sent when the storefront loads or the visitor changes filters. Diamond inventory IDs are sent when a visitor opens a detail page, requests a video URL, or uses WooCommerce add-to-cart. If the merchant enables AccountAuthentication, the configured dealer password is also sent once during plugin initialisation (<code>initToolApi</code>). The plugin does not intentionally send visitor name, email, or phone number to JewelCloud inventory APIs.</li>
<li><strong>Terms of service.</strong> https://gemfind.com/pages/terms-of-service — please refer to GemFind for Terms of Service, as JewelCloud is operated by GemFind Digital Solutions.</li>
<li><strong>Privacy policy.</strong> https://www.jewelcloud.com/policies/privacy-policy</li>
</ul>
<p>JewelCloud is operated by GemFind Digital Solutions. GemFind’s Terms of Service define the GemFind Network as including <code>www.jewelcloud.com</code>. Use the GemFind Terms link above for contractual terms; use the JewelCloud privacy policy link above for JewelCloud data-handling practices.</p>
<h4>2. JewelCloud diamond view tracking (platform.jewelcloud.com)</h4>
<ul>
<li><strong>What it is and what it’s used for.</strong> GemFind/JewelCloud analytics endpoint that records when a visitor views a diamond detail page in the storefront (v1 and v2).</li>
<li><strong>What data is sent and when.</strong> Dealer ID, vendor/retailer ID, diamond inventory ID, the site’s origin URL, and the visitor’s public IPv4 address (see Geolocation DB below). Sent from the visitor’s browser as a POST to <code>https://platform.jewelcloud.com/DiamondTracking.aspx</code> once per diamond detail page load, after diamond details are loaded and an IP address is obtained.</li>
<li><strong>Terms of service.</strong> https://gemfind.com/pages/terms-of-service — please refer to GemFind for Terms of Service, as JewelCloud is operated by GemFind Digital Solutions.</li>
<li><strong>Privacy policy.</strong> https://www.jewelcloud.com/policies/privacy-policy</li>
</ul>
<h4>3. Geolocation DB (geolocation-db.com)</h4>
<ul>
<li><strong>What it is and what it’s used for.</strong> Public IP lookup service used to obtain the visitor’s public IPv4 address for JewelCloud diamond view tracking (see section 2 above).</li>
<li><strong>What data is sent and when.</strong> The visitor’s browser sends a request to <code>https://geolocation-db.com/json/</code> when a diamond detail page loads. The plugin only reads the returned IPv4 address and forwards it to the JewelCloud tracking endpoint. No visitor name, email address, phone number, or form data is sent to this service by the plugin.</li>
<li><strong>Terms of service.</strong> https://geolocation-db.com/terms</li>
<li><strong>Privacy policy.</strong> https://geolocation-db.com/privacy</li>
</ul>
<h4>4. Facebook (connect.facebook.net, facebook.com)</h4>
<ul>
<li><strong>What it is and what it’s used for.</strong> Optional Facebook Like button on diamond detail pages when the merchant enables “Show Facebook Like” in plugin settings. The v1 storefront loads the Facebook SDK via the <code>react-facebook</code> library (<code>connect.facebook.net</code>). Share links may open <code>facebook.com</code> in a new tab without loading the SDK.</li>
<li><strong>What data is sent and when.</strong> Page URL and standard Facebook widget/SDK telemetry as described in Meta’s policies. Sent only when <code>show_Facebook_Like</code> is enabled and the visitor views a diamond detail page that renders the Like widget. The plugin does not send visitor form data to Facebook.</li>
<li><strong>Terms of service.</strong> https://www.facebook.com/terms.php</li>
<li><strong>Privacy policy.</strong> https://www.facebook.com/privacy/policy</li>
</ul>
<h4>5. Google reCAPTCHA</h4>
<ul>
<li><strong>What it is and what it’s used for.</strong> Optional spam protection on storefront contact forms (Drop a Hint, Email a Friend, Schedule a Viewing, Request More Info). Loaded only when the merchant configures a reCAPTCHA Site Key in plugin settings (scripts from Google).</li>
<li><strong>What data is sent and when.</strong> Standard reCAPTCHA telemetry (browser/device signals, IP address, interaction data) is sent to Google when a visitor submits a protected form. With no Site Key configured, the plugin makes no calls to Google reCAPTCHA. The plugin does not store this data; Google does.</li>
<li><strong>Terms of service.</strong> https://policies.google.com/terms</li>
<li><strong>Privacy policy.</strong> https://policies.google.com/privacy</li>
</ul>
<h4>6. Camweara virtual try-on (cdn.camweara.com)</h4>
<ul>
<li><strong>What it is and what it’s used for.</strong> Optional virtual try-on experience (iframe) provided by Modaka Technologies (Camweara) when the merchant enables try-on in plugin settings (<code>display_tryon</code>). The iframe is loaded from <code>https://cdn.camweara.com</code>.</li>
<li><strong>What data is sent and when.</strong> Diamond or setting identifiers embedded in the iframe URL (carat, shape, SKU/stock number, company name). Sent only when the visitor opens the try-on feature on a diamond or setting detail page and try-on is enabled in settings. No visitor name, email, or message content is sent by the plugin to Camweara.</li>
<li>Terms of service. At the time of release, Camweara does not publish a separate Terms of Service page. Please<br />
contact Camweara directly for any contractual terms applicable to your account.</li>
<li>Contact: https://camweara.com/contact-us/</li>
<li><strong>Privacy policy.</strong> https://www.camweara.com/privacy-policy</li>
</ul>
<p>Use of GemFind Diamond Link (including the optional Camweara try-on integration) is governed by GemFind Terms of Service. Camweara is operated by Modaka Technologies; data handling for the try-on iframe is described in Camweara’s privacy policy. Modaka Technologies does not publish a separate public Terms of Service URL for Camweara — merchant contractual terms are provided when subscribing to Camweara (contact info@modakatech.com).</p>
<h4>7. Optional: GemFind support notification (off by default)</h4>
<ul>
<li><strong>What it is and what it’s used for.</strong> Optional email copy of the merchant registration form to addresses the site owner configures.</li>
<li><strong>What data is sent and when.</strong> If enabled via the <code>gemfindDL_share_registration_with_support</code> option and the <code>gemfindDL_support_registration_recipients</code> filter, the merchant’s name, email, phone, and shop domain are emailed to the configured recipient addresses when the registration form is submitted. <strong>Disabled by default</strong> — no data is sent unless the site owner explicitly enables this.</li>
<li><strong>Terms of service.</strong> https://gemfind.com/pages/terms-of-service</li>
<li><strong>Privacy policy.</strong> https://gemfind.com/pages/privacy-policy</li>
</ul>
<h4>8. Optional: Remote SMTP settings API (off by default)</h4>
<ul>
<li><strong>What it is and what it’s used for.</strong> Optional sync of SMTP mail settings from a merchant-configured remote HTTP API into the plugin database. Used only when <code>GEMFINDDL_REMOTE_FORM_API_URL</code> is defined in <code>wp-config.php</code> or the <code>gemfindDL_remote_form_api_base</code> filter returns a base URL. No remote URL is hardcoded or called by default.</li>
<li><strong>What data is sent and when.</strong> The site’s shop domain is sent to the configured remote API endpoint to retrieve SMTP host, port, credentials, and from-address settings. This happens only when an administrator triggers SMTP sync or the plugin attempts to load remote SMTP config. <strong>Disabled by default</strong> — no data leaves the site unless the merchant explicitly configures a remote API URL.</li>
<li><strong>Terms of service.</strong> Not applicable when disabled (default). When enabled, governed by the merchant’s chosen remote API provider.</li>
<li><strong>Privacy policy.</strong> Not applicable when disabled (default). When enabled, governed by the merchant’s chosen remote API provider.</li>
</ul>
<h4>9. Optional: Social share links (pinterest.com, twitter.com — user-initiated)</h4>
<ul>
<li><strong>What it is and what it’s used for.</strong> Optional share icons on diamond detail pages. When a visitor clicks a share icon, the browser opens a Pinterest or Twitter/X share URL with the current page address. No SDK is loaded and no request is made until the visitor clicks.</li>
<li><strong>What data is sent and when.</strong> Only the current page URL is passed in the share link when the visitor clicks Pinterest or Twitter/X share. No visitor name, email, or form data is sent by the plugin.</li>
<li><strong>Terms of service (Pinterest).</strong> https://policy.pinterest.com/en/terms-of-service</li>
<li><strong>Privacy policy (Pinterest).</strong> https://policy.pinterest.com/en/privacy-policy</li>
<li><strong>Terms of service (Twitter/X).</strong> https://twitter.com/en/tos</li>
<li><strong>Privacy policy (Twitter/X).</strong> https://twitter.com/en/privacy</li>
</ul>
<h3>Privacy policy</h3>
<p>Sites using this plugin should disclose in their privacy policy that:</p>
<ul>
<li>Visitor diamond search and inventory requests are processed through the JewelCloud API (<code>api.jewelcloud.com</code>), operated by GemFind Digital Solutions.</li>
<li>When a visitor views a diamond detail page, the storefront may request the visitor’s public IP from Geolocation DB (<code>geolocation-db.com</code>) and send a tracking ping to JewelCloud (<code>platform.jewelcloud.com</code>) with dealer ID, diamond ID, site URL, and IP address.</li>
<li>Email addresses and messages submitted through Drop a Hint, Email a Friend, Schedule a Viewing, or Request More Info are sent to the jeweler’s configured admin email address using either the WordPress mailer or the SMTP credentials saved in the plugin.</li>
<li>If the merchant configures a reCAPTCHA Site Key, Google reCAPTCHA collects browser and device signals on protected forms.</li>
<li>If the merchant enables Facebook Like, Meta/Facebook may collect data per their policies when the Like widget loads.</li>
<li>If visitors use social share icons, Pinterest or Twitter/X may receive the page URL per their policies (see “External services” #9 above).</li>
<li>If the merchant enables virtual try-on, Camweara (<code>cdn.camweara.com</code>) loads in an iframe with product identifiers in the URL.</li>
<li>If the merchant opts in to support notifications (see “External services” #7 above), customer name, email, phone, shop domain and site URL are emailed to the configured recipients.</li>
<li>If the merchant configures a remote SMTP settings API (see “External services” #8 above), the shop domain is sent to that remote service to retrieve mail settings.</li>
<li>Completing the in-plugin merchant registration form can optionally email the WordPress site administrator (off by default; enable with the <code>gemfindDL_send_installer_registration_thank_you</code> filter).</li>
<li>WooCommerce, if used, applies its own checkout and customer data policies.</li>
</ul>


GemFind Diamond Link

Embed the GemFind Diamond Link diamond search and listing tool on your WordPress site with a shortcode, admin settings, and JewelCloud inventory.

Touchtry JwelAR vs GemFind Diamond Link