Skip to main content
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.
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

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.
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.

​
Next steps

To inspect an ad response first, follow Ad Serving Quickstart. You need the API address and an administrator account. If you need a token for catalog integration, see API Access and Authentication.