Skip to content

Commit c077ee6

Browse files
Update src/connections/destinations/catalog/optimizely-web/index.md
1 parent 015afee commit c077ee6

File tree

1 file changed

+1
-1
lines changed
  • src/connections/destinations/catalog/optimizely-web

1 file changed

+1
-1
lines changed

src/connections/destinations/catalog/optimizely-web/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -229,7 +229,7 @@ For example, let's say you run a redirect experiment on page `http://home.com` t
229229

230230
Our Optimizely Web destination detects this and send the effective referrer value as a property of the subsequent Experiment Viewed. Segment also overrides the `context.page.referrer` with the effective referrer.
231231

232-
More importantly, to send the true referrer value with the initial `page` call inside the Segment snippet, you can look up `window.optimizelyEffectiveReferrer`, and if it exists, you can pass that into your `page` call. This is how you might modify your Segment snippet to pass the extra code inside [ready()](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/#ready) so its only called after Optimizely SDK has finished loading:
232+
More importantly, to send the true referrer value with the initial `page` call inside the Segment snippet, you can look up `window.optimizelyEffectiveReferrer`, and if it exists, you can pass that into your `page` call. This is how you might modify your Segment snippet to pass the extra code inside [ready()](/docs/connections/sources/catalog/libraries/website/javascript/#ready) so its only called after Optimizely SDK has finished loading:
233233

234234
```javascript
235235
<script>

0 commit comments

Comments
 (0)