Digioh Destination
Digioh quick info
Digioh is in beta, and accepts Track, and Identify calls. If you reference it in the Integrations object, call it “Digioh”.
Digioh allows you to grow your email lists with personalized forms, landing pages, paywalls and email preference centers. Digioh makes it easy with a drag and drop builder and built-in integrations to your favorite marketing tools.
This destination is maintained by Digioh. For any issues with the destination, contact the Digioh Support team.
Getting Started
- From the Destinations catalog page in the Segment App, click Add Destination.
- Search for “Digioh” in the Destinations Catalog, and select the Digioh destination.
- Choose which Source should send data to the Digioh destination.
- Go to the Digioh dashboard, find and copy the “API key” parameter in your
<script>
tag.<script async type='text/javascript' src='https://www.lightboxcdn.com/vendor/API_KEY/lightbox_inline.js'></script>
- Enter the “API Key” and your Digioh account email in the Digioh destination settings in Segment.
Identify
If you aren’t familiar with the Segment Spec, take a look at the Identify method documentation to learn about what it does. An example call would look like:
analytics.identify('userId123', {
email: 'john.doe@example.com'
});
Segment sends Identify calls to Digioh as an identify
event.
The email
field is required. Identify calls without an email
fail with a 400
code.
Track
If you aren’t familiar with the Segment Spec, take a look at the Track method documentation to learn about what it does. An example call would look like:
analytics.track('Login Button Clicked')
Segment sends Track calls to Digioh as a track
event.
Be sure you send an Identify call for any user who will trigger Track calls. If Digioh receives a Track call for an unknown userId
, the call is dropped.
Personas
You can send computed traits and audiences generated using Segment Personas to this destination as a user property. To learn more about Personas, contact us for a demo.
For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Personas sends an Identify call with the property order_completed_last_30days: true
. When the user no longer satisfies this condition (for example, it’s been more than 30 days since their last order), Personas sets that value to false
.
When you first create an audience, Personas sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.
Settings
Segment lets you change these destination settings from the Segment app without having to touch any code.
API Key
The API Key is your Vendor GUID, located under Digioh Setup Instructions
Digioh Account Email
Please enter your Digioh account email
This page was last modified: 20 Apr 2021
Need support?
Questions? Problems? Need more info? Contact us, and we can help!