add_customer_details Event

The add_customer_details event is triggered when a user submits their contact or billing details during checkout. This can include name, email, phone number, and address. Capturing this event is critical for tracking checkout progress.

The add_customer_details model

This model reflects the details submitted by the customer and any cart or session identifiers.

Properties

  • Name
    event
    Type
    string
    Description

    Must be set to add_customer_details.

  • Name
    user_id
    Type
    string
    Description

    Unique identifier for the user submitting customer info.

  • Name
    session_id
    Type
    string
    Description

    Unique identifier for the session.

  • Name
    ecommerce.currency
    Type
    string
    Description

    ISO 4217 currency code (e.g., USD).

  • Name
    ecommerce.value
    Type
    float
    Description

    Total value of the transaction/cart at this point.

  • Name
    customer.email
    Type
    string
    Description

    Email address of the customer (can be hashed if needed).

  • Name
    customer.phone
    Type
    string
    Description

    Phone number of the customer.

  • Name
    customer.name
    Type
    string
    Description

    Full name of the customer.

  • Name
    customer.address
    Type
    string
    Description

    Street-level address.

  • Name
    customer.city
    Type
    string
    Description

    City name.

  • Name
    customer.region
    Type
    string
    Description

    State or region.

  • Name
    customer.country
    Type
    string
    Description

    Country (ISO 3166-1 alpha-2).


Push event to the dataLayer

dataLayer.push example

dataLayer.push({
  event: 'add_customer_details',
  user_id: 'user-246',
  session_id: 'session-qwe',
  ecommerce: {
    currency: 'USD',
    value: 120.00
  },
  customer: {
    email: 'jane.doe@example.com',
    phone: '+1234567890',
    name: 'Jane Doe',
    address: '123 Main St',
    city: 'New York',
    region: 'NY',
    country: 'US'
  }
});

Best Practices

  • Only fire this event after form submission, not on each field change.
  • Consider hashing email and phone for privacy-compliant tracking.
  • Don't send sensitive data like full credit card details.

Use Cases

The add_customer_details event supports:

  • Step-by-step funnel visualization
  • Form field abandonment analysis
  • Conversion rate optimization
  • Personalization and customer journey analytics

Was this page helpful?