Managing Data-In Connections

Once you have started sending data to Triple Whale via the Data-In API, you can manage your Data-In connections from the Data In section on the Integrations page.

Viewing Connected Accounts

To view and manage your connected Data-In API accounts, click the Manage button. A popup will appear showing a list of your accounts.

Each account name follows the structure: <endpoint>:<platform>:<platform_account_id> (or for the Ads endpoint: <endpoint>:<channel>:<channel_account_id>).

This lets you group and identify each API connection across different endpoints, platforms, and account IDs.

📘

Note

Sending data to the following endpoints will not create an account in the Manage Data In Connection popup:

• Enrich Orders Data
• Enrich Products Data
• Enrich Pixel With Offline Events

This is because data sent to enrichment endpoints will update existing records, rather than create new records; this data cannot be deleted.

Deleting Data (Hard Delete)

To permanently delete all data sent to a specific Data-In API account:

1. Click Manage.

2. Locate the account you want to delete.

3. Click the three-dot menu (⋮) and select Delete.

   

4. Click Confirm in the confirmation popup.

   

❗️

Deleting account data is irreversible.

Managing Test Data

To isolate test records, we recommend sending test payloads using a unique platform_account_id, which you can later delete entirely from the Manage popup.

Voiding Records (Soft Delete)

To exclude specific records from reporting without deleting all data from an account, you can "void" them by resending the same record with all values unchanged, except set void: true.

This soft-deletes the record while preserving the account and all other data.

Endpoints that support voiding records:

• Ads
• Orders
• Subscriptions

📘

Voiding behavior for orders and refunds

Iforder.void = true:

• The entire order will be voided.
• All associated refunds (order.refunds) will also be voided — even if refund.void = false.

Iforder.void = false:

• Only refunds where refund.void = true will be voided.
• Refunds with refund.void = false will remain active and counted in reporting.

To void an existing refund, all of the following fields must match exactly:

• order_id
• refund_id
• order.created_at (must match the same date in the shop’s timezone)
• refund.refunded_at (must also match the same date in the shop’s timezone)
• platform
• platform_account_id