Acquisition reporting
Understand referrers, sources, mediums, and landing pages.
Connect traffic, events, and conversions to the customers who matter. Get a clearer picture of what brings people in—and what brings them back.
$2 in free usage credits. Start with one app. Grow into the stack.See the channels and pages bringing people in.
Explore the steps between a visit and a useful action.
Connect identified events to a real contact.
Built for businesses reaching millions. Trusted by seven-figure agencies.
THE WORK BEHIND THE WORK
A growing pageview total can hide the question that matters: are the right people finding value? Reports become useful when you can move from the headline number to the activity behind it.
Saasco brings traffic breakdowns, event exploration, and funnels into the same analytics workspace. Investigate a change, follow a journey, and keep the customer context close.
BUILT FOR THE WAY YOU WORK
Traffic reporting, event exploration, funnels, and individual journeys. The useful parts of analytics, connected to the rest of your customer stack.
01 / THE BIG PICTURE
Open Reports and get your bearings: unique users, sessions, pageviews, visit time, bounce rate, and completed events. Compare periods, then explore the pages, referrers, countries, and campaigns behind the change.
Reports · Explore the metrics and breakdowns in the preview above.
02 / FROM INTEREST TO ACTION
A signup is a beginning. Build a funnel from the events that define a useful customer journey, then see where people continue and where they drop away. Make your next improvement a specific one.
Illustrative funnel · Signed Up → Created Project → Invited Teammate.
03 / THE PEOPLE IN THE NUMBERS
Explore a tracked event and its properties, or follow an identified user’s activity. When you connect the SDK to a customer identity, that same event history becomes useful context in CRM and Support.
product: Everyday Vesselquantity: 1/objects/everyday-vesselutm_source: newsletterSample event history · Customer identity supplied through the SDK.
THE DETAILS MAKE THE DIFFERENCE
Understand referrers, sources, mediums, and landing pages.
Track sessions, visit duration, pageviews, and bounce rate.
Investigate actions and the properties attached to them.
Describe the journey using the events that matter to you.
Connect identified visitors to their activity over time.
Keep an eye on the resources used by your reports.
PUT IT TO WORK
Choose a situation. See how the product helps you move it forward.
Compare traffic sources and landing pages over the campaign period.
Inspect the events people trigger after they arrive.
Build a funnel around the steps from interest to conversion.
A clearer view of where attention turns into action.
FROM IDEA TO FIRST RESULT
Start with Analytics. Everything else can wait until you need it.
Get started free Explore the documentationAdd Saasco to your site and initialize it with your project ID.
Track the moments you care about and identify signed-in customers.
Use the debugger, open Reports, and build your first funnel.
Go beyond the pageview. Identify a customer and send the actions that matter to your business through the JavaScript SDK. The same activity becomes context for the rest of your stack.
Explore the API schemaimport {
Saasco,
} from "saasco-sdk";
const saasco = new Saasco({
projectId: "YOUR_PROJECT_ID",
});
await saasco.identify("u_123");
await saasco.track("Signed Up", {
plan: "team",
});Install saasco-sdk and use your project ID. Add these calls to the matching actions in your app.
ROOM TO GROW
Current ingestion rate. Analytics query compute and other activity are metered separately.
Explore pricingFree usage credits included.
Top up when you’re ready for more.
Yes. Start with Analytics and connect other Saasco apps when you need them. You do not need to migrate your whole customer stack at once.
Page visits, sessions, and custom events with properties. Define event names around real actions in your business, such as Signed Up or Purchase Completed.
Yes, event-step funnels are part of Analytics. You choose the steps that describe the journey you want to investigate.
Identify your customers through the SDK using a stable ID. Their activity can then appear alongside the customer context in CRM and Support.
No. The displayed rate covers ingestion requests. Queries and other metered work draw from the same balance and are additional.
A pageview tells you someone arrived. A connected customer history helps you understand why they stay. Bring both into the same conversation.
Start with Analytics