My team is working on a proof of concept to minimize the amount of page flicker that occurs before Target fires and shows alternate content. So far, we've been able to hard-code into our SPA the ability to hide original content before we show the alternative. But, this would happen for every user if we pushed to production. Not what we want.
Based on the above explanation, is there a way to capture the Activity ID to control test entry to only those who qualify? I should note that we use a third-party tag manager, and it's been suggested that we do so there. However, we're wondering is there's another way?
Below is a very crude example of what we're doing:
// Declare private variable for page, url, activity ID and CSS selector