What is the best way to combine testing methods (a/b test...

[#1]

---

@frihed30 wrote:

---

@Jon_Tehero 
What is the best way to combine testing methods (a/b testing while personalising - XT & AB). To make sure that you are always improving? 

---

Hello @frihed30 ,

Great question! Within our A/B activity, you can do both personalization and experimentation. This allows you to test out your personalization techniques and learn what is working the most. You can get pretty sophisticated in testing your personalization by utilizing a feature that allows you to serve different variations of the same experience to different audiences. This could come in handy if you were personalizing content across different geos with different languages, etc.  

[#2]

---

@mravlich wrote:

@Jon_Tehero  Hi -> with the new A4T view in workspace, will we ever use calculated metrics within the view to get confidence levels? Any tips for using this now? Thanks.

---

Hi @mravlich,

This is definitely a common request among our customers. Check out my reply to Shani2 on the same topic.

[#3]

@Shani2 Check out this Spark page on additional best practices for leveraging A4T: https://spark.adobe.com/page/Lo3Spm4oBOvwF/

[#4]

@drewb6915421 -> the link doesn't seem to work. It just redirects me back to this thread. 

[#5]

https://spark.adobe.com/page/Lo3Spm4oBOvwF/  

[#6]

Hey Jon,

@wixyFun asked the following in our forums:

Hi, 

I have some issues with Catalog and inclusion rules comparisons in adobe target recommendations. 

I am trying to use " is less than or equal to" to compare same entity attribute values that are numeric and it looks like adobe thinks of the attribute values as strings , so only when using "equals" I get a correct entity match.

For example, entity.hoursSinceUpdate = 358 is returned when searching/filtering for hoursSinceUpdate is less than or equal to 72

What could be causing this issue? 

Should I delete entities from the catalog or try updating them instead? 

Any suggestions are appreciated, thank you

https://experienceleaguecommunities.adobe.com/t5/adobe-target-questions/entity-attributes-cannot-be-...

[#7]

---

@Shani2 wrote:

Hi again, @Jon_Tehero, I have a statistical question. Is there a feature in the roadmap for the user to be able to select a one tailed test as the statistical method in the Target UI during the experience setup? Currently, by default, the Target statistical engine is configured to support a two tailed test as well as the Sample Size calculator. Technically we can manually adjust the significance level in the sample size calculator if we wished to convert to a single tailed test and manually choose to end a test based on a set of given parameters, however, it would be a lot less effort if that could be automated by being able to select one-sided vs two-sided tests in the UI. One-tailed tests require less time to run and has a lower error probability than two-tailed tests (i.e. alpha is not halved) if testing for a specific direction (i.e. positive/negative). If for example. we are truly testing for superiority, then testing for a negative impact has no value and the cost is having a test run for longer than needed for the business question of interest. As we look for more ways to be agile and become more efficient with our testing program, I am eager to learn if expanding alternative ways of computing statistical significance is in Target’s product roadmap? Thank you!

---

@Shani2,

Thank you for sharing your feedback on one-tailed experiments. We do not have anything on our roadmap at this time for supporting one-tailed tests.

[#8]

@Jon_Tehero do you have any tips for scaling the testing amount within a SPA (single-page application)?

[#9]

Thank you.

[#10]

---

@peterhartung wrote:

Hey Jon,

@wixyFun asked the following in our forums:

Hi, 

I have some issues with Catalog and inclusion rules comparisons in adobe target recommendations. 

I am trying to use " is less than or equal to" to compare same entity attribute values that are numeric and it looks like adobe thinks of the attribute values as strings , so only when using "equals" I get a correct entity match.

For example, entity.hoursSinceUpdate = 358 is returned when searching/filtering for hoursSinceUpdate is less than or equal to 72

What could be causing this issue? 

Should I delete entities from the catalog or try updating them instead? 

Any suggestions are appreciated, thank you

https://experienceleaguecommunities.adobe.com/t5/adobe-target-questions/entity-attributes-cannot-be-...

---

Hello @wixyFun,

Thank you for your question. You are correct in that the "is less than or equal to" operator is looking for a numeric value. However, when you create a custom entity.attribute, the default data type is string. If you reach out to customer care, they can submit a ticket to convert the field type to a numeric field so that the evaluation will work as intended. I will make sure we add this information to our documentation as well.