Release 23.3.3 #4085
Merged
Release 23.3.3 #4085
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
* Init * Intro edits * Draft complete * Apply suggestions from code review Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> * Remove * Update src/partners/index.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> * Update src/partners/index.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> * Update src/partners/index.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> * Clarifications from Sharan * No longer in Dev preview Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com>
Add note about the API Key being region specific
…ice-mode Update Amplitude Classic Destination [DOC-629]
…versions API Destination (#4025) * Update index.md * Update src/connections/destinations/catalog/actions-facebook-conversions-api/index.md Co-authored-by: markzegarelli <mark.zegarelli@segment.com> Co-authored-by: markzegarelli <mark.zegarelli@segment.com>
Co-authored-by: stayseesong <83784848+stayseesong@users.noreply.github.com>
Co-authored-by: stayseesong <83784848+stayseesong@users.noreply.github.com>
Co-authored-by: stayseesong <83784848+stayseesong@users.noreply.github.com>
Fix Youbora Destination Typos
Unhide commandbar docs
* add correct actions slug * add config option Co-authored-by: Niall Brennan <niall.brennan@segment.com>
* Update language * Update src/connections/sources/catalog/cloud-apps/facebook-lead-ads/index.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com>
…#4072) * Update 02-simple-install.md * Update src/getting-started/02-simple-install.md Co-authored-by: markzegarelli <mark.zegarelli@segment.com> * Update src/getting-started/02-simple-install.md Co-authored-by: markzegarelli <mark.zegarelli@segment.com>
* Update index.md * Update src/connections/sources/catalog/libraries/website/javascript/index.md Co-authored-by: markzegarelli <mark.zegarelli@segment.com>
* Update index.md Add info block about whether customer should set up one source or multiple sources * Update src/connections/sources/index.md Co-authored-by: markzegarelli <mark.zegarelli@segment.com> * Update src/connections/sources/index.md Co-authored-by: markzegarelli <mark.zegarelli@segment.com> * Update src/connections/sources/index.md Co-authored-by: markzegarelli <mark.zegarelli@segment.com> Co-authored-by: markzegarelli <mark.zegarelli@segment.com>
* Update on choosing the Intercom workspace There is no information on how to choose the Intercom workspace to access. Hence, updating the information in step 5 of ## Getting started. Statement added as below: Select the Intercom workspace to access from a dropdown list beside the statement "Segment wants to access". * Update index.md As advised by Spencer in Jira ticket https://segment.atlassian.net/browse/KCS-32, replace: "Select the Intercom workspace to access from a dropdown list beside the statement "Segment wants to access with "If you have multiple Intercom workspaces, please choose the one that you'd like to connect to Segment" * Update src/connections/destinations/catalog/actions-intercom-cloud/index.md Co-authored-by: markzegarelli <mark.zegarelli@segment.com>
add details about data type mismatch
…s-session-id-stored-in-local-storage Add Amplitude Session ID Info #3972
…4078) * Update actions.md * Move data into a table to improve readability Co-authored-by: markzegarelli <mark.zegarelli@segment.com>
* Release 23.3.2 (#4071) * Update faq.md * Developer Center 2.0 documentation (#4007) * Init * Intro edits * Draft complete * Apply suggestions from code review Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> * Remove * Update src/partners/index.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> * Update src/partners/index.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> * Update src/partners/index.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> * Clarifications from Sharan * No longer in Dev preview Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> * Update Amplitude Classic Destination DOC-629 * Update EU Endpoint Language DOC-629 * Update index.md Add note about the API Key being region specific * Revert commit * Add section highlighting User Data parameter mappings to Facebook Conversions API Destination (#4025) * Update index.md * Update src/connections/destinations/catalog/actions-facebook-conversions-api/index.md Co-authored-by: markzegarelli <mark.zegarelli@segment.com> Co-authored-by: markzegarelli <mark.zegarelli@segment.com> * added react native quick link * add section for api token security * update copy * Small edits * Update src/api/public-api.md Co-authored-by: stayseesong <83784848+stayseesong@users.noreply.github.com> * Update src/api/public-api.md Co-authored-by: stayseesong <83784848+stayseesong@users.noreply.github.com> * Update vale rules (#4055) * posthog: update instructions for Cloud EU * Add Audiences and Journeys Guide [netlify-build] * add correct actions slug (#4060) Co-authored-by: Niall Brennan <niall.brennan@segment.com> * Add platform code for setting writekey (#4050) * add platform code * add platform code * Update src/connections/sources/catalog/libraries/mobile/react-native/index.md Co-authored-by: markzegarelli <mark.zegarelli@segment.com> * Update src/connections/sources/catalog/libraries/mobile/react-native/index.md Co-authored-by: markzegarelli <mark.zegarelli@segment.com> Co-authored-by: Niall Brennan <niall.brennan@segment.com> Co-authored-by: markzegarelli <mark.zegarelli@segment.com> * add info about how data comes from Clearbit (#4040) * add info about how data comes from Clearbit Customers in the past have been confused about dataflow with Clearbit and about why they see analytics-ruby events in their Debugger. This update clarifies that a bit. There are past Zendesk tickets that all confirm Clearbit data comes back to Segment using analytics-ruby. In addition, Clearbit published this line about it in one of their blog posts: https://clearbit.com/blog/enterprise-grade-analytics-for-startups-2#:~:text=Segment%E2%80%99s%20robust%20API%20and%20Ruby%20library%20enabled%20our%20engineering%20team%20to%20quickly%20build%20an%20event%20emitting%20service%20that%20sends%20usage%20and%20behavioral%20data%20from%20Clearbit%20applications%20and%20services%20into%20Segment%2C%20tracking%20everything%20from%20API%20usage%20and%20page%20views%20to%20signups%20and%20subscribe%20events.. * Update src/connections/destinations/catalog/clearbit-reveal/index.md Co-authored-by: markzegarelli <mark.zegarelli@segment.com> * Apply suggestions from code review * Apply suggestions from code review * Apply suggestions from code review * Apply suggestions from code review * catalog update (#4064) * Add new product limits for Engage (#3965) Co-authored-by: Ashton Huxtable <78318468+ashton-huxtable@users.noreply.github.com> Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> Co-authored-by: pwseg <paul.wooley@segment.com> Co-authored-by: Sarah Rudy <78389005+sarahrudy@users.noreply.github.com> Co-authored-by: pwseg <86626706+pwseg@users.noreply.github.com> Co-authored-by: bobbyatsegment <93934274+bobbyatsegment@users.noreply.github.com> Co-authored-by: stayseesong <STACY.S.SONG@GMAIL.COM> Co-authored-by: Sal Olivares <git@salolivares.com> Co-authored-by: Sal Olivares <salolivares@users.noreply.github.com> Co-authored-by: stayseesong <83784848+stayseesong@users.noreply.github.com> Co-authored-by: Xavier Vello <xavier@posthog.com> Co-authored-by: Niall Brennan <niallbrennan87@gmail.com> Co-authored-by: Niall Brennan <niall.brennan@segment.com> Co-authored-by: Spencer Attick <23665784+spencerattick@users.noreply.github.com> * Catalog update for Jan 19 Co-authored-by: Ashton Huxtable <78318468+ashton-huxtable@users.noreply.github.com> Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> Co-authored-by: pwseg <paul.wooley@segment.com> Co-authored-by: Sarah Rudy <78389005+sarahrudy@users.noreply.github.com> Co-authored-by: pwseg <86626706+pwseg@users.noreply.github.com> Co-authored-by: bobbyatsegment <93934274+bobbyatsegment@users.noreply.github.com> Co-authored-by: stayseesong <STACY.S.SONG@GMAIL.COM> Co-authored-by: Sal Olivares <git@salolivares.com> Co-authored-by: Sal Olivares <salolivares@users.noreply.github.com> Co-authored-by: stayseesong <83784848+stayseesong@users.noreply.github.com> Co-authored-by: Xavier Vello <xavier@posthog.com> Co-authored-by: Niall Brennan <niallbrennan87@gmail.com> Co-authored-by: Niall Brennan <niall.brennan@segment.com> Co-authored-by: Spencer Attick <23665784+spencerattick@users.noreply.github.com>
Analytics Node Next
markzegarelli
requested review from
forstisabella,
pwseg,
rchinn1,
kdaswani,
stayseesong and
a team
as code owners
forstisabella
approved these changes
Jan 19, 2023
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.
No description provided.