Use this checklist to get from a new Oviond account to your first client-ready report.
This article is for agency owners, account managers, and reporting teams setting up Oviond for the first time.
Use it when you want the shortest sensible path: one client, one report or dashboard project, the right data sources connected inside that project workflow, then one test share. The aim is to make the first reporting workflow simple, dependable, and repeatable before you scale it across more clients.
You will need:
access to your Oviond account,
the name of the first client you want to set up,
a rough idea of whether the client needs a report, dashboard, or both,
access to at least one marketing account for that client,
your agency branding details if you want the first report to be white-labelled.
If you are joining an existing agency account, ask your Oviond account admin to invite you instead of creating a separate account.
Go to app.oviond.com and sign in or sign up.
If this is your first sign-in, complete the onboarding flow. Oviond’s documentation describes onboarding as a 4-step setup covering your full name, company name, company website, and how many clients you report for.
Open Clients from the left sidebar and choose Add Client.
Add the client you want to report on first. Start with one real client rather than trying to set up every client at once.
Create a project for the client.
Use a report if the client expects a structured update, such as a monthly report. Use a dashboard if the client or your team needs a live view that can be checked more often.
Start simple. Add only the pages and widgets needed to prove the report works.
Inside the project workflow, connect or select the data sources the report or dashboard needs.
Choose the platform you need for the first report, such as an ads, analytics, or social platform, then follow the authorization flow. You need access to the client’s account on that platform before Oviond can pull reporting data from it.
Before sharing anything with the client, check:
the correct client is selected,
the correct report or dashboard project is selected,
the correct data source is connected or selected inside the project,
the correct profile or account is selected,
the date range contains data,
the widgets show the metrics you expect.
This is the step that prevents most embarrassing reporting issues.
If the report will be client-facing, check the branding before sharing it.
Depending on your setup, this may include logo, colours, theme, email sender, and custom domain settings.
Share the report with yourself or your team first.
Only send it to the client once you have checked the data, branding, layout, and access. If this will become a recurring report, test the automation before relying on it for a live monthly send.
By the end of this checklist, you should have:
one client created,
one report or dashboard project started,
at least one data source connected or selected inside that project workflow,
the first data check completed,
a share or delivery test completed before the client sees it.
That is enough for a useful first setup. You can add templates, automations, custom domains, more clients, and team members after the first report works. Reporting should feel done before it becomes automated.
Check that you have access to the client’s marketing account outside Oviond first. If you do not have the right permissions in the source platform, the connection will not work properly in Oviond.
Check the selected client, project, data source, profile, widget, and date range. Empty reports are often caused by the wrong profile or a date range with no data.
Start with the client’s normal reporting rhythm. If they expect a monthly update, build a simple monthly report. If they need regular visibility, build a dashboard.
Stop. Pick one client and one report or dashboard project. Get that working first, then scale the setup.
Send Oviond support:
the client name,
the report or dashboard project name,
the data source you are trying to connect or select,
the widget or metric that looks wrong,
the date range selected,
what you expected to happen,
what happened instead,
a screenshot of any error message.
