Support Device Type and Browser Lookups on the edge
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- backend
Research direction
Review the existing Analytics, Target, and Audience Manager data paths to understand where device type and browser data are currently handled. Then trace how data is sent to the edge and represented in XDM. Done means the lookups occur before delivery to all three solutions and the resulting data is consistently available in XDM.
Written by the indexing model from the issue text.
Description
Currently these are done by Analytics, Target and Audience Manager separately so the data isn't part of the XDM. This would do the lookups before the data goes to AA, AT, and AAM to enable a view that is similar between solutions and make the data available in the XDM.
- Dominant language
- JavaScript
- Stars
- 104
- Forks
- 63
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 21
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from adobe/alloy
-
__VERSION__ within dist build is not replaced, causes missing version in XDM implementation detailsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
adobe/alloy#1323 · 3 comments ·
Maintainers usually reply within 1 day
-
3.0.0Openbranch:main release
Difficulty 5/5 Over a week Newbie friendliness 15/100
adobe/alloy#1170 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 32/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
adobe/alloy#1021 · 5 comments ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
ai-driven-fuzzing bug Cosmetic
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
linagora/cozy-client#1831 ·
Maintainers usually reply within 1 day
-
ai-driven-fuzzing bug Major
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day
-
[ordering-review] workshop order graph: 1 confirmed ordering problem, 3 cycles are false positivesOpen
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
githubnext/gh-aw-workshop#5331 ·
Maintainers usually reply within 1 day
-
Remove: 21 SexturyOpenchannels:remove check:passed
Difficulty 1/5 Under an hour Newbie friendliness 65/100
Maintainers usually reply within 4 days