[BD-5773] Fix incorrect in-app message type names in campaign export endpoints

[atom-evens]

Summary

A user reported that the documented in-app message type names are incorrect in two campaign export API endpoint pages:

1. Export Campaign Analytics (/campaigns/data_series): The message types list at the bottom of the page referenced in_app_message, but the multivariate response example directly above it uses trigger_in_app_message. Changed in_app_message to trigger_in_app_message to match the actual API response.

2. Export Campaign Details (/campaigns/details): The channel field description listed in-app_message (with a hyphen instead of an underscore), which is both inconsistently formatted and incorrect. Changed in-app_message to trigger_in_app_message.

Test plan

• Verify the Export Campaign Analytics page renders correctly and the message types list now shows trigger_in_app_message.
• Verify the Export Campaign Details page renders correctly and the channel type list now shows trigger_in_app_message.

Made with Cursor

Fixes #11445

[Copilot]

Pull request overview

Fixes documented in-app message type names for campaign export endpoints so they align with the response examples (and expected API values), improving accuracy for API consumers.

Changes:

• Updates /campaigns/details response field description to use trigger_in_app_message for the channel value list.
• Updates /campaigns/data_series message type list to use trigger_in_app_message to match the multivariate response example.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
_docs/_api/endpoints/export/campaigns/get_campaign_details.md	Adjusts documented channel enum values in the response schema to use trigger_in_app_message.
_docs/_api/endpoints/export/campaigns/get_campaign_analytics.md	Updates the “possible message types” list to match the trigger_in_app_message key used in the response example.

[zairro]

Lgtm!