Is there any way to avoid injecting UEM into Gomez synthetic transactions
Customer does not want to measure Gomez synthetic transactions with UEM, as they don't want to use up their UEM quota on synthetics. Any way to avoid this?
Hi Joe,
Currently we cannot restrict the injection for the synthetic agents. What you can try (not sure it works) is use the injection restriction by browser and make a rule set "include the following browsers" and add for all the available browsers in the drop down field a rule.
This might stop the injection for synthetic but will definitely also restrict capturing for some rare other browsers as well.
Let me know if it works? I also will place this RFE at the team.
Cheers Klaus
Was there a workaround/RFE put in place for this? We are in the same situation (around 20% of visits to a specific application are synth/Gomez, and are skewing our conversion rate goals). We cannot make a rule set "include the following browsers" and add for all the available browsers in the drop down field, as there are other "real" user agents not available in the drop down.
I believe dynaTrace V 6 will no longer count Gomez synthetic requests as part of the visit count
The gomez visits are no longer counted as licence visits but still in the visit measure context.
Welcome the
Dynatrace Community Forums
Check out the Forum User Guide and Forum Guidelines to learn how to get started.Community Member of the Month
August 2017
Announcing Dynatrace's Community Member of the Month for August 2017, Rick B.! Click here to read more! 