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 ...

Hi @carlosvelarde,Second attempt, hopefully this is helpful. There are 3 ways/methods to pass a conversion mbox/location with order data in it to Target. If using at.js version 1.x you can use the first 2 methods only. If using at.js version 2.x you can use all 3 methods. I personally, prefer to use...

Yes, the mbox.js has been deprecated. To fire a custom mbox location with at.js 2.x you will want to use the new getOffers() function. Details can be found here: https://experienceleague.adobe.com/docs/target/using/implement-target/client-side/at-js-implementation/functions-overview/adobe-target-get...

Yes, if you use the visual experience composer to setup the activity you need the target-global-mbox request to be made. Make sure the page load/auto created mbox is enabled and download your at.js after that is set.

Hi @jsolano918,Yes, you can do that! If it's easier for you to implement a custom mbox across those 50 product pages than to write a refinement rule to address those pages that's a totally viable solution with Adobe Target. I'd just give the mbox a name that is meaningful and helps the person settin...

Ah, looking closer at your screen shot of your getOffers() it does appear like you have an extra space in the "productPurchasedId" key name. Can you double check that and try it without a trailing space?

Hi @carlosvelarde,Your implementation looks to be fine. However, the reporting it sounds like you want to do is beyond Target reports. The passing of the productPurchasedId is for 2 main purposes in Target. 1) For informing Recommendations about specific entity/products getting purchased - to enable...

Yes the mbox name can be whatever you choose. The key part is really just the profile parameter name and values because you'll be using those in the Audience definition. You don't really need to reference the mbox name so I tend to use something generic like 'dataCapture' in these cases.