Thanks to visit codestin.com
Credit goes to github.com

Skip to content

rename UserLeap destination to Sprig Cloud, edits on Sprig (Actions) #2359

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

bgila
Copy link
Contributor

@bgila bgila commented Jan 14, 2022

  • Would love to rename the UserLeap integration to Sprig Cloud now that our company has been renamed, and with "Cloud" to differentiate it from the Sprig (Actions) destination, which is device-mode only (Web only at the moment).
  • I would also love to update the destination catalog page, with this content: Segment Catalog Template - Google Docs. This document also links to updated screenshots and logo. -- I can open a help ticket for that change if that would be helpful.

Proposed changes

-- rename userleap integration, update documentation and remove outdated/redundant explanations
-- minor cleanup on the Sprig (Actions) documentation

Merge timing

  • ASAP once approved

Related issues (optional)

@bgila bgila requested a review from a team as a code owner January 14, 2022 20:42
@bgila bgila requested review from stayseesong and removed request for a team January 14, 2022 20:42
<!-- If applicable, add information regarding the migration from a classic destination to an Actions-based version below -->

## Migration from the classic Sprig destination

To prevent duplicate events from being tracked, please disable your existing Sprig destination when you enable Sprig (Actions).
To prevent duplicate events being created in Sprig, ensure that for each Segment source, this destination and the Sprig Cloud destination are not both enabled at the same time.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
To prevent duplicate events being created in Sprig, ensure that for each Segment source, this destination and the Sprig Cloud destination are not both enabled at the same time.
To prevent the creation of duplicate events in Sprig, ensure that this destination and the Sprig Cloud destination aren't enabled at the same time for each Segment source.

@stayseesong stayseesong merged commit 76cc7ed into segmentio:develop Jan 18, 2022
@github-actions
Copy link
Contributor

Thank you for your contribution! Your pull request is merged, but may take a day or two to appear on the site.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants