Hi @JudithKo  Are you using ACDL extension or you're injecting the ACDL file directly?  here in your case, the approach you tried -  adobeDataLayer.eventInfo.articleName: The adobeDataLayer object contains all pushed data but does not directly expose event-specific attributes like eventInfo.eventInf...

Hi @amit007  Firstly, when you say mobile app means you talking about (android/iOS based) native apps.  So far I'm aware Adobe Target allows mainly A/B test or Experience Target(XT) test on mobile apps.  To start with - Here is the documentation link that gives you overview, prerequisites, setup ste...

Hi @caride  Yes you're correct. If you use a CNAME like OURCOMPANY.tt.omtrdc.net then Adobe routes traffic through its edge nodes close to request origin.  So, in your case the mboxedge37 is the internal assignment for routing traffic.  I think the edge number is not fixed as it depends upon the use...

Hi @ALB15  Yes, seems that's correct. I just did google and seems like this default option iPad automatically requests desktop versions of sites however user can request for mobile version site through Safari settings.   Now in this scenario, seems there is no built in option in Adobe Target so you'...

Hi @ALB15  If I understood correctly, you're facing issues with Safari browser for iPad12 right?  I would suggest to check below things and see if this helps to get the things done for you.  1) Check the User agent string for your safari browser on your iPad 12 ..  you can check here https://www.wha...

Hi @Jennifer_Dungan  Thank you for all insights. Really appreciate it.  @JyotiSharmaV you can think of the approach suggested by Jennifer and see if you can achieve in your use case.  Thanks.   

Hi @JyotiSharmaV  I believe UTM Parameters and CID (campaign identifier) are supposed to do the same thing: Hold descriptive data about your online marketing campaigns.  In Adobe you put all campaign data in one parameter, separated by a delimiter. The campaign parameter might be named “cid”, but ac...

Hi @MelissaMa7 - Glad that issues resolved for you. 

Hi @MelBe1  Can you once validate your A/B test in browser via either "delivery" call ( if you've implemented Target using at.js) or "interact" call ( if you've implemented Target using web sdk) and see the response or via response tokens. - Check whether you're getting right experience?.  Also what...

Hi @robinl39529461 Does that mean you're not using Alloy.js right?   as you mentioned that you're using your own API to send data, can you check which API gives you the above information?