|
| 1 | +title: Antavo Source |
| 2 | + |
| 3 | +[Antavo](http://www.antavo.com){:target="_blank”} allows you to synchronize loyalty events and profile updates into |
| 4 | +Segment. |
| 5 | + |
| 6 | +The Antavo Source allows you to sync profile updates and loyalty events into Segment Destination apps and Segment |
| 7 | +warehouse. |
| 8 | + |
| 9 | +This source is maintained by Antavo. For any issues with the |
| 10 | +source, [contact the Antavo support team ](mailto:[email protected]). |
| 11 | + |
| 12 | +## Getting started |
| 13 | + |
| 14 | +1. From your workspace's Sources catalog page click `Add Source`. |
| 15 | +2. Search for "Antavo" in the Sources Catalog, select Antavo, and click Add Source. |
| 16 | +3. On the next screen, you can name the Source (e.g., Antavo or Loyalty Engine). |
| 17 | + 1. The name is used as a label in the Segment app, and Segment creates a related schema name in your warehouse. |
| 18 | + 2. The name can be anything, but we recommend using something that reflects the source and distinguishes amongst your |
| 19 | + 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 |
| 27 | + syncing events. |
| 28 | + |
| 29 | +  |
| 30 | +9. Go to the Outbound settings page and select: |
| 31 | + - The events you want to sync to Segment |
| 32 | + - The customer attribute updates you want to sync to Segment. |
| 33 | + |
| 34 | +  |
| 35 | + |
| 36 | +## Events |
| 37 | + |
| 38 | +Two main event types are synced into Segment: Profile updates and loyalty events. Both event types require userID, which |
| 39 | +can be selected in Antavo. Any customer attribute in Antavo can be selected as “external customer ID.” |
| 40 | + |
| 41 | +### Profile updates |
| 42 | + |
| 43 | +This event happens when a customer attribute - added to the **Customer field sync** - changes. |
| 44 | + |
| 45 | +Antavo always includes the `userId`. Customer attributes are included in `traits` object. |
| 46 | + |
| 47 | +``` |
| 48 | +{ |
| 49 | + "traits": { |
| 50 | + "first_name": "New", |
| 51 | + "last_name": "Name", |
| 52 | + }, |
| 53 | + "userId": "antavo-customer-id", |
| 54 | + "timestamp": "2024-11-26T15:19:14.000Z", |
| 55 | + "type": "identify", |
| 56 | +} |
| 57 | +``` |
| 58 | + |
| 59 | +### Loyalty events |
| 60 | + |
| 61 | +When a built-in or custom loyalty event - added to the **Event sync** - happens, event data are streamlined to the |
| 62 | +Antavo Source. |
| 63 | + |
| 64 | +Antavo always includes the `userId`. Event properties are included in `properties` object. |
| 65 | + |
| 66 | +``` |
| 67 | +{ |
| 68 | + "properties": { |
| 69 | + "points": 5000 |
| 70 | + }, |
| 71 | + "type": "track", |
| 72 | + "event": "point_add", |
| 73 | + "userId": "antavo-customer-id", |
| 74 | + "timestamp": "2024-11-26T15:15:49.000Z", |
| 75 | +} |
| 76 | +``` |
| 77 | + |
| 78 | +## Adding Destinations |
| 79 | + |
| 80 | +As the last step of the Antavo Source setup, you can select Destinations to receive data. |
| 81 | + |
| 82 | +Log into your downstream tools and check to see that your events appear as expected, and that they contain all of the |
| 83 | +properties you expect. If your events and properties don’t appear, check |
| 84 | +the [Event Delivery](https://github.com/segmentio/segment-docs/blob/develop/docs/connections/event-delivery){:target="_ |
| 85 | +blank”} tool, and refer to the Destination docs for each tool for troubleshooting. |
| 86 | + |
| 87 | +If there are any issues with how the events are arriving to |
| 88 | +Segment, [contact the Antavo support team ](mailto:[email protected]). |
0 commit comments