Web Channel in AJO is not working as expected | Community
Skip to main content
S
SR10
Level 3
September 22, 2023
Solved

Web Channel in AJO is not working as expected

  • September 22, 2023
  • 4 replies
  • 2508 views

I'm currently in the process of integrating a web channel into our AJO implementation. Following the guidelines outlined in the 'Web Channel Prerequisites' documentation, I have successfully configured the web SDK. To test this setup, I've been utilizing Adobe's provided Luma enablement site and injecting tag scripts using a debugger.

 

I've accomplished creating an audience using the edge segment evaluation method, and I can confirm that data is flowing from the website into the AEP datasets, with profiles being successfully added to this audience.

 

However, when I attempt to use this audience in a web campaign with the debugger enabled for the site, I'm not observing the expected changes on the website page as specified in the web campaign configuration.

 

I would greatly appreciate any assistance with this matter and any insights you may have regarding any steps or details I might be overlooking

 

Thanks

Sankar

Best answer by akshaaga

@sr10 ,

 

It's great to hear that you've successfully configured the web SDK and data is flowing into Adobe Experience Platform (AEP) datasets. However, if you're not observing the expected changes on the website page when using the audience in a web campaign, there are several areas you can investigate to troubleshoot the issue:

1. *Web Campaign Configuration*: Double-check your web campaign configuration. Make sure that the audience you're targeting is correctly set up, and the campaign actions are defined accurately.

2. *Audience Validation*: Verify that the audience you created is populating as expected. You can use the segment preview functionality in AEP to ensure that the audience members match your criteria.

3. *Audience Synchronization*: Ensure that the audience is synchronizing properly with the web channel. There might be a delay in audience updates, and it's essential to confirm that the audience members are correctly identified on your website.

4. *Action Execution*: Check the campaign actions, such as JavaScript code, and confirm that they are properly structured and functional.

 

Troubleshooting issues in Adobe Experience Platform can sometimes be complex, and it may require a combination of checking configuration settings, monitoring logs, and making adjustments to your campaign setup.

4 replies

Anuhya-Y
Community Advisor
Anuhya-YCommunity Advisor
Community Advisor
September 22, 2023

@sr10 what is the version of AEP Web SDK ? 

I had faced similar issue, after updating AEP Web SDK to the latest version, web campaign started working as expected.

S
SR10Author
Level 3
September 22, 2023

Hi @anuhya-y ,

 

Thank you for your response.I am also using the same version. PFB the screenshot.

 

 

akshaaga
Adobe Employee
akshaagaAdobe EmployeeAccepted solution
Adobe Employee
October 14, 2023

@sr10 ,

 

It's great to hear that you've successfully configured the web SDK and data is flowing into Adobe Experience Platform (AEP) datasets. However, if you're not observing the expected changes on the website page when using the audience in a web campaign, there are several areas you can investigate to troubleshoot the issue:

1. *Web Campaign Configuration*: Double-check your web campaign configuration. Make sure that the audience you're targeting is correctly set up, and the campaign actions are defined accurately.

2. *Audience Validation*: Verify that the audience you created is populating as expected. You can use the segment preview functionality in AEP to ensure that the audience members match your criteria.

3. *Audience Synchronization*: Ensure that the audience is synchronizing properly with the web channel. There might be a delay in audience updates, and it's essential to confirm that the audience members are correctly identified on your website.

4. *Action Execution*: Check the campaign actions, such as JavaScript code, and confirm that they are properly structured and functional.

 

