Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Dynamic variables - Adobe Analytics extension

Avatar

Avatar
Validate 1
Level 1
miguelf8022634
Level 1

Likes

3 likes

Total Posts

2 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
View profile

Avatar
Validate 1
Level 1
miguelf8022634
Level 1

Likes

3 likes

Total Posts

2 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
View profile
miguelf8022634
Level 1

01-08-2018

I want to use dynamic variables mapping to send the same value in a prop and a eVar. I have mapped a data element in the eVar and the prop with "D=v1".

My problem is that the prop1="D=v1" is sent even when the eVar1 doesn't take value and is not sent.

Is there a way to avoid that behavior other than coded it instead of use the configuration interface?

Regards,

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Coach
MVP
StewSchilling
MVP

Likes

342 likes

Total Posts

278 posts

Correct Reply

85 solutions
Top badges earned
Coach
Give Back 25
Springboard
Bedrock
Validate 1
View profile

Avatar
Coach
MVP
StewSchilling
MVP

Likes

342 likes

Total Posts

278 posts

Correct Reply

85 solutions
Top badges earned
Coach
Give Back 25
Springboard
Bedrock
Validate 1
View profile
StewSchilling
MVP

02-08-2018

One option to consider is to move the replication of eVar1 to prop1 out of Launch and into processing rules.

You could set up a conditional processing rule that only sets prop1 on hits having eVar1 set.  

Pro: Doing it this way cleans up the beacon.  It saves a few bytes.

Con: The functionality is hidden in processing rules.

The other option is to put the logic in AA doPlugins and test for a value of evar1 before setting prop1=D=v1

Answers (2)

Answers (2)

Avatar

Avatar
Validate 1
Level 1
miguelf8022634
Level 1

Likes

3 likes

Total Posts

2 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
View profile

Avatar
Validate 1
Level 1
miguelf8022634
Level 1

Likes

3 likes

Total Posts

2 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
View profile
miguelf8022634
Level 1

02-08-2018

I will keep the beacon with the dynamic variables since they won't have impact (they will be discarded). I don't want hidden the implementation in the processing rule or switch to code implementation.

I think that Lauch library should be updated to clean this if the copied variable is empty... I'm pretty sure that DTM did.

Thank you for the answers!

Avatar

Avatar
Validate 1000
Community Manager
jantzen_belliston-Adobe
Community Manager

Likes

339 likes

Total Posts

2,331 posts

Correct Reply

819 solutions
Top badges earned
Validate 1000
Springboard
Validate 500
Validate 250
Validate 100
View profile

Avatar
Validate 1000
Community Manager
jantzen_belliston-Adobe
Community Manager

Likes

339 likes

Total Posts

2,331 posts

Correct Reply

819 solutions
Top badges earned
Validate 1000
Springboard
Validate 500
Validate 250
Validate 100
View profile
jantzen_belliston-Adobe
Community Manager

01-08-2018

I'd guess this is happening because of data element storage duration settings. Have a read through this blog post and see if this fixes your issue. If not, can you provide us a URL and steps to replicate the scenario along with an idea of what you'd expect to see in the image requests?

Thanks,
Jantzen