Target Workspace Audience Retrieval Issue

[test1234567]

Hello Community,

I have set up the integration between AEM and Target. Currently, I am trying to pull audiences from a specific Target workspace, but the integration only retrieves audiences from the default workspace. The Developer Console (Project) is configured, and the API integration is associated with a different project (not the default), yet it still only accesses the default workspace.

Question 1:
Is there a way to pull audiences from a different workspace instead of the default one? If so, what configuration changes are needed to enable this?

Question 2:
Also, in the Developer Console, for the API integration, I am unable to specify or select the default workspace; I can only select a project-specific workspace. What steps are required to add or enable the default workspace?

Question 3:

I am also encountering an error when saving or syncing activities to Target. Could this be related to a permissions issue? Please advise.

04.09.2025 20:09:20.466 *DEBUG* [10.96.204.188 [1757034439974] POST /libs/cq/analytics/testandtarget/command HTTP/1.1] com.day.cq.analytics.testandtarget.impl.service.WebServiceImpl Unexpected response status code [400] for request [https://mc.adobe.io/test/target/activities/xt?includeMarketingCloudMetadata=true].
{"httpStatus":400,"requestId":"sX4RViyr0SDwJ9Sd6AAlrJXZDfFeouPG","requestTime":"2025-09-05T01:09:20.414925723Z","errors":[{"errorCode":"OfferId.ABActivity.options.offerId","message":"Offer not accessible in provided workspaces. Id: 5738310","meta":{"options[0].offerId":5738310}}]}
04.09.2025 20:09:20.467 *DEBUG* [10.96.204.188 [1757034439974] POST /libs/cq/analytics/testandtarget/command HTTP/1.1] com.day.cq.analytics.testandtarget.impl.TokenManager Releasing token content-campaigns-test-portal-target-experience-project-personalization
04.09.2025 20:09:20.480 *ERROR* [10.96.204.188 [1757034439974] POST /libs/cq/analytics/testandtarget/command HTTP/1.1] com.day.cq.analytics.testandtarget.impl.servlets.commands.SynchronizeCampaignCommand Save activity request failed!

@davidjgonzalezzzz @EstebanBustamante @RiteshY18 @Gokul_Agiwal @Umesh_Thakur @pradnya_balvir @Amelia_Waliany @ParitMittal @pradnya_balvir 

[AmitVishwakarma]

Hi @test1234567 ,

The problem you're seeing, where AEM only pulls audiences from the default Target workspace and throws a 400 error on sync, is almost always a permissions issue. The technical service account from your API integration doesn't have rights to the other workspace.

Here’s how to fix it:

Step 1: Grant Access in Adobe Admin Console

This is the most critical part. The API user (technical account) from your Developer Console project needs to be explicitly given access to the specific Target workspace you want to use.

  - Go to the Adobe Admin Console (adminconsole.adobe.com).

  - Navigate to Products > Adobe Target.

  - You'll see a list of Product Profiles. Each profile here controls access to a specific Target workspace (e.g., the "Default" profile controls the "Default Workspace").

  - Click on the Product Profile that has the same name as the desired Target workspace.

  - Go to the Users tab and click Add User.

  - In the pop-up, switch to the Service Accounts tab.

  - Find and select the technical service account from your integration (it will look like an email address, e.g., IMSe9c...@techacct.adobe.com).

  - Assign it the Approver role. This gives it the necessary permissions to create and sync activities.

  - Click Save.

This step directly solves Question 1 and Question 3. It grants the service account permission to see audiences and work with activities in that specific workspace.

Step 2: Refresh the Connection in AEM

After updating permissions, you must force AEM to re-authenticate and get a new access token with the updated permissions.

  - In AEM, go to Tools > Cloud Services > Adobe Target Configurations.

  - Open your configured Target cloud service.

  - Click the Edit (wrench icon) button.

  - Simply re-enter the same Client ID and Client Secret and click Connect to Target. This refreshes the connection.

  - Click OK to save.

Step 3: Verify the Fix

Q1: Pull audiences from a different workspace?
Yes. This is controlled by the service account's Product Profile membership in the Adobe Admin Console, not in AEM or the Developer Console. Add the account to the correct profile (Step 1).

Q2: Select default workspace in Developer Console?
You can't. Workspace access is not configured in the Developer Console. The Developer Console only creates the API credentials. You must then assign those credentials to a Product Profile in the Adobe Admin Console to grant them access to any workspace, including the default one.

Q3: Is the 400 error a permissions issue?
Yes, definitively. The error "Offer not accessible in provided workspaces" means the API user trying to sync the activity does not have permission to work in the target workspace. Granting access in the Admin Console (Step 1) fixes this.

Thanks,
Amit

[test1234567]

Thank you for your inputs. Regarding the steps you provided, I do not see any option to switch to the Service Accounts tab. I am not sure if this is related to permissions for my user account. If possible, could you please share a screenshot?

Additionally, I have already granted approver access to both the Default Workspace and the project-specific workspace under the API Integration tab. In your response, you mentioned the Service Accounts tab and selecting the technical service account from the integration. Is this step also required, in addition to granting approver permission in the API Integration tab? Please confirm.

Go to the Users tab and click Add User.

  - In the pop-up, switch to the Service Accounts tab.

[test1234567]

Could you explain the difference between granting approver/editor permissions to credentials (the project created in the developer console) versus granting permissions under the Service Accounts tab to the technical service account from the integration, as you suggested?

Also, I do not see the Service Accounts tab in the Add User popup. Do we need to enable any additional permissions to make this tab visible in the admin console? Please advise.

[test1234567]

Since the Service Account tab was not visible in the Add User popup, I searched for the email ID using the user field/textbox and added the account using the technical service account email. I then granted approver privileges to the required workspaces. Please let me know if this is the correct approach.

I have also assigned the approver permission for the integration project (created in Developer Console) under the API Integration tab.

Additionally, I refreshed the existing connections in AEM by re-authenticating, but I am still encountering the same error. I am not sure if it is still pointing to a different workspace other than the default workspace. I have already verified that the default workspace ID does not match 5883104. Could you help me understand what could be causing this issue?

07.09.2025 21:06:56.798 *DEBUG* [10.97.193.234 [1757297192660] POST /libs/cq/analytics/testandtarget/command HTTP/1.1] com.day.cq.analytics.testandtarget.impl.service.WebServiceImpl Unexpected response status code [400] for request [https://mc.adobe.io/project/target/activities/xt?includeMarketingCloudMetadata=true].
{"httpStatus":400,"requestId":"TKTIdHtcaWzAE7aXquWHsv3EotCrcJPN","requestTime":"2025-09-08T02:06:56.719598608Z","errors":[{"errorCode":"OfferId.ABActivity.options.offerId","message":"Offer not accessible in provided workspaces. Id: 5883104","meta":{"options[0].offerId":5883104}}]}
07.09.2025 21:06:56.799 *DEBUG* [10.97.193.234 [1757297192660] POST /libs/cq/analytics/testandtarget/command HTTP/1.1] com.day.cq.analytics.testandtarget.impl.TokenManager Releasing token content-campaigns-test-portal-target-experience-project-persona
07.09.2025 21:06:56.801 *ERROR* [10.97.193.234 [1757297192660] POST /libs/cq/analytics/testandtarget/command HTTP/1.1] com.day.cq.analytics.testandtarget.impl.servlets.commands.SynchronizeCampaignCommand Save activity request failed!

[Umesh_Thakur]

can you check your user's access to workspace from which you are trying to pull the audiences and as you already mentioned that audiences are being synched so there should not be any configuration issues there.