Hello,
I’d like to request your input on the most robust and future-proof way to implement Adobe Target on a Single Page Application (SPA) — particularly for a complex hotel booking system.
Currently, the implementation is client-side via Adobe Tag Manager, which has led to flickering, broken tests due to re-rendering, extended QA cycles, many workarounds which lead to slower experimentation velocity — all of which impact sprint delivery and overall efficiency.
While the agency (Adobe Licensed Architects) positioned this setup as industry best practice, Adobe’s own documentation recommends a hybrid implementation for SPAs. This approach combines client-side flexibility (at.js) with server-side or Edge Delivery stability, ensuring faster performance, more reliable experiment delivery, and reduced flicker — especially critical in dynamic, transaction-heavy environments like hotel booking systems.
Furthermore, I would like to understand how Target calls are triggered across different implementation types (client-side via Tag Manager, hybrid, and server-side) and how these variations impact Adobe Target call volumes and associated licensing costs.
Given these considerations, I’d appreciate your perspective on how we can align our setup more closely with Adobe’s recommended hybrid model to support both scalability and experimentation velocity moving forward.
Thank you for your insights.
Best regards,
/Stella
