Skip to content

Override the Drip destination connection modes #2813

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 28, 2022
Merged

Override the Drip destination connection modes #2813

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions src/_data/catalog/overrides.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,18 @@
# This file is manually generated. When you add or remove an item, add or remove
# it from the `overrides-list.yml` too.
items:
- slug: drip
id: 54521fd525e721e32a72eeaa
connection_modes:
device:
web: true
mobile: true
server: false
cloud:
web: false
mobile: true
server: true

- slug: clevertap
id: 5711271880412f644ff13150
connection_modes:
Expand Down
7 changes: 4 additions & 3 deletions src/connections/destinations/catalog/drip/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,8 +1,9 @@
---
title: Drip Destination
id: 54521fd525e721e32a72eeaa
cmode-override: true
---
Our Drip destination code is all open-source on GitHub if you want to check it out: [Javascript](https://github.com/segment-integrations/analytics.js-integration-drip),(iOS and Android work using the server destination).
The Drip destination code is all open-source on GitHub if you want to check it out: [Javascript](https://github.com/segment-integrations/analytics.js-integration-drip),(iOS and Android work using the server destination).

## Getting Started

Expand All @@ -11,11 +12,11 @@ When you enable Drip in the Segment web app, your changes appear in the Segment

## Identify

When you call [`identify`](/docs/connections/spec/identify/) on analytics.js, we call [`identify`](/docs/connections/spec/identify/) on Drip and pass through all of the user traits that were included on that call. You must pass email as a trait to identify the user to Drip. Note that if you want to do cross-domain tracking, after you've enabled it in the Drip UI, you'll need to pass `email` as a trait on the identify call on both domains.
When you call [`identify`](/docs/connections/spec/identify/) on analytics.js, Segment calls [`identify`](/docs/connections/spec/identify/) on Drip and passes through all of the user traits that were included on that call. You must pass email as a trait to identify the user to Drip. Note that if you want to do cross-domain tracking, after you've enabled it in the Drip UI, you'll need to pass `email` as a trait on the identify call on both domains.

## Track

When you call [`track`](/docs/connections/spec/track/), we'll send the event to Drip with the event `name` and all `properties` that you specified. If you include `revenue` as a property, it will get passed to Drip as the conversion value of this event.
When you call [`track`](/docs/connections/spec/track/), Segment sends the event to Drip with the event `name` and all `properties` that you specified. If you include `revenue` as a property, it will get passed to Drip as the conversion value of this event.

**Note:**
- If you are sending custom server side events, you must include an `email` property of the user that the event belongs to.
Expand Down