Integrating the transaction tag is essential to track sales generated via the iAdvize platform. This script allows you to track key information, such as the unique transaction identifier, its amount, and the details of the purchased products, ensuring accurate conversion tracking after conversations.

This guide explains how to manually install the transaction tag on your site to ensure correct and effective integration.

1. Integrate the transaction tag

In your administration

Go to the Settings tab > Integration > iAdvize tags then click on Go to the setup guide

Select the option "Add the tracking code manually"

If you wish to send your developer or agency all the necessary documentation, click on Send an invitation. They will receive an email with the instructions, without needing to access the iAdvize administration.

The main iAdvize tag must be present, otherwise transactions will not be recorded.
Insert the following JavaScript code just before the closing tag </body> on all order confirmation pages to ensure proper transaction tracking.
Do not insert this script on pages other than those dedicated to payments.
Do not modify the structure of the code provided by iAdvize to avoid any errors.
Test on different browsers and devices to verify compatibility and proper functioning of the script.

<script>
  window.iAdvizeInterface = window.iAdvizeInterface || [];
  window.iAdvizeInterface.push(function(iAdvize) {
    iAdvize.recordTransaction({
      amount: 123.45, // Replace this value with the actual transaction amount
      id: "unique-identifier-6789" // Unique transaction identifier,
      products: [
        // Product ID, quantity ordered, unit price
        { id: 'SKU123', quantity: 2, price: 29.99 },
        { id: 'SKU456', quantity: 1, price: 40.01 },
      ],
    });
  });
</script>

💡 Replace 123.45 with the actual transaction amount (using a period as the decimal separator).

💡 Replace unique-identifier-XXXX with the unique transaction identifier generated by your system.

💡 Product IDs (id) must match those defined in your iAdvize product knowledge base.

Which identifier should you use: variant or parent product?

In your iAdvize catalog, each row corresponds to a variant (a combination of size, color, etc.) identified by the id field, which must be unique per source. Variants of the same product are grouped together via the item_group_id field.

The id provided in the transaction tag must match an id present in your catalog.

→ Recommendation: push the purchased variant's id into your datalayer on the order confirmation page, and use it in the transaction tag. This is the only reliable approach, allowing iAdvize to track sales by variant and refine product suggestions.

If your datalayer only exposes the parent product identifier, there is no clean workaround on the iAdvize catalog side: using item_group_id as the id would cause duplicates (multiple variants sharing the same identifier), which is not allowed within a single source. The solution is therefore to update your datalayer so that it exposes the variant identifier.

2. Verify the transaction tag installation

Once your tags are implemented, you can test whether their integration is correct.

Conduct an iAdvize conversation on your site
Complete a transaction on your site
Verify that the transaction appears in iAdvize reports.

If you notice transaction discrepancies between iAdvize and your analytics tools, consult the documentation on technical constraints related to transactions to adapt the integration.

If you use a tag manager such as Google Tag Manager (GTM), consult the dedicated article for simplified installation.

1. Integrate the transaction tag

2. Verify the transaction tag installation

Related articles