Details of a server call and how to make a report about it

[FerGarAlv]

Hello everyone, I want to know if it's possible to know what specific metrics are taken into consideration to build the server call graphic. I´ve been reading some of yall questions in here and some of you say that the ocurrences metric can give us a close number of server calls but is there any way that I can know specific dimensions that are part of that ocurrences metric. For example, pages with page views, interactions with page interactions, etc. All of this because my team is working on reducing the server calls we currently have and for this we need to know which dimensions we have to look at. (We have a mobile app).

Thanks in advance!

[John_Man]

Hi @FerGarAlv 

Occurrences should be a close match with server calls billing/usage report in most cases, and I think it equals to Page Pages + Page Events (not 100% sure though).

But you also need to check the Bot traffic consumption as well. I've seen a few cases where Bot traffic % is high due to external screen scraping agents, internal SEO spider agents etc.

Data source upload can contribute to server calls as well.

Thanks,

[FerGarAlv]

Thank you John, you gave me a lot of clarity for my report!

[manojs57813206]

server calls aren’t directly exposed as a built-in metric tied to specific dimensions like Pages or Interactions. However:

OCCURRENCES is often used as a proxy to estimate server calls because it counts each time a dimension had a value on a hit (server call).

For mobile apps, every track call (like trackState, trackAction) generates a server call, so looking at dimensions populated on those hits helps identify contributors.

[FerGarAlv]

So the sum of my page views (trackstate) and page interactions (trackAction) should be the same as the ocurrences? or a number close to it?

[manojs57813206]

No , not page view, if you are in AA then it should be occurrence of tracksate and trackaction and if you are in CJA then it will be events 

[John_Man · Accepted solution]

For moible app in AA, Page Views should be the total trackState calls, while Custom Link Instances should be the total trackAction calls which equals to Page Events (as mobile app does not have download/exit/activity map links etc). And total Occurrences = Page Views + Page Events.

But if you are using AEP SDK with Edge Network, Page Events will likely has a bigger number than Custom Link Instances, as Lifecycle calls for Edge Network is not counted as part of Custom Link Instances (but still as part of Page Events).

And if there's Web Views in the mobile app, hvae to take considerations on its server call usage as well.

Thanks