Configuration Field for A4T Trackingserver | Community
Skip to main content
H
hegi90
Level 3
March 28, 2022
New

Configuration Field for A4T Trackingserver

  • March 28, 2022
  • 3 replies
  • 1355 views

Currently if you use at.js 2.0, the tracking server for a4t (analytics for target) is automatically set by the ECID Extension. But if you use a first party proxy configuration where your trackingserver is not your CNAME but your first party domain, the data is not flowing into adobe analytics. So it would great to set the tracking server in the Adobe Target v2 Extension UI, in case you use a proxy configuration on your analytics and ECID. In that case the trackingserver for a4t should be the CNAME and not the firstparty proxy domain, because even with a redirect on the firstparty domain, data will not flow into analytics. 

    3 replies

    Kishore_Reddy
    Community Advisor
    Kishore_ReddyCommunity Advisor
    Community Advisor
    March 29, 2022

    Hey @hegi90 

    Hope you are doing well!

    Implementation steps for an at.js implementation section in this article could help.

    Also, take a look at this discussion: https://experienceleaguecommunities.adobe.com/t5/adobe-target-questions/tracking-server-for-adobe-analytics-not-set-when-loading-adobe/td-p/383715 

     

    Best,

    Kishore

    H
    hegi90Author
    Level 3
    March 30, 2022

    Hi @kishore_reddy 

    Thanks for your reply. I solved it on my side with a workaround. Inside the Adobe Target Request, I change the Tracking Server to the CNAME, and after the request is sent, I reset it to the proxy domain (currently not running on web sdk).

    Kishore_Reddy
    Community Advisor
    Kishore_ReddyCommunity Advisor
    Community Advisor
    March 30, 2022

    Glad to hear that @hegi90 🙂

    Terms & ConditionsAccessibility statement

    Loading footer...