Overview

The Custom Connection Builder lets you send custom POST requests to third-party services whenever selected in-app events occur. With it, you can recreate Apphud’s built-in integrations or design your own payloads for any supported event.

📘

Note

Connection Builder is available on Expert and Enterprise plans.

How to Add a Custom Connection

Step 1 – Create a Connection

In Apphud, navigate to Connections > Integrations, find Connection Builder at the top of the list, and click Add Connection.

As with other integrations, each custom connection is created for a specific data source platform. During setup, you’ll be prompted to select a Source:
iOS, Android, Flows, iOS (Web-to-App), or Android (Web-to-App).

Step 2 – Configure Name and URL

After selecting a source, you’ll be taken to the connection settings page. Enter a Name and URL for the connection. Events will be sent to the specified URL via POST requests.

Step 3 – Add Headers

Define request headers by specifying Header Name and Value.
To include multiple headers, click Add Header and fill in the additional fields.

Step 4 – Set Up Request Body

In the Body Configuration section, compose your JSON payload using supported Liquid macros (see macro reference below).

Step 5 – Select Events

Choose the events you'd like to send through the connection. You can also rename these events using custom labels.

Step 6 – Apply Event Filters (Optional)

Click + Where to add filters that determine when events should be sent.
If an event is enabled but doesn't match the filter conditions, it will appear as Skipped in the event logs with the reason “Event did not match filters.”

📘

Important Note

No need to create a filter "Environment = Production". By default Apphud skips sandbox events so this filter is redundant.

Add powerful event filters to ensure only specific data is sent to a destination. For example:

• Revenue > $29
• Product duration = Weekly
• Trial started = true

These filters can be applied per connection for precise control.

Below is a list of available filters grouped by category:

General

Environment: Sandbox, Production
App Version: supports =, >, < (e.g., > 1.20.1)

User

Country by IP
Store Country Has Advertising ID (IDFA)

Product

Type: Auto-renewable, Non-renewing
Duration: Weekly, Monthly, Annually Family Shared Product ID Revenue (USD): supports comparison (<, >, =)

Attribution

Ad Network
Channel Campaign Name

User Properties

Keys with exact values

❗️

Note

Filters do not apply to non-receipt events like user_created, paywall_shown, except for Store Country and Environment.

Step 7

Save the Connection.
The connection can be Enabled right away, however, we recommend testing a connection before enabling it.

Liquid Macros List

App

Event

User

User LTV Predictions (Coming Soon)

Attribution

Click Event

Special Functions

You can also check the "Remove null values" setting under the "Request body" field to ensure such parameters won't be sent.

Conditional Logic in JSON

With Connection Builder, you can embed conditional logic directly in your request body using Liquid if/else tags.

Example: Send a has_idfa flag based on the availability of IDFA:

"has_idfa": {% if user.idfa %} 1 {% else %} 0 {% endif %}

You can also apply conditions to multi-line blocks or entire JSON payloads:

{% if user.country == "US" %}
{ "region": "NA" }
{% else %}
{ "region": "Other" }
{% endif %}

Value Modifiers

Transform values on the fly using built-in modifiers. Examples include arithmetic operations, string formatting, and date formatting.

Arithmetic:

"revenue_x2": {{ event.receipt.price | times: 2 }}

String case formatting:

"product": "{{ event.receipt.product_id | upcase }}"

Date formatting:
For more on date formatting, check this Liquid guide.

"event_time": "{{ event.created_at | date: "%Y-%m-%d %H:%M:%S.000" }}"

UNIX timestamp:

"timestamp": "{{ event.created_at | date: "%s" }}"

For more on date formatting, check this Liquid guide.

Preview a Payload

While setting up your integration, you can preview the generated payload at any time. Click the eye 👁️ icon in the JSON editor toolbar, then enter an Event ID or Transaction ID to view the payload.

• Event ID. It's the Apphud's internal event ID which can be found in the Events tab. Include ID column in the table. If the ID column doesn't exist, try to clear browser cache first.
• Transaction ID. Store's Transaction ID.

Note: This preview does not trigger an actual HTTP request.

Test a Connection

To simulate a real connection, enter a valid Transaction ID from your app. Apphud will fetch the corresponding event, receipt, and user data, then send a test POST request using your configuration.

All configured filters will be applied during the test.

Note: If you're using a sandbox transaction, be sure to include the filter Environment = Sandbox. Otherwise, the event will be skipped.

• If the transaction is invalid or belongs to a different app, an error message will appear: "Transaction was not found."
• If the test is successful, a popup will display the response payload.
  ⚠️ Keep in mind: the test result is shown only once and cannot be accessed again after closing the popup.