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/actions-amplitude/index.md
+14Lines changed: 14 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,6 +37,20 @@ Amplitude (Actions) provides the following benefits over the classic Amplitude d
37
37
38
38
Once you have a mapping, you can follow the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customizing-mappings).
39
39
40
+
### Log Purchases in existing destination instances
41
+
42
+
Initially, the Log Event Action was reporting purchases to Amplitude for all events containing a `products` array, even if the products were just added to cart. This inflated the LTV Chart in Amplitude.
43
+
44
+
To resolve this, purchase reporting takes place in a new Action called Log Purchase.
45
+
46
+
For instances created prior to before the Log Purchases action was released, you need to manually add the Log Purchases Action to report purchases to Amplitude.
47
+
48
+
To manually add the Log Purchases Action:
49
+
1. Add a new Mapping for the Log Purchases Action. The default trigger for this action is Order Completed events.
50
+
2. Modify the Trigger if you need to report purchases for any other events.
51
+
3. Modify the Trigger of Log Event to exclude these same events. This helps you to avoid sending the same event twice.
52
+
4. Enable the Log Purchases mapping.
53
+
40
54
### Connection Modes for Amplitude (Actions) destination
41
55
42
56
The Amplitude (actions) destination does not offer a device-mode connection mode. If you're using one of Segment's new libraries ([Analytics.js 2.0](/docs/connections/sources/catalog/libraries/website/javascript/), [Swift](https://github.com/segmentio/analytics-swift) or [Kotlin](https://github.com/segmentio/analytics-kotlin)) with the Actions-framework version of the destination, you do not need the device-mode connection.
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/actions-snap-conversions/index.md
+2-3Lines changed: 2 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,9 +7,6 @@ id: 6261a8b6cb4caa70e19116e8
7
7
8
8
The Snapchat Conversions API destination is a server-to-server integration with the [Snapchat Conversions API](https://marketingapi.snapchat.com/docs/conversion.html#conversions-api){:target="_blank"} that allows advertisers to pass web, app, and offline events from Segment directly to Snap. Data shared through the Snapchat Conversions API is processed similarly to events passed through the Snap Pixel or App Ads Kit (SDK). By passing events, advertisers can access post-view and post-swipe campaign reporting to measure performance and incrementality. Depending on the data shared and timeliness of integration, it’s also possible to use events passed through the Conversions API for solutions such as custom audience targeting, campaign optimization, Dynamic Ads, and more.
9
9
10
-
> info ""
11
-
> The Snapchat Conversions API destination is in beta and is in active development. Some functionality may change before it becomes generally available.
12
-
13
10
## Benefits of the Snapchat Conversions API
14
11
The Snapchat Conversions API destination provides the following benefits:
15
12
-**Clear mapping of data.** Actions-based destinations enable you to define the mapping between the data Segment receives from your source and the data Segment sends to Snap.
@@ -83,3 +80,5 @@ In addition, Segment creates a SHA-256 hash of the following fields before sendi
83
80
- Phone Number
84
81
- IP Address
85
82
83
+
> warning ""
84
+
> If you hash identifiers upstream before sending to Segment, Segment still hashes that data before sending to Snap. This results in a double hash that won't be able to be matched on. Please ensure your fields are not hashed prior to sending through the Snapchat Conversions API destination.
0 commit comments