Structuring Segment to work with analytics

Very new to Segment! How does one structure Segment to work with analytics so that data from marketing site/blog vs the product itself are not confused? E.g. with a dashboard of DAU, WAU, MAU one would only want to see product data; yet, with everything going into Segment, presumably one’s DAU would be inflated by folk on the home page, blog readers and such. It seems impractical to use filters rather than a top down; ‘Marketing Site Metrics’ & ‘Product Metrics’.

2 Likes

Which analytics platform are you using? Segment gives you flexibility to apply destination filters based on properties/fields in events before sending off to destinations (ex. amplitude) so you could always setup two separate destinations based on the events - that, or just apply filters in the analytics platform based on fields like URLs

2 Likes

@Marco, Thank you. We’re Mixpanel. I’ll take a look at destination filters; having two destinations, that go to the same analytics platform makes sense to organize things.

2 Likes

If you have two separate sources for product vs site, you may just be able to hook up each to their own destination (or filter on some type of sourceID if that’s passed at all - unsure if that’s the case though).

2 Likes

Right. We’re most similar in structure to something like Headspace.com (marketing site + blog) and my.Headspace.com (product) - separate sources

2 Likes

Side-note: There’s a Segment Community slack where you can ask these type of Q’s as well. Definitely helps having the segment teams for feedback :+1:

2 Likes

Hi Folks, Here’s a piece of advice from Graham Hunter from Segment. He’s a marketing guy and runs the Segment Startup Program (only semi-technical) but here’s his recommendation.

Don’t create separate workspaces/ javascript sources in Segment or Amplitude (or whatever Product Analytics suite you use). This can make it difficult to track performance of the marketing site into the product.

Here is a great article on how to do this with Amplitude and Segment:
https://medium.com/together-software/getting-started-guide-to-measuring-active-users-with-amplitude-segment-98fa75a383bd

1 Like

Separating your app and marketing subdomain can be good as it makes it easy to differentiate between the two. My understanding is that it’s mostly done because of eng and security benefits.
Be careful in reporting though, as Amplitude saves the URL and Path/Slug. The latter strips off the root domain.

1 Like

Thank you @Michael, that’s super useful. Especially the point around tracking flow from marketing into product.