Clarify Segment<>Iterable ecommerce connection #1486
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Per this ticket: https://segment.zendesk.com/agent/tickets/420194, our docs are pretty unclear on exactly what Iterable requires for the ecommerce events we map for customers. Based on https://github.com/segmentio/integrations/blob/master/integrations/iterable/lib/index.js#L163-L206 and https://github.com/segmentio/integrations/blob/master/integrations/iterable/lib/mapper.js, we pretty much just send the `products` array we are given to Iterable, but turns out, the endpoints we hit requires some basic fields in each product object: https://api.iterable.com/api/docs#commerce_trackPurchase and https://api.iterable.com/api/docs#commerce_updateCart. I tried to clarify these requirements better for less confusion in the future.
|
Deploy preview for segment-docs ready! Built with commit b1accf9 |
sanscontext
reviewed
Mar 30, 2021
sanscontext
reviewed
Mar 30, 2021
Co-authored-by: LRubin <sanscontext@users.noreply.github.com>
sanscontext
reviewed
Apr 7, 2021
sanscontext
approved these changes
Apr 7, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Per this ticket: https://segment.zendesk.com/agent/tickets/420194, our docs are pretty unclear on exactly what Iterable requires for the ecommerce events we map for customers. Based on https://github.com/segmentio/integrations/blob/master/integrations/iterable/lib/index.js#L163-L206 and https://github.com/segmentio/integrations/blob/master/integrations/iterable/lib/mapper.js, we pretty much just send the
productsarray we are given to Iterable, but turns out, the endpoints we hit requires some basic fields in each product object: https://api.iterable.com/api/docs#commerce_trackPurchase and https://api.iterable.com/api/docs#commerce_updateCart. I tried to clarify these requirements better for less confusion in the future.