Skip to content

Commit 283729a

Browse files
committed
Add notes about required user agent info and Segment's iOS library
1 parent f25bb9f commit 283729a

File tree

1 file changed

+7
-1
lines changed
  • src/connections/destinations/catalog/actions-magellan-ai

1 file changed

+7
-1
lines changed

src/connections/destinations/catalog/actions-magellan-ai/index.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,8 +32,14 @@ Optionally, if you need Magellan AI to process GDPR deletion requests:
3232
* Magellan AI only supports Segment's Replay feature for mobile events.
3333

3434
[
35+
### Lead
36+
3537
Magellan AI's `Lead` action is semantically closest to Segment's B2B SaaS `Signed Up` event and uses it as the default Trigger. However, Magellan AI's API spec considers `Lead` an e-commerce event, requiring a value and a currency. You may:
3638
* Configure your sources sending `Signed Up` events to include the additional e-commerce-style fields
3739
* Consider mapping an alternative event to the `Lead` action, such as `Promotion Clicked` or `Product Added to Wishlist`, depending on your use case
38-
* Map `Signed Up` events to the `Lead` action, providing dummy values in the mapping like `0` for the value and `USD` for the currency
40+
* Map `Signed Up` events to the `Lead` action, providing dummy values in the mapping like `0` for the value and `USD` for the currency
41+
42+
### Install, Third-Party Event
43+
44+
Magellan AI's API spec requires a user agent, but Segment's iOS library does not provide user agent information in the event context. In order to use this action with the Segment's iOS library, you may provide either a static user agent string or a placeholder value in the mapping.
3945
]: #

0 commit comments

Comments
 (0)