Tutorials and Guides
Talon.One offers reporting on the data you send via our integration API, showing you basic stats such as campaign performance and customer activity over a time period.
For businesses with an existing data warehouse and BI reporting tools, it's more desirable to instead pull data from Talon.One into the same unified warehouse so that it can more easily be joined with data from other sources. Our Management API offers a number of operations to help you accomplish this synchronization.
Every request to our Integration API results in an event being recorded. This event will contain attributes as well as information about any effects that were triggered by campaign rules in response to the event. Events are immutable once created, which means that you can safely retrieve all events sorted by time, and continuously poll for events newer than the last one received.
Customer sessions group together events. They can be seen as mutable views over the immutable event data. As such, it's recommended that you only sync sessions after you have received events belonging to that session.
Events (and by extension, sessions) may belong to a customer profile. Profiles
are always mutable, and contain aggregate values such as
keeps a running tally of the
Session.Total property for all closed sessions.
The general algorithm for keeping an up-to-date copy of Talon.One data in your data warehouse is:
lastSyncvariable with the value of the
createdtimestamp of the last event you already have stored. If no events have been stored, set the
createdtimestamp of your application.
sessionsToFetchvariables as empty sets.
createdAfterquery parameter that should be set to the same value as
lastSync. The response will contain an integer
totalResultSizeproperty and a
dataarray containing events.
talon_one_eventrecord in your data warehouse
event.sessionIdis non-zero, add it to the
event.profileIdis non-zero, add it to the
response.totalResultSizeis equal to the number of items in
talon_one_profile_snapshotrecord in your data warehouse.
talon_one_session_snapshotrecord in your data warehouse.
This above process can be run continuously, and the sleep interval can be tuned to balance between the number of API requests performed and the latency of updates to your data warehouse.
Depending on the sophistication of your existing BI tools, it may be desirable
to "renormalize" the nested event/effect data at step 4.1. For further reference
on the structure of events and how to interpret the
event.effects array, see
Handling Effects in the Integration API documentation.
If you’d like a member of our support team to respond to you, please send a note to email@example.com