Segment>Split integration: Map identity to a trait?

Follow

Remi Gabillet

• October 05, 2020 19:15

Hi, I have Split set up on a B2C where all splits are at the "company" level.

 

In our Segment integration, users are uniquely identified with a user_id and the company_id is passed a trait. 

 

I would like to send Segment events to Split in order build metrics. Unfortunately, I'm not able to map the Split company_id to the matching Segment trait. The current configuration page only allows matching to Segment's anonymous_id or user_id.

Any ideas on how to get company-level success metrics using segment data?

 

0

• 

  Bilal Al-Shahwany

  • October 06, 2020 01:04

  Hi Remi,

  We have a doc article that provide steps how to send events from Segments account id trait to Split account traffic type: https://help.split.io/hc/en-us/articles/360021218331-Segment-Integrating-Segment-with-Split-using-Account-Traffic-Type

  Please let me know if you have any questions.

  Thanks

  Bilal

  0

  Comment actions Permalink
• 

  Remi Gabillet

  • October 06, 2020 17:04

  This seems a bit tricky but I think it could work for us. I'm glad you have thought about this setup!

  Thanks for sharing Bilal.

  0

  Comment actions Permalink
• 

  Remi Gabillet

  • October 06, 2020 17:13

  I'm diving into this right now but I don't under the line "Select Split traffic type Dummy". I have 3 traffic types set up: company, location, user. Do I need to create a new type? If so, how do I do that?

  0

  Comment actions Permalink
• 

  Remi Gabillet

  • October 06, 2020 17:23

  I have 2 more questions for you Bilal:

  
  #2 It seems that I can pass split traffic type definitions through track() properties or group() traits. These make sense. Can I also pass them to identify() traits?

  
  #3 Can I pass multiple split traffic types in one call? If so, should I use

  syntax A:
  {
  ...
  "properties": {
  "split": [{
  "company": "318738",
  "location": "1234"
  }],
  ...
  "type": "track",
  "userId": "318738-325351",
  "originalTimestamp": "2015-12-12T19:11:01.152Z"
  }

  
  or syntax B:
  {
  ...
  "properties": {
  "split": [
  { "company": "318738" },
  { "location": "1234" }
  ],
  ...
  "type": "track",
  "userId": "318738-325351",
  "originalTimestamp": "2015-12-12T19:11:01.152Z"
  }

   

  0

  Comment actions Permalink
• 

  Channing Benson

  • October 06, 2020 18:47

  Hello Remi,

  Question 2: "Can I use identify() to pass traffic type traits?"

  No.

  I would also caution that I do not fully understand how the Segment group call is supposed to interact with traffic types. I believe that for your use case, using extra properties in track events to identify the key for a particular traffic type under which to register that event is the way to go.

  Question 3: "Can I pass multiple split traffic types in one call?"

  Yes, and the syntax to use is syntax B. Here's how it looks in my JS code:

  analytics.track("Memo_added", {priority: memoPriority, split: [{partner: "partner-0000"},{ga_anonymous: "ga_id_123"}]});
  
  

  That call produces three events in split, all with different traffic types and keys (but the same other data):

  

  Of course, in your code you would want to use variables for the key value rather than literals like I did.

  Hope this helps.

  -- Channing

  0

  Comment actions Permalink
• 

  Remi Gabillet

  • October 29, 2020 22:41

  Thanks Channing, this helps a lot, and I think this will solve our use-case.

   

  I'm going to play with these custom segment attributes on the track() calls for now and see if it works as expected.

  0

  Comment actions Permalink

Please sign in to leave a comment.