Offline hits

 

Foreword

The AT Internet SDK enables you to store, on the user’s device, any hits that couldn’t be sent due to loss of Internet connection. For this, the SDK uses Windows ApplicationDataContainer API.

Use of this feature is subject to the subscription to an option. This feature may increase the disk space that your application occupies on a user’s device.

 

Setting up the storage mode

You can set up the storage management mode directly within the Tag Composer interface, or via the Tracker’s SetConfig method.

Three modes are available:

  • Required: Hits are only stored when a loss of connection is detected.
  • Always: Hits are never sent. They are directly stored on the device.
  • Never (by default): Hits are never stored. If a loss of connection is detected at the same time as an attempt to send the hit, the hit will be lost.

To edit the hit storage mode, add the following code to the desired area:

Save hits during loss of connection:

Always save hits:

Never save hits:

 

Sending saved hits

At any moment (if an Internet connection is established), you can request that stored hits be sent.

To do this, the Tracker exposes an offline object offering a send method:

This method sends all stored hits in an asynchronous manner, and deletes them if the send was successful. If the send failed, two new attempts will be made during the next hit send. If all attempts fail, the hit will be deleted from storage.

Thanks to this method, you may decide at which moment you want hits to be sent. By setting the storage mode to always, you can simply call the Send method to trigger sending at the desired moment.

 

Recovering hits

 

Listing

You can recover the list of saved hits at any moment. To do this, the get method of the Offline class is available in the Tracker.

This method returns an object list Hit. This object possesses the following properties:

  • url: URL of the hit
  • CreationDate: the date the hit was created
  • RetryCount: number of attempts to send the hit
  • IsOffline: indicates that the hit comes from storage
  • Type: type of hit (e.g. Screen, Touch …)
 

First saved hit

You can recover the first hit saved via the Oldest method of the Offline class:

 

Last saved hit

You can recover the last saved hit via the latest method of the Offline class:

 

Counting

You may obtain the number of hits stored in the database at any moment. To do this, the Offline class exposes a Count method:

 

Deleting hits

You can manually delete stored hits thanks to the following static methods:

  1. Delete: Deletes all stored hits

  2. Delete(Date olderThan): Deletes hits older than the date passed in the parameter

Was this post helpful?
Yes
No
Last update: 15/12/2016