# Amplitude (analytics browser)
### What this integration does
Each time a visitor is exposed to an AB Tasty campaign, we add a **timestamped `ABTasty` event** to their Amplitude timeline—no custom wiring. The event carries two fields that tell you exactly what they saw:
* `abtasty_campaign` → `campaignName (campaignId)`
* `abtasty_variation` → `variationName (variationId)`
**,All campaign views are appended**: when an Amplitude **user profile is available**, every exposure is attached to that profile; otherwise the event is recorded against the current device and will surface under the user once they are identified, per Amplitude behavior.
Because it’s an event, you can break down funnels, retention, and cohorts by **campaign** and **variation**, compare variants side‑by‑side, and join experiment exposure with your existing product analytics—all within Amplitude.
***
### Requirements
* [**Amplitude Analytics Browser SDK v2**](#user-content-fn-1)[^1] is installed on your site. *(See “Amplitude Browser SDK 2”.)*
* `window.amplitude` and `window.amplitude.track` are available when AB Tasty runs.
* The connector uses **`amplitude.track()`** to send the `ABTasty` event. *(See “Amplitude track” method.)*
***
### How Campaign Data Is Sent
AB Tasty sends one analytics event **`ABTasty`** for each campaign exposure. The event payload contains:
* `abtasty_campaign`: ` ()`
* `abtasty_variation`: ` ()`
***
### How to Set Up the Integration (AB Tasty)
1. Go to Integrations → Integration Hub.
2. [Search Amplitude ](#user-content-fn-2)[^2]\(analytics browser) and select it.
3. Click on Create
4. Give the connector a name.
5. *(Optional)* Tick Automatically add to future campaigns.
6. Click Create.
{% hint style="info" %}
👉 If you checked the box, the connector will appear automatically in the Advanced step of your future campaigns. It does not apply retroactively to existing campaigns.
{% endhint %}
***
### How to Check if Events Are Sent Properly
#### Console (Debug Mode)
1. Open your website.
2. Paste this in the browser console:
`document.cookie = "abTastyDebug=true;path=/;";`
3. Trigger an AB Tasty campaign. You should see a **debug log** indicating the `ABTasty` event was sent.
#### Network Tab
1. Open DevTools → **Network**.
2. Filter for requests to:
`https://api.eu.amplitude.com/2/httpapi`
3. Inspect the payload and confirm `event_properties` include:
* `abtasty_campaign`
* `abtasty_variation`
{% hint style="warning" %}
Region endpoints may differ (e.g., US vs EU). Use the endpoint that matches your Amplitude data residency.
{% endhint %}
***
### Retrieve the Event in Amplitude
1. Go to your **Amplitude dashboard**.
2. Open **Live Events**.
3. A new **`ABTasty`** event should appear, attached to the current user.
4. Click the user/event to view details, including:
* `abtasty_campaign`
* `abtasty_variation`
***
### Good to Know
* The event is automatically linked to an **Amplitude user ID** (e.g., `user_42`).
* You may set this yourself (see *Custom User Identifier* in Amplitude docs), or
* Let Amplitude assign one randomly.
* You can build user cohorts based on `ABTasty` events to group users by the campaigns/variations they saw.
* Works alongside your existing Amplitude events—use `ABTasty` as a breakdown dimension in funnels and retention charts.
***
### FAQ
**Does AB Tasty create users in Amplitude?**\
No. Amplitude creates user profiles according to its standard behaviour when events arrive.
**Can we change the event name or keys?**\
Use the defaults (`ABTasty`, `abtasty_campaign`, `abtasty_variation`) for consistent reporting.
**Is an Amplitude API key needed in AB Tasty?**\
No. This integration utilises your client-side Amplitude SDK, which is already on the site.
[^1]: 
[^2]: 
What this integration does
Each time a visitor is exposed to an AB Tasty campaign, we add a **timestamped `ABTasty` event** to their Amplitude timeline—no custom wiring. The event carries two fields that tell you exactly what they saw:
* `abtasty_campaign` → `campaignName (campaignId)`
* `abtasty_variation` → `variationName (variationId)`
**,All campaign views are appended**: when an Amplitude **user profile is available**, every exposure is attached to that profile; otherwise the event is recorded against the current device and will surface under the user once they are identified, per Amplitude behavior.
Because it’s an event, you can break down funnels, retention, and cohorts by **campaign** and **variation**, compare variants side‑by‑side, and join experiment exposure with your existing product analytics—all within Amplitude.
***
### Requirements
* [**Amplitude Analytics Browser SDK v2**](#user-content-fn-1)[^1] is installed on your site. *(See “Amplitude Browser SDK 2”.)*
* `window.amplitude` and `window.amplitude.track` are available when AB Tasty runs.
* The connector uses **`amplitude.track()`** to send the `ABTasty` event. *(See “Amplitude track” method.)*
***
### How Campaign Data Is Sent
AB Tasty sends one analytics event **`ABTasty`** for each campaign exposure. The event payload contains:
* `abtasty_campaign`: `