Skip to content

Commit 91161a2

Browse files
authored
Merge pull request #471 from segmentio/repo-sync
repo sync
2 parents 5332e45 + 8d7522e commit 91161a2

File tree

4 files changed

+36
-5
lines changed

4 files changed

+36
-5
lines changed

src/connections/destinations/catalog/firebase/index.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -108,14 +108,15 @@ By default, Segment only bundles `Firebase/Core` which is [Firebase's Analytics
108108

109109
## Setting up Firebase with Analytics-React-Native
110110

111-
If you use Segment's React Native source library, you must explicitly bundle the mobile SDKs for both iOS and Android with your project.
111+
If you use Segment's older React Native source library, you must explicitly bundle the mobile SDKs for both iOS and Android with your project.
112112

113113
1. Use yarn to add the `analytics-react-native-firebase` SDKs. (`@segment/analytics-react-native-firebase`)
114114
2. Add `import` statements to your code so you can access the SDKs.
115115
3. Go to the `await analytics.setup` configuration in your code, and find (or add) the `using:` item. Add "Firebase" to the list of device-mode destinations in the `using` item.
116116
4. Change to your iOS directory and run `pod install`.
117117
5. Add the `analytics-react-native-firebase` module to your `build.gradle` file. (See Step.4 of [Getting Started on Android](/docs/connections/destinations/catalog/firebase/#getting-started-on-android))
118118

119+
For React Native 2.0 you can reference the [install guide](https://github.com/segmentio/analytics-react-native/blob/master/packages/plugins/plugin-firebase/README.md){:target="_blank"}.
119120
## Identify
120121

121122
When you call `identify` Segment will map to the corresponding Firebase Analytics calls:

src/connections/sources/catalog/libraries/mobile/react-native/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -492,7 +492,7 @@ These are the example plugins you can use and alter to meet your tracking needs:
492492
| IDFA | `@segment/analytics-react-native-plugin-idfa` |
493493
494494
## Supported Destinations
495-
Segment supports these destinations for Analytics React Native 2.0 in device-mode, with more to follow. Cloud-mode destinations are also supported:
495+
Segment supports a large number of [Cloud-mode](/docs/connections/destinations/#connection-modes) destinations. Segment also supports the below destinations for Analytics React Native 2.0 in device-mode, with more to follow:
496496
- [Adjust](https://www.npmjs.com/package/@segment/analytics-react-native-plugin-adjust){:target="_blank"}
497497
- [Amplitude Session](https://www.npmjs.com/package/@segment/analytics-react-native-plugin-amplitude-session){:target="_blank"}
498498
- [Appsflyer](https://www.npmjs.com/package/@segment/analytics-react-native-plugin-appsflyer){:target="_blank"}

src/connections/sources/catalog/libraries/website/javascript/upgrade-to-ajs2.md

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -70,3 +70,29 @@ Analytics.js 2.0 asynchronously loads different pieces of the library as needed.
7070
### Using trackLink on elements that are not links
7171

7272
Previously, it was possible to attach `trackLink` to any element, and a `trackLink` call would fire for that element if it wasn't a link. Now, when you attach `trackLink` to a non-link element, an additional search of that element's children occurs for any nested links and fires track calls based on those links. If you wish to fire track calls on non-link elements that have links as children, you can use a `track` call instead.
73+
74+
## FAQs
75+
76+
### I'm already using Analytics 2.0, why am I still receiving the message to upgrade?
77+
It's possible that a different source you're using is still leveraging an older version of Analytics.js. A way to see which sources are on which versions is to go to the source overview page, then filter on the Analytics.js version.
78+
79+
It's also possible that you have used a write key from another source type (like Ruby) to instrument your Javascript source. To upgrade these sources, you may need to create a new javascript source and replace the write key.
80+
81+
### Should I expect any glitches or downtime when switching to Analytics 2.0?
82+
Segment expects no downtime or glitches when switching to A.js 2.0.
83+
84+
### How can I validate that my source is using Analytics.js 2.0?
85+
If you're using A.js 2.0, the library field will look like the code snippet below ( `next` will be part of the version field):
86+
87+
```js
88+
"library": {
89+
"name": "analytics.js",
90+
"version": "next-1.XX.X"
91+
}
92+
```
93+
94+
### Are there specific things to test from an engineering point of view?
95+
Like any software upgrade, Segment advises you to start with one source, or a development or staging source. Then you should ensure that traffic is flowing the way you expect it to and that it goes to the appropriate destinations.
96+
97+
### What happens if I don't upgrade by the end of service date?
98+
There will not be any changes to your sources on the end of service date. However, if you encounter issues or need support, the support team will advise you to upgrade to 2.0. All new features will only be available on the 2.0 versions.

src/partners/checklist.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,17 +2,21 @@
22
title: Public Beta Checklist
33
---
44

5+
> info ""
6+
> The Developer Center is currently not accepting new components. Segment is committed to redeveloping the Developer Center and a new version will be launched in the future. Include [your information here](https://airtable.com/shrvZzQ6NTTwsc6rQ){:target="_blank"} to join the waitlist!
7+
8+
59
The purpose of this checklist is to give you a window into the full integration lifecycle, from how you first get started with Developer Center, to how we'll test your app before it goes live.
610

711
## 1. Partner Access
812

913
First you will need a Segment account and access to Dev Center.
1014

11-
Start on the [Developer Center Partner page](https://segment.com/partners/developer-center/) to request access during signup. If you already have an account you can log in and go to the [request access to developer center](https://app.segment.com/developer/request-access) page.
15+
Start on the [Developer Center Partner page](https://airtable.com/shrvZzQ6NTTwsc6rQ) to request access during sign-up. If you already have an account you can log in and go to the [request access to developer center](https://airtable.com/shrvZzQ6NTTwsc6rQ) page.
1216

1317
Make sure to sign up with your company email address and to answer all the survey questions to expedite approval.
1418

15-
- Create Segment account and request access for Dev Center ([link](https://app.segment.com/signup?redirect=%2Fdeveloper%2Frequest-access&partner_signup=))
19+
- Create Segment account and request access for Dev Center ([link](https://airtable.com/shrvZzQ6NTTwsc6rQ))
1620

1721

1822
- Complete partner survey
@@ -168,7 +172,7 @@ To maintain the quality of the partner integrations catalog, the Segment Develop
168172

169173

170174
- Review documentation partner submitted using [HackMD Template](https://hackmd.io/t7amLXluS7-39rg7ARZgSA?both=)
171-
- All signup, API key and data delivery matches test
175+
- All sign-up, API key and data delivery matches test
172176

173177

174178
- Review catalog information partner submitted using [Google Docs Template](https://docs.google.com/document/d/1kKvqYtZeDPnBjvCrtQSuO3BBH70b_CLO13hYrYIOOtA/edit)

0 commit comments

Comments
 (0)