Skip to content

Commit df45eb9

Browse files
author
markzegarelli
authored
Merge pull request #1358 from segmentio/James9446-evergage-deprecation
Deprecate Evergage
2 parents d0431ae + 518e638 commit df45eb9

File tree

1 file changed

+4
-10
lines changed
  • src/connections/destinations/catalog/evergage

1 file changed

+4
-10
lines changed

src/connections/destinations/catalog/evergage/index.md

Lines changed: 4 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -5,16 +5,10 @@ rewrite: true
55

66
[Evergage](https://www.evergage.com/) offers a cloud-based platform that empowers digital marketers to increase engagement and conversions through real-time 1:1 personalization. The `analytics.js` Evergage Destination is open-source. You can browse the code [on GitHub](https://github.com/segment-integrations/analytics.js-integration-evergage).
77

8-
This document was last updated on October 29, 2018. If you notice any gaps, out-dated information or simply want to leave some feedback to help us improve our documentation, [let us know](https://segment.com/help/contact)!
8+
This document was last updated on January 8, 2021.
99

10-
## Getting Started
11-
12-
{% include content/connection-modes.md %}
13-
14-
1. From the Segment web app, click **Catalog**.
15-
2. Search for "Evergage" in the Catalog, select it, and choose which of your sources to connect the destination to.
16-
3. Enter your Evergage Account Key (this is the subdomain you use to login to Evergage with; if your account is "testaccount.evergage.com", then use "testaccount");
17-
4. Finally, enter the name of the Evergage Dataset you want data to flow to (by default this is "engage");
10+
> warning "The Evergage destination has been deprecated"
11+
> The Evergage Destination was deprecated on January 8, 2021 and is no longer supported or maintained. It is no longer available in the Segment catalog, but remains available to existing users.
1812
1913
## Identify
2014
If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like:
@@ -40,7 +34,7 @@ analytics.group('companyId123', {
4034
A `groupId` is required on all `group` calls sent to {{ integration.name}}. When you call `group` Segment will call both `setCompany` and `setAccountField` in the [Evergage library](https://doc.evergage.com/display/EKB/Send+Data+to+Evergage) to insert both the `groupId` and corresponding group traits into {{ integration.name}}.
4135

4236
## Track
43-
If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like:
37+
If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like:
4438

4539
```javascript
4640
analytics.track('Email Opened', {

0 commit comments

Comments
 (0)