> For the complete documentation index, see [llms.txt](https://rosetta-ai.gitbook.io/help-center/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rosetta-ai.gitbook.io/help-center/faq/adstyle-performance-on-ga-ga4.md).

# AdStyle Performance on GA/GA4

Introducing the new ads type, AdStyle, designed to drive traffic between fashion and lifestyle ecosystems by recommending cross-industry product ads to shoppers when they complete checkout online. AdStyle helps fashion ecosystems reach broader demographics across industries and age groups.

Rosetta AI has set up tracking codes so you can easily monitor ad performance in GA/GA4 by:

* Breadcrumb to check performance on GA/GA4: Acquisition → Traffic acquisition → Search: Session source / medium → Check the UTM tracking code set by Rosetta.ai's UTM tag: `rosetta/paid-rosetta-ad`

{% hint style="warning" %}
Note: The performance data tracked by GA/GA4 uses different attribution algorithms compared to Rosetta.ai's performance tracking and attribution calculations.
{% endhint %}


---

# 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://rosetta-ai.gitbook.io/help-center/faq/adstyle-performance-on-ga-ga4.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.