Skip to content

Commit aa5d6e3

Browse files
authored
Got rid of last sentence
1 parent fae3f47 commit aa5d6e3

File tree

1 file changed

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

1 file changed

+1
-3
lines changed

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

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -64,12 +64,10 @@ Segment also handles the following mapping:
6464
6565
### Page
6666

67-
Segment maps Page calls to it `track` events. When you call `analytics.page('<name>')`, Segment automatically converts it into a Track call with the formatted event name `Viewed <name> Page`. For example, `analytics.page('Home');` becomes `analytics.track('Viewed Home Page');`.
67+
Segment maps Page calls to its `track` events. When you call `analytics.page('<name>')`, Segment automatically converts it into a Track call with the formatted event name `Viewed <name> Page`. For example, `analytics.page('Home');` becomes `analytics.track('Viewed Home Page');`.
6868

6969
This event is then forwarded to Optimizely as a custom event named `Viewed Home Page`. To capture this event in Optimizely, you’ll need to define a Custom Event with the matching API name.
7070

71-
Segment maps the `page` event to other downstream destinations like a regular Segment `page` event.
72-
7371
### Experiment Listeners
7472

7573
Upon activation of an Optimizely experiment, an “Experiment Viewed” Track event is sent to Segment. The event includes Optimizely experiment metadata which is sent whenever the Optimizely [`campaignDecided` listener](https://docs.developers.optimizely.com/web/docs/add-listener#section-campaign-decided){:target="_blank"} is activated.

0 commit comments

Comments
 (0)