Let us know

After adding the code into your development environment, it would be a good time to share a link with Eyekandy so that we can begin our pre-live QA and align on next steps.

Product Inventory Matching

If you have integrated a service that utilises product matching (uses a Unique Product Identifier), it is advised that you share your Product Feed with us. This will ensure that the the maximum number number of AR model matches are made available for your inventory.

Technical Steps

In this step by step guide there were some sections that are important but make more sense to discuss after adding the code onto your site as at this point any and all issues will (for the first time) be visible.

The following short sections cover some of the technical setup that may be required to allow the integrated content to load as expected when deployed on your site.

Content Security Policy

Loading external content onto some sites may require edits to your Content Security Policy.

Domain Whitelisting

It is possible that firewalls running in an office or enterprise environment may need to have the domains listed in the Domain Whitelisting reference page.

Events and User Interactions

Whens users interact with the Eyekandy components, it is only possible to observe the events that occur in the "Light DOM". Due to this Eyekandy has implemented a system that allows you to listen for events and then react to them as desired, see the Observing Events reference page for more information.