General

Q: How often is my data updated?

A: The data is available in the event browser QA tool within about 5 minutes of being sent to the system, the metrics that drive the Engage campaign segmentation are updated within 1 minute of the event happening. The dashboards and analysis tools are updated every 1-2 hours.

Q: Do you support HTTPS for event collection and engage?

A: Yes, the collect and engage URLs support HTTPS as well as HTTP.

Integration

Q: My game is multi-platform, should I set up different environments for each platform or have one singular environment?

A: The system lets you define the platform as a parameter in the event, so by sending this you can use a single environment. This is exposed through all the tools including a filter on the dashboard. The alternative is to use different environments, both options work but our recommendation is to use a single environment and the platform parameter.

 

Q: How can I ensure accuracy around revenue tracking?

A: The system supports revenue validation using the transaction receipt from the IAP to verify that the revenue is valid.

To set this up please see the section transaction validation in our SDK documentation.

It works really nicely as you will see only validated revenue in your dashboards, but you can also drill in to the validation data in Data Mining to get a feel for the scale of false purchases. You could even use A/B Testing or Targeting to alter the game behaviour for those users.

 

Q: What are the pros and cons of implementing an REST API vs an SDK?

A: The data is sent to the system through a REST interface. The SDK’s are wrappers for the REST interface which provide helper methods to make creating the JSON simpler and also provide a local storage for mobile devices where connectivity is an issue. There is nothing to stop you using the REST API on any device including mobile and some developers have done this as they are looking for total control of the data flow. The SDK’s provide easy implementation of some features such as image messaging and push notifications, also for SmartAds the SDK’s are essential. The REST API will always provide the low level support, the SDKs provide a higher level implementation which should make integration easier.

 

Q: My game has launched and now I see a lot of invalid events in the event browser with the reasons “Duplicate event” and “Event timestamp outside valid boundaries”.

A: Duplicate events occur when the game has not received an OK on sending the events but it has already managed to send the events. It will then retry and the same event will be received twice by collect. Our SDK’s as of version 4.1 will send a unique ID for each event, once we see the same ID twice we will consider the second one invalid. Usually these errors can be ignored and they can therefore also be filtered out in the event browser. The event timestamp outside of valid boundaries error will occur when the eventTimestamp is set by the device and the timestamp is either more than a month in the past or more than 2 days in the future.

 

Q: I want to send some events from a server or a 3rd party service outside of the player session. I won’t have access to a player sessionID and I don’t want to generate a new one as it will incorrectly inflate my player’s session count.

A: These are called GHOST events, they record valuable player information but are sent outside the player session. These are likely to be attribution events or transaction events that have come from a 3rd party payment provider. In these scenarios you can safely omit the sessionID parameter and value on any events that you wish to exclude from session counting and session length calculations.
NB : If you have game events that were created before Jul 2016 you will need to contact support for assistance if you wish to change any sessionID parameters to Optional.

Dashboards

Q: The retention numbers look high, the game has been running for a number of months before implementing the deltaDNA analytics SDK.

A: New users are defined as the first time deltaDNA sees the user and not the newPlayer event. The reason for this is that not all games send a newPlayer event accurately or at all so relying on this event would make these charts unusable. The effect of this is that games that have an existing user base will show a higher initial retention rate as existing players will be counted as new players in these charts. This will settle out over a couple of week.

Q: What is the difference between the All Player Retention and the New Player Retention.

A: The All Player Retention looks at the number of active users on a day and shows you what percentage of these players come back N days after this. The New Player Retention considers only players who have installed on the date and shows the percentage of players that come back on day N after installing. The New Player Retention usually shows the most drastic changes over time, the All Player Retention can be used to focus on the behavior of returning players.

 

Q: Can I view the different currencies coming in from my transactions?

A: The dashboard will convert the currencies to a single currency of your choice which is defined at set up. This is so you can get an easy to see representation of the revenue being generated. The original currency is stored in the event and using the data mining tool you can inspect and query the individual currencies.

A/B Testing & Targeting

