Estimated response times in In-App Messages – EMMA Support

EMMA guarantees minimum response times in the resolution of content requests for In-App formats. These guaranteed response times are subject to the implementation of the SDK in your App and the user's connection. To do this, review good practices in the implementation of the SDK.

Average response times for In-App formats

	Minimum time (1)	Average time (2)	Maximum time (3)
AdBall	0,1 seg.	0,5 seg.	0,8 seg.
Banner	0,2 seg.	0,9 seg.	1,0 seg.
StartView	0,2 seg.	0,7 seg.	1,5 seg.
Native Ad	0,2 seg.	1,0 seg.	1,2 seg.

(1) Minimum average time for 50% of requests received by EMMA.
(2) Average time for 95% of the requests received by EMMA.
(3) Maximum response time for 99% of requests received by

Average response times for event tracking

	Minimum time (1)	Average time (2)	Maxium time (3)
Track Event	0,5 seg.	2,3 seg.	4,5 seg.
Track Event with Rules	0,5 seg.	1,8 seg.	1,9 seg.

(1) Minimum average time for 50% of requests received by EMMA.
(2) Average time for 95% of the requests received by EMMA.
(3) Maximum response time for 99% of requests received by

Data loading considerations in Native Ads

We must also bear in mind that in the formats that you need to download additional content such as images, you should also take into account that loading time, since in environments where we have a volatile connection such as 3G or 4G environments and depending on the coverage , we may experience longer download times.

Here is an example table for load times:

Image size	3G	4G	WiFi
100 Kb	0,9 seg.	0,03 seg.	0,01 seg.
500 Kb	4,7 seg.	0,18 seg.	0,07 seg.
1 Mb	9,5 seg.	0,36 seg.	0,14 seg.
2 Mb	19 seg.	0,72 seg.	0,28 seg.

Succes ratio

	Success Ratio
AdBall	99%
Banner	99%
StartView	99%
Native Ad	99%
Track Event	99%
Track Event with Rule	99%

Performance reports

Below are indicative performance reports on the correct implementation of the EMMA SDK in Apps.

AdBall

Banner

StartView

Native Ad

Track Event

Track Event with Rule