At a Glance:
This article will guide you through the steps to set up Webhook Data Support on the Apptrove panel.
What is Webhook Support?
Webhook Support allows Apptrove to automatically send install and in-app event data to your external systems in real time. This helps automate data sharing with analytics platforms, CRMs, data warehouses, and custom applications without the need for manual exports.
What Data Can Be Sent?
You can configure webhooks to send:
Installs
In-App Events
Fraudulent Installs
Fraudulent Events
For each webhook type, you can choose which parameters should be included in the payload.
Request Parameters
Apptrove supports custom webhook payloads using macros. These macros are automatically replaced with actual attribution and event data when the webhook is triggered.
Commonly used parameters include:
Param | Description |
{campaign} | Campaign name |
{camp_id} | Campaign ID |
{partner_name} | Media source/partner name |
{site_id} | Publisher or site ID |
{platform} | Device platform |
{geo} | Country |
{gaid} | Google Advertising ID |
{idfa} | Apple Device identifier |
{trackier_install_id} | Install identifier |
{trackier_click_id} | Click identifier |
{event_name} | Event name |
{revenue} | Event revenue |
{currency} | Revenue currency |
You can include any parameter available in Apptrove logs, allowing you to send detailed attribution, campaign, device, and event information to your external systems.
Where to Find This Option?
Navigate to the bottom bar on your Apptrove dashboard.
Click on the three dots (...).
Select “Webhook Data Support” from the list.
How to Add a Webhook
Method:
HTTP Request Methods
GET
Data is sent as URL parameters.
Best suited for:
Simple integrations
Small payloads
Basic data transfers
POST
Data is sent in the request body, typically in JSON format.
Best suited for:
Install and event data
Large payloads
Advanced integrations
We recommend using POST for most webhook integrations as it supports larger and more structured payloads.
Name and Type: Choose a name for the webhook along with the type of data that you want to send. It could be either an install or an in-app event. You can even filter the data for events if you don't want to see data for all events.
Description: In case you want to add any description for this webhook, you can add that as part of this section.
URL Details: Enter the webhook URL. You would need to add macros if you use the GET method to receive the data that you want. A whole list of macros has been uploaded to the platform, and you can copy-paste it as part of your URL. Values would automatically replace the macros once the URL is hit.
Body: This is relevant for the POST method. You can send the data inside the body with the macros of your wish
Add Filters
Filters allow you to control which data triggers the webhook. Instead of receiving all installs or events, you can limit webhook delivery to specific campaigns, partners, agencies, channels, or geographic regions.
Filter | Description |
Countries | Send webhook data only for users from selected countries. |
Campaigns | Trigger webhooks only for specific campaigns. |
Channels | Restrict webhook delivery to selected marketing channels. |
Agencies | Send data only for campaigns managed by selected agencies. |
Partners | Filter webhook events based on specific media sources or partners. |
Example: If you select India under Countries and Facebook under Partners, the webhook will only be triggered for installs or events originating from Facebook campaigns in India.
Manage Webhooks
Once a webhook has been created, it is displayed on the Webhooks page along with its configuration details.
For each webhook, you can view:
Title – Name of the webhook.
Type – The event type associated with the webhook (Install, In-App Event, Fraudulent Install, or Fraudulent Event).
Webhook URL – The destination endpoint where data is sent.
Status – Indicates whether the webhook is currently active.
Created – Date and time when the webhook was created.
You can manage existing webhooks directly from this page by:
Enabling or disabling a webhook using the Status toggle.
Editing an existing webhook to update its configuration.
Deleting a webhook that is no longer required.
Webhook Logs
The Webhook Logs page provides detailed logs for every webhook request sent by Apptrove. These logs help you verify webhook deliveries and troubleshoot issues with external endpoints.
For each webhook request, you can view:
Request status
Webhook URL
Request payload
Response received from the destination server
Response latency
Install ID
Event Log ID (for in-app events)
Error (if any)
Created date
This information makes it easier to confirm whether webhook requests were successfully delivered or to identify errors returned by your endpoint. If a webhook is not behaving as expected, review the response status and response body in the Webhook Logs to identify any issues returned by your endpoint.
Filter Webhook Logs
To quickly locate specific requests, you can filter webhook logs by:
Webhook Type
Partner ID
Install ID
Event ID
These filters help narrow down webhook requests for troubleshooting and validation.
Points to Note
Install and event webhooks can be configured separately.
Your endpoint must be able to receive HTTP requests.
Test webhook delivery before enabling it in production.
Only the parameters added to the payload template will be sent in the webhook request.
Broaden Your Knowledge:
We are delighted to have assembled a world-class team of experienced professionals who are ready to take care of your queries and answer any questions you may have.
Feel free to reach out to us at any time by emailing us at support@apptrove.com or by using the in-platform chat feature. We'd love to hear from you!