Q: How long do I have to wait until A/B Tests and Targeting campaigns that I have set-up go live.

A: It can take up to 5 minutes for A/B Tests and Targeting to go live.

 

Q: How frequently are user segments updated?

A: There are three types of Segment that you can create.

  1. Visualisation based segments will go live within 5 minute of you setting them up and are continually refreshed as new events that influence them are processed, this is typically within 4-5 seconds of an event arriving.
  2. Manual segments will go live within 5 minute of you setting them up and are continually refreshed as new events that influence them are processed, this is typically within 4-5 seconds of an event arriving.
  3. Target Lists based segments are processed once every 24 hours in the early hours of the morning (UTC) or upon saving. This is because they are not solely based on live events updating a player’s state, like the two segementation types above. Target lists can be based on queries that look deeper in to the data and therefore target in-activity or combinations of events. e.g. Target Whales who haven’t played in last 30 days.

SmartAds

Q: What types of ads does SmartAds support?

A: SmartAds supports both interstitial and rewarded video ads.

 

Q: Which ad networks does SmartAds use?

A: SmartAds supports two types of Ad Networks: Direct and Exchange. Our direct ad networks include Admob, Vungle, Amazon, Unity Ads, Ad Colony, Flurry, Chartboost, Mopub, Inmobi & Mobfox.  You can find a full list of the ad networks that we work with here.

 

Q: Can we choose which ad networks we work with?

A: Yes, you can choose which ad networks to include in your game when you compile and install the SDK.  You can find a full list of the ad networks that we work with here.

 

Q: Are there any options to change the mediation waterfall and use one network before the other?

A: We manage the waterfall to ensure that you get the best revenue available for your ads. We can work with you to set certain networks to always be at the ‘top’ of the waterfall and will therefore always show an ad first (if an ad is available). (only available on Enterprise)

 

Q: Can we create our own internal cross-promotion ads to show within our games?

A: Yes, we can set up house ads for you (internal cross promotion ads). We can also control where in the waterfall the house ads will sit. (only available on Enterprise)

 

Q: Do you blacklist certain ads by default?

A: Yes, we automatically blacklist gambling and adult entertainment ads.

 

Q: Can we restrict certain ads from appearing if they are over a certain content rating?

A: Yes, we can restrict certain ads so that they are child-friendly or age appropriate for your app. (only on Enterprise)

 

Q: What’s the difference between OnDemand SmartAds and Enterprise SmartAds?

A: With OnDemand you will be using deltaDNA’s default ad networks and waterfall.  This provides maximum efficiency with a complete managed ad solution.  The Enterprise version of SmartAds provides increased control on the ads that are displayed, allowing you to define blacklists of ads that you don’t want to be shown in your game. With Enterprise you have flexibility on which ad networks you can work with, and can re-order the waterfall if you wish.  If you wish to show house ads, you will also need to use Enterprise.

 

Q: How do I know which option is most suitable for my game?

A:  If you have a minimum of 1M impressions per game per month, and would like the ability to customise your ad networks, then Enterprise may be the best option for you.  If you game generates less than 1M impressions per month then OnDemand is the best option for you.  If you don’t know how many impressions your app will generate, then we recommend that you start with On Demand ads until your app reaches a bigger audience.
Q: What are the minimum requirements for my game in order to integrate SmartAds?

A:  You must use deltaDNA’s core analytics platform and SDK for Smart Ads to work properly.  Our SDKs are available in IOS, Android and Unity.  Unity requires Unity 5. iOS is iOS 7 or higher, and Android is API15.

 

Q: Where can I get access to the SmartAds SDKs?

A: You can access the SmartAds SDKs from Github

 

Q: How does the payment of SmartAds work?

A: In terms of payment, we are registered with all the ad networks so deltaDNA will manage the payments on your behalf. We will make payment to you within 30 days of the month end in which we receive payment from the ad networks.

 

Q: Where can I find further information about SmartAds?

A: You can find further information about SmartAds on the docs site. You can also download our SmartAds brochure from our website.