adobe.target.trackEvent() is failing with 400 response status | Community
Skip to main content
H
HariharanSubra1
Level 2
November 15, 2022
Solved

adobe.target.trackEvent() is failing with 400 response status

  • November 15, 2022
  • 1 reply
  • 1996 views

Hi All,
I am trying to track the click event through the adobe.target.trackEvent().  I am using target JS 2.3.0 version.
I tried in all the browsers still seeing this issues. 
Example: 

adobe.target.trackEvent({'mbox':'click_track_mbox'})

it's throwing the 400 status code. 

Any one can help me on this.

Thanks,
Hariharan Subramanian

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by LucasPafumeVivo

    I tried in Incognito browser with disabled all the extension  and I tried in firefox , safari as well.  its not only my machine. i tried some other machine as well.  same error.

    Thanks,
    Hariharan S


    I have this problem and I try two things:

    1 - Insert this code after the "Target Load page " and before the "Target - Add params to all request" on adobe launch:
    window.targetPageParams = function(){
    return{"at_property": "c58090d5-ZZZZ-TTTT-XXXX-YYYYYYYYYYYY"};
    };

    2 -  After creating the experience on Adobe Target in VEC mode, I have to select in the page "Experiences" the follow steps "configurations -> Properties -> Activities properties"  and set my current property.

    Maybe this will help you

    Best


    1 reply

    Perrin_Ennen
    Community Advisor
    Perrin_EnnenCommunity Advisor
    Community Advisor
    November 16, 2022

    Hello @hariharansubra1,
    the 400 error indicates a request error to the server. The correct status in this case would be 204.

     

    But activities are played out as usual? Otherwise I would recommend to check the implementation.

     

    Currently there is no maintenance work - but it could be the case temporarily. https://status.adobe.com/products/503476

     

    Alternatively I would test the current version at.js 2.10.0.

    The code is correct in itself - and works for me. I have tested it with the 2.10.0 version and Target with CNAME.

      H
      HariharanSubra1Author
      Level 2
      November 16, 2022

      Hi @perrin_ennen ,

      It's not 204 in my case. It's always throwing 400. It's throwing the same error for getoffer method also. 

        Perrin_Ennen
        Community Advisor
        Perrin_EnnenCommunity Advisor
        Community Advisor
        November 17, 2022

        What you could also try - to open it in an incognito window - and there disable all browser extensions.

          Terms & ConditionsAccessibility statement

          Loading footer...