Self-Service integration is not recommended except for very specific use-cases.
Tangiblee recommends managed integration for 95% of our clients. Through managed integration, Tangiblee runs QA and is responsible for ensuring that Tangiblee CTA and modal adhere to clients' ongoing changes and deployments. However, it is important to note that you should notify Tangiblee (email@example.com) if you have an ongoing product layout page or replatforming changes to take place that we should be aware of. If not, we will only see that change on the page after it is deployed to production and the Tangiblee CTA will not appear until we update our mapping to reflect these changes.
What is a possible use case for Self-Service Integration?
If you take advantage of a Progressive Web Application that is running on top of your existing e-commerce platform, then it might be advised to utilize self-service integration. However, we would recommend a conversation outlining all potential integration options with the Tangiblee engineering team.
In the case of a Self-Service Integration, the client implements its own mapping code (tangiblee-mapper.js) and has full control of its logic.
Self-Serviced integration consists of two code blocks:
- Mapping Code (tangiblee-mapper.js)
- Tangiblee API code (tangiblee.min.js)
For example, if a client needs two versions of the Snippet to support two different environments like PRD and STD, it may be done by using two separate tangiblee-mapper.js files for the PRD and STG environments.
Typical Self-Service Integration
Here is an example of Self-Service Integration: Basic Self-Service Sample Link.
The tangiblee-mapper.js is similar to Managed Integration Production PDP version example but now written by the client and hosted on the PDP directly instead of loading it from Tangiblee CDN.
[.good]Only generic Tangiblee API calls are made to the Tangiblee CDN equaling one less round trip to load the mapper.js from the Tangiblee CDN.[.good]
- One SKU on a PDP
- One active Locale
- No Price/Currency/ATC in-widget
- No Order Tracking
Multi SKU Multi Locale Self-Service Integration
Advanced Self-Service Integration example: Advanced Self-Service Integration Sample Link.
Same as in the previous example, also in the Advanced example, the Mapping Code is written by the client and hosted on the client's PDP.
This example shows how to use Tangiblee on:
- Multiple SKUs on a PDP (in this case two).
- Multiple locales
- Price/Currency/ATC in-widget
- Order Tracking on Thank You Page