Add section : Replays & Destination Filters

[lizkane222]

Customers don't always know how replays and destination filters interact, so adding this section explicitly could reduce number of responses between CSE & customer. Ticket : https://segment.zendesk.com/agent/tickets/506599

Proposed changes

Replays & Destination Filters

Replays are subject to the Destination Filters you’ve configured on that destination. For example, this means that if you request that identify calls be included in the replay, but your destination has a Destination Filter that blocks identify events, then none of those identify events will actually make it to the destination, as they’d be blocked by the filter. Though, the better practice would be to not include identify events in the Replay at all if you know they’ll be blocked by the destination filter.

When you request a replay, you’ll be asked to provide a list of the events (type and/or name) that you’d like to be included in the replay. If you specify a list of events, then only those specified events will be included in the replay. If you’d like all events from that source to be sent in the replay, then you don’t need to specify the events and all events will be included in the replay.

Customers don’t always know how replays and destination filters interact, so adding this section explicitly could reduce number of responses between CSE & customer, as well as inform the customer of this behavior before requesting a replay.
Tickets : https://segment.zendesk.com/agent/tickets/506599, https://segment.zendesk.com/agent/tickets/500786, https://segment.zendesk.com/agent/tickets/479970

Merge timing

• ASAP once approved?

Related issues (optional)

[github-actions]

Thank you for your contribution! Your pull request is merged, but may take a day or two to appear on the site.