VTEX Ads uses view tracking to measure when banner advertisements are effectively displayed to users. This guide explains how to properly send view events when banner ads become visible to users.

• View events should only be sent for banner ads.
• View events require both user_id and session_id for proper attribution.
• View URLs are unique to each ad and should be obtained from the Get ads response.

🚧 Don't construct event URLs manually. Always use the URL provided from the POST Get ads request.

This is extremely important to ensure long-term stability of the integration, because the parameters of the event URL may change over time, but the integration itself does not.

View events are not budget-gated the way impressions are. When a campaign reaches its daily budget cap, impression counting is interrupted while view events may still be recorded, so reported views can exceed reported impressions. See Understanding ads events for the full budget-validation model.

Use the POST Track ad views endpoint to send view events. Check the endpoint documentation for detailed information about all available fields.

Request example:

Successful response example:

A successful response will have HTTP code 202.

Failed response example:

A failed response will have HTTP code 422. The error message follows the RFC 8927 format.