Skip to content

Commit fae3f47

Browse files
sade-wusipwseg
andauthored
Update src/connections/destinations/catalog/optimizely-web/index.md
Co-authored-by: pwseg <[email protected]>
1 parent 2e7fadc commit fae3f47

File tree

1 file changed

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

1 file changed

+3
-1
lines changed

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

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -64,7 +64,9 @@ Segment also handles the following mapping:
6464
6565
### Page
6666

67-
Segment maps `page` calls to its own `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');`. This event is then forwarded to Optimizely as a custom event named `Viewed Home Page`.
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');`.
68+
69+
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.
6870

6971
Segment maps the `page` event to other downstream destinations like a regular Segment `page` event.
7072

0 commit comments

Comments
 (0)