You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/adjust/index.md
+9Lines changed: 9 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -231,6 +231,14 @@ The destination will automatically recognize the spec'd `orderId` property, and
231
231
232
232
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)).
233
233
234
+
### Sending in-app events from Adjust to Segment
235
+
236
+
Customers can forward in-app events from Adjust to Segment by following these steps:
237
+
238
+
1. Navigate to the Segment module within the Adjust dashboard.
239
+
2. Go to the **Data sharing** section.
240
+
3. Use the **Map your events** option to select and map the in-app events you'd like to forward to Segment.
241
+
234
242
### In-app purchase receipts
235
243
236
244
The destination does not currently support in-app purchase receipts. If this is important to you, [reach out to support](https://segment.com/help/contact/){:target="_blank”}.
@@ -246,3 +254,4 @@ By default, our destination enables event buffering for Adjust. This saves your
246
254
### Deep linking
247
255
248
256
The destination does not automatically support deep linking out of the box (you'd need to write code here regardless). This means you can use [Adjust's deep-linking](https://github.com/adjust/ios_sdk#7-set-up-deep-link-reattributions){:target="_blank"} by accessing [the Adjust SDK directly](/docs/connections/sources/catalog/libraries/mobile/ios/#faq).
0 commit comments