Open pacholoamit opened 1 month ago
Change tracker generation endpoint so you can choose from a list of “features”. Like if user wanted “retargeting liquidm” , “retargeting nexxen”, etc.
Do some research into composing the segment id
object that contains segment provider + segment id
Lets say someone has a seat on LiquidM, or Soapbox, etc.
Add segmentId
Tag generator in the future - Add credentials in the params so the users can generate their own segments?
// =====
Solve problem, how can we support multiple segments in the tracker?
User wouldn’t know for where the segment ids are from but the backend would know
We can work on the nexxen segment generation
Action items: [ ] - Define supporting multiple segment ids but hidden (s1, s2, s3) - https://github.com/MediaJel/mediajel-tracker/issues/456
Change tracker generation endpoint so you can choose from a list of “features”. Like if user wanted “retargeting liquidm” , “retargeting nexxen”, etc.
Do some research into composing the segment id
object that contains segment provider + segment id
Lets say someone has a seat on LiquidM, or Soapbox, etc.
Add segmentId
Tag generator in the future - Add credentials in the params so the users can generate their own segments?
// =====
Solve problem, how can we support multiple segments in the tracker?
User wouldn’t know for where the segment ids are from but the backend would know
We can work on the nexxen segment generation
Action items: [ ] - Define supporting multiple segment ids but hidden (s1, s2, s3) - https://github.com/MediaJel/mediajel-tracker/issues/456