Which connector?: Attentive

Additional details:  

The current Attentive connector only syncs via Attentive's webhooks (CUSTOM_ATTRIBUTE, EMAIL_SENT, EMAIL_OPENED, EMAIL_MESSAGE_LINK_CLICK, SMS_SENT, SMS_MESSAGE_LINK_CLICK, SMS_EMAIL_SUBSCRIBED, SMS_EMAIL_UNSUBSCRIBED, SMS_INBOUND). Attentive also offers a nightly SFTP data feed (General Events + Conversions) that exposes several fields we need for reporting and that aren't available anywhere in the webhook payloads. Requesting this connector be configured to also ingest Attentive's SFTP feed, or that the equivalent fields be added if Attentive exposes them another way.

Fields needed and where Attentive documents them (https://docs.attentive.com/docs/attentive-sftp-data-feeds):
— campaign_name, campaign_type — General Events feed, "the name of the campaign associated with a message"
— parent_message_name — General Events feed, "name of the parent message, for messages triggered by another message" (covers our "trigger_name" need)
— message_type / message_subtype (AUTOMATED + WELCOME/LEGAL/OTHER) — closest available proxy for journey categorization; Attentive has no dedicated journey name/ID field
— delivered — EMAIL_DELIVERY_EVENTS type, sub-event EMAIL_DELIVERED (email); message_sid, the carrier delivery confirmation (SMS)
— email_bounces / email_bounce_rate — EMAIL_DELIVERY_EVENTS sub-events EMAIL_SOFT_BOUNCE and EMAIL_HARD_BOUNCE, plus bounce_classification
— conversions, revenue — separate Conversions Data Feed, keyed by message_id/message_name, with amount (purchase amount), order_id, quantity
— cvr, conversion_rate, average_order_value — not raw fields; these are computable once conversions and sent counts are both synced, same as how unsubscribe_rate is already handled as "derived" in the current schema

Not requesting: message_variant. No equivalent field exists in Attentive's webhooks, REST/GraphQL API, or SFTP feeds — nothing to point you to.