Skip to content

Add FAQ & Troubleshooting section to Destination Actions docs #4193

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Apr 4, 2023

Conversation

bobbyatsegment
Copy link
Contributor

Proposed changes

These docs do not currently have a FAQ & Troubleshooting section - added this to cover two scenarios that customers have written in about.

  1. Validation error when using the Event Tester - a validation error with the description "You may not have any subscriptions that match this event" will surface when sending an event with an Actions destination's event tester that does not match the trigger of any configured and enabled mappings:
    Screen Shot 2023-02-07 at 3 39 13 PM

Added a bullet that covers this error along with options for resolving it (creating a new mapping to handle the event being tested or using a test event that matches an existing mapping)

  1. Multiple mappings triggered by the same event - this has been asked by several customers, and couldn't find another location for this information, so created a bullet for this as well.

For example, in my own workspace's GA4 destination instance I have two custom event mappings, one generates an event called "event_one", and the other generates an event called "event_two". Both are configured to trigger on an event called "Segment Test Event Name":

two_mappings_same_event

By using the destination's event tester, I can see that multiple requests are made to Google, and can cycle through them by clicking the arrows at the top by the "Event Lifecycle" heading:

First request sent for custom event event_one:
first_ga4_request

Second request sent for custom event event_two:
second_ga4_request

Merge timing

Related issues (optional)

@bobbyatsegment bobbyatsegment marked this pull request as ready for review March 29, 2023 15:20
@stayseesong stayseesong merged commit e067556 into develop Apr 4, 2023
@stayseesong stayseesong deleted the bobbyatsegment-patch-1 branch April 4, 2023 16:32
@github-actions
Copy link
Contributor

github-actions bot commented Apr 4, 2023

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants