Skip to content
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

[BUG] Segment - Identify User and Track user action do not send event to Segment #7325

Closed
vunguyenhung opened this issue Jul 21, 2023 · 3 comments · Fixed by #7418
Closed
Assignees
Labels
bug Something isn't working prioritized Prioritized issue triaged For maintainers: This issue has been triaged by a Pipedream employee

Comments

@vunguyenhung
Copy link
Collaborator

Describe the bug
I created a new Segment HTTP source and add the write key to Pipedream's Segment account
image
image

Then I executed 2 actions for track and identify user
Screenshot 2023-07-21 at 12 50 23
image
image

But I don't see new event on Segment for both Identify and Track
image
image

Expected behavior
There should be new event when I executed the Pipedream Segment actions

Additional context
Reported by a customer here: https://pipedream-users.slack.com/archives/CMZG4EBJ9/p1689913634401379

@vunguyenhung vunguyenhung added bug Something isn't working prioritized Prioritized issue labels Jul 21, 2023
@vunguyenhung vunguyenhung changed the title [BUG] Segment - Identify User and [BUG] Segment - Identify User and Track user action do not send event to Segment Jul 21, 2023
@vunguyenhung vunguyenhung added the triaged For maintainers: This issue has been triaged by a Pipedream employee label Jul 24, 2023
@vunguyenhung vunguyenhung added this to To Do in Component (Source and Action) Backlog via automation Jul 24, 2023
@vunguyenhung vunguyenhung moved this from To Do to Prioritized in Component (Source and Action) Backlog Jul 24, 2023
@michelle0927 michelle0927 self-assigned this Jul 28, 2023
@michelle0927 michelle0927 moved this from Prioritized to Doing in Component (Source and Action) Backlog Jul 28, 2023
@michelle0927 michelle0927 moved this from Doing to Ready for PR review in Component (Source and Action) Backlog Jul 28, 2023
@vellames vellames moved this from Ready for PR review to In Review in Component (Source and Action) Backlog Jul 31, 2023
@vellames vellames moved this from In Review to Ready for QA in Component (Source and Action) Backlog Jul 31, 2023
@vunguyenhung vunguyenhung moved this from Ready for QA to In QA in Component (Source and Action) Backlog Aug 1, 2023
@vunguyenhung vunguyenhung moved this from In QA to Changes Required in Component (Source and Action) Backlog Aug 1, 2023
@vunguyenhung
Copy link
Collaborator Author

Hello everyone, I have tested this PR and there're some test cases failed or needed improvement.

Please check the test report below for more information
https://vunguyenhung.notion.site/BUG-Segment-Identify-User-and-Track-user-action-do-not-send-event-to-Segment-7325-bf31eb5c2d354a639a0a0fd4d87bb750

@michelle0927 michelle0927 moved this from Changes Required to Ready for PR review in Component (Source and Action) Backlog Aug 4, 2023
@jcortes jcortes moved this from Ready for PR review to In Review in Component (Source and Action) Backlog Aug 4, 2023
@jcortes jcortes moved this from In Review to Ready for QA in Component (Source and Action) Backlog Aug 4, 2023
@michelle0927
Copy link
Collaborator

@vunguyenhung Note for QA: To retest the "Webhook Destination" source, you'll need to reconnect your account and enter an access_token in addition to the write_key.

@vunguyenhung vunguyenhung moved this from Ready for QA to In QA in Component (Source and Action) Backlog Aug 6, 2023
@vunguyenhung vunguyenhung moved this from In QA to Ready for release in Component (Source and Action) Backlog Aug 7, 2023
@vunguyenhung
Copy link
Collaborator Author

Component (Source and Action) Backlog automation moved this from Ready for release to Done Aug 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working prioritized Prioritized issue triaged For maintainers: This issue has been triaged by a Pipedream employee
Development

Successfully merging a pull request may close this issue.

2 participants