How to use virtual try-on with Meta Ads

1. Is your product page ready for ad traffic?

Install and enable Spequlo on the storefront first. Open the actual product URL you plan to advertise and confirm that the try-on button appears for the intended product. Check that the product is enabled for try-on and that your store has available try-ons.

On a phone, open the panel, provide a test photo, generate a result and return to the product. Check the selected product and variant as you continue to the cart. Use a real product page rather than the Spequlo shopper demo: the campaign should bring shoppers to the store where they can buy.

2. How do you open try-on from an ad link?

Add spequlo_open=tryon to the destination product URL. For a URL with no query string, an example is https://your-store.com/products/linen-shirt?spequlo_open=tryon. If it already contains a variant or campaign parameter, append &spequlo_open=tryon before any fragment instead of adding a second question mark.

Keep your existing campaign tags. For example, /products/linen-shirt?utm_source=instagram&utm_medium=paid_social&spequlo_open=tryon keeps those tags and asks the widget to open. The recognised value is exactly tryon in lowercase.

Load the final URL on your storefront and confirm that the product-context panel opens when the widget is ready. The parameter opens the panel; the shopper still starts generation themselves. Also test the same product without the parameter to confirm the usual experience.

3. How do you compare automatic opening with the usual page?

For a controlled comparison, use a campaign destination without spequlo_open=tryon. Explicit opening links are excluded from the Meta-traffic experiment because they already ask the widget to open. Combining them would prevent the intended comparison.

In your Spequlo dashboard, find Test Spequlo with ad shoppers. Choose a treatment share between 5% and 95%, then start the test. The treatment sees the panel open automatically and the control sees the product page as usual. Both groups can use Spequlo, so this measures automatic opening rather than Spequlo versus no Spequlo.

A device receives a stable group assignment for the test. The widget records one exposure for the run within a browser session and opens automatically only for a new treatment exposure. The same browser can return in a later session; this is not a permanent, person-level holdout.

4. Which Facebook and Instagram visits qualify for the test?

The widget checks for fbclid, a recognised utm_source such as facebook, instagram, fb, ig or meta, or a Facebook or Instagram referrer. It remembers the signal category for up to 30 minutes within the browser session, so a shopper can arrive on a collection page and then navigate to a product.

For this eligibility check, the widget retains the category of signal rather than the raw click identifier or UTM value. Missing referrers or stripped parameters can leave a visit unrecognised. Organic social links can qualify too: the detection is evidence of Meta-origin traffic, not confirmation of paid campaign attribution.

5. How do you verify the Shopify try-on events?

If you need events as well as landing-page behaviour, check the Shopify path separately. Spequlo publishes spequlo:try_on_started for a generation start, spequlo:try_on_completed for a viewed result and spequlo:outfit_created for a completed complementary outfit generation, when Shopify's analytics publisher is available.

Have your receiving pixel or integration subscribe to the custom event names you need. The available payload includes selected product identifiers and, when available, an event identifier, product name and product value. It does not include shopper photos, measurements or email addresses. A product value is not proof of a purchase.

Trigger each relevant action on the storefront and verify receipt in the Shopify pixel setup. If you have configured forwarding to Meta, verify receipt there separately. A published Shopify event does not by itself confirm that Meta received it. This guide does not install a Meta pixel or a direct Conversions API connection.

6. What should you review before keeping automatic opening?

Compare the groups over the same period using the dashboard's visitors, completed try-ons, add-to-cart activity, purchasers and orders. Give purchase outcomes more weight than panel opens: the treatment deliberately opens the panel, so an increase in opens is expected.

Check the mobile shopping flow alongside the counts. If the experience gets in the way of browsing or buying, stop the test from the dashboard. Stopping the experiment does not remove a spequlo_open=tryon parameter from any ad URLs you configured separately.

Interpret results with the browser-based identity limits in mind. One person on two devices can appear as two visitors, storage changes can reset identity, and some journeys will not link to an order. Keep Meta's campaign reporting separate from this storefront experiment; the experiment does not supply ad spend or a campaign ROAS calculation.

Questions, answered

Why did my ad link fail to open the fitting room?

Check that the final product URL still contains spequlo_open=tryon, the widget is enabled for that product, and try-ons are available. Confirm that redirects preserve the parameter and test the final destination on a phone.

Why does a visitor not appear in the Meta-traffic test?

The test must be running, the page must be eligible for the widget, and the browser needs a recognised Meta traffic signal. Explicit spequlo_open=tryon links are outside the experiment. A repeat visit within the same browser session does not create another exposure.

Does opening the panel count as a completed try-on?

No. The Shopify start event requires generation to begin. The completion event requires the shopper to view the result. Panel opens are a different action.

Do I need a Meta access token for ad-link opening?

No. The URL parameter and the storefront experiment do not require a Meta account connection. Sending custom events onward to Meta requires its own receiving integration and configuration.

Can I run this as a Spequlo-versus-no-Spequlo holdout?

The built-in Meta-traffic test compares automatic opening with the usual page, where Spequlo remains available. A test that removes Spequlo from the control group needs a different setup.