Skip to main content

Custom Integration

This integration is the solution for customers whose e-commerce platform is not native to edrone

Mariana Mazzi avatar
Written by Mariana Mazzi
Updated this week

In cases where the customer's e-commerce platform is not native to edrone, integration is customized using Google Tag Manager (GTM). The customer needs to have a developer capable of proceeding with the integration, and we offer our documentation to be used as a basis.


How does custom integration work?

First, you need to have a GTM account and have it installed in the store that will be integrated. Then, following the instructions from our documentation, the developer will create tags to add their customized script, which aims to capture all the necessary data in the store.


Do the tags created interfere with those already existing in GTM?

No, these tags should be independent and only communicate with the ☰edrone API.


What data is captured?

We capture events that relate customer actions in the store to the communication we do through ☰edrone. The events include mandatory data:

  • Homepage_view

Homepage view.

  • Subscribe - Footer | Register | Checkout

Newsletter subscription form, when available.

- Name, email, phone number, and/or birthday, when available.

  • Category_view

Category page view.

- Category name and ID, when available.

  • Product_view

Product page view.

- Quantity, ID, SKU, title, category name and ID, image URL, and product.

  • Add_to_cart

Adding a product to the shopping cart, either from the product list on the home page or category page (when there is an “add to cart” button), or from the product page.

- ID, SKU, title, image, and product URL.

  • Order

Purchase completed.

- Name, email, city, country, currency, total amount, purchase ID, product ID, SKU, title, image and product URL, quantity, category name and ID.


What is the difference between native integration and custom integration?

The difference lies in communication with the platform server. In native integrations, we can receive data via webhooks directly from each store's backend. In custom integrations, however, since we do not have access to the server, this data must be available on the stores' frontend, either in HTML or dataLayer.


Need additional help?

If you have questions, please don't hesitate to contact us at hello@edrone.me

Did this answer your question?