Skip to content

Commit 994d3cc

Browse files
Merge pull request #6370 from segmentio/6119-content-referring-to-quantcast-when-im-trying-to-do-stuff-with-optimizely
Fix Quantcast plugin title bug, Vale fixes
2 parents c869897 + 5f1ebb0 commit 994d3cc

File tree

2 files changed

+22
-17
lines changed

2 files changed

+22
-17
lines changed

src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/optimizely-full-stack-swift.md

Lines changed: 15 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -3,12 +3,12 @@ title: Analytics Swift Optimizely Full Stack Plugin
33
strat: swift
44
---
55

6-
Add OptimizelyFullStack session tracking support to your applications via this plugin for [Analytics-Swift](https://github.com/segmentio/analytics-swift)
6+
Add OptimizelyFullStack session tracking support to your applications using this plugin for [Analytics-Swift](https://github.com/segmentio/analytics-swift)
77

88
> warning ""
9-
> This plugin simply adds session data for OptimizelyFullStack, and events are sent via Cloud Mode.
9+
> This plugin simply adds session data for OptimizelyFullStack, and events are sent using Cloud Mode.
1010
11-
## Getting Started
11+
## Getting started
1212

1313
1. In your Segment source dashboard, enable the "Optimizely Full Stack" destination (*not the "Optimizely Web" destination*).
1414
2. Include your Optimizely project's `datafile` URL in your Segment settings.
@@ -18,14 +18,16 @@ Add OptimizelyFullStack session tracking support to your applications via this p
1818

1919
## Adding the dependency
2020

21-
### via Xcode
22-
In the Xcode `File` menu, click `Add Packages`. You'll see a dialog where you can search for Swift packages. In the search field, enter the URL to this repo.
21+
### Using Xcode
22+
In the Xcode `File` menu, click `Add Packages`. You'll see a dialog where you can search for Swift packages. In the search field, enter the URL to this repo:
2323

24+
```
2425
https://github.com/segment-integrations/analytics-swift-integration-optimizely-full-stack
26+
```
2527

2628
You'll then have the option to pin to a version, or specific branch, as well as which project in your workspace to add it to. Once you've made your selections, click the `Add Package` button.
2729

28-
### via Package.swift
30+
### Using Package.swift
2931

3032
Open your Package.swift file and add the following do your the `dependencies` section:
3133

@@ -55,9 +57,10 @@ let analytics = Analytics(configuration: Configuration(writeKey: "<YOUR WRITE KE
5557
.trackApplicationLifecycleEvents(true))
5658
analytics.add(plugin: OptimizelyFullStack(optimizelyKey: "<Optimizely Production Key>"))
5759
```
58-
Please Note : Here "optimizelyKey" you can get from Optimizely Dashboard Settings. You can use development or production SDK key respectively.
60+
> info ""
61+
> Generate your `optimizelyKey` from the Optimizely Dashboard Settings. You can use a development or production SDK key.
5962
60-
Your events will now be given OptimizelyFullStack session data and start flowing to OptimizelyFullStack via Cloud Mode.
63+
Your events will now be given OptimizelyFullStack session data and start flowing to OptimizelyFullStack in Cloud Mode.
6164

6265

6366
### Track
@@ -74,7 +77,7 @@ Segment also handles the following mapping:
7477
`revenue` values should be passed as a Segment `property`. The value should be an integer and represent the value in cents, so, for example, $1 should be represented by `100`.
7578

7679
> note ""
77-
> **Note:** [Custom Event Tags](https://docs.developers.optimizely.com/full-stack/docs/include-event-tags) in Optimizely, which include all Event Tags except `revenue` and `value`, are not displayed on the Optimizely results page, however they are available in a [Data Export](https://docs.developers.optimizely.com/web/docs/data-export) report. Event Tags can be strings, integers, floating point numbers, or boolean values. Optimizely rejects events with any other data types (for example, arrays).
80+
> **Note:** [Custom Event Tags](https://docs.developers.optimizely.com/full-stack/docs/include-event-tags){:target="_blank”} in Optimizely, which include all Event Tags except `revenue` and `value`, are not displayed on the Optimizely results page, however they are available in a [Data Export](https://docs.developers.optimizely.com/web/docs/data-export){:target="_blank”} report. Event Tags can be strings, integers, floating point numbers, or boolean values. Optimizely rejects events with any other data types (for example, arrays).
7881
7982
Segment defaults to identifying users with their `anonymousId`. Enabling "Use User ID" setting in your Segment dashboard means that only `track` events triggered by identified users are passed downstream to Optimizely. You may optionally fall back to `anonymousId` when `userId` is unavailable by setting `fallbackToAnonymousId` to `true`.
8083

@@ -84,14 +87,14 @@ Invoking a Segment `identify` event sets Segment `traits` as Optimizely `attribu
8487

8588
### Notification Listeners
8689

87-
Notification listeners are not available for Segment `track` events when implementing Optimizely using Segment using cloud-mode. [Notification listeners](https://docs.developers.optimizely.com/full-stack/docs/notification-listeners) are still available with any native call invoked from your Optimizely client instance.
90+
Notification listeners are not available for Segment `track` events when implementing Optimizely using Segment using cloud-mode. [Notification listeners](https://docs.developers.optimizely.com/full-stack/docs/notification-listeners){:target="_blank”} are still available with any native call invoked from your Optimizely client instance.
8891

8992
## Engage
9093

9194
Follow these instructions on how to set up Engage and Optimizely:
9295

93-
* [Using Segment Personas and Optimizely Full Stack for Omnichannel Experiments](https://www.optimizely.com/insights/blog/segment-personas-optimizely-full-stack-omnichannel-experiments/){:target="_blank"}
96+
[Using Segment Personas and Optimizely Full Stack for Omnichannel Experiments](https://www.optimizely.com/insights/blog/segment-personas-optimizely-full-stack-omnichannel-experiments/){:target="_blank"}
9497

9598

9699
## GDPR Support
97-
Segment supports deleting/suppressing users in Optimizely using the [Segment app](/docs/privacy/user-deletion-and-suppression/). In order to do this however, you will need to create a [Personal Access Token](https://developers.optimizely.com/x/authentication/personal-token/) in Optimizely and provide it as the value of the Access Token setting.
100+
Segment supports deleting/suppressing users in Optimizely using the [Segment app](/docs/privacy/user-deletion-and-suppression/). In order to do this however, you will need to create a [Personal Access Token](https://developers.optimizely.com/x/authentication/personal-token/){:target="_blank”} in Optimizely and provide it as the value of the Access Token setting.

src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/quantcast-swift.md

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,20 @@
11
---
2-
title: Analytics Swift Optimizely Full Stack Plugin
2+
title: Analytics Swift Quantcast Plugin
33
strat: swift
44
---
55

66
## Adding the dependency
77

8-
### via Xcode
9-
In the Xcode `File` menu, click `Add Packages`. You'll see a dialog where you can search for Swift packages. In the search field, enter the URL to this repo.
8+
### Using Xcode
9+
In the Xcode `File` menu, click `Add Packages`. You'll see a dialog where you can search for Swift packages. In the search field, enter the URL to the following repo:
1010

11+
```
1112
https://github.com/segment-integrations/analytics-swift-integration-quantcast
13+
```
1214

1315
You'll then have the option to pin to a version, or specific branch, as well as which project in your workspace to add it to. Once you've made your selections, click the `Add Package` button.
1416

15-
### via Package.swift
17+
### Using Package.swift
1618

1719
Open your Package.swift file and add the following do your the `dependencies` section:
1820

@@ -42,4 +44,4 @@ let analytics = Analytics(configuration: Configuration(writeKey: "<YOUR WRITE KE
4244
.trackApplicationLifecycleEvents(true))
4345
analytics.add(plugin: QuantcastDestination())
4446
```
45-
Your events will now be given to Adobe session data and start flowing to Adobe via Cloud Mode.
47+
Your events will now be given Adobe session data and start flowing to Adobe in Cloud Mode.

0 commit comments

Comments
 (0)