Connection Builder

The Connection Builder lets you compose your own integration from scratch — send custom POST requests with fully templated JSON bodies to any third-party service whenever selected in-app events occur. Use it to recreate Apphud's built-in integrations, send events to internal systems, or build payloads tailored to APIs not covered by the standard integration catalog.

📘

Note

Connection Builder is available on Expert and Enterprise plans.

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.

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 (on the All or Custom tabs), and click Add Connection.

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

Step 2 - Configure URL and Request method

After selecting a source, you'll be taken to the connection settings page. Enter a Name and URL for the connection.

Choose a Request method from the dropdown.
As a rule, clients prefer that events are 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. Note that the button is shown only if you added at least one Header.

Step 4 - Set up request body

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

Remove null values settings is set to ON by default. Fields with null values will be excluded from the payload.

Step 5 - Apply Event Filters (optional)

The standard for integrations Environment configuration block will help you to define which data will be sent to the destination, so, you can use these settings as the initial high-level filter. By default only production events are sent.

📘

Important Note

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

Then, go to Filters tab. Click + Add filter to add conditions that determine which events should be sent.
If an event is enabled but doesn't match the filter conditions, it appears as Skipped in the event logs with the reason "Event did not match filters."

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.

Available filters grouped by category:

❗️

Note

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

Step 6 - Select events

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

Step 7 - Save and test

Save the connection. The connection can be Enabled right away — however, we recommend testing it first.

Liquid Macros

Use these macros inside your JSON body. Each renders the corresponding value at send time.

App

Event

User

User LTV Predictions (Coming Soon)

Attribution

Click Event

Special Functions

Check the Remove null values setting under the Request body field to ensure null parameters are not 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, string case formatting, and date formatting.

Arithmetic:

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

String case formatting:

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

Date formatting:

"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, see the Liquid date format guide.

Preview a Payload

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

• Event ID — Apphud's internal event ID, which can be found in the Events tab. Enable the ID column in the table. If the ID column doesn't exist, try clearing browser cache first.
• Transaction ID — store's Transaction ID.

📘

Note

This preview does not trigger an actual HTTP request.

Test a Connection

Once a new integration configuration is saved, Test connection button will be enabled.

To simulate a real connection, click on it and 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 are applied during the test.

📘

Sandbox transactions

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.

⚠️

Important Note

The test result is shown only once and cannot be accessed again after closing the popup.