A list of all global properties used across all environments can be found here.
At the core of Snapyr is the individual user, whose actions you can track to provide the optimal experience. The first time any of the SDKs launch, a unique Anonymous ID will be created and saved to the device’s storage. This will tie the user the current device and stay constant. This ID can be reset using the
Reset call via the various SDKs.
Later, if the SDK calls
Identify to send a known User ID, the User ID as well as Anonymous ID will be sent as traits with every message.
Currently, Snapyr does not support publishing communications from a campaign to anonymous users. Once
Identify has been called to assign a user ID, the user will become eligible to receive communication depending on what contact information is available (email, phone number, or device ID).
Every message sent by Snapyr includes the message context, with info about the device, app, etc.
Most fields in the context dictionary are pre-set and collected automatically such as
A list of all the possible fields can be found here.
The Snapyr SDK queues API calls and uploads them in batches. This limits the number of network calls made, and helps save battery on the user’s device and prevent the network from being overloaded.
When you send an event, the SDK saves it to disk. When the queue size reaches the maximum size (20 by default), the library flushes the queue and uploads the events in a single batch. Since the data is saved to desk immediately, it isn’t lost even if the app is killed or the operating system crashes… it will be smartly sent the next time the app starts up.
Snapyr saves up to 1,000 calls on disk, and these never expire.
Having trouble? Contact us at email@example.com