From 2e7fadc2a126292079a2e0a6c5a65d3d61e92edd Mon Sep 17 00:00:00 2001 From: Sharon Adewusi Date: Wed, 6 Aug 2025 19:41:34 +0100 Subject: [PATCH 1/3] Clarifying how Page events are sent to Optimizely --- src/connections/destinations/catalog/optimizely-web/index.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/src/connections/destinations/catalog/optimizely-web/index.md b/src/connections/destinations/catalog/optimizely-web/index.md index db6ffc7eef..fadb1ba94e 100644 --- a/src/connections/destinations/catalog/optimizely-web/index.md +++ b/src/connections/destinations/catalog/optimizely-web/index.md @@ -64,13 +64,14 @@ Segment also handles the following mapping: ### Page -Segment maps `page` calls to its own `track` events. For example, invoking `analytics.page('Page Viewed')` using Segment's API maps the event to a `analytics.track('Page Viewed')` event. Segment maps the `track` event to other downstream destinations like a regular Segment `track` event. +Segment maps `page` calls to its own `track` events. When you call `analytics.page('')`, Segment automatically converts it into a track call with the formatted event name `Viewed 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`. + +Segment maps the `page` event to other downstream destinations like a regular Segment `page` event. ### Experiment Listeners 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. - > info "Activating a Web experiment sends 'Experiment Viewed' Track events to Segment" > When you activate an Optimizely Web experiment, Optimizely automatically sends an "Experiment Viewed" Track event to Segment. This makes the Optimizely Web integration act as both a Destination and a Source, because the Track calls enrich and send Experiment Decisions and Exposure event data to Segment, which you can then send to other platforms. From fae3f4766788235aba7dbe78dc5549385a8a8416 Mon Sep 17 00:00:00 2001 From: Sharon Adewusi Date: Thu, 7 Aug 2025 14:23:28 +0100 Subject: [PATCH 2/3] Update src/connections/destinations/catalog/optimizely-web/index.md Co-authored-by: pwseg <86626706+pwseg@users.noreply.github.com> --- src/connections/destinations/catalog/optimizely-web/index.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/src/connections/destinations/catalog/optimizely-web/index.md b/src/connections/destinations/catalog/optimizely-web/index.md index fadb1ba94e..8525f4e1a6 100644 --- a/src/connections/destinations/catalog/optimizely-web/index.md +++ b/src/connections/destinations/catalog/optimizely-web/index.md @@ -64,7 +64,9 @@ Segment also handles the following mapping: ### Page -Segment maps `page` calls to its own `track` events. When you call `analytics.page('')`, Segment automatically converts it into a track call with the formatted event name `Viewed 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`. +Segment maps Page calls to it `track` events. When you call `analytics.page('')`, Segment automatically converts it into a Track call with the formatted event name `Viewed 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`. To capture this event in Optimizely, you’ll need to define a Custom Event with the matching API name. Segment maps the `page` event to other downstream destinations like a regular Segment `page` event. From aa5d6e3e70ae1efbe83527e59588856be8d45259 Mon Sep 17 00:00:00 2001 From: Sharon Adewusi Date: Thu, 7 Aug 2025 14:24:36 +0100 Subject: [PATCH 3/3] Got rid of last sentence --- src/connections/destinations/catalog/optimizely-web/index.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/src/connections/destinations/catalog/optimizely-web/index.md b/src/connections/destinations/catalog/optimizely-web/index.md index 8525f4e1a6..c203028a89 100644 --- a/src/connections/destinations/catalog/optimizely-web/index.md +++ b/src/connections/destinations/catalog/optimizely-web/index.md @@ -64,12 +64,10 @@ Segment also handles the following mapping: ### Page -Segment maps Page calls to it `track` events. When you call `analytics.page('')`, Segment automatically converts it into a Track call with the formatted event name `Viewed Page`. For example, `analytics.page('Home');` becomes `analytics.track('Viewed Home Page');`. +Segment maps Page calls to its `track` events. When you call `analytics.page('')`, Segment automatically converts it into a Track call with the formatted event name `Viewed 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`. To capture this event in Optimizely, you’ll need to define a Custom Event with the matching API name. -Segment maps the `page` event to other downstream destinations like a regular Segment `page` event. - ### Experiment Listeners 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.