Expose Daisycon compensation_code and transaction-level fields in connector#1929

Currently the Daisycon connector only uses the Statistics API endpoint, which does not expose compensation_code or transaction-level data.

For advertisers using multiple products with different compensation models, this makes it impossible to accurately report costs per product.

Daisycon receives and stores the compensation_code for each transaction. This field is also available in the Daisycon transaction export, but is currently not exposed through the Windsor.ai Daisycon connector.

Requested enhancement:
Please add support for transaction-level reporting (e.g. transaction_advertiser_part endpoint) and expose at minimum:

• compensation_code
• transaction_id
• transaction status (approved/open/disapproved)
• commission/program amount

Expected benefit:
This would allow advertisers to:

• Report affiliate costs per product category
• Calculate Cost per Sale (CPS) by product
• Create automated reporting without manual transaction exports

Without this field, all costs are aggregated into a single total and cannot be allocated to the correct product line.