Website: https://cerestag.com/
Integration Requires Assistance
This integration requires assistance from our support team for setup and configuration. Please contact our support team at support@earthranger.com and we’ll guide you through the process to ensure everything is set up correctly.
We are actively working to make this integration self-service in the future. Stay tuned for updates!
Prerequisites
Gundi
User has an account in the legacy Gundi portal (v1).
Link: https://cdip-prod01.pamdas.org/, ask user to click Register and to notify you when it has been done.
User has been added to a Gundi Organization.
Data Source
Ceres Wild account.
Data Delivery
Event Type “ceres_alert” has been created in EarthRanger.
An auth token has been created in EarthRanger for this integration. The EarthRanger user owning the token has been granted permissions to the Event Category hosting the “ceres_alert” event type.
Configuration
Notes for Support (click to expand)
1. Create an Outbound Integration
2. Create an Inbound Integration
Go to Gundi v1.
Go to the Inbound Integrations and select Add Integration.
Follow the steps below to configure the integration.
Name: Enter a suitable name (e.g., "Ceres Wild - AccountName")
Owner: Select the integration's owner
Type: Ceres Wild
Provider Key: Leave empty. Gundi will automatically give it a name.
Default Device Group: Leave empty. Gundi will automatically create a default group.
Endpoint: Leave empty
Token: Leave empty
Login/Password: Leave empty
Click Save
3. Configure the Default Device Group with the Outbound Configuration created for this connection.
Next Steps
After logging in to the Ceres Portal, the user should select “EarthRanger” as their software. The portal will then prompt them to sign in to the Gundi Portal.
Once logged in, they will be redirected back to the Ceres Portal, where they will be asked to choose a connection. In most cases, only one integration will be available, which they should select.
Characteristics
- This integration will trigger an event or alert whenever the collar detects either no activity or unusually high activity.
Additional Resources
Data Delivery
The time it takes for data to appear in your destination system depends on several factors, such as latency introduced by the source, network conditions, and intermediary systems. While these factors may vary, Gundi typically checks for available data at scheduled intervals (approximately every 10 minutes).
If data is not available in your system after this interval, please check the source of the data for its availability. If the issue persists, contact our Support team for assistance.
Tags: Animal Tracking, Movement Data, Push Integration, Data Provider, Gundi v1
Last Update: Aug 25, 2025