API vs SDK

✨ Preface

Incorporate the AMP client-side script (SDK) or server-side API across all pages of your website and application. This integration is crucial for monitoring pageview interactions. The client-side script facilitates the addition of elements such as tags or recommendations to your pages, while the server-side API enables you to embed the specific components you wish to display.

🔷 AMP API

AMP APIs offer two main benefits, compatibility and SEO friendly. Read below for detailed explanations.

1️⃣ Compatibility

You can decide where to utilize the response data on your own. It can be used on websites and apps, and you can integrate it as you see fit in terms of placement and location.

🚧

Beware of the misplacement of an API

Please contact your Customer Success Specialist before implementing an API to other pages. For example, Related Products V1 offers product recommendations on cart pages. If it is placed on a product page, there might be an additional usage fee due to the higher traffic on these pages.

2️⃣ SEO Friendly

Content is pre-generated as a response to an HTTP request. The content on this website originates from pre-constructed source files. These files are transformed into HTML pages and then uploaded to an HTTP hosting server. We call that Server-Side Rendering (SSR). Server-side rendering (SSR) transforms your HTML files into a format that is easily interpretable by the end user's browser. This allows Googlebot to access the fundamental HTML content of your webpage without any obstruction from JavaScript, ensuring that users view the page in its fully rendered form, complete with all its visual and auditory features. As a result, your website achieves accurate ranking on Google, while providing users with an exceptionally engaging and visually appealing web experience.

🔶 AMP SDK

The AMP SDK offers an easy way to integrate with the AMP APIs. It delivers API responses accompanied by a customizable template user interface, which your team can tailor to suit your particular commerce store's needs. Here are the advantages of SDK.

1️⃣ Low Implementation Effort

You just need a marketing person who can operate GTM and put the script to it, through simple parameter settings, HTML, and CSS adjustment abilities to install it on the website. Significantly speed up the development process by providing pre-built components and tools for common tasks.

2️⃣ Style Controls

In general, when we provide product features, we also offer an interface for setting the style of that feature. Users can decide on the style as well as set up the functional logic in the AMP interface. If it's an API user, they might need to write their programs to set and modify the style.

3️⃣ Consistency

With an SDK, you're more likely to follow the service's best practices for usage, resulting in a more stable and consistent integration.

4️⃣ Support and Updates

SDKs usually include support tools and are regularly updated for new features and security improvements.

🤔 So Which One Suits Me?

1. If you wish to use our tags to create more product categories and generate more organic traffic, we would recommend integrating our services via API. You can set up functional logic in the AMP interface, but you cannot adjust any settings related to style.
2. If you only want to use the data returned by API, and you have frontend and designer resources to handle user experience, then we would recommend integrating our services via API.
3. If you want to not only access the data provided by the AMP API but also wish to design styles and layouts through AMP, then we recommend you use the SDK.
4. Can I use both? Yes! If your goal is to suggest products through a Pop Up, with the ability to control the Pop Up's activation timing and display tags that server-side rendered on category pages, then integrating the Pop-up recommendation feature via the SDK and implementing tags on your category pages via the API would be the approach to take.