POST call and plugin usage | Community
Skip to main content
arpits88575721
arpits88575721
Level 2
April 5, 2021
Solved

POST call and plugin usage

  • April 5, 2021
  • 1 reply
  • 719 views

For one of my tracking scenario, Adobe is automatically generating a POST call potentially because the request size is greater than 2047 bytes, for that specific post-call we are seeing that one of the variables is not receiving a standard camel case value that we enforce through the plugin within app measurement library. What could be the reason for the same? 

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 yuhuisg

There are 2 possibilities that I can think of:

  1. For other requests, the variable is displaying a similar problem, i.e. not being forced to the correct casing. But somehow this was never noticed till now.
  2. For this particular request, it sounds like there's some extra processing being done, since more variables are being tracked. Could it be that somewhere in that extra code, this particular variable has been "reset" somehow such that your plugin is not being called?

I think #2 is the more likely scenario.

1 reply

yuhuisg
Community Advisor
yuhuisgCommunity AdvisorAccepted solution
Community Advisor
April 6, 2021

There are 2 possibilities that I can think of:

  1. For other requests, the variable is displaying a similar problem, i.e. not being forced to the correct casing. But somehow this was never noticed till now.
  2. For this particular request, it sounds like there's some extra processing being done, since more variables are being tracked. Could it be that somewhere in that extra code, this particular variable has been "reset" somehow such that your plugin is not being called?

I think #2 is the more likely scenario.

Terms & ConditionsAccessibility statement

Loading footer...