Adobe Target

Join us for our second AMA on experimentation and personalization strategies with Target, occurring on June 3rd!

RSVP now

A4T: Inability to QA in Debugger

Level 3

9/12/18

Since A4T data collection is done server side as opposed to client side, we are unable to see the variables fire within the debugger - makes for QA-ing our impression and clicks tags impossible.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Related Conversations

Allow for applying same audience refinement to more than one location in Forms Composer

Ability to edit shadow DOM content with html editor in the VEC

Addition of the Activity ID Column in the Activities List

113

When copying an activity to a different workspace, list workspaces alphabetically

100

Export CSV button on Activities and Audiences tabs in Adobe Target

366

Adobe Target

A4T: Inability to QA in Debugger

Learn

Documentation

Events

Community

Support

Resources

Adobe account

Adobe