Vespucci Destination

1. From the Destinations catalog page in the Segment App, click Add Destination.
2. Search for "Vespucci" in the Destinations Catalog, and select the Vespucci destination.
3. Choose which Source should send data to the Vespucci destination.
4. Go to your "Your Active Projects" section on your Vespucci Dashboard. Click on the + button. Enter a name and select "Segment Destination" as the DataPipe.
5. Depending on your project configuration, select one of the two tracking methods and click "Create" to create your project.
6. Take note of the API key associated with this project. Back in the Segment App, enter your API key in the Vespucci destination settings.

If you aren't familiar with the Segment Spec, take a look at the Page method documentation to learn about what it does. An example call would look like:

analytics.page()

Segment sends Page calls to Vespucci as a screen.

If you aren't familiar with the Segment Spec, take a look at the Screen method documentation to learn about what it does. An example call would look like:

[[SEGAnalytics sharedAnalytics] screen:@"Home"];

Segment sends Screen calls to Vespucci as a screen.

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:

1
analytics.identify('userId123', {
2
  email: 'john.doe@example.com'
3
});

Segment sends Identify calls to Vespucci as an identify event.

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 Vespucci as an action event.

You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule 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, Engage 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), Engage sets that value to false.

When you first create an audience, Engage 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.

Segment lets you change these destination settings from the Segment app without having to touch any code.