Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Added steps on sending in-app events to Segment [DOC-1131] #7683

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

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

sade-wusi
Copy link
Contributor

Proposed changes

Adjust now allows customers to send in-app events to Segment.

Merge timing

  • ASAP once approved

@sade-wusi sade-wusi requested a review from a team as a code owner June 17, 2025 14:44
@sade-wusi sade-wusi added the content-update updates to content that are not new features, includes grammar fixes, added notes label Jun 17, 2025
@sade-wusi sade-wusi requested a review from pwseg June 17, 2025 14:44
Copy link
Contributor

@pwseg pwseg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One quick change, but approved!

@@ -231,6 +231,14 @@ The destination will automatically recognize the spec'd `orderId` property, and

If you're using Adjust's iOS SDK, it will automatically takes care of duplicate purchase events. Segment uses Adjust's default deduplication (using `transactionId`) when you send an `orderId` (see the [ecommerce spec](/docs/connections/spec/ecommerce/v2/#order-completed)).

### Sending in-app events from Adjust to Segment

Customers can forward in-app events from Adjust to Segment by following the steps below:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Customers can forward in-app events from Adjust to Segment by following the steps below:
Customers can forward in-app events from Adjust to Segment by following these steps:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content-update updates to content that are not new features, includes grammar fixes, added notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants