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

# Getting Started Guide

> Prepare the data A2 needs and follow the steps through comparing advertising performance.

A2 integration can start in two ways, depending on your goal: inspect an ad response first, or connect product and user activity data from your service.

| Start with | What you'll do | Start here |
| - | - | - |
| An ad response | Configure a sample ad in Ad Manager, then request it through the Decision API. No catalog or user activity data is required. | [Ad Serving Quickstart](https://docs.aiderx.io/development/en/quick-start.md) |
| Product and user data | Integrate the product catalog, user activity logs, and ad events. Once integrated, you can compare results with A/B testing. | [Product Catalog](https://docs.aiderx.io/development/en/catalog.md) · [User Activity Logs](https://docs.aiderx.io/development/en/user-events.md) |

> [!NOTE]
>
> To serve personalized ads and improve ad performance in your service, we strongly recommend integrating the product catalog, user activity logs, and ad events.

The ad request in the quickstart does not require an access token. Catalog registration through the management API does. User activity logs can be sent without a token.

## Data to send to A2

| Data | What to send | How A2 uses it |
| - | - | - |
| [Product Catalog](https://docs.aiderx.io/development/en/catalog.md) | IDs, names, images, categories, and other information for products to advertise. | Selects the best ad for each user based on product information. |
| [User Activity Logs](https://docs.aiderx.io/development/en/user-events.md) | Product views, clicks, cart additions, purchases, and other activity on catalog products within your service. | Understands user interests and behavior to inform ad selection. |
| [Ad Event Tracking](https://docs.aiderx.io/development/en/ad-events-and-logs.md) | Impressions, clicks, and conversions for ads selected by A2. | Aggregates ad performance and adjusts ad delivery speed (pacing) to budgets and target impressions. |

Register products in the catalog when using product-based ads or recommendations. The sample House ad in the Quickstart does not need a catalog. Send as many supported activity events as your service can collect. Connect impressions and clicks according to your tracking configuration, and connect conversions when measuring a goal such as a purchase.

> [!NOTE]
>
> User activity logs describe activity on catalog products regardless of whether the user interacted with an A2 ad. Ad tracking records the outcomes of ads selected by A2. If a purchase serves both purposes, send each log separately.

## Before connecting data

The A2 environment must be deployed, and you need its API address. Also prepare the following items to connect product and user data.

| Prerequisite | What to confirm |
| - | - |
| API address | The deployed environment's address and permitted network access. |
| Ad Manager account | Access needed to issue a token, configure ads, and view analytics. |
| Product information | Products to advertise and their IDs. |
| User and device identifiers | User IDs and device IDs used by your service. |
| Measurement goal | The action to compare, such as a click or purchase, and when it occurs. |

## Next steps

To inspect an ad response first, follow [Ad Serving Quickstart](https://docs.aiderx.io/development/en/quick-start.md). You need the API address and an administrator account.

If you need a token for catalog integration, see [API Access and Authentication](https://docs.aiderx.io/development/en/api-access-and-auth.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.