Access: Must be enabled for your organization. Contact your Gradial team to get access.
What you can do
Activity management
Create A/B and Experience Targeting drafts, edit, rename, schedule, set priority, activate, deactivate, and review change history across every workspace.
Verified delivery
Before an activity goes live, Gradial opens every experience in a real browser and checks that each one shows the content it should.
Page-scoped changes
An activity that changes a component is tied to the page it was built for, so a change to one hero does not spread to every page that shares it.
Audiences, offers & mboxes
Work with audiences, offers, mboxes, properties, and environments. Create reusable audiences, or target audiences that Adobe Experience Platform sends to Adobe Target. Experience Platform audiences need the Adobe Experience Platform integration connected with the same IMS org ID as your Adobe Target connection.
In-context previews
Preview each experience in Gradial before launch, so reviewers do not need to open Adobe Target.
Performance reporting
Read performance and order reports for an activity. For activities that report to Adobe Analytics, see Reporting source.
Before you start
You need:- An active Adobe Experience Cloud organization with Adobe Target.
- Access to Adobe Developer Console for that organization. Adobe asks that your account has both Product Admin and Developer access to Adobe Target.
- Your Adobe Target Tenant ID (the name in your Target URL after
#/@). - The IMS Org ID from your Adobe credential details.
- A Gradial Organization Admin or Owner role.
On Adobe Target Premium, an integration gets a role per workspace (Adobe calls a workspace a product profile). To create, edit, and activate activities, give the integration the Approver role. Editor can create and edit activities before they are live but cannot approve a launch, and Observer is read-only. API requests that name a workspace need Approver on it. See Adobe’s integration roles and Admin API reference.
Connect Adobe Target
1
Create credentials in Adobe Developer Console
- Go to Adobe Developer Console and sign in for the correct Experience Cloud organization.
- Create or open the project you want to use for this integration.
- Click Add API and select Adobe Target.
- Choose OAuth Server-to-Server as the credential type.
- If prompted, select the product profiles the integration should be allowed to use. These correspond to your Adobe Target workspaces. If your account does not use workspaces and properties, select the Default Workspace option.
- From the credential details screen, copy the Client ID, Client Secret, and Organization ID.
2
Find your Tenant ID
Sign in to Adobe Experience Cloud and open Adobe Target. Your Tenant ID is the name in the URL after
#/@. For example, in https://experience.adobe.com/#/@yourcompany/target, the Tenant ID is yourcompany.The Tenant ID must be letters and numbers only, 3 to 50 characters. It is not your Target client code, so use the name from the Experience Cloud URL. See Adobe’s authentication guide.
3
Add the integration in Gradial
- In Gradial, go to Settings → Integrations.
- Find the Adobe Target card and select it.
- Fill in the connection details:
- Click Save.
4
Assign to an Environment
- Go to Settings → Environments and select the Environment where Adobe Target should be available.
- Add the Adobe Target integration to that Environment.
- Repeat for any additional Environments.
How Grady builds and verifies activities
1
Check the page
Grady loads the page, confirms Adobe Target (at.js or the Web SDK) is running, and confirms that every selector it plans to change matches exactly once. The check fails if Adobe Target is not detected on the page.
2
Create a draft
Grady saves the activity as a draft that is not serving traffic. A/B visitor percentages must add up to 100. Grady is set up to give each activity a single conversion metric, and to include one default experience with no audience in every Experience Targeting activity, shown to visitors who match no targeted audience.
3
Verify every experience
Gradial opens each experience in a browser and checks that the experiences render consistently, show different content from one another, and include any text you asked for. Activities with several components or locations are checked location by location.
4
Check other pages
When Grady supplies a comparison page with the same components, Gradial confirms the activity does not appear on it. If no suitable comparison page was checked, the activity card shows Other pages not checked.
5
Activate when you ask
Activation and scheduling are refused unless the activity’s current content passed verification. If the content changes afterward, the activity must be verified again.
Verification results
The activity card shows one of these outcomes. Only a verified activity can be activated or scheduled from Gradial.Using activities
Page scope
A selector identifies content within a page, not which page it is on. To keep a change to a shared component from appearing everywhere, Gradial requires every component-level activity to be limited to one page.- Grady is set up to scope an activity to one exact page URL (no query strings or fragments) unless you ask for more than one page.
- A rule for several pages needs a property and must start with a fixed path segment. Only that fixed start limits delivery.
- An activity whose saved page rule is missing, or broader than intended, is blocked from going live.
Editing activities
- A/B drafts can be edited in place. An edited activity must be verified again before it goes live.
- Experience Targeting drafts can be edited in place, keeping the same page, audiences, and locations. To move the activity to another page, change its audiences, or change its locations, Grady creates a new draft instead.
- Experience Targeting activities with unusual settings cannot be edited in place. Examples are single-page-app views, entry constraints, device or app targeting, reporting audiences, and Customer Journey Analytics reporting.
- Live and scheduled activities cannot be edited from Gradial. Grady proposes a new draft with the change, and you switch over from the old activity to the new one in Adobe Target. The one exception is the traffic split change under Opt-in capabilities.
Reporting source
Activities report to Adobe Target by default. To report to Adobe Analytics (Analytics for Target, or A4T), the activity needs a report suite, which Grady looks up through your connected Adobe Analytics integration. Adobe Target rejects an Analytics-reported activity if your account is not set up for A4T. Adobe requires a provisioning request, which can take up to five business days, plus Adobe Target and Adobe Analytics running on the page and access to the report suite and the Web Services Access group in Adobe Analytics. See Adobe’s A4T requirements and permission requirements. For these activities, the results of record live in Adobe Analytics. What Gradial returns depends on whether Portfolio monitoring is enabled for your organization:- Without Portfolio monitoring, Gradial returns Adobe Target’s own count of visitors and Target-defined conversions, with a warning that it is not the activity’s result. Success metrics chosen in Analytics are not included, so numbers can differ from Analytics and from Adobe Target’s own report.
- With Portfolio monitoring, Grady reads results from Adobe Analytics. See Portfolio monitoring.
Accounts without properties
Properties and workspaces are part of Adobe Target Premium. Accounts without them, such as Target Standard, have an empty property list. That is normal. On these accounts Gradial can still create and activate activities, with these limits:- Activities are created for one exact page. Route patterns are not available.
- The page rule is the only delivery boundary. It must stay exactly that page, optionally narrowed by visitor conditions such as browser or location.
- Activities cannot be edited in place. To change one, Grady creates a new draft and verifies it again.
Opt-in capabilities
Each of these is turned on separately for your organization.Ramp a live A/B split
Access: Must be enabled for your organization. Contact your Gradial team to get access.
- The new percentages must cover the same experiences and add up to 100.
- An organization Owner or Admin must approve the change. The approval card, Change live Adobe Target traffic split, shows the activity ID, the current split, and the requested split.
- The ramp is refused if the split in Adobe Target changed since Grady read it.
- Only live A/B activities can be ramped. Change a saved or deactivated activity through normal draft editing.
- Adobe Target saves the whole activity on every update, so an edit someone makes in Adobe Target moments before Gradial saves can be overwritten without warning. Ask Grady to check the activity if anyone else was editing it.
- Grady offers a dated line for the activity’s Notes with the time, the old and new split, who asked, and a link to the Task. The ramp does not write it by itself. See the next section.
Add a note to an A/B activity
Access: Must be enabled for your organization. Contact your Gradial team to get access.
- Each note is one line of plain text, 1 to 2,000 characters, with no line breaks or emoji.
- The Notes field holds 2,048 characters in total. A note that would go over is not saved. Make room in Adobe Target, then ask again.
- The approval card is Add a note to an Adobe Target activity, and it shows the exact text.
- A line already in the Notes is not added twice.
- Gradial saves the whole activity, so the overwrite caveat above applies. If the activity has Adobe Target settings Gradial cannot safely carry through, the save is refused and you are told to add the note in Adobe Target.
- Only A/B activities are supported.
Portfolio monitoring and Analytics results
Access: Must be enabled for your organization. Contact your Gradial team to get access.
- Collisions. Finds activities that can reach the same visitor at the same time in the same place: they share a property, their schedules overlap, they change the same mbox or CSS selector, and their page rules overlap. It checks live and scheduled activities, and you can include drafts to check before launch. Each group is rated high, medium, or low, and shows which activity wins on priority where that can be determined. Selectors are compared as text, so two selectors that reach the same element in different ways are not caught.
- Performance anomalies. Compares the last 7 days with the 7 days before and flags significant moves in conversion rate and in visitors per day. You can change the window, the minimum visitors, and the threshold. Revenue per visitor is shown as a change only and is never flagged.
- Skipped activities are listed. Types without a performance report, such as Auto-Allocate and Recommendations, and activities Adobe could not return in time are listed as skipped, never reported as healthy. Low-traffic activities show as no data or insufficient data.
- Analytics results. For activities that report to Adobe Analytics, Grady reads visitors and visits per experience from the activity’s first report suite, over the activity’s lifetime (the last 90 days if it has no start date). Conversions and conversion rate are included when the goal is a click or mbox goal defined in Adobe Target. Goals chosen in Adobe Analytics are not read, so Grady points you to the Analytics for Target panel in Analysis Workspace. This needs exactly one connected Adobe Analytics integration. If there is none, or more than one, the report says so instead of showing Adobe Target’s count.
Limits
- Verified authoring uses CSS selector locations. Activities that use mboxes can be created as drafts and inspected, but Gradial does not verify them, so activate them in Adobe Target.
- Activities whose content comes from an existing offer, such as an exported AEM Experience Fragment, stay in draft because Gradial cannot verify the referenced content. Verify and activate them in Adobe Target.
- On accounts that use properties, an activity must name a workspace, and that workspace must contain every property the activity uses.
Example workflow
- Start with a performance insight from Adobe Analytics or CX Optimizer.
- Identify the audience that should get a different experience.
- Ask Grady to draft the activity, offers, and audiences for that page and component.
- Review the verification result and preview each experience.
- Ask Grady to activate the activity.
- Read the performance report as results come in.
Troubleshooting
“Invalid client” error from Adobe Gradial does not check your credentials when you save. Adobe checks them the first time the integration is used. Copy the Client ID and Client secret again from Adobe Developer Console with no extra spaces. Tenant ID not recognized Use letters and numbers only, 3 to 50 characters, taken from your Adobe Target URL after#/@, with no slashes or extra text. If the format is fine but the name is wrong, Adobe refuses requests with a 403 and Gradial shows “Adobe Target authentication failed. Reconnect the integration in Settings.”
IMS org ID error
The IMS org ID must end in @AdobeOrg. Copy it directly from the Adobe Developer Console credential details screen.
The property list is empty
This is normal for accounts without properties. See Accounts without properties.
Activation was refused
Gradial only activates an activity whose current content passed verification. Ask Grady to verify the activity again. If the activity is built on mboxes or an existing offer, activate it in Adobe Target.
Adobe refuses to create or activate activities
Check that the integration has the Approver role on the workspace the activity uses. Editor cannot approve a launch.
Grady says ramping, notes, or monitoring is not enabled
Those are opt-in capabilities. Contact your Gradial team to get access.
A ramp or note says another change is already in progress
Another Task, or a save Adobe Target did not confirm, is holding the activity. Wait about three minutes, then ask Grady to try again.
An A4T activity shows Adobe Target’s count instead of Analytics results
Analytics results need Portfolio monitoring enabled and exactly one Adobe Analytics integration connected. Without both, you get Adobe Target’s own count with a warning.
A verified activity shows “Other pages not checked”
No comparison page was provided, or none contained every component the activity changes. Ask Grady to verify again with a sibling page that contains the same components.
Previews not loading automatically
Activities Grady creates record the page they were built for, and previews load against it. For older activities, set a Default preview URL in the integration settings, or enter a URL in the Preview URL field on the activity page.
Integration not available in a Workspace
Assign the integration to the correct Environment under Settings → Environments.