source-facebook-marketing: Add engaged view (ev) attribution windows to action attribution reporting

[devin-ai-integration]

Summary

Requested by Teo (@tgonzalezc5) (teo@airbyte.io).

When pulling data from the Facebook Marketing source connector, the action_attribution_windows parameter sent to the Facebook Insights API should include the engaged view (ev) attribution window types in addition to the existing click and view windows.

Current Behavior

The connector currently requests the following action_attribution_windows (defined in ALL_ACTION_ATTRIBUTION_WINDOWS in base_insight_streams.py):

• 1d_click
• 7d_click
• 28d_click
• 1d_view

This means streams like custom insights reporting (e.g. custom_table_actions, custom_table_action_values) only include click and 1d_view attribution data.

Expected Behavior

The connector should also request the following engaged view attribution windows:

• 1d_ev
• 7d_ev
• 28d_ev

These are valid Facebook Marketing API attribution windows and are needed to get complete attribution reporting data.

Relevant Code

• source_facebook_marketing/streams/base_insight_streams.py (line 35-40) — ALL_ACTION_ATTRIBUTION_WINDOWS list

Impact

This affects all Ads Insights streams that use action_attribution_windows in their API requests. Adding the ev windows will surface engaged view attribution data in action-related fields (e.g. actions, action_values, cost_per_action_type, etc.).

Considerations

• Adding new attribution windows is a schema change — new *_1d_ev, *_7d_ev, *_28d_ev columns will appear in action stats objects.
• This should be evaluated for whether it constitutes a breaking change (new columns appearing in existing streams). Since these are additive columns, this may be non-breaking.
• The JSON schemas for action stats (shared/ads_action_stats.json) will need to be updated to include the new ev window properties.

---

Internal Tracking: https://github.com/airbytehq/oncall/issues/11511

[octavia-bot]

AI Triage Starting...

Thank you for opening this issue! I'm an AI assistant that will do an initial review and may:

• Ask clarifying questions if needed
• Suggest relevant documentation or workarounds
• Flag this for internal visibility

Note: Community issues are reviewed on a best-effort basis and do not have a guaranteed response time. For additional help:

• Join the Airbyte Community Slack to connect with other users and community members
• If you're an Airbyte Cloud customer, you can open a support ticket or contact your account representative, referencing this issue URL

View playbook

• 🔗 Session URL: https://app.devin.ai/sessions/129d5f6beb2048c69d82846084e8474d

✅ Devin AI session created successfully!

[devin-ai-integration]

---

Devin session

[devin-ai-integration]

Hi devin-ai-integration, thank you for reporting this!

This is a valid feature request — the Facebook Marketing API supports engaged view (ev) attribution windows (1d_ev, 7d_ev, 28d_ev), and the connector currently only requests click and 1d_view windows. Adding these would surface engaged view attribution data in action-related fields.

I'm escalating this to the internal team for implementation.

Note: A related but distinct oncall issue (airbytehq/oncall#11344) already tracks adding the incrementality attribution window. The engaged view (ev) windows requested here are a separate set of attribution types.

---

Need more help? Join Airbyte Community Slack for peer support, or if you're a Cloud customer, open a support ticket referencing this URL.

This message is generated from Devin.ai (internal session link).

[devin-ai-integration]

This issue has been escalated to the internal team for tracking: https://github.com/airbytehq/oncall/issues/11511

This message is generated from Devin.ai (internal session link).