AdobeDocs / AdobeDocs/analytics.en

Conversion Variable Syntax = “Original Value (First) vs “Most Recent (Last)” allocation binding

Open Beginner friendly
#315 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
CSS
Stars
19
Forks
108
PR merge metrics
No merged PRs in 30d

Description

Issue in ./help/admin/tools/manage-rs/edit-settings/conversion-var-admin/merchandising-evars.md

There is confusion in the statement "Any attempt to rebind these products after this original binding takes place are ignored when the Allocation (binding) setting is set equal to “Original Value (First)”. This is because earlier in the page it has been established that even if we choose “Original Value (First)” for a Conversion Variable Syntax, it will always remain “Most Recent (Last)”.

See paragraph below that is causing the confusion:
"
**Merchandising eVar allocation (binding) setting**
As mentioned before, all merchandising eVars with Conversion Variable Syntax have only “Most Recent (Last)” allocation. Thus, the Allocation setting for merchandising eVars does not determine what values are inserted into the post_evar column as a visitor continues to use the site. Rather, this setting determines which eVar value binds to a product and how such products allocate their success events back to the eVar values they are bound to."

Contributor guide

Open the contributing guide

Research direction

Open ./help/admin/tools/manage-rs/edit-settings/conversion-var-admin/merchandising-evars.md and read the surrounding sections on Conversion Variable Syntax and merchandising eVar allocation. Revise the quoted paragraph so the difference between the syntax’s value behavior and the allocation binding setting is unambiguous. Done means the page no longer presents “Original Value (First)” and “Most Recent (Last)” as contradictory settings.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
74/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.