> For the complete documentation index, see [llms.txt](https://docs.drivepoint.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.drivepoint.io/using-the-web-app/reports/cohort-analysis/segment-crossover.md).

# Segment Crossover

*This report should be used to answer the common questions of what percent of customers start with this segment (e.g. "One time purchase") and eventually buy this other segment (e.g. "Subscription") and how well you are doing this over time.*

## Definitions

<table><thead><tr><th>Name</th><th width="124">Type</th><th>Definition</th></tr></thead><tbody><tr><td><strong>Intervals Since First Purchase</strong></td><td>Dimension</td><td>Calculated as the number calendar intervals (e.g. months) from the date of the first purchase, this dimension defines each series on the chart and each column within the table of this report. </td></tr><tr><td><strong>Cohort Months</strong></td><td>Dimension</td><td>A month range filter that can select the window of time in which a customer made their first purchase.</td></tr><tr><td><strong>Cohort Interval</strong></td><td>Dimension</td><td><em>Defaulted to Month.</em> Each option groups first-time customers together into cohorts based on the interval selected.</td></tr><tr><td><strong>Purchase Path</strong></td><td>Dimension</td><td><p>First Segment -> Returning Segment<br><br>This does not mean that the customer bought the Returning Segment right after the First Segment, but eventually did. It is instead a display of the fact that the customer started with the First Segment and eventually bought the different Returning Segment.</p><p><br><em>For instance, a customer buys a NonSubscription as their first and second purchase. This becomes their <strong>First Segment</strong>.  On their third purchase, they buy a Subscription, which is represented here as their <strong>Returning Segment</strong>. As a result, the <strong>Purchase Path</strong> is "NonSubscription -> Subscription".</em></p></td></tr><tr><td><strong>Cohort Size</strong></td><td>Metric</td><td>The number of customers acquired within the <strong>Cohort Interval</strong>.</td></tr><tr><td><strong>Calculation Method</strong></td><td>Metric</td><td><em>Defaulted to Cumulative.</em> <br><br><strong>Incremental:</strong> The number of customers that have purchased a different segment than the one they started with on the <strong>Intervals Since First Purchase / Cohort Size</strong><br><br><strong>Cumulative:</strong> Simply a cumulative version of <strong>Incremental</strong></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.drivepoint.io/using-the-web-app/reports/cohort-analysis/segment-crossover.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.