Hi @renatoz28,I agree this is likely not possibly with Analytics segments alone. You need a Target profile script to help with counting prior impressions. Here in the other post I walk through how to do this sort of thing. The use case is similar to yours I think.Solved: Show experience 3 times in o...

Hi @MA1985v1,This can be done with some customization and an XT or Experience Targeting activity. An XT activity will allow you to create experiences and then prioritize the order that a visitor qualifies for them. Move experiences to the top for higher priority. Tracking the views of each experienc...

Hi @Maple-Michelle1, Perhaps you've solved this already. Normally the out of the box Browser > Language audience rule options should work fine. However, if you find them not working as expected you could use a profile script to define an audience. The profile script could check for the four language...

Hi @Maple-Michelle1, I think the "clicked an element" method is probably the easiest one to use. However, there are other ways. You could use a custom code modification in the VEC (or via a form composed test) to add a small JS that inserts an onclick action on the button/link to fire an adobe.targe...

Hi @bkmills,When you first create an A4T activity in Target, a back-end process has to run in order to list the new activity and experiences in the Target related dimensions in Analytics Workspace. This usually only takes a few hours after the activity is first saved, but could take a day in some ca...

Hi @rrrrrraul,#1: It does rely on the same A4T configuration option the typical client-side deployment of Target does (using an SDID parameter). This does assume a Target server-side deployment and a client-side deployment of ECID and Analytics. Then you should be setting a server-state for the ECID...

There is no feature to handle this particular situation in Target. However, you could use a custom JS code offer to handle something like this. Within the JS add a delay and then call a function to render your experience/content change.

I believe the native splitter is also based on a random number generation. Your profile script should already be mimicking the same behavior. Here's a little in help docs on it. https://experienceleague.adobe.com/docs/target/using/introduction/how-target-works.html?lang=en#a%2Fb-test

Hi @Tienzen, Yes, that should split traffic into 2 groups as efficiently as the native splitter.Extra tip: if you modify the profile script to simply return the random number between 1-100 you can then use the audience rule to split to groups of: 2, 4, 5, 10, etc. Your current profile script will on...

Hi @chrish75788707,Looks like you are using Target as the reporting source. So, the first things I'd check are (and it sounds like you've already checked - but just for others who may see this):Confirm my metric settings in the activity. Are the mbox names exactly what I'm expecting? Have you added ...