adobe / adobe/target-nodejs-sdk-samples
Next server-side example and A4T reporting
- Dominant language
- JavaScript
- Stars
- 19
- Forks
- 42
- PR merge metrics
- No merged PRs in 30d
Description
Hi!
I've took the `next-server-side-rendering-demo` example and tried to implement A4T reporting according to this [doc](https://adobetarget-sdks.gitbook.io/docs/integration-with-experience-cloud/analytics-for-target-a4t-reporting)
I've updated all static files (`AppMeasurement.js`, `at.js`, `VisitorAPI.js`), `target-config.json` and added the following changes to the `helpers/target-server-side.js`

After running the code, I was hoping to see the corresponding A/B test report in Adobe Analytics, but I don't see any reports.
My A/B test has been created with form composer, where I've defined a simple JSON offer (feature flag) like
```
A experience
{
"value": false
}
B experience
{
"value": true
}
```
Have I made something wrong or missed something? Or maybe A4T reporting doesn't work for form composer?
Contributor guide
Research direction
Run the next-server-side-rendering-demo and compare its target-config.json, helpers/target-server-side.js, and static AppMeasurement.js, at.js, and VisitorAPI.js files with the linked A4T documentation. Done means identifying the reporting setup issue and confirming that the form-composer test produces an Adobe Analytics A/B report.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, next.js
- Domain
- analytics, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100