Tangiblee transforms existing product images into an on-brand interactive experience, that leverage the advantage of the digital interface (smartphone, laptop, etc`) used to browse the website.
Adding Tangiblee to your website is as simple as adding a Tag (one line of code) to the product-detail-page (PDP) on which it is configured to render as a call-to-action (CTA).
Tangiblee CTA is fully customizable to your brand and style; it can be a clickable image, a stand-alone button, a text link, or any element the user can interact with (click, hover, etc.). The CTA can be served either from the Tangiblee platform or directly from your CDN or CMS - whatever best fits your technical needs.
Integrating Tangiblee is basically means mapping the logic of the PDP to the logic of Tangiblee platform - we call the file that contains that mapping logic: mapper.js
The mapper.js can be written by Tangiblee team or by your team, depends which type of integration you chose.
With this option, Tangiblee team develops the initial implementation of mapping code (mapper.js) tailoring Tangiblee to the PDP layout and structure of the Client’s website.
Client's team installs mapper.js either as a Tag or hosts it as a file and add it directly to the website. Going forward, Client's IT has full control over mapper.js content to customize Tangiblee and update it according to changes in the PDP structure.
Pros: Ideal for fast integration to launch Tangiblee; requires minimal effort from the client. Provides full control to Client's IT team in terms of customization going forward. No need to update Tangiblee team on every PDP structure change.
Cons: None :)
Click here to see examples and detailed instructions on how to implement Semi-Managed Integration.
Managed (Less flexible, easy to start with)
With this option, Tangiblee team will complete 99% of the integration work providing the client with a single line of code (aka a Tag or a snippet) that is already tailored to the current product-detail-page layout and structure of the client’s website. The one line of code that Tangiblee provides is a wrapper to the mapper.js that is loaded from Tangiblee CDN.
Pros: Ideal for initial integration to launch Tangiblee; requires minimal effort from the client.
Cons: Less flexible, customizations are done by Tangiblee team; Client MUST update Tangiblee team when PDP structure is updated, to ensure Tangiblee continues to work on client's website.
Click here to see examples and detailed instructions on how to implement Managed Integration.
Self-Service (More flexible, requires more work)
With this option, Client’s IT team gets full access to the Tangiblee API script to map and tailor the Tangiblee experience to the specific layout of their product-detail-page - basically, the Client writes it's own mapper.js
Pros: Enables full customization of the Tangiblee experience, giving full control to the client on how the Tangiblee CTA is rendered and how the experience is configured.
Cons: Requires more work from the client’s IT team. This includes writing mapper.js that relies on Tangiblee API script.
We recommend to use this integration after initial integration was successfully implemented and the client is looking to maximize the value it gets from Tangiblee, and has the IT resources to allocate for that.
Click here to see live examples and detailed instructions on how to implement Self-Service Integration.