| Will a web banner appear immediately to the user after it is set? |
The SDK is cached in the user’s browser with an expiration limit—this might be up to 30 minutes, depending on the setting for a particular instance. This means that if the user has just opened your website and received the SDK, they will not receive any changes to the SDK for the duration of the expiration interval. Therefore, while some users will see the new banner immediately, it might take some time for all users to be able to see the new banner. |
| What will happen if multiple web banners have the same priority set and same conditions? |
If multiple banners have their conditions fulfilled and have the same priority, the banner which has been shown to this user the least number of times in the past 24 hours will be selected. |
| What will happen if I have no conditions set for the web banner? |
If no conditions are set, the banner will always be considered for display and will only be limited by frequency cap and priority settings. |
| Who is considered "user" in web banners settings? |
A user is defined by "cookie" in the browser. Each "user" is assigned a "cookie" hence is identified as a separate "user". During identity stitching various cookies can be stitched together based on the identity stitching algorithm. |
| What is the definition of "session" in web banner frequency? |
It is the activity of the user for the 30 minutes interval of time. |
| If a web banner is re-named which name is used in reporting or in attributes? |
Usually it is the latest name that is used in attributes or reporting, but each individual name can be tracked as well (to discuss details contact the Meiro team). |
