-
Notifications
You must be signed in to change notification settings - Fork 381
Antavo Source documentation #7275
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.
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
Changes from all commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
db70413
antavo source docs
bbantavo d1a2e87
Merge branch 'develop' into antavo/source
bbantavo 1996e65
layout and typo fixes
bbantavo ae384f6
updated title
bbantavo 2dcce8c
quote character fix
bbantavo 3ca576d
updated texts
bbantavo 000144e
Merge pull request #4 from antavo/antavo/source-updates
bbantavo c0acc01
added id
bbantavo 08a2189
Merge pull request #5 from antavo/antavo/source-updates
bbantavo f7aaf48
updated title formatting
bbantavo b4774ce
updated index.md
bbantavo 81d888e
Merge pull request #7 from antavo/antavo/source-updates
bbantavo File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Binary file added
BIN
+220 KB
.../sources/catalog/cloud-apps/antavo/images/1-antavo-enable_segment_extension.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added
BIN
+193 KB
...urces/catalog/cloud-apps/antavo/images/2-antavo-configure_segment_extension.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added
BIN
+238 KB
...ions/sources/catalog/cloud-apps/antavo/images/3-antavo-configure_event_sync.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
82 changes: 82 additions & 0 deletions
82
src/connections/sources/catalog/cloud-apps/antavo/index.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,82 @@ | ||
--- | ||
title: Antavo Source | ||
id: WXNgKpZMsd | ||
--- | ||
|
||
[Antavo](http://www.antavo.com){:target="_blank"} allows you to synchronize loyalty events and profile updates into Segment. | ||
|
||
The Antavo Source allows you to sync profile updates and loyalty events into Segment Destination apps and Segment warehouse. | ||
|
||
This source is maintained by Antavo. For any issues with the | ||
source, [contact the Antavo support team](mailto:support@antavo.com). | ||
|
||
## Getting started | ||
|
||
1. From your workspace's Sources catalog page click `Add Source`. | ||
2. Search for "Antavo" in the Sources Catalog, select Antavo, and click Add Source. | ||
3. On the next screen, you can name the Source (e.g. Antavo or Loyalty Engine). | ||
1. The name is used as a label in the Segment app, and Segment creates a related schema name in your warehouse. | ||
2. The name can be anything, but we recommend using something that reflects the source and distinguishes amongst your environments. | ||
4. Click Add Source to save your settings. | ||
5. Copy the Write key from the Segment UI. | ||
6. Log into your Antavo account. | ||
7. Select Twilio Segment integration in Antavo platform. | ||
|
||
 | ||
8. Insert the Segment write key and select which attribute contains the userID that will be used as User identifier when syncing events. | ||
|
||
 | ||
9. Go to the Outbound settings page and select: | ||
- The events you want to sync to Segment. | ||
- The customer attribute updates you want to sync to Segment. | ||
|
||
 | ||
|
||
## Events | ||
|
||
Antavo syncs two main types of events to Segment: Profile Updates and Loyalty Events. Profile Updates are sent as Segment Identify events, while Loyalty Events are sent as Segment Track events. | ||
|
||
Both event types include a `userId`, which can be configured in Antavo. You can designate any customer attribute as the "external customer ID" to use as the Segment `userId`. | ||
|
||
### Profile updates | ||
|
||
Profile Updates occur when a customer attribute, added to the Antavo **Customer field sync**, updates. Customer attributes are included in the traits object. | ||
|
||
``` | ||
{ | ||
"traits": { | ||
"first_name": "New", | ||
"last_name": "Name", | ||
}, | ||
"userId": "antavo-customer-id", | ||
"timestamp": "2024-11-26T15:19:14.000Z", | ||
"type": "identify", | ||
} | ||
``` | ||
|
||
### Loyalty events | ||
|
||
Loyalty Events occur when a built-in or custom event, added to the Antavo Event sync, is triggered. The event data is then sent to the Segment Antavo Source. Event properties are included in the properties object. | ||
|
||
``` | ||
{ | ||
"properties": { | ||
"points": 5000 | ||
}, | ||
"type": "track", | ||
"event": "point_add", | ||
"userId": "antavo-customer-id", | ||
"timestamp": "2024-11-26T15:15:49.000Z", | ||
} | ||
``` | ||
|
||
### Integrations Object | ||
Antavo automatically filters data from being sent to Salesforce destinations ([Salesforce (Actions)](https://segment.com/docs/connections/destinations/catalog/actions-salesforce){:target="_blank"}, [Salesforce Marketing Cloud (Actions)](https://segment.com/docs/connections/destinations/catalog/actions-salesforce-marketing-cloud){:target="_blank"}) and the [Antavo](https://segment.com/docs/connections/destinations/catalog/antavo){:target="_blank"} destination. This is achieved by adding these destinations to the [Integrations object](https://segment.com/docs/guides/filtering-data/#filtering-with-the-integrations-object){:target="_blank"} in the event payloads. Since Antavo has a dedicated Salesforce integration, this filtering helps prevent infinite loops. | ||
|
||
## Adding Destinations | ||
|
||
As the last step of the Antavo Source setup, you can select Destinations to receive data. | ||
|
||
Log into your downstream tools and check to see that your events appear as expected, and that they contain all of the properties you expect. If your events and properties don’t appear, check the [Event Delivery](https://github.com/segmentio/segment-docs/blob/develop/docs/connections/event-delivery){:target="_blank"} tool, and refer to the Destination docs for each tool for troubleshooting. | ||
|
||
If there are any issues with how the events are arriving to Segment, [contact the Antavo support team](mailto:support@antavo.com). |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Integrations Object
Antavo automatically filters data from being sent to Salesforce destinations (Salesforce (Actions), Salesforce Marketing Cloud (Actions)) and the Antavo destination. This is achieved by adding these destinations to the Integrations object in the event payloads. Since Antavo has a dedicated Salesforce integration, this filtering helps prevent infinite loops.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hi @tcgilbert !
thanks for the suggestion! we'll apply it shortly
quick note: the links seems to be pointing to
github.com
domain (throwing 404s), but I'm guessing it should be tosegment.com
insteadThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @tcgilbert !
Updated this section, please check!