Skip to main content
Saravanan_Digital_AnalytiB
Level 1
August 14, 2026
Question

Adobe Target Production Delivery Issue for a Specific Property

  • August 14, 2026
  • 4 replies
  • 62 views

Hi everyone,

I'm currently facing an issue with an Adobe Target activity and wanted to check if anyone has come across something similar.

The activity is working as expected in the Development environment, but it is not delivering after moving the library build to Production. We have verified that the correct build has been published to Production.

What makes this a bit confusing is that the issue is happening only for one market property. The other market properties are working fine with their respective Production builds.

Has anyone faced a similar issue where an activity works in Development but does not deliver in Production for a specific property? Are there any additional configurations or checks that we should look into?

    4 replies

    Gokul_Agiwal
    Community Advisor
    Gokul_AgiwalCommunity Advisor
    Community Advisor
    August 14, 2026

    Hi ​@Saravanan_Digital_AnalytiB  

    Before jumping straight on solution, it would be helpful to understand a bit more about your Adobe Target setup.

    • Are you using at.js or AEP Web SDK for the Target implementation?
    • Is the activity associated with a Target Property/Workspace or are you referring to Adobe Tags ( Adobe launch property) ? If it’s Target property, is the affected market mapped to the same property as the working markets?
    • Is the activity using Page Load, SPA View, or a custom mbox/location?
    • Is the issue that the activity is not returned in the Target delivery response, or is it returned but not rendered on the page?
    • Does the affected market use the same code base and launch/tag configuration as the other markets that are working?
    • Are there any market-specific audiences, profile scripts, geo-targeting rules, or URL conditions configured in the activity?
    • Have you checked the Target request using Experience Cloud Debugger or browser network calls to compare a working market versus the affected one?

     Understanding above details will help to determine the issues. Looking forward to your reply. 

    Thanks, Gokul
    Saravanan_Digital_AnalytiBAuthor
    Level 1
    August 14, 2026

    ​@Gokul_Agiwal, thanks for your response, please refer to the below

    • Are you using at.js or AEP Web SDK for the Target implementation?-- AEP Web SDK
    • Is the activity associated with a Target Property/Workspace or are you referring to Adobe Tags ( Adobe launch property) ? If it’s Target property, is the affected market mapped to the same property as the working markets? -- referring to Adobe launch property
    • Is the activity using Page Load, SPA View, or a custom mbox/location? -- rule is executing on DOM Ready (for exit intent popup activity)
    • Is the issue that the activity is not returned in the Target delivery response, or is it returned but not rendered on the page? -- can you elaborate please?
    • Does the affected market use the same code base and launch/tag configuration as the other markets that are working? -- yes, but other markets use different Launch Properties
    • Are there any market-specific audiences, profile scripts, geo-targeting rules, or URL conditions configured in the activity? -- Nope
    • Have you checked the Target request using Experience Cloud Debugger or browser network calls to compare a working market versus the affected one? -- Yes
    Gokul_Agiwal
    Community Advisor
    Gokul_AgiwalCommunity Advisor
    Community Advisor
    August 18, 2026

    Hi ​@Saravanan_Digital_AnalytiB  

    Thank you for the response and sorry for late to coming back on this .. 

    Since you're using AEP Web SDK and the issue is happening only for one market, I'd start by comparing the network calls between a working market and the affected market.

    A quick question on your comment around checking the Target request:

    • If the activity is not present in the Target/Web SDK response at all, then Target is likely not qualifying the visitor for the activity. This usually points to configuration differences such as datastream settings, URL matching, property/workspace setup, environment configuration, or audience qualification. 
    • If the activity is present in the response but the popup never appears, then the issue is more likely related to rendering, selectors, JavaScript execution, or rule timing on the page. 

    My gut feeling is that this is either a datastream/configuration difference in the affected Launch property or the activity is simply not being qualified in the Target response. 

    Could you share what difference you observed in the Web SDK network response between a working market and the affected market? That's likely where the root cause will show up.    

    If the website URL is publicly accessible (or if you can share a page that can be accessed externally), I'd be happy to take a look from my side and see if I can spot anything unusual in the implementation or network calls.  You can DM me directly. . 

    Thanks 

    Thanks, Gokul
    Terms & ConditionsAccessibility statement

    Loading footer...