You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{% if destMethods.size > 0 %}<li>Accepts {% for method in destMethods%}{% if destMethods.size == 1 %}{{method}} calls.{% else %}{% unless forloop.last == true %}{{method}}, {% endunless %}{% if forloop.last == true%}and {{method}} calls.{%endif%}{% endif %}{% endfor %}</li>{% endif %}
37
+
{% if destMethods.size > 0 %}<li>Accepts {% for method in destMethods%}{% if destMethods.size == 1 %}{{method}} calls.{% else %}{% unless forloop.last == true %}{{method}}, {% endunless %}{% if forloop.last == true%}and {{method}} calls{%endif%}{% endif %}{% endfor %}</li>{% endif %}
38
38
<li>Referred to as <strong>{{destinationInfo.previous_names | join: '</strong>, or <strong>' }}</strong> in the <ahref="/docs/guides/filtering-data/#filtering-with-the-integrations-object">Integrations object</a></li>
39
+
{% if destinationInfo.status == "PUBLIC_BETA" %}<li>This destination is in <spanclass="release-pill">Beta</span></li>{% endif %}
When Segment loads data into your warehouse, each sync goes through two steps:
2
+
1.**Ping:** Segment servers connect to your warehouse. For Redshift warehouses, Segment also runs a query to determine how many slices a cluster has. Common reasons a sync might fail at this step include a blocked VPN or IP, a warehouse that isn't set to be publicly accessible, or an issue with user permissions or credentials.
3
+
2.**Load:** Segment de-duplicates the transformed data and loads it into your warehouse. If you have queries set up in your warehouse, they run after the data is loaded into your warehouse.
<tdmarkdown="span">*optional if userID is set instead*</td>
3
+
<tdmarkdown="span">*required; optional if `userID` is set instead*</td>
4
4
<tdmarkdown="span">String</td>
5
-
<tdmarkdown="span">A pseudo-unique substitute for a User ID, for cases when you don't have an absolutely unique identifier. A userId or an anonymousId is required.
6
-
5
+
<tdmarkdown="span">A pseudo-unique substitute for a User ID, for cases when you don't have an absolutely unique identifier. A `userId` or an `anonymousId` is required.
6
+
7
7
See the [Identities docs](/docs/connections/spec/identify#identities) for more details.
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/appsflyer/index.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,6 +5,12 @@ id: 54521fd525e721e32a72ee8f
5
5
---
6
6
[AppsFlyer](https://www.appsflyer.com/) is the world's leading mobile attribution & marketing analytics platform, helping app marketers around the world make better decisions. Our AppsFlyer destination code is open-source. You can browse the code on GitHub for [iOS](https://github.com/AppsFlyerSDK/segment-appsflyer-ios) and [Android](https://github.com/AppsFlyerSDK/AppsFlyer-Segment-Integration).
7
7
8
+
Segment's Appsflyer destination code is open source and available on GitHub. You can view these repositories:
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/firebase/index.md
+6-39Lines changed: 6 additions & 39 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,10 +5,14 @@ id: 579a568e80412f644ff19cf7
5
5
---
6
6
Firebase is Google's platform for mobile apps. The Segment Firebase destination requires that you bundle the Firebase SDK with your project. The Segment-wrapped destination code then runs on the user's device, and sends its tracking calls to the Firebase API endpoints, and a copy to Segment for archiving.
7
7
8
-
9
8
> info ""
10
9
> As of October 2019, Firebase replaced the legacy version of Google Analytics Classic for mobile devices. (If you used Google Analytics for mobile, see the [migration guide](/docs/connections/destinations/catalog/google-analytics/migrating/).)
11
10
11
+
Segment's Firebase destination code is open source and available on GitHub. You can view these repositories:
@@ -112,43 +116,6 @@ If you use Segment's React Native source library, you must explicitly bundle the
112
116
4. Change to your iOS directory and run `pod install`.
113
117
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))
114
118
115
-
116
-
## Setting up Firebase with Analytics-Kotlin
117
-
If you're using the [Analytics-Kotlin library](/docs/connections/sources/catalog/libraries/mobile/kotlin-android), follow these steps to set up Firebase with Analytics-Kotlin:
118
-
1. In your top-level `build.gradle` file add these lines:
119
-
```kotlin
120
-
buildscript {
121
-
...
122
-
repositories {
123
-
google()
124
-
}
125
-
dependencies {
126
-
...
127
-
classpath 'com.google.gms:google-services:4.3.5'
128
-
}
129
-
}
130
-
```
131
-
2. In your app-module `build.gradle` file add these lines:
3. Copy the [FirebaseDestination.kt](https://github.com/segmentio/analytics-kotlin/blob/main/samples/kotlin-android-app-destinations/src/main/java/com/segment/analytics/destinations/plugins/FirebaseDestination.kt) file into your project's codebase.
145
-
4. Copy your `google-service.json` file to your app-module.
146
-
5. Go to your project's codebase and add these lines where you intialize the analytics client:
147
-
```kotlin
148
-
val Firebase = FirebaseDestination()
149
-
analytics.add(Firebase)
150
-
```
151
-
152
119
## Identify
153
120
154
121
When you call `identify` Segment will map to the corresponding Firebase Analytics calls:
@@ -273,7 +240,7 @@ Then, enter the deep link URL scheme in your Segment Firebase destination settin
273
240
274
241
### **Conversion Tracking and Adwords Conversions**
275
242
276
-
FirebaseisGoogle's recommended method for reporting conversions to Adwords. To use Firebase, track the conversion events as you normally would with Segment and Segment will send them through to Firebase.
243
+
Firebase is Google's recommended method for reporting conversions to Adwords. To use Firebase, track the conversion events as you normally would with Segment and Segment will send them through to Firebase.
0 commit comments