Connector name: Impact Brand

Table name: contract_event_payout_group

Column to add: payout (decimal) — sourced from the Payout field on each PayoutGroup object in TemplateTerms.EventPayouts[].PayoutGroups[]. Your engineer Shubham confirmed the connector currently reads only ID, Rank, and PayoutRate from this object and omits Payout entirely

API documentation link: https://integrations.impact.com/brand-api-reference/reference/contracts/models.md (see the PayoutGroup schema — Payout is defined as {"type":"number","format":"decimal"}, a sibling field to PayoutRate)

Additional details: 

This gap was identified while investigating tiered partner payout agreements that appeared correctly in the impact.com UI but were incomplete in our Fivetran-synced data.

Repro steps:

1. GET /Advertisers/{AccountSID}/Campaigns/{CampaignId}/Contracts/{ContractId} for an active contract returns TemplateTerms.EventPayouts[].PayoutGroups[] for a SALE-category event, with multiple tiers, each including a Payout value.
2. The corresponding row in our destination table contract_event_payout_group for that same group ID contains only id, contract_event_payout_event_type_id, and rank — no payout value.
3. Sibling child tables contract_payout_group_rule / contract_payout_group_rule_value correctly capture that tier's conditions for the same group ID, confirming the connector reads this object but drops the Payout field specifically.

Your team confirmed via the linked support ticket that the connector currently reads only ID, Rank, and PayoutRate from each PayoutGroup object, and that Payout is not read at all — this feature request is to close that gap.

Business impact: without this field, we cannot determine the actual amount owed to a partner for a given payout tier from our warehouse — this affects reconciliation of live, active partner payout agreements.

See technical issue #403240 for more details