Skip to content

Commit c9a8d7e

Browse files
author
markzegarelli
committed
add ajs2 upgrade note
1 parent 644245e commit c9a8d7e

File tree

8 files changed

+17
-0
lines changed

8 files changed

+17
-0
lines changed

src/_includes/content/ajs-upgrade.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
<div class="premonition success"><div class="fa fa-check-square"></div><div class="content"><p class="header">Upgrade to Analytics.js 2.0</p>
2+
<p markdown=1>Actions-based destinations require features found in [Analytics.js 2.0](/docs/connections/sources/catalog/libraries/website/javascript/). [Upgrade your Analytics.js](/docs/connections/sources/catalog/libraries/website/javascript/upgrade-to-ajs2/) source to take advantage of Actions-based destinations, performance improvements, and more.</p>
3+
</div></div>

src/connections/destinations/actions.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,9 @@ You can also choose which event types, event names, or event property values tri
1414

1515
Each Actions-framework Destination you see in the Segment catalog represents a feature or capability of the destination which can consume data from your Segment source. The Action clearly lists which data from the events it requires, and which data is optional. For example, Amplitude requires that you always send a `LogEvent` , or Slack always requires a `PostMessage`. Each Action also includes a default mapping which you can modify.
1616

17+
{% include content/ajs-upgrade.md %}
18+
19+
1720
## Benefits of Destination Actions
1821

1922
- **Easier setup**: Users see fewer initial settings which can decrease the time spent configuring the destination.

src/connections/destinations/catalog/actions-amplitude/index.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -27,6 +27,8 @@ Amplitude (Actions) provides the following benefits over the classic Amplitude d
2727
- **Session tracking in cloud-mode**. Amplitude (Actions) supports sending session details from cloud-mode sources.
2828

2929
## Getting started
30+
{% include content/ajs-upgrade.md %}
31+
3032

3133
1. Before you start, go to your [Amplitude workspace](https://analytics.amplitude.com){:target="_blank"}. Click **Settings** in the bottom left, then click **Projects** in the left menu. Select your **Project**. Copy the Amplitude API Key and Secret Key for the project.
3234
2. From the Segment web app, click **Catalog**, then click **Destinations**.

src/connections/destinations/catalog/actions-braze-cloud/index.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,7 @@ Braze Cloud Mode (Actions) provides the following benefit over Braze Classic:
2323
- **E-commerce mappings**. Segment implementations that don't follow the e-commerce spec due to incompatible event names (for example, Trip Booked vs Order Completed) can use Event Triggers to log purchases in Braze Cloud Mode (Actions).
2424

2525
## Getting Started
26+
{% include content/ajs-upgrade.md %}
2627

2728
1. From the Segment web app, click **Catalog**.
2829
2. Search for "Braze" in the Catalog, select **Braze Cloud Mode (Actions)**, and choose which of your sources to connect the destination to.

src/connections/destinations/catalog/actions-braze-web/index.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,8 @@ Braze Web Mode (Actions) provides the following benefits over Braze Classic:
2323
- **E-commerce mappings**. Users who can't follow the e-commerce spec due to incompatible event names (for example, Trip Booked vs Order Completed) can log purchases in Braze Web Mode (Actions).
2424

2525
## Getting Started
26+
{% include content/ajs-upgrade.md %}
27+
2628

2729
1. From the Segment web app, click **Catalog**.
2830
2. Search for "Braze" in the Catalog, select **Braze Web Mode (Actions)**, and choose which of your sources to connect the destination to.

src/connections/destinations/catalog/actions-customer-io/index.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,8 @@ redirect_from:
2323
- **Track an anonymous event**. Track events from users who are not yet known to Customer.io. If you have the Customer.io *event merging* feature enabled, Customer.io associates all incoming events that share an `anonymous_id` received in the last 30 days.
2424

2525
## Getting started
26+
{% include content/ajs-upgrade.md %}
27+
2628

2729
1. From the Segment web app, click **Catalog**, then click **Destinations**.
2830
2. Find the Destinations Actions item in the left navigation, and click it.

src/connections/destinations/catalog/actions-fullstory/index.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,8 @@ hide-dossier: true
1717

1818

1919
## Getting started
20+
{% include content/ajs-upgrade.md %}
21+
2022

2123
1. From the Segment web app, click **Catalog**, then click **Destinations**.
2224
2. Find the Destinations Actions item in the left navigation, and click it.

src/connections/destinations/catalog/actions-slack/index.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,8 @@ Slack (Actions) provides the following benefits over the classic Slack destinati
2424

2525

2626
## Getting Started
27+
{% include content/ajs-upgrade.md %}
28+
2729

2830
1. From the Segment web app, click **Catalog**, then click **Destinations**.
2931
2. Find the Destinations Actions item in the left navigation, and click it.

0 commit comments

Comments
 (0)