|
| 1 | +--- |
| 2 | +title: Antavo Source |
| 3 | +id: WXNgKpZMsd |
| 4 | +--- |
| 5 | + |
| 6 | +[Antavo](http://www.antavo.com){:target="_blank"} allows you to synchronize loyalty events and profile updates into Segment. |
| 7 | + |
| 8 | +The Antavo Source allows you to sync profile updates and loyalty events into Segment Destination apps and Segment warehouse. |
| 9 | + |
| 10 | +This source is maintained by Antavo. For any issues with the |
| 11 | +source, [contact the Antavo support team ](mailto:[email protected]). |
| 12 | + |
| 13 | +## Getting started |
| 14 | + |
| 15 | +1. From your workspace's Sources catalog page click `Add Source`. |
| 16 | +2. Search for "Antavo" in the Sources Catalog, select Antavo, and click Add Source. |
| 17 | +3. On the next screen, you can name the Source (e.g. Antavo or Loyalty Engine). |
| 18 | + 1. The name is used as a label in the Segment app, and Segment creates a related schema name in your warehouse. |
| 19 | + 2. The name can be anything, but we recommend using something that reflects the source and distinguishes amongst your environments. |
| 20 | +4. Click Add Source to save your settings. |
| 21 | +5. Copy the Write key from the Segment UI. |
| 22 | +6. Log into your Antavo account. |
| 23 | +7. Select Twilio Segment integration in Antavo platform. |
| 24 | + |
| 25 | +  |
| 26 | +8. Insert the Segment write key and select which attribute contains the userID that will be used as User identifier when syncing events. |
| 27 | + |
| 28 | +  |
| 29 | +9. Go to the Outbound settings page and select: |
| 30 | + - The events you want to sync to Segment. |
| 31 | + - The customer attribute updates you want to sync to Segment. |
| 32 | + |
| 33 | +  |
| 34 | + |
| 35 | +## Events |
| 36 | + |
| 37 | +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. |
| 38 | + |
| 39 | +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`. |
| 40 | + |
| 41 | +### Profile updates |
| 42 | + |
| 43 | +Profile Updates occur when a customer attribute, added to the Antavo **Customer field sync**, updates. Customer attributes are included in the traits object. |
| 44 | + |
| 45 | +``` |
| 46 | +{ |
| 47 | + "traits": { |
| 48 | + "first_name": "New", |
| 49 | + "last_name": "Name", |
| 50 | + }, |
| 51 | + "userId": "antavo-customer-id", |
| 52 | + "timestamp": "2024-11-26T15:19:14.000Z", |
| 53 | + "type": "identify", |
| 54 | +} |
| 55 | +``` |
| 56 | + |
| 57 | +### Loyalty events |
| 58 | + |
| 59 | +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. |
| 60 | + |
| 61 | +``` |
| 62 | +{ |
| 63 | + "properties": { |
| 64 | + "points": 5000 |
| 65 | + }, |
| 66 | + "type": "track", |
| 67 | + "event": "point_add", |
| 68 | + "userId": "antavo-customer-id", |
| 69 | + "timestamp": "2024-11-26T15:15:49.000Z", |
| 70 | +} |
| 71 | +``` |
| 72 | + |
| 73 | +### Integrations Object |
| 74 | +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. |
| 75 | + |
| 76 | +## Adding Destinations |
| 77 | + |
| 78 | +As the last step of the Antavo Source setup, you can select Destinations to receive data. |
| 79 | + |
| 80 | +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. |
| 81 | + |
| 82 | +If there are any issues with how the events are arriving to Segment, [contact the Antavo support team ](mailto:[email protected]). |
0 commit comments