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

POST call and plugin usage

Avatar

Avatar
Applaud 5
Level 1
arpits88575721
Level 1

Likes

4 likes

Total Posts

6 posts

Correct Reply

0 solutions
Top badges earned
Applaud 5
Boost 3
Boost 1
View profile

Avatar
Applaud 5
Level 1
arpits88575721
Level 1

Likes

4 likes

Total Posts

6 posts

Correct Reply

0 solutions
Top badges earned
Applaud 5
Boost 3
Boost 1
View profile
arpits88575721
Level 1

05-04-2021

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? 

Accepted Solutions (0)

Answers (1)

Answers (1)

Avatar

Avatar
Publish 1
MVP
yuhuisg
MVP

Likes

195 likes

Total Posts

592 posts

Correct Reply

117 solutions
Top badges earned
Publish 1
Affirm 100
Springboard
Bedrock
Validate 1
View profile

Avatar
Publish 1
MVP
yuhuisg
MVP

Likes

195 likes

Total Posts

592 posts

Correct Reply

117 solutions
Top badges earned
Publish 1
Affirm 100
Springboard
Bedrock
Validate 1
View profile
yuhuisg
MVP

05-04-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.