Question

Integration of talon one and Segment engage

  • 30 April 2024
  • 3 replies
  • 48 views
S
Rank

We use Segment Engage as our Engagement Platform and Talon One for promo handling. Wanted to check the viability of this use case if anyone else has tried this - 

When a user enters and audience/ or triggers an event, we want to generate a personalised promo code in Talon One and send it to Segment engage (in real timish) to send across to that user in an email. 

Specific question on this, how can we bring this incoming promo code from talon one into email template as a user trait. There is no default integration of Talon One and Segment for engagement use cases. (there is one for CDP data transfer, creating audience etc use case)

 

 

3 replies

TKing
Rank

Hi Saurabh,

Integrating Talon.One with Segment for the purpose of generating personalized promo codes and incorporating them into email templates sent via Segment Engage involves a multi-step process. While there isn't a direct, out-of-the-box integration between Talon.One and Segment specifically for engagement use cases like the one you've described, you can achieve this workflow by leveraging Segment's ability to collect and distribute data across different platforms, including Talon.One and Segment Engage. Here's a high-level overview of how you can set this up:

Step 1: Trigger Event or Audience Membership in Segment

  1. User Activity: Start with a user performing an action or meeting criteria that places them into a specific audience within Segment. This could be anything from signing up, making a purchase, or any other event you track.

Step 2: Send Data from Segment to Talon.One

  1. Segment to Talon.One: Use Segment to send this event data to Talon.One. Although there's no direct integration for engagement scenarios, you can utilize Segment's ability to forward events and user traits to Talon.One through a custom setup or webhook. This would involve:
    • Configuring a webhook in Segment as a destination that points to a Talon.One API endpoint.
    • Mapping the relevant data fields (e.g., user ID, event details) that Talon.One needs to generate a promo code.

Step 3: Generate Promo Code in Talon.One

  1. Promo Code Generation: Once Talon.One receives the data, it uses its rules engine to generate a personalized promo code based on the event or audience criteria met.

Step 4: Send Promo Code Back to Segment

  1. API Call from Talon.One to Segment: After generating the promo code, Talon.One needs to send this code back to Segment. This can be achieved through an API call from Talon.One to Segment, updating the user's profile with the promo code as a custom user trait. This step might require a custom function or service that listens for webhook calls from Talon.One and then uses the Segment API to update user traits.

Step 5: Use Segment Engage to Send Email

  1. Segment Engage Email Template: With the promo code now stored as a user trait in Segment, you can use Segment Engage to create an email campaign. In the email template, dynamically insert the promo code by referencing the custom user trait that contains the code.

Considerations:

  • Custom Development: This workflow requires some custom development, particularly for the API integration between Talon.One and Segment to update user traits with the promo code.
  • Real-Time Processing: While described as "real-time," there may be slight delays in processing and communication between systems. It's important to account for this in the user experience.
  • Security and Data Handling: Ensure secure handling of data and API calls between Segment and Talon.One
S
Rank

Hi, thanks for the above explanation. Few questions - 

  1. You did not take into account this direct integration between segment and Talon.one (as a destination)  - https://segment.com/docs/connections/destinations/catalog/talon-one-actions/#update-customer-session. It has an action to update customer session and customer profile in Talon One directly. How can I leverage this for this use case?
  2. The way custom trait for promo code is being handled, I think it would require Eng resources for every new campaign that we want to do, since we would need to have different custom traits for different campaigns. Is there a way to handle this through the UI itself. At this point, I would like to bring your attention to the native integration of talon one and Segment as described above. There is a mapping for updating customer session in Segment UI iteself, here if you scroll down there is something called callback destination uri, callback api key etc. Can I leverage this for my use case?

 

Andrew Rawson
Rank
Userlevel 1

​​​@Saurabh Kanchan, 
If I’m understanding correctly, the data flow would look something like this:

User creates welcome event (Sign in, sign up, etc.), you want to generate a Promo Code for them/those events and TalonOne will be generating the Promo Code (because Segment cannot mint new Promo Codes). So Segment will track those ‘welcome events’ and generate the audience of who should receive a promo code, then that would flow to TalonOne to append promo code for those users. From there, it seems we need to provide that list of users (with Promo Codes attached) to the ESP somehow, right? 

From the folks I’ve asked internally there seems to be a couple ways to do this. You could re-ingest users as an identify call, with TalonOne as a source, to then pass to your ESP connected to Segment. Or send those users directly to the ESP from TalonOne (if that is possible, I’m not familiar with TalonOne’s integration capabilities for sending data in that regard). 

Alternatively, this is more advanced but if TalonOne’s process is real-time for assigning the promo code, you could create destination insert function in the ESP to send that Identify call into the ESP, and enrich the payload within Segment and send to ESP that way. This would require the Integrations API in TalonOne, and would require coding as well. https://docs.talon.one/docs/dev/integration-api/overview 

Let me know if this helps! If not we can open up a support ticket on your behalf with all of this context included. 

Reply


Terms & Conditions