Tangiblee API enables customized Tangiblee UX and controls the results tracking implemented on your website.
Tangiblee integration with a PDP consists of two logical blocks, the Tangiblee API and the mapper.js that tailors the API to the specific PDP structure. Below is a detailed explanation for each of the blocks.
An abstraction layer to all the front-end functionalities and capabilities supported by Tangiblee's Platform that can be used on a web-page. Every integration of Tangiblee into a web-page is using Tangiblee API to access Tangiblee, load the CTA and launch the Tangiblee experience. The code that wraps the Tangiblee API and activates it is called the Mapping Code.
In the case of Self-Service Integration, the client’s IT team will write the mapper.js that calls Tangiblee API; however, in the case of Managed Integration, the Tangiblee API is called from the Mapping Code that is provided by Tangiblee.
This layer binds the web-page or PDP to Tangiblee API by acting as a mapper for the information that exists on the web-page and restructures that information to fit Tangiblee API. The tangiblee-mapper.js is unique for each particular type of PDP and for each client website.
tangiblee-mapper.js can be created, maintained, and hosted by either the client or by Tangiblee. PDPs continuously change and evolve over time so maintaining the tangiblee-mapper.js is critical to ensure the Tangiblee Platform can run without errors.
The main data points that the tangiblee-mapper.js logic binds to the Tangiblee API are:
Advanced Features: localization, show/hide add-to-cart button, show/hide price & currency, Google Analytics tracking customization, order, and revenue tracking.