Troubleshooting issues in Adobe Experience Platform can sometimes be complex, and it may require a combination of checking configuration settings, monitoring logs, and making adjustments to your campaign setup.

    D
    deepikawadhwa1
    December 1, 2023

    Hi @sr10  Please check your Active-On-Edge Merge Policy for the segment. If it is not enable try to enable it and please also check data stream setting its AJO seting is enable there.

     

    Thanks,

    R
    Riya
    July 3, 2025

    I am also facing the similar issue. However when I check Assurance logs , it says the profile is not present in the ajo segment. Below is the error payload.

    Not sure what is the exact issue?

    Any help will be appreciated.

    "execution": {
            "uuid": "86f76e3d-bace-468e-bc35-2c636aceb3d3",
            "sessionUuid": "53db027d-6055-4405-8ac3-dfb328b8a2cb",
            "clientId": "5166b755-ec2f-472d-a9eb-8fc960ee73ea",
            "orgId": "D1D7123F524450A60A490D45@AdobeOrg",
            "vendor": "com.adobe.experience_platform.ajo",
            "type": "service",
            "timestamp": 1751545218544,
            "payload": {
                "name": "com.adobe.experience_platform.ajo/execution",
                "timestampMs": 1751545218294,
                "attributes": {
                    "requestId": "ee5d538a-256c-43f6-85d9-7d552f4184a9-f03f2cde763f452e",
                    "eventIndex": "0",
                    "serviceName": "com.adobe.experience_platform.ajo",
                    "source": "IDS"
                },
                "messages": [
                    "No activities qualified"
                ],
                "logLevel": "info",
                "context": {
                    "X-Konductor": "25.6.1-HOTFIXLOG4JUPGRADE:474d114cc",
                    "X-Adobe-Edge": "IRL1",
                    "x-edge-cell": "cell-0",
                    "x-edge-region": "irl1",
                    "datastreamId": "c29454f2-9a09-4647-9fb0-5acc2eab05b2",
                    "unqualifiedActivities": {
                        "6378f6a3-bfdc-42bb-92d4-cfb26a081b37": {
                            "id": "6378f6a3-bfdc-42bb-92d4-cfb26a081b37",
                            "activityUid": "fb83399e544655788e7aca0ab0fed980f69d08a4edbcf1ccc30412b8200f032b",
                            "type": "journey",
                            "exclusionReasons": [
                                {
                                    "params": [
                                        "6378f6a3-bfdc-42bb-92d4-cfb26a081b37_d0f20a99-7bf5-4da2-8496-334713137d2b"
                                    ],
                                    "text": "Segment %s not found in profile",
                                    "code": "exclusion.reason.segment.not.found"
                                }
                            ],
                            "identityNamespace": "ECID",
                            "scheduleStart": "2025-07-03T12:01:50.659040Z",
                            "scheduleEnd": "2035-07-01T12:01:50.659Z",
                            "surfaces": [
                                "web://moments-adobe-dm-sites.s3.us-east-1.amazonaws.com/apl-sites/bootcamp/index.html"
                            ]
                        }
                    },
                    "unqualifiedActivitiesDetailed": [
                        {
                            "id": "6378f6a3-bfdc-42bb-92d4-cfb26a081b37",
                            "context": {
                                "type": "journey",
                                "activityUid": "fb83399e544655788e7aca0ab0fed980f69d08a4edbcf1ccc30412b8200f032b",
                                "packageId": "78003c49-2600-4f2c-b920-6e0f84b68aad",
                                "surfaces": [
                                    "web://moments-adobe-dm-sites.s3.us-east-1.amazonaws.com/apl-sites/bootcamp/index.html"
                                ],
                                "messages": [
                                    {
                                        "key": "0eb6300e-09d9-4b84-905a-a6d018db1ce6:317dbea9-bcfd-488d-9a59-bc666baf0474",
                                        "id": "0eb6300e-09d9-4b84-905a-a6d018db1ce6",
                                        "publicationId": "317dbea9-bcfd-488d-9a59-bc666baf0474"
                                    }
                                ],
                                "scheduleStart": "2025-07-03T12:01:50.659040Z",
                                "scheduleEnd": "2035-07-01T12:01:50.659Z",
                                "audienceSegmentId": "6378f6a3-bfdc-42bb-92d4-cfb26a081b37_d0f20a99-7bf5-4da2-8496-334713137d2b",
                                "audienceNamespace": "joai",
                                "journeyId": "6378f6a3-bfdc-42bb-92d4-cfb26a081b37_d0f20a99-7bf5-4da2-8496-334713137d2b",
                                "journeyActionId": "d0f20a99-7bf5-4da2-8496-334713137d2b",
                                "isTestExecution": false,
                                "identityNamespace": "ECID",
                                "exclusionReasons": [
                                    {
                                        "params": [
                                            "6378f6a3-bfdc-42bb-92d4-cfb26a081b37_d0f20a99-7bf5-4da2-8496-334713137d2b"
                                        ],
                                        "text": "Segment %s not found in profile",
                                        "code": "exclusion.reason.segment.not.found"
                                    }
                                ]
                            }
                        }
                    ]
                }
            }
    Silvio6
    Silvio6
    Level 5
    October 1, 2025

    I'm facing the "exclusion.reason.segment.not.found" for In-app too. Were you able to understand this?

    Terms & ConditionsAccessibility statement

    Loading footer...