Automatically map eVars, props and events without processing rules

Open
  • Is something wrong?
#668 6 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
api, web-dev

Research direction

Start with the WebSDK sample payload in this issue and compare the existing direct mappings for name and server with previousPageName and pageDomain. Done means eVars, props, and events can be mapped directly as requested, without requiring processing rules, with the behavior verified for the illustrated payload.

Written by the indexing model from the issue text.

Description

enhancement Need response
Expected Behaviour

Directly map eVars, props and events to Analytics in the same way name, server and siteSection are directly mapped without a processing rule.

Actual Behaviour

Some webPageDetails are mapped directly others must be added with a process rule which adds an extra maintenance level.

Reproduce Scenario (including but not limited to)
Steps to Reproduce
Platform and Version

WebSDK

Sample Code that illustrates the problem
"web" :{
		"webPageDetails" : {
		 "name" : "MySite:Home",            // Automatically mapped
		 "server": "www.mydomain.nl",    // Automatically mapped

          	 	 "previousPageName": "MySite:Home",   // Mapped manual in processing rules to eVars/props
          	 	 "pageDomain": "www.mydomain.nl",      // Mapped manual in processing rules to eVars/props
desirable situation
          	 	 "eVar":[
					"1":"ValueForEVar1",
					"3":"ValueForEVar3" 
					etc ... 
					],
          	 	 "prop":[
					"1":"ValueForProp1",
					"2":"ValueForProp2" 
					etc ... 
					],
          	 	 "events" : ... same thing...
Logs taken while reproducing problem
Dominant language
JavaScript
Stars
104
Forks
63
Avg merge
1d 18h
Merged PRs (30d)
21

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from adobe/alloy

All issues in adobe/alloy

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.