diff --git a/src/_layouts/integration.html b/src/_layouts/integration.html
index 008de2e673..8c709214a1 100644
--- a/src/_layouts/integration.html
+++ b/src/_layouts/integration.html
@@ -36,6 +36,7 @@
{{ page.title }}
{%- endif -%}
+
{%- if page.excerpt -%}
+
+
+
+ {%- unless page.hide_toc -%}
+ {% include sidebar/mobile-menu-side.html %}
+ {%- endunless -%}
{{ content }}
diff --git a/src/_sass/pages/_integration.scss b/src/_sass/pages/_integration.scss
index af0e5f381f..20b7893a08 100644
--- a/src/_sass/pages/_integration.scss
+++ b/src/_sass/pages/_integration.scss
@@ -6,21 +6,10 @@
}
&__body {
- margin-top: 70px;
+ margin-top: 30px;
- & > h2 {
- margin-top: 70px;
- position: relative;
-
- &::after {
- height: 1px;
- width: 100%;
- position: absolute;
- top: -35px;
- left: 0;
- background-color: rgba(color(secondary), 0.16);
- content: "";
- }
+ @include breakpoint(large up) {
+ margin-top: 50px;
}
}
}
diff --git a/src/connections/destinations/catalog/optimizely-web/index.md b/src/connections/destinations/catalog/optimizely-web/index.md
index e95b9b8360..9e70e5b2ce 100644
--- a/src/connections/destinations/catalog/optimizely-web/index.md
+++ b/src/connections/destinations/catalog/optimizely-web/index.md
@@ -25,6 +25,8 @@ If you’re interested in implementing Optimizely Full Stack server-side or on m
* [Use Optimizely to A/B test which CTAs lead to more signups](https://segment.com/recipes/ab-test-cta-signups-optimizely/)
* [Test which call to action (CTA) results in more shopping cart conversions with Optimizely](https://segment.com/recipes/ab-test-cta-conversions-optimizely/)
+---
+
## Implementation Prerequisite
Optimizely works differently than other Segment destinations: It requires that customers implement at least some Optimizely functionalities natively.
@@ -35,6 +37,8 @@ This limitation requires that customers include a native Optimizely snippet or i
Segment provides specific implementation details for each Optimizely product in the sections below, in addition to details of the out-of-the-box mappings Segment's Optimizely component handles for Optimizely users.
+---
+
## Optimizely Classic Web
### Getting Started
@@ -161,6 +165,8 @@ analytics.identify({
If you run multiple experiments during a user session, since `traits` are cached, subsequent experiments would fire `identify` calls that contain previous experiment data.
+---
+
## Optimizely Classic Android
{% capture noteAndroid %}
@@ -210,6 +216,8 @@ Upon an Optimizely experiment activation, Segment’s Optimizely Classic<>Androi
.putValue("variationName", optimizelyExperimentData.variationName));
```
+---
+
## Optimizely Classic iOS
{% capture noteIOS %}
@@ -227,7 +235,7 @@ For Segment’s Optimizely Full Stack iOS destination, see Segment's [Optimizely
{% include components/list-steps.html number="5" content="Instantiate Segment’s global Analytics object with an Optimizely factory registered:" %}
```objc
- [config use:[SEGOptimizelyIntegrationFactory instanceWithToken: /* your Optimizely project id /* launchOptions:launchOptions]];
+ [config use:[SEGOptimizelyIntegrationFactory instanceWithToken: /* your Optimizely project id */ launchOptions:launchOptions]];
```
Since Optimizely needs to be initialized as early as possible, you need to supply the Optimizely `projectId` when you initialize the factory registered with the analytics client. Once registered, Segment maps `track` and `identify` to Optimizely.
@@ -263,6 +271,8 @@ Upon an Optimizely experiment activation, Segment’s Optimizely Classic<>iOS SD
}];
```
+---
+
## Optimizely X Web
### Getting Started
@@ -363,6 +373,8 @@ If you’re sending your experiments to Google Analytics in the form of `track`

+---
+
## Optimizely Full Stack (JavaScript)
### Getting Started
@@ -407,6 +419,8 @@ If you are sending anonymous data to Optimizely X Full Stack via their server-si
});
```
+---
+
## Troubleshooting
### No Data for Anonymous Users