Know which release cost you orders.
You built your own app or service. Adea reads its database and its code, checks your numbers every night, and when one moves it tells you which release, which commit and which customers, so your developer starts with the answer instead of the search.
Free planNo cardRead-only access
Only Android 4.12
since Thursday 10:30Android checkouts completed, by app version
Android orders fell from 760 to 470 yesterday. iOS and the website are normal.
What Adea watches on your platform.
Adea reads your database when you connect and works out what your business counts: orders, customers, deliveries. Then it learns what's normal for each number, per app and per weekday, and speaks up when one leaves it.
- Orders a dayAll apps together. The first number to move when something breaks.2,140
- Orders from the Android appPer app and version, so a bad release shows up on its own, the same day.470
- Checkouts completedOf everyone who starts checkout. Falls when a step in it stops working.62%
- New customers a weekMoves with campaigns and the app stores, and shows what a launch really brought.1,380
- Deliveries on timePer area and time slot, so one late route doesn't hide in the average.94%
- Average basketMoves with delivery fees, minimum orders and offers.€53
Normal rangeOutside normalLast four weeks
Ask like you'd ask your developer.
Without waiting for your developer. Write the question, and the answer comes in seconds, with the tables and the code it came from.
More questions owners ask
- Which areas had the most late deliveries last week?
- What do customers who stop ordering have in common?
- How many customers used the new reorder button since it shipped?
- Which change made the average basket go up in September?
How often is checkout completed on each app version since Thursday?
The answer
Android 4.12 completes only 21% of checkouts. Every other version is between 64% and 71%.
Lists your team works through.
When an answer is a group of customers or orders, Adea turns it into a list that keeps itself up to date. Each row has an owner and a status.
- 248in the list today
Stuck at checkout, didn't order
A reminder and an apology the same day brings many of them back.
Worked by: Nanna, customer care
- 312in the list today
Ordered every week, nothing for three weeks
Regulars drifting off, with what they usually order.
Worked by: Marketing
- 64in the list today
Late deliveries this week
By route and driver, so the pattern is easy to see.
Worked by: Logistics
Works with your stack
A user that can only read on your database, and your code if you like. Nothing to install in your app.
PostgreSQLA user that can only read
MySQLA user that can only read
MariaDBA user that can only read
BigQueryA read-only service account
SnowflakeA user that can only read
Amazon RedshiftA user that can only read
GitHubInstall the GitHub app
GitLab, Bitbucket and any gitA read-only deploy key
StripeA read-only API key
SlackInstall the app
Questions owners ask
Can Adea write to our database?
No. Adea connects through a user that can only read, and refuses one that can write. Every query is checked before it runs, and it never runs anything that changes data.
Does Adea need our code?
No, the database is enough to watch your numbers and answer questions. With your code connected, Adea can also tell you which release or commit moved a number, and how your business rules really work.
What happens to our code?
Adea reads it on demand in a sealed space that holds it only in memory and wipes it after 20 idle minutes. It never runs your code, and it never keeps whole files or the repository.
Which databases does Adea read?
PostgreSQL, MySQL, MariaDB, BigQuery, Snowflake and Redshift. A read replica is best if you have one, so Adea never competes with your app for the main database.
See what Adea finds in your data.
Connect a read-only user for free. No card, and your first numbers arrive the same day.