Developer Platform
  • Home
  • Getting Started
    • General Information
    • Features Overview
    • Security
  • APPs
    • Public Apps
      • Shopify
      • Salesforce
      • Zendesk
      • Google Analytics
    • Build your App
      • Getting started
      • My Apps
      • App information
      • App Parameters
      • App Plugins
      • Add Webhooks
      • Submit your Apps
      • App security
      • Developer Policy
  • Use Cases
    • Copilots
      • Product Catalog sync through API
      • FAQ sync through API
    • Visitor experience
      • Integrating custom buttons into your site
      • Check availability before escalating to iAdvize
      • Authenticated Messaging
        • Introduction
        • Web client-side implementation
          • Authenticated Messaging overview
          • Brief timeline of the integration process
          • How to enable authenticated mode in the administration portal?
          • How to implement the customer authentication backend (token provider)?
          • How to authenticate with iAdvize in client's website?
          • How to deal with activation success or failure?
          • How to logout?
          • Compatibility with Mobile SDK
          • FAQ
        • Web backend implementation
          • Important information and recommendations
          • Signature and Encryption Detailed Process
          • Technical backend implementation
          • FAQ
      • Cross-domain Conversation Continuity
      • Customize replies with Markdown
    • Agent workspace
      • Custom App example and step-by-step tutorial
        • Get Started
        • Work with the Desk
        • Intent / Trigger
        • JWT
        • References
    • Administration
      • Users
        • SAML SSO Authentication - Implementation Guide
        • Create, update and delete users via API
        • Manage the availability of your users with the iAdvize API
        • Integrate the iAdvize conversation panel into an existing tool
      • Anonymize a conversation or visitor data
    • Data & Analytics
      • Extract conversation transcript
      • Retrieve metrics and KPIs
        • Pre-aggregated indicators
        • Understand transaction data
        • Understand conversation data 1/2
        • Understand conversation data 2/2
        • Understand satisfaction data
        • Understand production indicators
  • Technologies
    • GraphQL API
      • Terminology
      • Reference
      • Authentication
      • Schema lifecycle
      • Error Management
      • Pagination
    • REST API (deprecated)
      • Statistic (deprecated)
      • Group (deprecated)
      • Call meeting (deprecated)
      • Operator (deprecated)
      • Skill (deprecated)
      • Transaction (deprecated)
      • Visitor (deprecated)
    • Webhooks
      • Reference
      • Guides
    • Desk events
      • Reference
    • Web & Mobile SDK
      • Javascript Web SDK
        • Reference
      • Javascript Callbacks
        • Reference
        • Guides
      • Mobile SDK
        • Gaperon (latest)
        • Fourme
        • Epoisses
        • Dauphin
        • 🤝Support Policy
        • 🤔Frequently Asked Questions
    • Custom App
    • External Bot
      • Implementation
        • Configuration flow
        • Conversation flow
        • Conversation objects
      • Configuration
      • FAQ
      • Best practices
Powered by GitBook
On this page
  • What gets sent to iAdvize?
  • How transactions are attributed to conversations
  • Example: How attribution works in practice
  • Important tip for querying
  • How to retrieve a list of all your transactions
  • What is the best query to use for my need?

Was this helpful?

  1. Use Cases
  2. Data & Analytics
  3. Retrieve metrics and KPIs

Understand transaction data

In iAdvize, transactions (such as purchases or leads) are tracked using the JavaScript transaction tag you install on key pages like the order confirmation or lead submission page.

What gets sent to iAdvize?

Each time a visitor completes a transaction on your site, the following information is sent to iAdvize:

  • Transaction ID (unique identifier)

  • Transaction amount

How transactions are attributed to conversations

By default, iAdvize links a transaction to a conversation if it occurs within 48 hours of the conversation ending.

This 48-hour attribution window can be customized. If needed, reach out to your Customer Success Manager (CSM) to adjust this setting.

Why is this important?

When you run a query to retrieve transaction data per conversation or per day, keep in mind that a transaction may not fall within the same time interval as the conversation that generated it.

Example: How attribution works in practice

Let’s say a visitor chats with your team on Monday and purchases something the next day:

  • Monday, Jan 1 — 10:00 AM: Conversation starts

  • Monday, Jan 1 — 10:12 AM: Visitor leaves; the conversation is closed

  • Tuesday, Jan 2 — 2:08 PM: Visitor completes a purchase on your website

This transaction will be attributed to the conversation from Monday, because it occurred within the 48-hour window.

Important tip for querying

Best practice:

When analyzing transactions linked to conversations, always extend your date range to account for the attribution window (48 hours by default, or whatever value is set in your account).

How to retrieve a list of all your transactions

What is the best query to use for my need?

  • Use the closedConversations query to retrieve transactions attached to specific conversations. These are available directly within the conversation object (if applicable).

PreviousPre-aggregated indicatorsNextUnderstand conversation data 1/2

Last updated 3 days ago

Was this helpful?

If you run a query using an interval that ends on Monday, Jan 1, after 10:12 AM the transaction that occurred on Tuesday, Jan 2 will not appear in the results, even though it’s linked to the Jan 1 conversation.

The query allows you to list and filter transactions.

If you wish to catch all transaction as soon as they go through, please make sure you read our information regarding our .

Use the to retrieve a list of all transactions, independently of conversations. This is useful for post-processing or analyzing attribution across time.

closedConversation
conversions
transaction webhook
conversions query