Houseware Destination

Houseware helps teams to generate actionable sales/conversion touchpoints in the user journeys to clock more revenue.

This destination is maintained by Houseware. For any issues with the destination, contact the Houseware Support team.

Getting Started

1. From the Destinations catalog page in the Segment App, click Add Destination.
2. Search for “Houseware” in the Destinations Catalog, and select the Houseware destination.
3. Choose which Source should send data to the “Houseware” destination.
4. Write an email to Houseware Support team and we will get back to you with an API Key in under 24 hours.
5. Enter the “API Key” in the “Houseware” destination settings in Segment.

After you authorize Segment to send events to Houseware, you can create rules in Warehouse based on the event data.

Supported methods

Houseware supports the following methods, as specified in the Segment Spec.

Page

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('Home')

Segment sends Page calls to Houseware as a pageview.

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 Houseware as an identify event.

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 Houseware as a track event.

Support

If you have any trouble with configuring your API Key, or see issues in your event delivery logs on Segment, feel free to reach out to our Houseware Support team.

Engage

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.

Settings

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