Get Started with Glispa Connect

Overview

Examples

Android

Overview

- Native Ads

List/Feed

Custom

- Standard IAB Formats

Banner

Interstitial

Video

- Others

GDPR

Troubleshooting

Admob Android Adapter

Mopub Android Adapter

DFP Android Adapter

iOS

Overview

- Native Ads

List/Feed

Custom

- Standard IAB Formats

Banner

Interstitial

Video

- Others

GDPR

Troubleshooting

- Adapters

Admob iOS Adapter

Mopub iOS Adapter

DFP iOS Adapter

API Documentation

Reporting API

Help

GDPR FAQ

General

Earnings

Payments and Accounting

Integration

Reporting

Legal and Privacy

Updates

SDK Deprecation Schedule

SDK Change Log

Android Change Log

iOS Change Log

Troubleshooting

Updated 6 months ago by Chris

Overview

Debug & Test mode

Glispa Connect (formerly Avocarrot) SDK for iOS provides a debug mode that will print useful information about what data is being sent to Glispa Connect Server in your logs.

AvocarrotSDK.testMode = YES;
          AvocarrotSDK.logEnabled = YES;
AvocarrotSDK.testMode = true;
          AvocarrotSDK.logEnabled = true;

Common issues

Why are my in-feed ads loading slowly?

If you are using in-feed native ads, you can leverage our ad caching to avoid ad latency issues when your users are scrolling through your app feed.

Glispa Connect SDK has a cache system for in-feed ads with specific sizes (deviates according to platforms). When you initialise in-feed ads, they will start loading and our SDK caches the in-feed ads when loading has completed. After this, they can be inserted into your feed without any delays. The ad must be shown to the user before it can load a new ad into the cache system.

See “How do I reduce ad latency?” more information on ad latency.

 

Why are my ads taking a while to load?

An ad can take some time to load due to the ad latency. This is the total time it takes for a server to receive and process a request. If our SDK integration was installed correctly, then the ad should serve without any lag time. But remember, ad latency can still depend on various external factors. The more layers (services or operations) you add to the integration, the greater the possibility for latency to occur.

Some external factors that affect latency include:

  • Ad networks and their 3rd party integrations
  • Countries
  • Platforms
  • Internet connection
  • Device version
  • Ad units
  • Configuration of the app

For further information on how to reduce latency, please refer to our recommendations here.

 

How do I reduce ad latency?

Our recommendations to minimize latency would be the following:

1. Consider implementing pre-loaded ads since it’s considered best practice and helps reduce overall ad latency. As a publisher, you have full control to separate the events to “showing and loading”. We recommend you to implement this method.

See “Why are my in-feed ads loading slowly?” for instruction on how to pre-load In-feed ads.

 

I’ve integrated the SDK but don’t see any impressions. What do I do?

There are two possible reasons you might not be seeing any impressions: Integration or Configuration.

1: Integration
Ideally, you can use the Demo app and enter your Ad Unit ID. This can be found in your dashboard under each ad placement.

Now, insert this Ad Unit ID in the Demo App. If the ad is served in the demo app, but not within YOUR app, then there is an integration issue.
If this is the case, please reach out to us and we will happily assist you!

  • You will be required to provide the following information:
  • – The Glispa Connect SDK integration code
  • – Set the app on the debug mode
  • – Logs for ad request

2: Configuration
If you entered the Ad Unit ID in the demo app and still did not see any ads served, then there is a configuration mistake. To resolve the issue, you will have to re-check the configuration and make sure all the ad placement IDs are correct.

For any additional information, please refer to our guidelines HERE:
Android: https://github.com/Avocarrot/android-sdk
iOS: https://github.com/Avocarrot/ios-sdk


Was this article useful?