Swrve Destination
Destination Info
- Accepts Page, Identify and Track calls.
- In Device-mode, refer to it as swrve in the Integrations object
Once the Segment library is integrated, toggle Swrve on in your Segment destination catalog. You can integrate Swrve as a mobile destination (iOS or Android). You'll need to get your app_id and api_key from the Swrve dashboard and add these to your mobile app.
Swrve supports the identify, track and screen methods.
- In your top-level project
build.gradleadd:
1repositories {2jcenter{3url = 'http://dl.bintray.com/swrve-inc/android'4}5maven {6url = 'https://maven.google.com'7}8}
- Add the Swrve Segment dependency to your app
build.gradle:
compile 'com.swrve:swrve-segment-integration:+'
- To do this, import the Swrve integration:
import com.segment.analytics.android.integrations.swrve.SwrveIntegration;
And add the following lines when initializing Segment:
1int appId = -1;2String apiKey = "api_key";34SwrveConfig swrveConfig = new SwrveConfig();5// To use the EU stack, include this in your config.6// swrveConfig.setSelectedStack(SwrveStack.EU);78Analytics analytics = new Analytics.Builder(this, "write_key")9.use(SwrveIntegration.createFactory(application, appId, apiKey, swrveConfig)10.build();
Note: Since Swrve needs to be initialized as early as possible, you need to supply the app_id and api_key key when you initialize the factory that is registered with the analytics client.
No further action is required to integrate in-app messages or Conversations, which are registered for and requested by default by our Swrve Segment destination.
- Add this line to your
Podfile:
pod 'Segment-Swrve'
- Register the integration. To do this, import the Swrve integration in your
AppDelegate:
#import <SwrveSegment/SEGSwrveIntegrationFactory.h>
And add the following lines:
1NSString *const SEGMENT_WRITE_KEY = @"...";2SEGAnalyticsConfiguration *config = [SEGAnalyticsConfiguration configurationWithWriteKey:SEGMENT_WRITE_KEY];34// FIXME Add your own App ID and Api Key here5int appId = 0;6NSString *apiKey =@"<Enter your own Api key here>";78SwrveConfig *swrveConfig = [[SwrveConfig alloc] init];910// TODO:11// To use the EU stack, include this in your config.12// swrveConfig.selectedStack = SWRVE_STACK_EU;1314[config use:[SEGSwrveIntegrationFactory instanceWithAppId:appId15apiKey:apiKey16swrveConfig:swrveConfig17launchOptions:launchOptions]];1819[SEGAnalytics setupWithConfiguration:config];
Note: Since Swrve needs to be initialized as early as possible, you need to supply the app_id and api_key key when you initialize the factory that is registered with the analytics client.
No further action is required to integrate in-app messages or Conversations, which are registered for and requested by default by our Swrve Segment destination.
When you call screen in your mobile app, we send a event prefixed with screen. to Swrve.
When you identify a user, we'll pass that userId as a user property named customer.id to Swrve.
All other traits will be sent to Swrve as custom user properties. Traits will be converted to strings before sending to Swrve.
When you track an event, we will send that event directly to Swrve as a custom event. Event properties will be sent to Swrve as event payloads. Properties will be converted to strings before sending.
Segment lets you change these destination settings from the Segment app without having to touch any code.
Optional
Android requires at least one setting