---
title: Target Lab Resources
slug: target-labs
docTags: 
createdAt: 2025-06-19T16:16:38.525Z
---

# Lab required browser extensions

To participate fully in the lab you will want the following Chrome browser extensions installed on your machine.

1. The [Adobe Experience Platform Debugger](https://chromewebstore.google.com/detail/adobe-experience-platform/bfnnokhpnncpkdmbokanobigaccjkpob) browser extension for Chrome
   1. We use this to monitor requests to the Adobe solutions
   2. We also use it to deploy a custom Tags property to your site for the lab
2. The [Adobe Experience Cloud Visual Editing Helper](https://chromewebstore.google.com/detail/adobe-experience-cloud-vi/kgmjjkfjacffaebgpkpcllakjifppnca) browser extension for Chrome
   1. This allows us to load your site pages within the *Visual Experience Composer* of Target

If your device is not allowed to install extensions we recommend you seek approval from your IT or switch to a personal device; otherwise, you will mostly be limited to watching the lab rather than doing hands-on exercises.

# Sites used in the lab

- [Adobe Data Collection UI](https://experience.adobe.com/#/data-collection) (Tags, Datastreams and Event Forwarding all located here)
- [Adobe Target UI](https://experience.adobe.com/#/target/activities)

# Login details

| **Lab #** | **Person** | **Login Email**                                                            |
| --------- | ---------- | -------------------------------------------------------------------------- |
| 01        | Sarah      | [trg.u01@pot5.aephandsonlabs.com](mailto\:trg.u01@pot5.aephandsonlabs.com) |
| 02        | Srivaths   | [trg.u02@pot5.aephandsonlabs.com](mailto\:trg.u02@pot5.aephandsonlabs.com) |
| 03        | Samantha   | [trg.u03@pot5.aephandsonlabs.com](mailto\:trg.u03@pot5.aephandsonlabs.com) |
| 04        | Alyssa     | [trg.u04@pot5.aephandsonlabs.com](mailto\:trg.u04@pot5.aephandsonlabs.com) |
| 05        |            | [trg.u05@pot5.aephandsonlabs.com](mailto\:trg.u05@pot5.aephandsonlabs.com) |
| 06        |            | [trg.u06@pot5.aephandsonlabs.com](mailto\:trg.u06@pot5.aephandsonlabs.com) |
| 07        |            | [trg.u07@pot5.aephandsonlabs.com](mailto\:trg.u07@pot5.aephandsonlabs.com) |
| 08        |            | [trg.u08@pot5.aephandsonlabs.com](mailto\:trg.u08@pot5.aephandsonlabs.com) |
| 09        |            | [trg.u09@pot5.aephandsonlabs.com](mailto\:trg.u09@pot5.aephandsonlabs.com) |
| 10        |            | [trg.u10@pot5.aephandsonlabs.com](mailto\:trg.u10@pot5.aephandsonlabs.com) |
| 11        |            | [trg.u11@pot5.aephandsonlabs.com](mailto\:trg.u11@pot5.aephandsonlabs.com) |
| 12        |            | [trg.u12@pot5.aephandsonlabs.com](mailto\:trg.u12@pot5.aephandsonlabs.com) |

## Usernames and passwords

Your username uses your lab # above in place of the "##":

| username                        | password        |
| ------------------------------- | --------------- |
| trg.u##@pot5.aephandsonlabs.com | targetLab\_0625 |

# Target Deployment via AEP Debugger

To deploy Target for the lab we'll use an existing Tags property and the Adobe Experience Platform Debugger to inject our Tags deployment onto the site (for the lab users only). 

## Tags script to add

:::BlockQuote
\<script src="[https://assets.adobedtm.com/d488cb72429b/745a813907dc/launch-8f16ad720def-development.min.js](https://assets.adobedtm.com/d488cb72429b/745a813907dc/launch-8f16ad720def-development.min.js)" async>\</script>
:::

## Deployment steps

1. In a new browser tab, navigate to your sites
2. Open the *Adobe Experience Platform Debugger*
   - If you don't have it installed, please install for [Chrome](https://chrome.google.com/webstore/detail/adobe-experience-platform/bfnnokhpnncpkdmbokanobigaccjkpob).
3. With the debugger open, reload the website and click the *Lock* button in the bottom right corner of the debugger. The debugger will detect the Adobe tags currently on the page.
4. In the debugger, click *Experience Platform Tags* in the left nav and select the *Configuration* tab.
5. Part way down the window you should see *Page Embed Codes*&#x20;
   1. If you see one listed here with a 3-dot Actions label to the right of it. Click the action and choose *Replace*.
   2. Paste the Development implementation code previously copied to the clipboard and click *Apply*.
6. If you do not see any *Page Embed Codes* listed then
   1. Click the *Add New Embed Code* button under the *Injected Embed Codes* section
   2. Paste the Development implementation code previously copied to the clipboard and click *Apply*.

![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/-poYbKYAIodiMrzOGzWNI_replace-embed-code.jpg)

# Post session feedback

We would love to hear your anonymous feedback about how the session went. We have a [short 4-question survey](https://forms.cloud.microsoft/r/q84bx7y7HL) that you can fill out in less than 60 seconds. We appreciate you providing feedback to help us improve.