Selstack is a platform for creators and businesses to build a public selling page, share individual offers, accept supported payments and bookings, and manage the resulting orders and customer details. A “Stack” is a selling page. This guide explains the relevant workflow and the seller’s responsibilities; payment methods, account requirements and some features depend on the business configuration and plan.
This task establishes the foundation for a usable Selstack workspace. This guide focuses on how to review business activity, priority cards and the next operational action.
Why this matters
This task helps you review business activity, priority cards and the next operational action. Complete it inside the business you intend to manage; the name in the workspace header tells you which business will receive the change.
Find the right starting point
Use the main navigation and match the page heading to the task. Dashboard is a summary, Stack manages public offers, Contacts holds customer and lead context, Payments contains orders, Wallet shows business balances, and Settings controls account or public identity.
Complete one clear change
Read the existing value before editing it. Enter current, truthful information and use the page’s primary save, publish or continue action once. If Selstack shows a field error, correct that field rather than opening another copy of the form.
Check the result
Look for the saved state, updated value or confirmation message. When the task affects a public link, open the real URL while signed out and inspect it on a phone. When it affects a record, reopen that record and match its name or reference.
If something looks wrong
Confirm the active business, refresh the relevant page once and compare the saved value with the public or downstream result. Do not create duplicate links or payment attempts to make an uncertain status disappear.
Example: Read Your Selstack Dashboard
A dashboard may show four successful payments this month, but fulfilment decisions still start by opening the individual records in Payments.
If Read Your Selstack Dashboard is not working
If a total looks unfamiliar, confirm the active business, reporting currency and period before reporting a data problem.
Confirm the result
- The workspace header shows the intended business.
- The page displays the expected saved or published state.
- Any public result is readable while signed out on a narrow screen.
- No duplicate link or action was created while checking the result.
When to ask Selstack for help
Begin with the decision behind the report
Selstack’s activity and customer records help a business understand what visitors and customers do around its offers. A useful review starts with a question: are people finding the page, asking relevant questions, completing purchases or receiving what they bought? These are different stages. Choose the report and period that relate to the decision rather than looking for the largest available number. A view can indicate attention, while an order and a confirmed payment provide different evidence about the business outcome.
Keep the reporting context consistent
Confirm the active business, date range and the meaning of each labelled metric before comparing results. A short campaign period should not be compared with an unrelated all-time total. Read the currency attached to money figures and distinguish gross customer payments from fees, refunds and seller receipts. A change in one number may reflect the chosen period or a different population rather than an improvement in the offer. Keep a note of the reporting context when sharing a conclusion with the team.
Follow the journey between stages
Compare how people reach an offer with the action the page asks them to take. If visits are present but useful enquiries are scarce, review the message and form. If enquiries are strong but purchases are weak, inspect the offer, customer questions and follow-up. If paid orders occur but support problems increase, look at delivery rather than treating the campaign as an unconditional success. Selstack brings related records into the workspace, but the business must interpret what each stage can and cannot establish.
Use campaign links carefully
Where supported tracking parameters are used, add them to the correct public destination and test the final address. Use clear naming that someone else in the business can understand later. A tracking label should describe the campaign or channel rather than contain a customer’s private information. Keep the naming consistent enough to compare related activity, and review whether the linked offer remains current. A well-labelled campaign that sends people to an unavailable or misleading page still creates a poor customer experience.
Treat external tracking as a separate responsibility
Pixels and analytics integrations have their own configuration, event definitions and consent considerations. Check the integration available for the account and verify the identifier belongs to the intended business. Do not paste arbitrary tracking code into product descriptions or forms. Review the platform’s supported integration controls and test the events appropriate to the customer journey. A tool receiving an event does not automatically prove that it represents the same business outcome as a recorded Selstack order.
Respect visitor choices and data limits
Optional tracking should follow the applicable consent choice and the platform’s supported behaviour. Avoid collecting personal information merely because a field or external tool makes it possible. Names, email addresses, identity details and full payment credentials should not be inserted into campaign URLs or ordinary analytics labels. Use reporting to understand aggregate activity and legitimate customer outcomes. If a customer relationship needs investigation, use the authorised order or contact record rather than attempting to reconstruct private information from tracking data.
Investigate discrepancies with a defined scope
Different systems can count different events, apply different time windows or exclude traffic differently. Start by writing down the specific comparison: which two reports, what period, which destination and what event definition. Check for duplicate attempts, test activity and mixed currencies where relevant. Do not change historical order records to make an external advertising report agree with them. If the discrepancy remains unexplained, provide support with safe references and the reporting context instead of a general claim that every number is wrong.
Read small samples with care
A few visits or orders can change percentages sharply. Use the underlying counts and the practical customer experience before declaring a reliable trend. A campaign that produced one additional sale may still be worth understanding, but it does not establish that a new headline will work for every audience. Review repeated questions and delivery outcomes alongside the chart. Qualitative evidence can show why a result happened and help the business choose a more focused next test.
Turn reporting into an operating routine
Choose a small set of useful outcomes, review them on a regular schedule and record the action taken. Assign responsibility for unresolved problems rather than letting a dashboard become a collection of observations. Keep the report connected to the business’s real capacity: an increase in demand needs a delivery process that can support it. Selstack’s records make activity easier to inspect, while good decisions still depend on consistent definitions, accurate context and a willingness to investigate what the figures do not yet explain.
Review Selstack pricing for current plans and online payment fees. For related tasks, visit the Help Centre. If the recorded result remains unclear, contact support with the relevant safe reference.
