> ## Documentation Index
> Fetch the complete documentation index at: https://launchdarkly.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# mParticle schema reference

<View title="Developer" />

<View title="Federal docs">
  <Danger>
    **This integration is not available in federal environments**

    To learn more, read <a href="/docs/home/infrastructure/federal">LaunchDarkly in federal environments</a>.
  </Danger>
</View>

<View title="EU docs" />

This topic explains the different event kinds for mParticle Data Export destinations. The JSON schemas for mParticle are formatted differently than LaunchDarkly's. The `index`, `identify`, and `summary` event kinds are **not available** in mParticle Data Export destinations, and other events are exported with different labels.

To learn more about the mParticle destination, read [mParticle's documentation](https://docs.mparticle.com/integrations/launchdarkly).

There are four different event kinds mParticle uses. They are:

* [`Feature` events](#feature-events): This event appears when a feature flag is evaluated.
* [`Click` events](#click-events): This event appears when an end user clicks on a CSS selector for which they have configured a metric in an experiment.
* [`Page view` events](#page-view-events): This event appears when an end user loads a page associated with an experiment metrics.
* [`Custom` events](#custom-events): The LaunchDarkly SDK sends a `custom` event.

## Feature events

This table lists `feature` events:

<table>
  <thead>
    <tr>
      <th>Description</th>
      <th>Event details</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        event\_type: custom\_event <br /><br />
        custom\_event\_type “other”<br /><br />
        event\_name: Feature
      </td>

      <td>Describes a feature flag evaluation which occurred in a LaunchDarkly SDK event\_type: “custom” for this event.</td>
    </tr>
  </tbody>
</table>

### Custom attributes

This table lists custom attributes:

<table>
  <thead>
    <tr>
      <th>Description</th>
      <th>Attribute event details</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>project</td>
      <td>ID of the LaunchDarkly project associated with the event.</td>
    </tr>

    <tr>
      <td>environment</td>
      <td>The LaunchDarkly environment ID, also called the client-side ID, associated with the event.</td>
    </tr>

    <tr>
      <td>version</td>
      <td>The version of event schema.</td>
    </tr>

    <tr>
      <td>flag\_version</td>
      <td>The version number of the flag when it was evaluated.</td>
    </tr>

    <tr>
      <td>value</td>
      <td>The value of the feature flag returned by feature flag evaluation.</td>
    </tr>

    <tr>
      <td>key</td>
      <td>The key of the flag requested.</td>
    </tr>

    <tr>
      <td>default</td>
      <td>Whether the flag evaluation was a result of the default value being used. Is set to true if feature flag evaluation failed, if omitted assumed to be false.</td>
    </tr>

    <tr>
      <td>reason\_kind</td>
      <td>If a <code>feature</code> event was generated through a "variation detail" method, the event will have a reason property with the JSON representation of the evaluation reason.</td>
    </tr>

    <tr>
      <td>prerequisite\_of</td>
      <td>Set to another flag’s key if this flag evaluation was only performed in order to determine whether the prerequisite values were met for the indicated flag.</td>
    </tr>

    <tr>
      <td>variation\_name</td>
      <td>The evaluated variation's name, if it exists. If the evaluated variation doesn't have a name, this field doesn't appear.</td>
    </tr>
  </tbody>
</table>

## Click events

This table lists `click` events:

<table>
  <thead>
    <tr>
      <th>Description</th>
      <th>Event details</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        event\_type: custom\_event<br /><br />
        custom\_event\_type “navigation”<br /><br />
        event\_name: Click
      </td>

      <td>Describes an event generated by the LaunchDarkly SDK when an end user clicks on a designated HTML element event\_type: “custom” for this event.</td>
    </tr>
  </tbody>
</table>

### Custom attributes

This table lists custom attributes:

<table>
  <thead>
    <tr>
      <th>Description</th>
      <th>Attribute event details</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>project</td>
      <td>ID of the LaunchDarkly project associated with the event.</td>
    </tr>

    <tr>
      <td>environment</td>
      <td>The LaunchDarkly environment ID, also called the client-side ID, associated with the event.</td>
    </tr>

    <tr>
      <td>version</td>
      <td>The version of event schema.</td>
    </tr>

    <tr>
      <td>key</td>
      <td>The key of the feature flag requested.</td>
    </tr>

    <tr>
      <td>url</td>
      <td>The URL of the page the end user was on when the click occurred.</td>
    </tr>

    <tr>
      <td>selector</td>
      <td>The CSS selector that was clicked.</td>
    </tr>
  </tbody>
</table>

## Page view events

This table lists `page view` events:

<table>
  <thead>
    <tr>
      <th>Description</th>
      <th>Event details</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        event\_type: screen\_view<br /><br />
        custom\_event\_type: other<br /><br />
        event\_name: Page view
      </td>

      <td>Describes an event generated by a LaunchDarkly SDK when an end user views an action changes the browser’s URL event\_type: “screen\_view” for this event.</td>
    </tr>

    <tr>
      <td>screen\_name</td>
      <td>URL stripped of query string.</td>
    </tr>
  </tbody>
</table>

### Custom attributes

This table lists custom attributes:

<table>
  <thead>
    <tr>
      <th>Description</th>
      <th>Attribute event details</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>project</td>
      <td>ID of the LaunchDarkly project associated with the event.</td>
    </tr>

    <tr>
      <td>environment</td>
      <td>The LaunchDarkly environment ID, also called the client-side ID, associated with the event.</td>
    </tr>

    <tr>
      <td>version</td>
      <td>The version of event schema.</td>
    </tr>

    <tr>
      <td>key</td>
      <td>The key of the feature flag requested.</td>
    </tr>

    <tr>
      <td>url</td>
      <td>The URL of the page the end user was on when the page view occurred.</td>
    </tr>
  </tbody>
</table>

## Custom events

This table lists `custom` events:

<table>
  <thead>
    <tr>
      <th>Description</th>
      <th>Event details</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        event\_type: custom\_event<br /><br />
        custom\_event\_type “other”<br /><br />
        event\_name: Custom
      </td>

      <td>Describes an event generated by a LaunchDarkly SDK in response to an end user calling the SDK’s "track" function event\_type: "custom" for this event.</td>
    </tr>
  </tbody>
</table>

### Custom attributes

This table lists custom attributes:

<table>
  <thead>
    <tr>
      <th>Description</th>
      <th>Attribute event details</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>project</td>
      <td>ID of the LaunchDarkly project associated with the event.</td>
    </tr>

    <tr>
      <td>environment</td>
      <td>The LaunchDarkly environment ID, also called the client-side ID, associated with the event.</td>
    </tr>

    <tr>
      <td>version</td>
      <td>The version of event schema.</td>
    </tr>

    <tr>
      <td>key</td>
      <td>The key of the [metric](/docs/home/metrics)
       associated with the custom event.</td>
    </tr>

    <tr>
      <td>metric\_value</td>
      <td>The numeric value of a [metric](/docs/home/metrics) if it is specified in the event.
      If no metric value was provided, this field doesn't appear.</td>
    </tr>
  </tbody>
</table>