AdobeDocs / AdobeDocs/experience-platform.en

Using Adobe Target with the Platform Web SDK - how to pass custom context parameters

Open
#15 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
11
Forks
148
PR merge metrics
No merged PRs in 30d

Description

Hey team.
It is clear how to pass profile and entities parameters:

```
alloy("sendEvent", {
renderDecisions: true,
data: {
__adobe: {
target: {
"profile.gender": "female",
"profile.age": 30
}
}
}
});
```
and
```
alloy("sendEvent", {
renderDecisions: true,
data: {
__adobe: {
target: {
"entity.id": "123",
"entity.genre": "Drama"
}
}
}
});
```

Still it is not clear how to pass custom context parameters (mbox parameters), eg pageName.
Could you please include such details?

Thanks,
Alberto

Issue in ./help/edge/personalization/adobe-target/target-overview.md

Contributor guide

Open the contributing guide

Research direction

Read ./help/edge/personalization/adobe-target/target-overview.md and review its existing guidance for profile and entity parameters. Add documentation explaining how to pass custom context parameters such as pageName, so readers can identify the supported request format.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
documentation
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.