JourneyStream Events

Base URLs

Encodings

Text: JourneyStream utilizes the utf8 encoding scheme for all of its messages.

Dates: JourneyStream accepts dates in the ISO 8601 format in the form
YYYY-MM-DDTHH:MI:SS.000000Z. This means that your event dates need to be converted to UTC before sending to JourneyStream.

Field Definitions

event_type - The type of event being sent to the stream. Accepted values are interaction, conversion, metric, and association. This field is required.

organization_uuid - Your organization’s uuid. This will be provided to you upon activation of the JourneyStream product. In the meantime, you can throw any standard uuid at the sandbox… Just keep it static across your test messages for easy auditing by our customer success team. This field is required.

who_uuid - A unique identifier representing a person. While this field has UUID in the name, any string representing a unique person from your system is accepted here. This field is required.

who_type - A string representing the type of who_uuid being sent. This can be any text string, but should be consistent in case and space usage (e.g if the who_uuid is a hashed phone number, then always use phone_number not Phone Number, Phone_Number, phone, or Phone # in some places). This field is optional.

event_date_time - The datetime that your event occurred at. JourneyStream will add a captured_at to your payload allowing us to see the difference between the event time and the capture time. This field is required.

integration - A text field representing the source of your event. This can be any text string, but should be consistent in case and space usage (e.g always use my_crm not My CRM, my_CRM, my crm, etc). This field is required.

touchpoint_id - The touchpoint id associated with the event. This can obtained from the Strala TouchPoints app. This field is required for Touchpoint Interaction Events.

Feel free to configure any uptime monitoring tool to poll the pulse endpoint as often as once per second.

Event Types

There are four types of events that can be posted to JourneyStream:

Touchpoint Interaction Events (interactions)

Conversion Events (conversions)

Association Events (associations)

Metric Events (metrics)

Touchpoint Interaction Events: Interactions are the events that a conversion event may be attributed to later. Any time someone interacts with your touchpoint, you would fire a touchpoint interaction event. These interactions range from visits on marketing websites to inbound phone calls in a call center.

The API will respond with a 201 Created message if the event was accepted. If the event was not accepted, a 400 Bad Request is returned.

Conversion Events: Conversions occur anytime you want to mark a milestone for attribution. A conversion could be something as simple as a lead form filled, a processed order, or a late stage sales opportunity.

The API will respond with a 201 Created message if the event was accepted. If the event was not accepted, a 400 Bad Request is returned.

Association Events: Associations are events that tie who_uuid values together. Anytime you want to inform Strala that two identifiers are linked, you would send this event. The typical association event is one that ties an anonymous identifier from a cookie or localstorage to a CRM identifier. Without associations, no chain of events can be formed and attribution will usually end up looking just like last touch. Associations are used in two ways: 1) to link multiple devices to a single person 2) to link multiple people to a single entity/account.

The parent_type or child_type should match the who_type that is sent via an interaction or a conversion.

The API will respond with a 201 Created message if the event was accepted. If the event was not accepted, a 400 Bad Request is returned.

Metric Events: Metrics are primarily used to factor cost into your attribution models. Send us metric events anytime you want log a measure associated with a particular touchpoint. Typically, metric events are used to increase the accuracy of cost data from ad platforms by overriding the platform reported cost and other aggregates.