Dynamic variables - Adobe Analytics extension | Community
Skip to main content
miguelf8022634
miguelf8022634
New Participant
August 1, 2018
Solved

Dynamic variables - Adobe Analytics extension

  • August 1, 2018
  • 3 replies
  • 2915 views

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,

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by Stewart_Schilling

    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

    3 replies

    miguelf8022634
    miguelf8022634Author
    New Participant
    August 3, 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!

    Stewart_Schilling
    Stewart_SchillingAccepted solution
    New Participant
    August 2, 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

      jantzen_b
      jantzen_b
      Employee
      August 1, 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

      Terms & ConditionsAccessibility statement

      Loading footer...