Skip to content

Commit 569aae9

Browse files
authored
Clarity in Adobe eVar
1 parent ccfb51d commit 569aae9

File tree

1 file changed

+3
-0
lines changed
  • src/connections/destinations/catalog/adobe-analytics

1 file changed

+3
-0
lines changed

src/connections/destinations/catalog/adobe-analytics/settings.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -333,6 +333,9 @@ You must configure an eVar mapping in your Segment destination settings to send
333333
An example eVar mapping in the Segment Destination settings UI should look like this:
334334
![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)
335335

336+
>info ""
337+
> 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
338+
336339
## Merchandising events
337340

338341
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).

0 commit comments

Comments
 (0)