Scribd
Upload
82 views7 pages

Segment IO-Use Case

Segment provides a single API call to integrate with multiple third party tools like Facebook, Google Analytics, and Marketo. It identifies website visitors, computes traits like lifetime value, and sends data to destinations like Google Analytics and Hubspot. Segment supports multiple businesses/workspaces and has been used for real-time personalization, data syncing between tools, and more for a print company use case. However, Segment has tight coupling with websites and business integrations rather than platform integrations, can be expensive, and faces competition from other vendors.

Uploaded by

shekcool
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
82 views7 pages

Segment IO-Use Case

Segment provides a single API call to integrate with multiple third party tools like Facebook, Google Analytics, and Marketo. It identifies website visitors, computes traits like lifetime value, and sends data to destinations like Google Analytics and Hubspot. Segment supports multiple businesses/workspaces and has been used for real-time personalization, data syncing between tools, and more for a print company use case. However, Segment has tight coupling with websites and business integrations rather than platform integrations, can be expensive, and faces competition from other vendors.

Uploaded by

shekcool
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 7

Segment IO- Use Case

Without Segment
One Single API

What if instead of making those


Different API calls to Facebook, Google
Analytics,Marketo,etc. you had to make a
single call? (primarily on the website).

That’s what segment gives you out of the


box.
With Segment

Snowflake
Everything in Audience
Builder + More
• Audience Identification
• Is the website visitor a Flyer purchaser?
• Is the website visitor a high value customer?
• Computed Traits and Hyper Personalization
• What is the LTV of the website visitor?
• What is my RFM segment of the website visitor?
• Destinations
• Google Analytics.
• Hubspot
• More..
• Sources
• Website Events(Add to Cart, Create Order)
• API Events (Fulfillment events, etc)
• Looker (Looker Computed Values)
• Other third party tools.
Multi-tenant
• Support for multiple businesses
(workspaces)
• Printdeal Use cases. (Low Code)
• Real time website personalization
• Cimcommerce data synced to Hubspot
• Looker calculated values in Hubspot Sync
• Hubspot data in Snowflake
• Refund emails via Hubspot.
• Abandoned Cart emails(Tradeprint as well)
• Real time product recommendations
• Product page selector performance tracking
Cons
• Heavy website integration. Tight coupling with Google
Analytics.
• Breaks the chasm. (Business vs Platform) Business
• Highest value in Website and Business Integrations
(Google Analytics , Facebook , etc.) and not in platform
integrations(Cimcommerce, Doc Core, Orders,
Shipping)
• Might be expensive.
• Audience Building is an addon and not part of the core plan.
Platform (Lake,
• Getting heavily crowded quickly . New players coming
Cimcommerce, Orders,
in.(Emarsys, Salesforce, Adobe, etc.) DocCore, Shipping,etc.)
• Open Source Alternative – Rudderstack, Unomi.
• Lacking in features. Features would need to be built.

You might also like