# Roadway Docs

## The Basics

- [Quickstart guide](https://docs.roadwayai.com/getting-started/readme.md)
- [How Roadway Works](https://docs.roadwayai.com/getting-started/how-roadway-works.md)
- [Warehouse-native](https://docs.roadwayai.com/implement-roadway/warehouse-native.md)
- [Connect Snowflake](https://docs.roadwayai.com/implement-roadway/warehouse-native/connect-snowflake.md)
- [Connect BigQuery](https://docs.roadwayai.com/implement-roadway/warehouse-native/connect-bigquery.md)
- [Connect Redshift](https://docs.roadwayai.com/implement-roadway/warehouse-native/connect-redshift.md)
- [Direct connectors](https://docs.roadwayai.com/implement-roadway/direct-connectors.md)
- [Warehouse Requirements](https://docs.roadwayai.com/data-requirements/warehouse-requirements.md)
- [Page Views](https://docs.roadwayai.com/data-requirements/warehouse-requirements/page-views.md): Tracking how people interact with your site
- [Users](https://docs.roadwayai.com/data-requirements/warehouse-requirements/users.md): Recording user signups and descriptive information
- [Revenue](https://docs.roadwayai.com/data-requirements/warehouse-requirements/revenue.md): Modeling your company's revenue
- [CRMs](https://docs.roadwayai.com/data-requirements/warehouse-requirements/crms.md): Tracking your sales-led growth funnel
- [Ad Spend](https://docs.roadwayai.com/data-requirements/warehouse-requirements/ad-spend.md): A record of Performance Marketing outcomes
- [Mobile Measurement Partners (MMPs)](https://docs.roadwayai.com/data-requirements/warehouse-requirements/mobile-measurement-partners-mmps.md): Attributing app installs and in-app conversions
- [Required IDs for attribution](https://docs.roadwayai.com/required-ids-for-attribution.md): Roadway requires different IDs across data sources (direct implementations) and within tables (warehouse-native) in order provide custom attribution across all metrics and data sources.
- [Implementing the Roadway Tag](https://docs.roadwayai.com/required-ids-for-attribution/implementing-the-roadway-tag.md): Follow the steps below (15-45 mins) to enable marketing attribution on metrics derived from CRM data through Anonymous IDs from Sessions on CRM contacts.
- [Add Anonymous IDs to CRM with Custom Forms](https://docs.roadwayai.com/required-ids-for-attribution/implementing-the-roadway-tag/add-anonymous-ids-to-crm-with-custom-forms.md): Choose your Sessions data source.
- [Segment with Custom Forms](https://docs.roadwayai.com/required-ids-for-attribution/implementing-the-roadway-tag/add-anonymous-ids-to-crm-with-custom-forms/segment-with-custom-forms.md)
- [Google Analytics with Custom Forms](https://docs.roadwayai.com/required-ids-for-attribution/implementing-the-roadway-tag/add-anonymous-ids-to-crm-with-custom-forms/google-analytics-with-custom-forms.md)
- [Add Anonymous IDs to CRM with Hubspot Forms](https://docs.roadwayai.com/required-ids-for-attribution/implementing-the-roadway-tag/add-anonymous-ids-to-crm-with-hubspot-forms.md)
- [Segment with Hubspot Forms](https://docs.roadwayai.com/required-ids-for-attribution/implementing-the-roadway-tag/add-anonymous-ids-to-crm-with-hubspot-forms/segment-with-hubspot-forms.md)
- [Google Analytics with Hubspot Forms](https://docs.roadwayai.com/required-ids-for-attribution/implementing-the-roadway-tag/add-anonymous-ids-to-crm-with-hubspot-forms/google-analytics-with-hubspot-forms.md): You must first add the Roadway tag


---

# 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
This site has an agentic ask interface you may use to query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.roadwayai.com/index.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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