From 569aae96e2ef6fe63e71b24aa49bafa8057818bf Mon Sep 17 00:00:00 2001 From: Jazma Foskin <82051355+jfoskin@users.noreply.github.com> Date: Tue, 1 Aug 2023 21:00:27 -0400 Subject: [PATCH 1/3] Clarity in Adobe eVar --- .../destinations/catalog/adobe-analytics/settings.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/src/connections/destinations/catalog/adobe-analytics/settings.md b/src/connections/destinations/catalog/adobe-analytics/settings.md index 622ff5f99b..0896e8bac4 100644 --- a/src/connections/destinations/catalog/adobe-analytics/settings.md +++ b/src/connections/destinations/catalog/adobe-analytics/settings.md @@ -333,6 +333,9 @@ You must configure an eVar mapping in your Segment destination settings to send An example eVar mapping in the Segment Destination settings UI should look like this: ![A screenshot of the Adobe Analytics settings page in Segment, with the Mappings section selected and two sample mappings under the eVars tab.](/docs/connections/destinations/catalog/adobe-analytics/images/eVar-mapping.png) +>info "" +> Please note, only properties can be mapped to Adobe eVar properties. So for example, you could map the following properties to Adobe: path, referrer, search, signup_mode, title and url + ## Merchandising events The Merchandising Events setting allows you to set eVars and events on a per-product basis within the "products" string, and supports increment and currency events. This provides robust product string support, which you can read more about [in the Adobe Analytics Compontents guide](https://marketing.adobe.com/resources/help/en_US/sc/implement/products.html). From 9c534ca2c9568c42feb2ab16ad1745d0f7f22aeb Mon Sep 17 00:00:00 2001 From: Jazma Foskin <82051355+jfoskin@users.noreply.github.com> Date: Wed, 20 Sep 2023 12:00:50 -0400 Subject: [PATCH 2/3] Adding images to help explain mappings.md --- .../destinations/catalog/adobe-analytics/settings.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/src/connections/destinations/catalog/adobe-analytics/settings.md b/src/connections/destinations/catalog/adobe-analytics/settings.md index 0896e8bac4..31cdcd0797 100644 --- a/src/connections/destinations/catalog/adobe-analytics/settings.md +++ b/src/connections/destinations/catalog/adobe-analytics/settings.md @@ -335,6 +335,11 @@ An example eVar mapping in the Segment Destination settings UI should look like >info "" > Please note, only properties can be mapped to Adobe eVar properties. So for example, you could map the following properties to Adobe: path, referrer, search, signup_mode, title and url +>![Adobe evar](https://github.com/segmentio/segment-docs/assets/82051355/999b398a-f752-47f6-8511-9b2ec866cbae) +>![adobe mapping](https://github.com/segmentio/segment-docs/assets/82051355/c22eb82d-c9cd-4a2a-b216-b9b36569a606) + + + ## Merchandising events From 0e6ba7a86d61ad667598ff185d207a84128dc587 Mon Sep 17 00:00:00 2001 From: pwseg <86626706+pwseg@users.noreply.github.com> Date: Thu, 5 Oct 2023 11:44:36 -0500 Subject: [PATCH 3/3] Fix callout --- .../destinations/catalog/adobe-analytics/settings.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/connections/destinations/catalog/adobe-analytics/settings.md b/src/connections/destinations/catalog/adobe-analytics/settings.md index 31cdcd0797..2334095bb0 100644 --- a/src/connections/destinations/catalog/adobe-analytics/settings.md +++ b/src/connections/destinations/catalog/adobe-analytics/settings.md @@ -333,8 +333,8 @@ You must configure an eVar mapping in your Segment destination settings to send An example eVar mapping in the Segment Destination settings UI should look like this: ![A screenshot of the Adobe Analytics settings page in Segment, with the Mappings section selected and two sample mappings under the eVars tab.](/docs/connections/destinations/catalog/adobe-analytics/images/eVar-mapping.png) ->info "" -> Please note, only properties can be mapped to Adobe eVar properties. So for example, you could map the following properties to Adobe: path, referrer, search, signup_mode, title and url +You can only map properties to Adobe eVar properties. For example, you could map the following properties to Adobe: `path`, `referrer`, `search`, `signup_mode`, `title` and `url`. + >![Adobe evar](https://github.com/segmentio/segment-docs/assets/82051355/999b398a-f752-47f6-8511-9b2ec866cbae) >![adobe mapping](https://github.com/segmentio/segment-docs/assets/82051355/c22eb82d-c9cd-4a2a-b216-b9b36569a606)